Has anyone run into the following problem? I've written a standalone EJB client that I deployed via JWS. It worked fine. I then decided to change the update method of the client's display to use the JMS provider that comes with the j2sdkee1.3 beta: the client is both a subscriber and a publisher to a topic.... so that all clients know when a change has been effected by any other client, and can modify their displays appropriately... thus keeping all the clients in sync. This works okay when I run the clients from a command line, but when I deploy with JWS, I get a message saying "Ignoring com/sun/jms/util/jms.properties due to exception java.lang.NullPointerException", with no further stack trace. This occurs at the call to myTopicConnectionFactory.createTopicConnection(). And needless to say, no messages are ever delivered. I've set the system property "jms.properties" to "$J2EE_HOME/config/jms_client.properties" in the client, which is bad form, as it requires the presence of that file on the client machine. This would be the same, I assume, as specifying a property in the jnlp file. If I don't specify the jms.properties at all, I get the following stack trace: Ignoring com/sun/jms/util/jms.properties due to exception java.lang.NullPointerException Caught an unexpected exception! java.lang.NullPointerException at java.util.Hashtable.put(Unknown Source) at com.sun.jms.JMSInitialContext.<init> (JMSInitialContext.java:58) at com.sun.jms.client.InitialClientContext.<init> (InitialClientContext.java:55) at com.sun.jms.client.InitialClientContext.getInstance (InitialClientContext.java:75) at com.sun.jms.ConnectionFactoryImpl.createConnection (ConnectionFactoryImpl.java:254) at com.sun.jms.TopicConnectionFactoryImpl.createTopicConnection (TopicConnectionFactoryImpl.java:77) at com.sun.jms.TopicConnectionFactoryImpl.createTopicConnection (TopicConnectionFactoryImpl.java:58) at com.sun.enterprise.jms.ConnectionFactoryWrapperStandalone.createTopicConnection (../../src/share/com/sun/enterprise/jms/ConnectionFactoryWrapperStandalone.java:55) at com.skyoptix.nms.security.client.SecurityClient.<init> (SecurityClient.java:181) at com.skyoptix.nms.security.client.SecurityClient.main (SecurityClient.java:85) at java.lang.reflect.Method.invoke(Native Method) at com.sun.javaws.Launcher.executeApplication (Launcher.java:701) at com.sun.javaws.Launcher.executeMainClass (Launcher.java:663) at com.sun.javaws.Launcher.continueLaunch (Launcher.java:546) at com.sun.javaws.Launcher.handleApplicationDesc (Launcher.java:334) at com.sun.javaws.Launcher.handleLaunchFile (Launcher.java:151) at com.sun.javaws.Launcher.<init>(Launcher.java:113) at com.sun.javaws.Main.main(Main.java:153) I realize the jms_client.properties file should be treated as a resource that resides in the executable jar downloaded by JWS. So I included it in the jar and had the client treat it as a ResourceBundle, and load the name/value pairs into the system properties. But, unsurprisingly, that didn't work either. Probably because the JMS implementation is written to load the properties from a file. I'd read the source for 1.3 beta if it were available, but all I can find from sun is 1.2.1. Anyone have any ideas? TIA, Bill __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
