|
JMS Client Connection issue on Windows 2000 Server
|
|
Replies:
4
-
Pages:
1
-
Last Post:
Mar 26, 2008 7:56 AM
Last Post By: igor.ge
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
7
Registered:
May 10, 2007 03:56:21 PM
|
|
|
|
JMS Client Connection issue on Windows 2000 Server
Posted:
May 10, 2007 04:06:29 PM
|
|
|
|
I am trying to run this tool on my Win2K 5 SP4, but see this error when I bring up the GUI (using Swing). I have the setup pointing to IBM's Java JRE 1.4.2, and the WAS bootstrap has a port of 58809. I am trying to connect to WAS SIBus.
I have the following specified:
InitialContext Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Provider URL: corbaloc:iiop:localhost:58809
When I run my standalone (custom) Java application client, it is able to connect to the above provider URL and works just fine.
Do I need any additional jars or fixes?
Error dump:
IBM WebSphere Application Server, Release 6.1
J2EE Application Client Tool
Copyright IBM Corp., 1997-2006
WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the J2EE Application Client Environment.
5/10/07 13:46:11:578 EDT 0000000a W UOW=null source=com.ibm.ws.ssl.config.SSL
Config org=IBM prod=WebSphere component=Application Server thread=[P=160296:O=0:
CT]
CWPKI0041W: One or more key stores are using the default password.
WSCL0035I: Initialization of the J2EE Application Client Environment has complet
ed.
WSCL0014I: Invoking the Application Client class com.ibm.jms.client.JMSClient
IBM Client Application for JMSVersion: 1.0.0
? Copyright IBM Corp. 2006
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at org.eclipse.osgi.framework.internal.core.BundleLoader.findDynamicSource(BundleLoader.java:874)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
|
|
Posts:
1
Registered:
May 22, 2007 06:33:07 PM
|
|
|
|
Re: JMS Client Connection issue on Windows 2000 Server
Posted:
May 22, 2007 06:34:52 PM
in response to: gbalu1's post
|
|
|
|
Did you find out anything about this exception? I'm encountering an NPE coming out of BundleLoader.findClass() as well, although mine gets into BundleLoader.findDynamicSource().
Thanks,
Eric
|
|
Posts:
5
Registered:
Oct 04, 2006 02:56:16 AM
|
|
|
|
Re: JMS Client Connection issue on Windows 2000 Server
Posted:
Jan 16, 2008 04:03:00 AM
in response to: gbalu1's post
|
|
|
|
Hi,
Apologies for not replying to this append sooner. This issue is caused by the OSGi bundle code that was included in WAS v6.1. It affected the way that resource strings were loaded when using the ResourceBundle class. However, this issue only affected the Swing UI... the SWT UI should work without any problems.
This problem has been fixed in one of the WAS v6.1 fixpacks (I believe it was FP11, but I am not sure). I am currently using WAS v6.1.0.13 and am able to use both the SWING and SWT UI's.
Thanks.
Martin Smithson.
|
|
Posts:
2
Registered:
Mar 24, 2008 10:23:34 AM
|
|
|
|
Re: JMS Client Connection issue on Windows 2000 Server
Posted:
Mar 24, 2008 10:29:15 AM
in response to: msmiths's post
|
|
|
|
I have the same problem on Windows Vista, working in RAD 7.0.0.5, after upgrading Websphere 6.1.0.2 to 6.1.0.15 (or even to 6.1.0.3).
I am running two Application Clients (one Swing and the other without GUI) and getting the same exception.
No JMS involved.
Please, help!
|
|
Posts:
2
Registered:
Mar 24, 2008 10:23:34 AM
|
|
|
|
Re: JMS Client Connection issue on Windows 2000 Server
Posted:
Mar 26, 2008 07:56:35 AM
in response to: igor.ge's post
|
|
|
|
Ok, the problem happened, because both the applications opened new threads, and the main thread then ended. At any point after that, class loading threw the exception.
When the main thread waits, everything works.
|
|
|
|
|
