Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JMS Messaging Client Error!!

108 views
Skip to first unread message

jgabri...@terra.com.br

unread,
Feb 8, 2006, 12:26:29 PM2/8/06
to
Need help about the JMS Messaging in WebSphere. I followed the Developer Technical Journal tutorial for setting up a Service Bus for testing purposes on my work. I'm using WebSphere v6.0.2.5 on a SUSE Linux Enterprise Server 9. But after all done, when i try to run the client application, i keep getting the same error message.
http://www-128.ibm.com/developerworks/websphere/techjournal/0504_reinitz/0504_reinitz.html

Command line call: ./launchClient.sh ../installableApps/PackageReceivedClient.ear -CCdumpJavaNameSpace=true -CCverbose=true

-------------------------ERROR MESSAGE-----------------------------------------
IBM WebSphere Application Server, Release 6.0
J2EE Application Client Tool
Copyright IBM Corp., 1997-2004
WSCL0012I: Processing command line arguments.
WSCL0001I: Command line, property file, and system property arguments resolved to:
File to launch = ../installableApps/PackageReceivedClient.ear
CC Property File = null
Client Jar File = <default>
Alternate DD = null
BootstrapHost =
BootstrapPort = <default>
Trace enabled = false
Tracefile = null
Init only = false
Classpath Parameter = null
Security Manager = disable
Security Manager Class = Not used. -CCsecurityManager=disable
Security Manager Policy = Not used. -CCsecurityManager=disable
Exit VM = false
Soap Connector Port = null
Application Parameters =
Provider URL = null
Dump Java Name Space = true
Admin Connector Host = null
Admin Connector Port = null
Admin Connector Type = null
Admin Connector User = null
PARENT_LAST mode = false
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0029I: Binding resource reference object:
JNDI name: jms/TheConnectionFactory ==> jms/TheConnectionFactory @ corbaloc:iiop:localhost
Type: javax.jms.ConnectionFactory
Description:
WSCL0031I: The object was bound successfully.

WSCL0029I: Binding resource reference object:
JNDI name: jms/PackageReceivedQueue ==> jms/PackageReceivedQueue @ corbaloc:iiop:localhost
Type: javax.jms.Queue
Description:
WSCL0031I: The object was bound successfully.

WSCL0600I: Binding HandleDelegate object.
WSCL0031I: The object was bound successfully.

Classpath: /opt/IBM/WebSphere/AppServer/Profiles/busServer/installedConnectors/sib.ra.rar
WSCL0900I: Initializing and starting components.
WSCL0910I: Initializing component: com.ibm.ws.runtime.component.WsByteBufferPoolManagerClientServiceImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.activity.ActivityServiceClientComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.runtime.component.ChannelFrameworkClientServiceImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.runtime.component.NonRecoverableComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.webservices.wssecurity.core.WSSecurityClientComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.runtime.component.CFSBinder
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.runtime.component.WSBBSBinder
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.cluster.channel.ChannelSelectionAdapterImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.handlerfw.impl.HandlerFrameworkServiceImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.ActivitySession.ActivitySessionClientComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.workarea.WorkAreaServiceClient
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.appprofile.AppProfileClientComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.webservices.component.WSClientImpl
WSCL0911I: Component initialized successfully.
WSCL0910I: Initializing component: com.ibm.ws.i18n.context.I18nClientComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0901I: Component initialization completed successfully.

==============================================================================
Name Space Dump
Starting context: (top)=java:
Time of dump: Wed Feb 08 15:22:44 BRST 2006
==============================================================================


==============================================================================
Beginning of Name Space Dump
==============================================================================

1 (top)
2 (top)/comp com.ibm.ws.naming.java.javaURLContextImpl
3 (top)/comp/websphere javax.naming.Context
4 (top)/comp/websphere/UserWorkArea com.ibm.ws.workarea.IWorkArea
5 (top)/comp/websphere/UserActivitySession java.lang.Object
6 (top)/comp/websphere/UserInternationalization com.ibm.websphere.i18n.context.UserInternationalization
7 (top)/comp/websphere/WorkAreaPartitionManager com.ibm.websphere.workarea.WorkAreaPartitionManager
8 (top)/comp/websphere/AppProfile javax.naming.Context
9 (top)/comp/websphere/AppProfile/TaskNameManager com.ibm.websphere.appprofile.TaskNameManager
10 (top)/comp/ORB java.lang.Object
11 (top)/comp/HandleDelegate java.lang.Object
12 (top)/comp/env com.ibm.ws.naming.java.javaURLContextImpl
13 (top)/comp/env/jms javax.naming.Context
[2/8/06 15:22:44:936 BRST] 0000000c W UOW=3-63294816-23682644:g02897 source=com.ibm.ws.naming.util.Helpers org=IBM prod=WebSphere component=Application Server thread=[Thread-1]
NMSV0605W: A Reference object looked up from the context "java:comp/env/jms" with the name "TheConnectionFactory" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name: com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: java.lang.Object
Type: JndiLookupInfo
Content: JndiLookupInfo: jndiName="jms/TheConnectionFactory"; providerURL="corbaloc:iiop:localhost"; initialContextFactory=""

