JMS doesn't work with VPN connection on weblogic8.1
tony yang
Hi:
We have used JMS topic on weblogic 7.x and we use both LAN and VPN connection.
However, when we switch to weblogic 8.1, although it works fine when using
LAN connection,
it does not work when using VPN connection. We tried three different machines,
got the same
error.
The error is:
weblogic.jms.common.JMSException: Error creating connection on the server
at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMS
ConnectionFactory.java:160)
at weblogic.jms.client.JMSConnectionFactory.createTopicConnection(JMSCon
nectionFactory.java:95)
at com.dynamex.decs.common.jms.DecsSubscriber.initialize(DecsSubscriber.
java:59)
at com.dynamex.decs.client.orderentry.swing.OrderEntry.initRMI(OrderEntr
y.java:1714)
at com.dynamex.decs.client.orderentry.swing.OrderEntry.<init>(OrderEntry
java:124)
at com.dynamex.decs.client.orderentry.swing.OrderEntry.main(OrderEntry.j
ava:3180)
Caused by: java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested
e
xception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed:
No
at com.sun.corba.se.internal.iiop.ShutdownUtilDelegate.mapSystemExceptio
n(Unknown Source)
at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
at weblogic.jms.frontend._FEConnectionFactoryRemote_Stub.connectionCreat
eRequest(_FEConnectionFactoryRemote_Stub.java:106)
at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMS
ConnectionFactory.java:139)
... 5 more
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed:
No
at com.sun.corba.se.internal.iiop.IIOPConnection.purge_calls(Unknown Sou
rce)
at com.sun.corba.se.internal.iiop.MessageMediator.handleInput(Unknown
So
urce)
at com.sun.corba.se.internal.iiop.messages.MessageBase.callback(Unknown
Source)
at com.sun.corba.se.internal.iiop.MessageMediator.processRequest(Unknown
Source)
at com.sun.corba.se.internal.iiop.IIOPConnection.processInput(Unknown
So
urce)
at com.sun.corba.se.internal.iiop.ReaderThread.run(Unknown Source)
Does anybody have the experience? Can anybody give a hint?
Thanks,
Tony
tony yang
I also have the log from weblogic server:
weblogic.jms.dispatcher.DispatcherException: Could not register a HeartbeatMoni
orListener for [weblogic.iiop.IIOPRemoteRef@745152c4] for weblogic.jms.C:dal603
t05:rcy:-l91
at weblogic.jms.dispatcher.DispatcherWrapperState.addPeerGoneListener(D
spatcherWrapperState.java:563)
at weblogic.jms.dispatcher.DispatcherManager.dispatcherAdd(DispatcherMa
ager.java:106)
at weblogic.jms.dispatcher.DispatcherManager.addDispatcherReference(Dis
atcherManager.java:196)
at weblogic.jms.frontend.FEConnectionFactory.connectionCreateInternal(F
ConnectionFactory.java:413)
at weblogic.jms.frontend.FEConnectionFactory.connectionCreateRequest(FE
onnectionFactory.java:385)
at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown Sour
e)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServer
ef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticat
dSubject.java:353)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java
144)
@
"tony yang" <tony...@dynamex.com> wrote:
>
>Hi:
>
> We have used JMS topic on weblogic 7.x and we use both LAN and
>VPN connection.
> However, when we switch to weblogic 8.1, although it works fine
>when using
>LAN connection,
>it does not work when using VPN connection. We tried three different
>machines,
>got the same
>error.
> The error is:
>
>weblogic.jms.common.JMSException: Error creating connection on the server
> at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMS
>ConnectionFactory.java:160)
> at weblogic.jms.client.JMSConnectionFactory.createTopicConnection(JMSCon
>nectionFactory.java:95)
> at com.dynamex.decs.common.jms.DecsSubscriber.initialize(DecsSubscriber.
>java:59)
> at com.dynamex.decs.client.orderentry.swing.OrderEntry.initRMI(OrderEntr
>y.java:1714)
> at com.dynamex.decs.client.orderentry.swing.OrderEntry.<init>(OrderEntry
>.java:124)
Tom Barnes
At first glance I don't know what is going on, and can only
make some random suggestions. Perhaps try
the t3 protocol (rather than iiop protocol) if you are using iiop
URLs to connect to JMS. If you are using the new 8.1 thin
client jars, try switching back and using full jar instead.
Perhaps try posting to the IIOP newsgroup.
Tom, BEA
tony yang
Tom:
Thanks,
We actually use t3. However, in terms of weblogic 8.1 doc, t3 transparently
uses iopp. So t3 or iopp both fails over VPN connection.
After replacing with full weblogic jar as you suggested, it works.
However, we really want the thin client because we have huge amount of client
deployments.
The other developers here also noticed other problems beside JMS problem
when using VPN connection and thin client jars.
We guess full weblogic.jar uses real t3 instead of iiop.
Seems that iiop does not work well over VPN connection.
Could you give some estimate of when we can have the new thin client jars
to support VPN connection (even not official release)?
Tony
Tom Barnes
Given that the thick jar works, I would classify the problem
as a bug - not a missing feature. The thin jar is contracted
to be just as capable as the thick jar. My guess is that
the bug is likely in IIOP but perhaps could be in JMS.
Contact customer support (this forum is not maintained by
customer support). Meanwhile, you can post your info
to the IIOP newsgroup to see if they can help.
You asked how long it would take to fix? That depends
on bug priority (set by the customer) and bug complexity,
but its usually measured in days or weeks (not months).
You can speed up the process by giving support your
logs and stack traces, as well as a simple reproducer,
and telling them you are willing to try out a prototype
patch. But before going through extra trouble, just give
them the logs/stack traces, in case it is a known issue
for which there is already a fix or there is a fix in progress.
Tom