JMS doesn't work with VPN connection on weblogic8.1 - Weblogic

This is a discussion on JMS doesn't work with VPN connection on weblogic8.1 - Weblogic ; 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. ...

+ Reply to Thread
Results 1 to 7 of 7

Thread: JMS doesn't work with VPN connection on weblogic8.1

  1. JMS doesn't work with VPN connection on weblogic8.1


    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.createCon nectionInternal(JMS
    ConnectionFactory.java:160)
    at weblogic.jms.client.JMSConnectionFactory.createTop icConnection(JMSCon
    nectionFactory.java:95)
    at com.dynamex.decs.common.jms.DecsSubscriber.initial ize(DecsSubscriber.
    java:59)
    at com.dynamex.decs.client.orderentry.swing.OrderEntr y.initRMI(OrderEntr
    y.java:1714)
    at com.dynamex.decs.client.orderentry.swing.OrderEntr y.(OrderEntry
    java:124)
    at com.dynamex.decs.client.orderentry.swing.OrderEntr y.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.ShutdownUtilDelegat e.mapSystemExceptio
    n(Unknown Source)
    at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
    at weblogic.jms.frontend._FEConnectionFactoryRemote_S tub.connectionCreat
    eRequest(_FEConnectionFactoryRemote_Stub.java:106)
    at weblogic.jms.client.JMSConnectionFactory.createCon nectionInternal(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.purg e_calls(Unknown Sou
    rce)
    at com.sun.corba.se.internal.iiop.MessageMediator.han dleInput(Unknown
    So
    urce)
    at com.sun.corba.se.internal.iiop.messages.MessageBas e.callback(Unknown
    Source)
    at com.sun.corba.se.internal.iiop.MessageMediator.pro cessRequest(Unknown
    Source)
    at com.sun.corba.se.internal.iiop.IIOPConnection.proc essInput(Unknown
    So
    urce)
    at com.sun.corba.se.internal.iiop.ReaderThread.run(Un known Source)


    Does anybody have the experience? Can anybody give a hint?

    Thanks,

    Tony

  2. Re: JMS doesn't work with VPN connection on weblogic8.1


    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.add PeerGoneListener(D
    spatcherWrapperState.java:563)
    at weblogic.jms.dispatcher.DispatcherManager.dispatch erAdd(DispatcherMa
    ager.java:106)
    at weblogic.jms.dispatcher.DispatcherManager.addDispa tcherReference(Dis
    atcherManager.java:196)
    at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateInternal(F
    ConnectionFactory.java:413)
    at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateRequest(FE
    onnectionFactory.java:385)
    at weblogic.jms.frontend.FEConnectionFactory_WLSkel.i nvoke(Unknown Sour
    e)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicS erverRef.java:466)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke( ReplicaAwareServer
    ef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicSe rverRef.java:409)
    at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(Authenticat
    dSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(Se curityManager.java
    144)
    @


    "tony yang" 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.createCon nectionInternal(JMS
    >ConnectionFactory.java:160)
    > at weblogic.jms.client.JMSConnectionFactory.createTop icConnection(JMSCon
    >nectionFactory.java:95)
    > at com.dynamex.decs.common.jms.DecsSubscriber.initial ize(DecsSubscriber.
    >java:59)
    > at com.dynamex.decs.client.orderentry.swing.OrderEntr y.initRMI(OrderEntr
    >y.java:1714)
    > at com.dynamex.decs.client.orderentry.swing.OrderEntr y.(OrderEntry
    >.java:124)
    > at com.dynamex.decs.client.orderentry.swing.OrderEntr y.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.ShutdownUtilDelegat e.mapSystemExceptio
    >n(Unknown Source)
    > at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
    > at weblogic.jms.frontend._FEConnectionFactoryRemote_S tub.connectionCreat
    >eRequest(_FEConnectionFactoryRemote_Stub.java:106)
    > at weblogic.jms.client.JMSConnectionFactory.createCon nectionInternal(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.purg e_calls(Unknown
    >Sou
    >rce)
    > at com.sun.corba.se.internal.iiop.MessageMediator.han dleInput(Unknown
    >So
    >urce)
    > at com.sun.corba.se.internal.iiop.messages.MessageBas e.callback(Unknown
    >Source)
    > at com.sun.corba.se.internal.iiop.MessageMediator.pro cessRequest(Unknown
    > Source)
    > at com.sun.corba.se.internal.iiop.IIOPConnection.proc essInput(Unknown
    >So
    >urce)
    > at com.sun.corba.se.internal.iiop.ReaderThread.run(Un known Source)
    >
    >
    > Does anybody have the experience? Can anybody give a hint?
    >
    > Thanks,
    >
    >Tony



  3. Re: JMS doesn't work with VPN connection on weblogic8.1

    Hi Tony,

    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 wrote:

    > 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.add PeerGoneListener(D
    > spatcherWrapperState.java:563)
    > at weblogic.jms.dispatcher.DispatcherManager.dispatch erAdd(DispatcherMa
    > ager.java:106)
    > at weblogic.jms.dispatcher.DispatcherManager.addDispa tcherReference(Dis
    > atcherManager.java:196)
    > at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateInternal(F
    > ConnectionFactory.java:413)
    > at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateRequest(FE
    > onnectionFactory.java:385)
    > at weblogic.jms.frontend.FEConnectionFactory_WLSkel.i nvoke(Unknown Sour
    > e)
    > at weblogic.rmi.internal.BasicServerRef.invoke(BasicS erverRef.java:466)
    > at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke( ReplicaAwareServer
    > ef.java:108)
    > at weblogic.rmi.internal.BasicServerRef$1.run(BasicSe rverRef.java:409)
    > at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(Authenticat
    > dSubject.java:353)
    > at weblogic.security.service.SecurityManager.runAs(Se curityManager.java
    > 144)
    > @
    >
    >
    > "tony yang" 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.createCon nectionInternal(JMS
    >>ConnectionFactory.java:160)
    >> at weblogic.jms.client.JMSConnectionFactory.createTop icConnection(JMSCon
    >>nectionFactory.java:95)
    >> at com.dynamex.decs.common.jms.DecsSubscriber.initial ize(DecsSubscriber.
    >>java:59)
    >> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.initRMI(OrderEntr
    >>y.java:1714)
    >> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.(OrderEntry
    >>.java:124)
    >> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.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.ShutdownUtilDelegat e.mapSystemExceptio
    >>n(Unknown Source)
    >> at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
    >> at weblogic.jms.frontend._FEConnectionFactoryRemote_S tub.connectionCreat
    >>eRequest(_FEConnectionFactoryRemote_Stub.java:106)
    >> at weblogic.jms.client.JMSConnectionFactory.createCon nectionInternal(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.purg e_calls(Unknown
    >>Sou
    >>rce)
    >> at com.sun.corba.se.internal.iiop.MessageMediator.han dleInput(Unknown
    >>So
    >>urce)
    >> at com.sun.corba.se.internal.iiop.messages.MessageBas e.callback(Unknown
    >>Source)
    >> at com.sun.corba.se.internal.iiop.MessageMediator.pro cessRequest(Unknown
    >>Source)
    >> at com.sun.corba.se.internal.iiop.IIOPConnection.proc essInput(Unknown
    >>So
    >>urce)
    >> at com.sun.corba.se.internal.iiop.ReaderThread.run(Un known Source)
    >>
    >>
    >> Does anybody have the experience? Can anybody give a hint?
    >>
    >> Thanks,
    >>
    >>Tony

    >
    >



  4. Re: JMS doesn't work with VPN connection on weblogic8.1


    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 wrote:
    >Hi Tony,
    >
    >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 wrote:
    >
    >> 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.add PeerGoneListener(D
    >> spatcherWrapperState.java:563)
    >> at weblogic.jms.dispatcher.DispatcherManager.dispatch erAdd(DispatcherMa
    >> ager.java:106)
    >> at weblogic.jms.dispatcher.DispatcherManager.addDispa tcherReference(Dis
    >> atcherManager.java:196)
    >> at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateInternal(F
    >> ConnectionFactory.java:413)
    >> at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateRequest(FE
    >> onnectionFactory.java:385)
    >> at weblogic.jms.frontend.FEConnectionFactory_WLSkel.i nvoke(Unknown

    >Sour
    >> e)
    >> at weblogic.rmi.internal.BasicServerRef.invoke(BasicS erverRef.java:466)
    >> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke( ReplicaAwareServer
    >> ef.java:108)
    >> at weblogic.rmi.internal.BasicServerRef$1.run(BasicSe rverRef.java:409)
    >> at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(Authenticat
    >> dSubject.java:353)
    >> at weblogic.security.service.SecurityManager.runAs(Se curityManager.java
    >> 144)
    >> @
    >>
    >>
    >> "tony yang" 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.createCon nectionInternal(JMS
    >>>ConnectionFactory.java:160)
    >>> at weblogic.jms.client.JMSConnectionFactory.createTop icConnection(JMSCon
    >>>nectionFactory.java:95)
    >>> at com.dynamex.decs.common.jms.DecsSubscriber.initial ize(DecsSubscriber.
    >>>java:59)
    >>> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.initRMI(OrderEntr
    >>>y.java:1714)
    >>> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.(OrderEntry
    >>>.java:124)
    >>> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.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.ShutdownUtilDelegat e.mapSystemExceptio
    >>>n(Unknown Source)
    >>> at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
    >>> at weblogic.jms.frontend._FEConnectionFactoryRemote_S tub.connectionCreat
    >>>eRequest(_FEConnectionFactoryRemote_Stub.java:106)
    >>> at weblogic.jms.client.JMSConnectionFactory.createCon nectionInternal(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.purg e_calls(Unknown
    >>>Sou
    >>>rce)
    >>> at com.sun.corba.se.internal.iiop.MessageMediator.han dleInput(Unknown
    >>>So
    >>>urce)
    >>> at com.sun.corba.se.internal.iiop.messages.MessageBas e.callback(Unknown
    >>>Source)
    >>> at com.sun.corba.se.internal.iiop.MessageMediator.pro cessRequest(Unknown
    >>>Source)
    >>> at com.sun.corba.se.internal.iiop.IIOPConnection.proc essInput(Unknown
    >>>So
    >>>urce)
    >>> at com.sun.corba.se.internal.iiop.ReaderThread.run(Un known Source)
    >>>
    >>>
    >>> Does anybody have the experience? Can anybody give a hint?
    >>>
    >>> Thanks,
    >>>
    >>>Tony

    >>
    >>

    >



  5. Re: JMS doesn't work with VPN connection on weblogic8.1

    Hi Tony,

    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

    tony yang wrote:
    > 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 wrote:
    >
    >>Hi Tony,
    >>
    >>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 wrote:
    >>
    >>
    >>>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.add PeerGoneListener(D
    >>>spatcherWrapperState.java:563)
    >>> at weblogic.jms.dispatcher.DispatcherManager.dispatch erAdd(DispatcherMa
    >>>ager.java:106)
    >>> at weblogic.jms.dispatcher.DispatcherManager.addDispa tcherReference(Dis
    >>>atcherManager.java:196)
    >>> at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateInternal(F
    >>>ConnectionFactory.java:413)
    >>> at weblogic.jms.frontend.FEConnectionFactory.connecti onCreateRequest(FE
    >>>onnectionFactory.java:385)
    >>> at weblogic.jms.frontend.FEConnectionFactory_WLSkel.i nvoke(Unknown

    >>
    >>Sour
    >>
    >>>e)
    >>> at weblogic.rmi.internal.BasicServerRef.invoke(BasicS erverRef.java:466)
    >>> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke( ReplicaAwareServer
    >>>ef.java:108)
    >>> at weblogic.rmi.internal.BasicServerRef$1.run(BasicSe rverRef.java:409)
    >>> at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(Authenticat
    >>>dSubject.java:353)
    >>> at weblogic.security.service.SecurityManager.runAs(Se curityManager.java
    >>>144)
    >>>@
    >>>
    >>>
    >>>"tony yang" 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.createCon nectionInternal(JMS
    >>>>ConnectionFactory.java:160)
    >>>> at weblogic.jms.client.JMSConnectionFactory.createTop icConnection(JMSCon
    >>>>nectionFactory.java:95)
    >>>> at com.dynamex.decs.common.jms.DecsSubscriber.initial ize(DecsSubscriber.
    >>>>java:59)
    >>>> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.initRMI(OrderEntr
    >>>>y.java:1714)
    >>>> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.(OrderEntry
    >>>>.java:124)
    >>>> at com.dynamex.decs.client.orderentry.swing.OrderEntr y.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.ShutdownUtilDelegat e.mapSystemExceptio
    >>>>n(Unknown Source)
    >>>> at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
    >>>> at weblogic.jms.frontend._FEConnectionFactoryRemote_S tub.connectionCreat
    >>>>eRequest(_FEConnectionFactoryRemote_Stub.java:106)
    >>>> at weblogic.jms.client.JMSConnectionFactory.createCon nectionInternal(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.purg e_calls(Unknown
    >>>>Sou
    >>>>rce)
    >>>> at com.sun.corba.se.internal.iiop.MessageMediator.han dleInput(Unknown
    >>>>So
    >>>>urce)
    >>>> at com.sun.corba.se.internal.iiop.messages.MessageBas e.callback(Unknown
    >>>>Source)
    >>>> at com.sun.corba.se.internal.iiop.MessageMediator.pro cessRequest(Unknown
    >>>>Source)
    >>>> at com.sun.corba.se.internal.iiop.IIOPConnection.proc essInput(Unknown
    >>>>So
    >>>>urce)
    >>>> at com.sun.corba.se.internal.iiop.ReaderThread.run(Un known Source)
    >>>>
    >>>>
    >>>> Does anybody have the experience? Can anybody give a hint?
    >>>>
    >>>> Thanks,
    >>>>
    >>>>Tony
    >>>
    >>>

    >



  6. Re: JMS doesn't work with VPN connection on weblogic8.1

    hi....ther
    plz can u tel me how to connect open MQ in a LAN connection.

  7. Re: JMS doesn't work with VPN connection on weblogic8.1

    Just making sure OR java messanger service but i prefer Whole messages and teenage slang is good with me mate XD

+ Reply to Thread