T3Client.connect() problem in weblogic 6.1 - Weblogic

This is a discussion on T3Client.connect() problem in weblogic 6.1 - Weblogic ; I am having problem in T3Client.connect() in Weblogic 6.1. Our application runs well in Weblogic 5.1 with T3Client.connect(), but the following error appears when the connect() is invoked in 6.1. Any idea? vm.t3.T3JVMConnection@53e51' because of: 'Server received a message over ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: T3Client.connect() problem in weblogic 6.1

  1. T3Client.connect() problem in weblogic 6.1


    I am having problem in T3Client.connect() in Weblogic 6.1. Our application runs
    well in Weblogic 5.1 with T3Client.connect(), but the following error appears
    when the connect() is invoked in 6.1. Any idea?

    vm.t3.T3JVMConnection@53e51' because of: 'Server received a message over an unin
    itialized connection: 'JVMMessage from: 'null' to: '1577296987682531743S:162.70.
    250.94:[7001,7001,7002,7002,7001,7002,-1]:ccDomain:scott' cmd: 'CMD_REQUEST',
    QO
    S: '101', responseId: '1', invokableId: '1', flags: 'JVMIDs Not Sent, TX Context
    Not Sent', abbrev offset: '91'''>
    <[WebAppServletContext(6748107,cc,/
    cc)] Servlet failed with Exception
    java.rmi.UnexpectedException: Marshalling: ; nested exception is:
    java.rmi.ConnectException: PeerGone; nested exception is:
    weblogic.rjvm.PeerGoneException: Config message not received after 60
    se
    conds
    java.rmi.ConnectException: PeerGone; nested exception is:
    weblogic.rjvm.PeerGoneException: Config message not received after 60
    se
    conds
    weblogic.rjvm.PeerGoneException: Config message not received after 60 seconds
    at weblogic.rjvm.RJVMImpl$ConfigTimeoutChecker.trigge r(RJVMImpl.java:108
    0)
    at weblogic.time.common.internal.ScheduledTrigger.exe cuteLocally(Schedul
    edTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.exe cute(ScheduledTrigg
    er.java:229)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:120)


  2. Re: T3Client.connect() problem in weblogic 6.1

    The T3Client API has nothing to do with JMS.

    Anyway, I think parts (or all?) of it have been deprecated
    (but perhaps not in 6.1). For more information you might try:
    weblogic.developer.interest.general

    Note that interoperability is not supported
    between 6.1 and earlier versions. (A 6.1
    client can't directly invoke something
    running on a 5.1 server - but there are some
    work-arounds.)


    "Scott Shen" chih-ping.shen wrote:

    > I am having problem in T3Client.connect() in Weblogic 6.1. Our application runs
    > well in Weblogic 5.1 with T3Client.connect(), but the following error appears
    > when the connect() is invoked in 6.1. Any idea?
    >
    > > vm.t3.T3JVMConnection@53e51' because of: 'Server received a message over an unin
    > itialized connection: 'JVMMessage from: 'null' to: '1577296987682531743S:162.70.
    > 250.94:[7001,7001,7002,7002,7001,7002,-1]:ccDomain:scott' cmd: 'CMD_REQUEST',
    > QO
    > S: '101', responseId: '1', invokableId: '1', flags: 'JVMIDs Not Sent, TX Context
    > Not Sent', abbrev offset: '91'''>
    > <[WebAppServletContext(6748107,cc,/
    > cc)] Servlet failed with Exception
    > java.rmi.UnexpectedException: Marshalling: ; nested exception is:
    > java.rmi.ConnectException: PeerGone; nested exception is:
    > weblogic.rjvm.PeerGoneException: Config message not received after 60
    > se
    > conds
    > java.rmi.ConnectException: PeerGone; nested exception is:
    > weblogic.rjvm.PeerGoneException: Config message not received after 60
    > se
    > conds
    > weblogic.rjvm.PeerGoneException: Config message not received after 60 seconds
    > at weblogic.rjvm.RJVMImpl$ConfigTimeoutChecker.trigge r(RJVMImpl.java:108
    > 0)
    > at weblogic.time.common.internal.ScheduledTrigger.exe cuteLocally(Schedul
    > edTrigger.java:238)
    > at weblogic.time.common.internal.ScheduledTrigger.exe cute(ScheduledTrigg
    > er.java:229)
    > at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:137)
    > at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:120)
    >



  3. Re: T3Client.connect() problem in weblogic 6.1


    Hi Tom,

    I am wondering what the work-arounds are in this situation?

    Thanks



    Tom Barnes
    wrote:
    >The T3Client API has nothing to do with JMS.
    >
    >Anyway, I think parts (or all?) of it have been deprecated
    >(but perhaps not in 6.1). For more information you might try:
    >weblogic.developer.interest.general
    >
    >Note that interoperability is not supported
    >between 6.1 and earlier versions. (A 6.1
    >client can't directly invoke something
    >running on a 5.1 server - but there are some
    >work-arounds.)
    >
    >
    >"Scott Shen" chih-ping.shen wrote:
    >
    >> I am having problem in T3Client.connect() in Weblogic 6.1. Our application

    >runs
    >> well in Weblogic 5.1 with T3Client.connect(), but the following error

    >appears
    >> when the connect() is invoked in 6.1. Any idea?
    >>
    >>
    >'weblogic.rj
    >> vm.t3.T3JVMConnection@53e51' because of: 'Server received a message

    >over an unin
    >> itialized connection: 'JVMMessage from: 'null' to: '1577296987682531743S:162.70.
    >> 250.94:[7001,7001,7002,7002,7001,7002,-1]:ccDomain:scott' cmd: 'CMD_REQUEST',
    >> QO
    >> S: '101', responseId: '1', invokableId: '1', flags: 'JVMIDs Not Sent,

    >TX Context
    >> Not Sent', abbrev offset: '91'''>
    >> <[WebAppServletContext(6748107,cc,/
    >> cc)] Servlet failed with Exception
    >> java.rmi.UnexpectedException: Marshalling: ; nested exception is:
    >> java.rmi.ConnectException: PeerGone; nested exception is:
    >> weblogic.rjvm.PeerGoneException: Config message not received

    >after 60
    >> se
    >> conds
    >> java.rmi.ConnectException: PeerGone; nested exception is:
    >> weblogic.rjvm.PeerGoneException: Config message not received

    >after 60
    >> se
    >> conds
    >> weblogic.rjvm.PeerGoneException: Config message not received after

    >60 seconds
    >> at weblogic.rjvm.RJVMImpl$ConfigTimeoutChecker.trigge r(RJVMImpl.java:108
    >> 0)
    >> at weblogic.time.common.internal.ScheduledTrigger.exe cuteLocally(Schedul
    >> edTrigger.java:238)
    >> at weblogic.time.common.internal.ScheduledTrigger.exe cute(ScheduledTrigg
    >> er.java:229)
    >> at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:137)
    >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:120)
    >>

    >



  4. Re: T3Client.connect() problem in weblogic 6.1


    Hi Tom,

    I am wondering what the work-arounds are in this situation?

    Thanks



    Tom Barnes
    wrote:
    >The T3Client API has nothing to do with JMS.
    >
    >Anyway, I think parts (or all?) of it have been deprecated
    >(but perhaps not in 6.1). For more information you might try:
    >weblogic.developer.interest.general
    >
    >Note that interoperability is not supported
    >between 6.1 and earlier versions. (A 6.1
    >client can't directly invoke something
    >running on a 5.1 server - but there are some
    >work-arounds.)
    >
    >
    >"Scott Shen" chih-ping.shen wrote:
    >
    >> I am having problem in T3Client.connect() in Weblogic 6.1. Our application

    >runs
    >> well in Weblogic 5.1 with T3Client.connect(), but the following error

    >appears
    >> when the connect() is invoked in 6.1. Any idea?
    >>
    >>
    >'weblogic.rj
    >> vm.t3.T3JVMConnection@53e51' because of: 'Server received a message

    >over an unin
    >> itialized connection: 'JVMMessage from: 'null' to: '1577296987682531743S:162.70.
    >> 250.94:[7001,7001,7002,7002,7001,7002,-1]:ccDomain:scott' cmd: 'CMD_REQUEST',
    >> QO
    >> S: '101', responseId: '1', invokableId: '1', flags: 'JVMIDs Not Sent,

    >TX Context
    >> Not Sent', abbrev offset: '91'''>
    >> <[WebAppServletContext(6748107,cc,/
    >> cc)] Servlet failed with Exception
    >> java.rmi.UnexpectedException: Marshalling: ; nested exception is:
    >> java.rmi.ConnectException: PeerGone; nested exception is:
    >> weblogic.rjvm.PeerGoneException: Config message not received

    >after 60
    >> se
    >> conds
    >> java.rmi.ConnectException: PeerGone; nested exception is:
    >> weblogic.rjvm.PeerGoneException: Config message not received

    >after 60
    >> se
    >> conds
    >> weblogic.rjvm.PeerGoneException: Config message not received after

    >60 seconds
    >> at weblogic.rjvm.RJVMImpl$ConfigTimeoutChecker.trigge r(RJVMImpl.java:108
    >> 0)
    >> at weblogic.time.common.internal.ScheduledTrigger.exe cuteLocally(Schedul
    >> edTrigger.java:238)
    >> at weblogic.time.common.internal.ScheduledTrigger.exe cute(ScheduledTrigg
    >> er.java:229)
    >> at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:137)
    >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:120)
    >>

    >



  5. Re: T3Client.connect() problem in weblogic 6.1

    I don't know, and this is not JMS related. Try customer
    support or, if you haven't already, try the "general"
    newsgroup instead.

    Scott Shen wrote:
    > Hi Tom,
    >
    > I am wondering what the work-arounds are in this situation?
    >
    > Thanks
    >
    >
    >
    > Tom Barnes
    > wrote:
    >
    >>The T3Client API has nothing to do with JMS.
    >>
    >>Anyway, I think parts (or all?) of it have been deprecated
    >>(but perhaps not in 6.1). For more information you might try:
    >>weblogic.developer.interest.general
    >>
    >>Note that interoperability is not supported
    >>between 6.1 and earlier versions. (A 6.1
    >>client can't directly invoke something
    >>running on a 5.1 server - but there are some
    >>work-arounds.)
    >>
    >>
    >>"Scott Shen" chih-ping.shen wrote:
    >>
    >>
    >>>I am having problem in T3Client.connect() in Weblogic 6.1. Our application

    >>
    >>runs
    >>
    >>>well in Weblogic 5.1 with T3Client.connect(), but the following error

    >>
    >>appears
    >>
    >>>when the connect() is invoked in 6.1. Any idea?
    >>>
    >>>
    >>
    >>'weblogic.rj
    >>
    >>>vm.t3.T3JVMConnection@53e51' because of: 'Server received a message

    >>
    >>over an unin
    >>
    >>>itialized connection: 'JVMMessage from: 'null' to: '1577296987682531743S:162.70.
    >>>250.94:[7001,7001,7002,7002,7001,7002,-1]:ccDomain:scott' cmd: 'CMD_REQUEST',
    >>>QO
    >>>S: '101', responseId: '1', invokableId: '1', flags: 'JVMIDs Not Sent,

    >>
    >>TX Context
    >>
    >>> Not Sent', abbrev offset: '91'''>
    >>> <[WebAppServletContext(6748107,cc,/
    >>>cc)] Servlet failed with Exception
    >>>java.rmi.UnexpectedException: Marshalling: ; nested exception is:
    >>> java.rmi.ConnectException: PeerGone; nested exception is:
    >>> weblogic.rjvm.PeerGoneException: Config message not received

    >>
    >>after 60
    >>
    >>>se
    >>>conds
    >>>java.rmi.ConnectException: PeerGone; nested exception is:
    >>> weblogic.rjvm.PeerGoneException: Config message not received

    >>
    >>after 60
    >>
    >>>se
    >>>conds
    >>>weblogic.rjvm.PeerGoneException: Config message not received after

    >>
    >>60 seconds
    >>
    >>> at weblogic.rjvm.RJVMImpl$ConfigTimeoutChecker.trigge r(RJVMImpl.java:108
    >>>0)
    >>> at weblogic.time.common.internal.ScheduledTrigger.exe cuteLocally(Schedul
    >>>edTrigger.java:238)
    >>> at weblogic.time.common.internal.ScheduledTrigger.exe cute(ScheduledTrigg
    >>>er.java:229)
    >>> at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:137)
    >>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:120)
    >>>

    >>

    >