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

JNLP's and JMS message

5 views
Skip to first unread message

Kyey

unread,
Dec 3, 2001, 6:18:55 PM12/3/01
to

Hello we have just migrated our app from 5.1 to 6.1 and we are continously getting
JMS Exception at random spot when we are starting our app (Basically creating
connections). We have a class named Notification that creates and maintains our
JMS conections. The following below is the exception:
weblogic.jms.common.JMSException: Error creating connection on the server

at weblogic.jms.client.JMSConnectionFactory.connectionCreate(JMSConnectionFactory.java:119)

at weblogic.jms.client.JMSConnectionFactory.createTopicConnection(JMSConnectionFactory.java:73)

at com.beyondbond.jms.Notification.<init>(Notification.java:186)

at com.beyondbond.jms.Notification.<init>(Notification.java:222)

at com.beyondbond.client.gui.entry.TradeEntryModel.<init>(TradeEntryModel.java:113)

at com.beyondbond.client.gui.entry.EntryIFrame.<init>(EntryIFrame.java:198)

at com.beyondbond.client.gui.common.DesktopPane.run(DesktopPane.java:218)

at java.lang.Thread.run(Unknown Source)

----------- Linked Exception -----------

java.rmi.MarshalException: failed to marshal connectionCreate(Lweblogic.jms.dispatcher.DispatcherWrapper;);
nested exception is:
java.io.NotSerializableException: weblogic.jms.dispatcher.DispatcherImpl

java.io.NotSerializableException: weblogic.jms.dispatcher.DispatcherImpl

at java.io.ObjectOutputStream.outputObject(Unknown Source)

at java.io.ObjectOutputStream.writeObject(Unknown Source)

at weblogic.common.internal.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:102)

at weblogic.jms.dispatcher.DispatcherWrapper.writeExternal(DispatcherWrapper.java:95)

at weblogic.common.internal.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:91)

at weblogic.common.internal.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:108)

at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:36)

at weblogic.rmi.internal.BasicRemoteRef.marshalArgs(BasicRemoteRef.java:212)

at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)

at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)

at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)

at $Proxy6.connectionCreate(Unknown Source)

at weblogic.jms.client.JMSConnectionFactory.connectionCreate(JMSConnectionFactory.java:115)

at weblogic.jms.client.JMSConnectionFactory.createTopicConnection(JMSConnectionFactory.java:73)

at com.beyondbond.jms.Notification.<init>(Notification.java:186)

at com.beyondbond.jms.Notification.<init>(Notification.java:222)

at com.beyondbond.client.gui.entry.TradeEntryModel.<init>(TradeEntryModel.java:113)

at com.beyondbond.client.gui.entry.EntryIFrame.<init>(EntryIFrame.java:198)

at com.beyondbond.client.gui.common.DesktopPane.run(DesktopPane.java:218)

at java.lang.Thread.run(Unknown Source)

Kye

unread,
Dec 5, 2001, 10:46:55 AM12/5/01
to
Found out that the answer to our problem lied in the jnlp itself, we had to
put the signed weblogic.jar before any of the other jars we used and this
fixed our problem.

"Kyey" <khe...@beyondbond.com> wrote in message
news:3c0c085f$1...@newsgroups.bea.com...

0 new messages