Exception data follows:
javax.naming.NameNotFoundException: Context: TestCell/nodes/busServerNode/servers/nodeagent, name: jms/TheConnectionFactory: First component in name jms/TheConnectionFactory not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4043)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1746)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1707)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1412)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:372)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:889)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191)
at com.ibm.ws.naming.urlbase.UrlBindingEnumeration.jndiBindingData(UrlBindingEnumeration.java:80)
at com.ibm.ws.naming.urlbase.UrlNameEnumeration.doNextBatch(UrlNameEnumeration.java:110)
at com.ibm.ws.naming.urlbase.UrlNameEnumeration.doInit(UrlNameEnumeration.java:82)
at com.ibm.ws.naming.util.WsnNamingEnumeration.init(WsnNamingEnumeration.java:132)
at com.ibm.ws.naming.urlbase.UrlNameEnumeration.<init>(UrlNameEnumeration.java:70)
at com.ibm.ws.naming.urlbase.UrlBindingEnumeration.<init>(UrlBindingEnumeration.java:65)
at com.ibm.ws.naming.urlbase.UrlContextImpl.listBindings(UrlContextImpl.java:1173)
at com.ibm.ws.naming.urlbase.UrlContextImpl.listBindings(UrlContextImpl.java:1213)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:657)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:758)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:758)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:758)
at com.ibm.websphere.naming.DumpNameSpace.doGenerateDump(DumpNameSpace.java:553)
at com.ibm.websphere.naming.DumpNameSpace.generateDump(DumpNameSpace.java:538)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:634)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:437)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:568)

[2/8/06 15:22:45:289 BRST] 0000000c W UOW=5-63294816-23682644:g02897 source=com.ibm.ws.naming.util.Helpers org=IBM prod=WebSphere component=Application Server thread=[Thread-1]
NMSV0605W: A Reference object looked up from the context "java:comp/env/jms" with the name "PackageReceivedQueue" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name: com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: java.lang.Object
Type: JndiLookupInfo
Content: JndiLookupInfo: jndiName="jms/PackageReceivedQueue"; providerURL="corbaloc:iiop:localhost"; initialContextFactory=""

Exception data follows:
javax.naming.NameNotFoundException: Context: TestCell/nodes/busServerNode/servers/nodeagent, name: jms/PackageReceivedQueue: First component in name jms/PackageReceivedQueue not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4043)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1746)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1707)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1412)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:372)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:889)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191)
at com.ibm.ws.naming.urlbase.UrlBindingEnumeration.jndiBindingData(UrlBindingEnumeration.java:80)
at com.ibm.ws.naming.urlbase.UrlNameEnumeration.doNextBatch(UrlNameEnumeration.java:110)
at com.ibm.ws.naming.urlbase.UrlNameEnumeration.doInit(UrlNameEnumeration.java:82)
at com.ibm.ws.naming.util.WsnNamingEnumeration.init(WsnNamingEnumeration.java:132)
at com.ibm.ws.naming.urlbase.UrlNameEnumeration.<init>(UrlNameEnumeration.java:70)
at com.ibm.ws.naming.urlbase.UrlBindingEnumeration.<init>(UrlBindingEnumeration.java:65)
at com.ibm.ws.naming.urlbase.UrlContextImpl.listBindings(UrlContextImpl.java:1173)
at com.ibm.ws.naming.urlbase.UrlContextImpl.listBindings(UrlContextImpl.java:1213)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:657)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:758)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:758)
at com.ibm.websphere.naming.DumpNameSpace.dumpContext(DumpNameSpace.java:758)
at com.ibm.websphere.naming.DumpNameSpace.doGenerateDump(DumpNameSpace.java:553)
at com.ibm.websphere.naming.DumpNameSpace.generateDump(DumpNameSpace.java:538)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:634)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:437)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:568)

