[openjms-developer] [ openjms-Bugs-1207935 ] publishing from websphere 5.1

[SourceForge.net]

Bugs item #1207935, was opened at 2005-05-25 02:13
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1207935&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: jndi
Group: v0.7.6.1
Status: Open
Resolution: None
Priority: 5
Submitted By: sanneoanu (sanneoanu)
Assigned to: Nobody/Anonymous (nobody)
Summary: publishing from websphere 5.1

Initial Comment:
1. I am using openJMS for publishing/subscribing
2. I am able to publish using openJMS example of
SimplePublisher.java as independent java classes,
through servlet in tomcat.

Problem:
The moment I use the same code in websphere 5.1 I am
getting null connections when "createTopicConnection"
is called. The exception is as below:

[5/23/05 18:14:12:350 EDT] 54205420 SystemErr R
java.lang.NullPointerException

[5/23/05 18:14:12:380 EDT] 54205420 SystemErr R at
java.lang.Throwable.<init>(Throwable.java:54)

[5/23/05 18:14:12:380 EDT] 54205420 SystemErr R at
java.lang.Throwable.<init>(Throwable.java:68)

[5/23/05 18:14:12:380 EDT] 54205420 SystemErr R at
java.lang.NullPointerException.<init>
(NullPointerException.java:63)

[5/23/05 18:14:12:380 EDT] 54205420 SystemErr R at
org.exolab.jms.client.JmsConnectionFactory.addConnect
ion(JmsConnectionFactory.java:171)

[5/23/05 18:14:12:380 EDT] 54205420 SystemErr R at
org.exolab.jms.client.JmsTopicConnectionFactory.create
TopicConnection(JmsTopicConnectionFactory.java:115)

[5/23/05 18:14:12:390 EDT] 54205420 SystemErr R at
org.exolab.jms.client.JmsTopicConnectionFactory.create
TopicConnection(JmsTopicConnectionFactory.java:103)

[5/23/05 18:14:12:390 EDT] 54205420 SystemErr R at
openjms.examples.client.console.SimplePublisher.main
(SimplePublisher.java)

Wonder if its a bug?

----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)

Date: 2005-06-08 15:12

Message:
Logged In: YES
user_id=557161

Looking at the code, I can't see that _connections ever gets set
to null. Are you using 0.7.6.1, or some other version.
The source for JmsConnectionFactory in 0.7.6.1 is here:
http://cvs.sourceforge.net/viewcvs.py/openjms/openjms/src/main/o
rg/exolab/jms/client/Attic/JmsConnectionFactory.java?
rev=1.19&only_with_tag=openjms_0_7_6_maint

----------------------------------------------------------------------

Comment By: sanneoanu (sanneoanu)
Date: 2005-05-25 02:20

Message:
Logged In: YES
user_id=1283997

To add on the above

Context context = ContextHelper.getContext(cmdline);
returns context, there is a difference in context data [as seen
in debugger]
java.naming.factory.url.pkgs=:com.ibm.ws.naming:com.ibm.w
s.naming:com.ibm.ws.naming} is also there in context-

myprops

This ..url.pkgs is not there at all when class is executed
independently. I removed this property but still the exception,
also dont know if this makes the problem

also when following is executed
TopicConnectionFactory factory = (TopicConnectionFactory)
context.lookup("JmsTopicConnectionFactoryNew");

factory is returned but the factory->_connections = null [as
seen in debugger]

I am not able to find any document which specify the different
usage in websphere.



----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1207935&group_id=54559