Embedded JMS Server setup

[V Leher]

This is probably the most stupid question and also a repost from the
other newsgroup. I tried solving it and going through the docs, and it
did not help.

I am trying to use the embedded JMS server. I created a JMS Topic
Connection Factory and a JMS topic destination. I also created a
Listener port and specified the Jndi names for the factory and destination.

When i deploy the ear file, which has the jms client as a servlet, it
cannot lookup either the topic connection factory or the topic
destination. It is giving a javax.naming.NameNotFoundException. So
clearly the jndi names for the embedded JMS is not getting bound. What
am i doing wrong here or what else should i be doing?

I am running the websphere v5.0.0 on a RHLinux v8.0.

Any help is appreciated.

thanks,
- Leher

[ravi_asthana]

How r u trying to access connection factory and topic while publishing ?
r u appending "java/env" before ur JNDI names ? If yes, please remove it
and try again. It might sound a studpid answer :-) But try it. It worked
in my case.

--
posted via MFF : http://www.MainFrameForum.com - USENET Gateway

[V Leher]

There is no java/env in front of the JNDI names. the JNDI names as
specified in the GUI and used for lookup is the same as leher/test/topic
. The JNDI names doesnot even show up in the dumpnamespace utility, so
it is obviously not getting bound to the namespace.

NO answer is ever stupid :-)

- Leher

[David Currie]

Hi,

When you say you 'created' a topic connection factory and topic presumably
you been defined via WebSphere system management on the WebSphere JMS
provider? If so, and after a server restart the resources don't appear when
you do a dumpNameSpace then, yes, you have a problem. Any clues in
SystemOut.log?

Regards,
David

[V Leher]

After scanning through the log files, came across several of these
exceptions when the server starts up which basically seems to cause the
problem. These were found in the nativestderr.log file. There was
nothing reported in the SystemOut.log file. I am attaching part of the
log file.

I will try reinstalling the server.

thanks,
- Leher

--- Log -------

[Loading superclasses of com/ibm/ws/runtime/component/binder/WASTopicBinder]
[Preparing com/ibm/ws/runtime/component/binder/WASTopicBinder]
[Signaling in VM: java/lang/ClassCastException, message:
com.ibm.ws.runtime.component.binder.WASTopicBinder]
at
java.beans.beancontext.BeanContextSupport.getChildVisibility(BeanContextSupport.java:1175)
at
java.beans.beancontext.BeanContextSupport.add(BeanContextSupport.java:430)
at com.ibm.ws.runtime.component.ContainerImpl.add(ContainerImpl.java:202)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.initializeResouceBinders(ResourceMgrImpl.java:190)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.initialize(ResourceMgrImpl.java:318)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:507)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:420)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.initialize(ApplicationServerImpl.java:68)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:507)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:443)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:95)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:126)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[Signaling in VM: java/lang/ClassCastException, message:
com.ibm.ws.runtime.component.binder.WASTopicBinder]
at
java.beans.beancontext.BeanContextSupport.getChildSerializable(BeanContextSupport.java:1188)
at
java.beans.beancontext.BeanContextSupport.add(BeanContextSupport.java:439)
at com.ibm.ws.runtime.component.ContainerImpl.add(ContainerImpl.java:202)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.initializeResouceBinders(ResourceMgrImpl.java:190)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.initialize(ResourceMgrImpl.java:318)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:507)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:420)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.initialize(ApplicationServerImpl.java:68)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:507)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:443)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:95)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:126)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

[V Leher]

I reinstalled the server, and now the exceptions donot happen but the
issue remains the same. I cannot find any errors or exceptions in any of
the log files.

Any ideas?
- Leher

[David Currie]

So you still don't see the resources when you do a dumpNameSpace? Is there
anything in SystemOut.log indicating that it is trying to bind the
resources?

Regards
David

[V Leher]

When I reinstall it gives the message that the "Unable to start the JMS
Server as WebSphere Embedded Messaging has not been installed". So i try
to reinstall with the Messaging feature, but the installer doesnot show
that feature at all during custom installation. And when i try to dull a
"full installation", it tries to install the Http Server web plugin
which i donot have/and don't require. Any ideas how i can get around this?

I tried installing the custom mode and then installing the 5.0.2 fixpack
on top of it with full installation, that seems to go smooth but when i
try to start up the server, it throws up the follwoing error.

[8/4/03 9:14:56:240 PDT] 21c2c851 JMSEmbeddedPr E MSGS0058E: Unable to
start the JMS Server as WebSphere Embedded Messaging has not been installed
[8/4/03 9:14:56:243 PDT] 21c2c851 JMSService E MSGS0001E: Starting
the JMS Server failed with exception: java.lang.Exception: MSGS0058E:
Unable to start the JMS Server as WebSphere Embedded Messaging has not
been installed
at
com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:213)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:251)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at
com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)

at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

[8/4/03 9:14:56:836 PDT] 21c2c851 ConfigError I WSVR0300I: Problems
found in
/usr/local/websphere/AppServer/config/cells/leher/nodes/leher/resources.xml
[8/4/03 9:14:56:846 PDT] 21c2c851 ConfigError W WSVR0307W: Invalid
namespace, resources.jms.internalmessaging, at line 7
[8/4/03 9:14:56:848 PDT] 21c2c851 ConfigError W WSVR0303W: Invalid
element tagname, connectionPool, at line 8
[8/4/03 9:14:56:850 PDT] 21c2c851 ConfigError W WSVR0303W: Invalid
element tagname, sessionPool, at line 9
[8/4/03 9:14:56:851 PDT] 21c2c851 ConfigError W WSVR0307W: Invalid
namespace, resources.jms.internalmessaging, at line 11
[8/4/03 9:15:02:600 PDT] 21c2c851 WsServer E WSVR0003E: Server
server1 failed to start
java.lang.NullPointerException
at
com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:519)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:413)
at
com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:362)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:117)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at
com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)

at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

[8/4/03 9:15:02:625 PDT] 21c2c851 WsServer E WSVR0009E: Error
occurred during startup

thanks for your help.
- Leher

[David Currie]

You're not using the trial download by any chance? Embedded messaging comes
as a separate download in that case.

Regards
David

[V Leher]

Yes, I am using the trial download. I cannot find the Embedded Messaging
trial download anywhere in the IBM download site. Can you point me to
where i might be able to get it from? I read a post saying that it is in
the same page as the App Server but i have not been able to see it there
or anywhere else for that matter.

thanks
- Leher

[David Currie]

On the trial download page there is an item titled "MQSeries v5.3 Trial".
This is the download you need. I agree that it is badly named.

Regards
David

[dsingh123]

HI,
I'm having the same problem as we are discussing in this topic....I have already tested my application with WAS5.0 ND (Without clustering) and Websphere MQ Pub/SUb(on a seprate machine) its working fine....But in clustering scenario as given below

Machine A - WAS 5.0 ND + Embedded Client + Deployment Manager }
Machine B - WAS 5.0 ND + Embedded Client } Both machines are in Cluster

Machine c - WebSphere MQ v5.3 + MA0C

and using the Deployment Manager console -> Resources -> WebSphere MQ JMS Provider - I configured Topic Connection factories and Topic Destinations

I have restarted the WAS on both the machine and also Deployment manager

BUT i cant see JNDI names when i run dumpnamespace under Deployment Manager....just for the heck i also checked under WAS servers also its not even there

Pl Help....AM I doing the right way...... I'll really appreciate your kind reply

Thanx
- Dave