14 (top)/comp/env/jms/TheConnectionFactory java.lang.Object
15 (top)/comp/env/jms/PackageReceivedQueue java.lang.Object

==============================================================================
End of Name Space Dump
==============================================================================

WSCL0035I: Initialization of the J2EE Application Client Environment has completed.
WSCL0014I: Invoking the Application Client class sender.Main
[2/8/06 15:22:45:320 BRST] 0000000c W UOW=7-63294816-23682644:g02897 source=com.ibm.ws.naming.util.Helpers org=IBM prod=WebSphere component=Application Server thread=[Thread-1]
NMSV0605W: A Reference object looked up from the context "java:" with the name "comp/env/jms/TheConnectionFactory" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name: com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: java.lang.Object
Type: JndiLookupInfo
Content: JndiLookupInfo: jndiName="jms/TheConnectionFactory"; providerURL="corbaloc:iiop:localhost"; initialContextFactory=""

Exception data follows:
javax.naming.NameNotFoundException: Context: TestCell/nodes/busServerNode/servers/nodeagent, name: jms/TheConnectionFactory: First component in name jms/TheConnectionFactory not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4043)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1746)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1707)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1412)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:372)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:889)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191)
at com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup(javaURLContextRoot.java:403)
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1280)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:201)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:142)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at sender.Main.main(Main.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:656)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:437)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:568)

[2/8/06 15:22:45:323 BRST] 0000000c W UOW=7-63294816-23682644:g02897 source=com.ibm.ws.naming.util.Helpers org=IBM prod=WebSphere component=Application Server thread=[Thread-1]
NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.java.javaURLContextRoot
Context method: lookup(Name)
Context name: java:
Target name: comp/env/jms/TheConnectionFactory
Other data: ""
Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is javax.naming.NameNotFoundException: Context: TestCell/nodes/busServerNode/servers/nodeagent, name: jms/TheConnectionFactory: First component in name jms/TheConnectionFactory not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4043)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1746)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1707)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1412)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:372)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:889)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191)
at com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup(javaURLContextRoot.java:403)
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1280)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:201)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:142)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at sender.Main.main(Main.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:656)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:437)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:568)


WSCL0100E: Exception received: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:656)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:437)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:568)
Caused by: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is javax.naming.NameNotFoundException: Context: TestCell/nodes/busServerNode/servers/nodeagent, name: jms/TheConnectionFactory: First component in name jms/TheConnectionFactory not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]]
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:952)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:191)
at com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup(javaURLContextRoot.java:403)
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1280)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:201)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:142)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at sender.Main.main(Main.java:21)
... 14 more


David Currie

unread,
Feb 9, 2006, 5:28:45 AM2/9/06
to
Looks like it is successfully binding the resources in to the local
namespace for the client container but the resources are defined as
indirections to resources defined on the server side. So, a couple of
things to check:

- the server is running and using the default ports
- that the binding names defined in the client deployment descriptor
match the JNDI names when the resources were defined on the server side

Regards,
David

jgabri...@terra.com.br

unread,
Feb 9, 2006, 12:11:12 PM2/9/06
to
First of all, thanks a lot for your reply. Thats the thing i cant understand i installed a fresh copy of Webshphere v6, no security enabled, default ports, and i have checked de JNDI names in deployment descriptor of the application client and on my server, and they are the same as follows:
jms/TheConnectionFactory
jms/PackageReceivedQueue

I've also checked the SystemOut.log file but no relevant messeges there...
But i found one error log under the tab Troubleshooting->Configuration Validation->Error in the Administrative Console.

Configuration Problems

CHKW3161E: The value of a J2EE resource factory's resource property is absent. (Provider name = SIB JMS Resource Adapter, Factory name = TheConnectionFactory)

Scope

cells/TestCell/nodes/busServerNode/resources.xml

Does the resource adapter have anything todo whith it?!? Thanks again.

jgabri...@terra.com.br

unread,
Feb 9, 2006, 2:54:31 PM2/9/06
to
I found using the dumpNameSpace.sh utility that the JNDI name is not going to the Node context as it suposed to do so. In the client application error message says that it is looking for the connection factory in the context "Context: TestCell/nodes/busServerNode/servers/nodeagent", but when i run the dumpNameSpace utility in this context i see that there is no connection factory there.

Command line call: ./dumpNameSpace.sh -startAt nodes/busServerNode/servers/nodeagent

--------------------------dumpNameSpace.sh OUTPUT-------------------------------
Getting the initial context
Getting the starting context

==============================================================================
Name Space Dump
Provider URL: corbaloc:iiop:localhost:2809
Context factory: com.ibm.websphere.naming.WsnInitialContextFactory
Requested root context: cell
Starting context: (top)=TestCell/nodes/busServerNode/servers/nodeagent
Formatting rules: jndi
Time of dump: Thu Feb 09 17:48:33 BRST 2006


==============================================================================


==============================================================================
Beginning of Name Space Dump
==============================================================================

1 (top)

2 (top)/servername java.lang.String
3 (top)/thisNode javax.naming.Context
3 Linked to context: TestCell/nodes/busServerNode
4 (top)/cell javax.naming.Context
4 Linked to context: TestCell



==============================================================================
End of Name Space Dump
==============================================================================

And the funny thing is that when i create all the default messaging components in the server scope, they go to the correct context.

Any clues?!?! Thanks for the help.

David Currie

unread,
Feb 10, 2006, 6:06:00 AM2/10/06
to
Ah - maybe this gives me a clue as to what your problem is. Here you are
looking at the namespace for the node agent rather than the server
itself which is where the resources should be defined. Similarly, you
should make sure that the client container is pointing at the bootstrap
port for the server rather than the node agent.

Regards,
David

David Currie

unread,
Feb 10, 2006, 5:59:18 AM2/10/06
to
Yes - this could be relevant. It seems to indicate that there is
something wrong with the configuration of the connection factory.
Unfortunately it doesn't give any indication as to what! I'm not sure
what to suggest other than deleting and recreating the connection factory.

Regards,
David

jgabri...@terra.com.br

unread,
Feb 13, 2006, 12:34:13 PM2/13/06
to
Getting this warning message when i try to deploy the enterprise application:

ADMA8019E: The resources that are assigned to the application are beyond the deployment target scope. Resources are within the deployment target scope if they are defined at the cell, node, server, or application level when the deployment target is a server, or at the cell, cluster, or application level when the deployment target is a cluster. Assign resources that are within the deployment target scope of the application or confirm that these resources assignments are correct as specified.

Step 4 - Provide listener bindings for message-driven beans resulted in the following resource warnings. If Application Resource Validation is set to fail, you will not be able to continue past.

Module:
Name: PackageReceived
URI: PackageReceived.jar,META-INF/ejb-jar.xml
Target: WebSphere:cell=TestCell,node=busServerNode,server=busServer
Resource Assignment:
Name: PackageReceivedActivationSpec
Scope: WebSphere:cell=TestCell,node=busServerNode,server=busServer
Type: J2CActivationSpec
JNDI: eis/PackageReceivedActivationSpec

But the thing is that in my administrative console i created the activation spec under the node scope, not the server.

jgabri...@terra.com.br

unread,
Feb 14, 2006, 11:26:20 AM2/14/06
to
Ok. Found out that the tutorial was only for a stand alone application server profile, but i was trying to configure it on a managed node profile. But anyway still the question about what are the steps for installing a SIB on a managed node?? Thanks for the replys!!

jgabri...@terra.com.br

unread,
Feb 15, 2006, 1:08:37 PM2/15/06
to
Finally solved the problem! As the resoucers where going to the server context even when i specified the node scope in the administrative console, i should have specified the BOOTSTRAP_ADRESS of the server insted of letting the client application search for JNDI names in the default addres, as this one belongs to the nodeagent. Thanks David for your help, it was one of the first things you said to check the ports...


Joao Gabriel

ben....@gmail.com

unread,
Feb 21, 2006, 3:58:48 PM2/21/06
to
Joao,

I am also following this article;). How did you solve you problem? How did you pass the BOOTSTRAP_ADRESS to the client? While creating the INitialConext()? What value did you pass?

I can actually make it work by using "jms/TheConnectionFactory" as the jndi name, but WAS would print some warning though.

Thanks in advance.

Ben.

jgabri...@terra.com.br

unread,
Feb 22, 2006, 1:43:36 PM2/22/06
to
Ben if you folowed the tutorial, and you are using the PackageReceivedClient.ear, you just have to check the BOOTSTRAP_ADDRESS of the server that is the bus member, and then in the command line calling the client application specify the port like this:
/launchClient.sh ../PackageReceivedClient.ear -CCBootstrapPort= "YOUR SERVER PORT"

Try this out.
Joao Gabriel

0 new messages