Failed to unmarshal class weblogic.jms.dispatcher.Response

          Hi,
          we are using WL6.1 SP2 on solaris as a standalone JMS server and we another WL61
          SP2 on solaris as application server. Our Application server connects to JMS server
          and does a Qbrowse to select some info from the Queue. We had a problem once in
          using the Qbrowser and below is the stacktrace. If anyone has any idea of this,please
          shed some light.
          Thanks
          Krish.
          weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          [java.rmi.UnmarshalException: failed to unmarshal class weblogic.jms.dispatcher.Response;
          nested exception is:                     
                  java.io.StreamCorruptedException: Type code out of range, is -2]
          java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
          Start server side stack trace:
          java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
          at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:186)
          at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.ja
          va:300)
          at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:906)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:940)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2263)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
          at weblogic.rmi.internal.StubInfo.readObject(StubInfo.java:73)
          at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.rmi.internal.StubInfo.readObject(StubInfo.java:73)
               at java.lang.reflect.Method.invoke(Native Method)
               at java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2214)
               at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
               at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
               at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
               at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:110)
               at weblogic.jms.dispatcher.DispatcherWrapper.readExternal(DispatcherWrapper.java:126)
               at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:99)
               at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
               at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown Source)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
               at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
               at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
               End server side stack trace
          

complete printstack trace
Assembler 7 unreachable -- failed to unmarshal class com.adobe.idp.Context; nested exception is:
java.io.InvalidObjectException: inauthentic principal assertion
java.rmi.UnmarshalException: failed to unmarshal class com.adobe.idp.Context; nested exception is:
java.io.InvalidObjectException: inauthentic principal assertion
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:293)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
at com.adobe.service.pdfm.Assembler7_2a0g3c_EOImpl_814_WLStub.login(Unknown Source)
at adobepdfassemblertest.AdobePDFAssembler.main(AdobePDFAssembler.java:102)
Caused by: java.io.InvalidObjectException: inauthentic principal assertion
at com.adobe.idp.Context.getValidatedAuthResultFromAssertion(Context.java:297)
at com.adobe.idp.Context.readResolve(Context.java:252)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:925)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1655)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.jav a:120)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:120)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:164)
... 4 more

Similar Messages

  • Weblogic MQ  :java.lang.ClassNotFoundException: Failed to load class weblog

    Hi
    I am getting this error in Log
    JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.UnmarshalException: Problem finding error class; nested exception is:
         java.lang.ClassNotFoundException: Failed to load class weblogic.messaging.kernel.KernelException
    Please help me to find out possible root cause for this errorstack.
    Thanks
    Edited by: 906163 on Jan 5, 2012 5:29 AM

    Hi,
    This is not the forum for WebLogic Messaging, i.e., JMS. This is the forum for Oracle MessageQ, and pure standalone messaging product similar to IBM MQ Series.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • JMSClientExceptions:055053 -WebLogic10 Cluster - Remote WebLogic JMS - Help

    All,
    We are using a foreign JMS provider from WeLogic 10 cluster to connect to the Remote WebLogic JMS Server. We are getting below error while posting the data to the queue. Any help , ideas as to why this is occuring please?
    / Error
    Error during connection/session creation:weblogic.jms.common.JMSException: [*JMSClientExceptions:055053*]Error creating connection to the server: java.rmi.UnmarshalException: failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is: java.io.StreamCorruptedException|portal
    Thanks a lot for your help.

    All
    The issue popped up gain. Below is the full stack trace. I confirmed that we are using the t3 URL to connect to remote JMS server (which is Weblogic 10 /JMS). Appreciate any insights help to resolve this issue.
    // Stack Trace
    weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.UnmarshalException:
    failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is:
    java.io.StreamCorruptedException
    at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:253)
    at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
    at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
    at com.juniper.core.mdb.MessageSender.initSession(MessageSender.java:79)
    at com.juniper.core.mdb.MessageSender.<init>(MessageSender.java:64)
    at com.juniper.core.mdb.MDBHelper.processMessage(MDBHelper.java:98)
    at com.juniper.core.mdb.BaseMDB.onMessage(BaseMDB.java:35)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:3964)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is:
    java.io.StreamCorruptedException
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:229)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
    at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreate(Unknown Source)
    at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:244)
    ... 15 more
    Caused by: java.io.StreamCorruptedException
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
    at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
    at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
    at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
    at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:227)
    ... 19 more
    Thanks
    Edited by: user3285437 on May 4, 2009 9:26 AM

  • Java.rmi.UnmarshalException: Failed to load class com.msl.security.provider

    Hi ,
    I have the following error while i am stopping a Weblogic instance. Did anyone face a similar issue, please let me know. I see a classnotfound error , but not sure what is that jar file. Is it a application jar or a weblogic one?
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    log4j: Trying to find [resources/comdev/default-log4j.properties] using context classloader java.net.URLClassLoader@183f74d.
    log4j: Using URL [jar:file:/teamrule/10.2/modules/com.bea.cie.comdev_5.3.0.0.jar!/resources/comdev/default-log4j.properties] for automatic log4j configuration.
    log4j: Reading configuration from URL jar:file:/teamrule/10.2/modules/com.bea.cie.comdev_5.3.0.0.jar!/resources/comdev/default-log4j.properties
    log4j: Hierarchy threshold set to [ALL].
    log4j: Parsing for [root] with value=[INFO, NA].
    log4j: Level token is [INFO].
    log4j: Category root set to INFO
    log4j: Parsing appender named "NA".
    log4j: Parsed "NA" options.
    log4j: Finished configuring.
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Connecting to t3://localhost:7009 with userid weblogic ...
    This Exception occurred at Sun Apr 10 14:17:03 UTC 2011.
    javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested excep
    tion is:
    java.lang.ClassNotFoundException: Failed to load class com.msl.security.providers.SessionPrincipal]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:673)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:466)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
    ... 48 more
    Problem invoking WLST - Traceback (innermost last):
    File "/web/10.2/user_projects/domains/dom/shutdown.py", line 1, in ?
    File "<iostream>", line 22, in connect
    WLSTException: 'Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7009 Use dumpStac
    k() to view the full stacktrace'
    Thanks a lot for your time.
    Manish

    Hi Manish,
    It seems that you are using a custom security provider and the weblogic server is not able to find the class / jar file that contains the class.
    java.lang.ClassNotFoundException: Failed to load class com.msl.security.providers.SessionPrincipal]
    Make sure you have all the required jar files in the server classpath.
    You can use the JarScan utility to find the jar that contains the class.
    Refer the below link regarding the jarScan.
    http://weblogic-wonders.com/weblogic/2011/01/26/finding-jar-files-using-jarscan/
    Regards,
    Anandraj
    http://weblogic-wonders.com

  • Java.rmi.UnmarshalException Failed to load class com.msl.security.providers

    Hi ,
    I have the following error while i am stopping a Weblogic instance. Did anyone face a similar issue, please let me know. I see a classnotfound error , but not sure what is that jar file. Is it a application jar or a weblogic one?
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    log4j: Trying to find [resources/comdev/default-log4j.properties] using context classloader java.net.URLClassLoader@183f74d.
    log4j: Using URL [jar:file:/teamrule/10.2/modules/com.bea.cie.comdev_5.3.0.0.jar!/resources/comdev/default-log4j.properties] for automatic log4j configuration.
    log4j: Reading configuration from URL jar:file:/teamrule/10.2/modules/com.bea.cie.comdev_5.3.0.0.jar!/resources/comdev/default-log4j.properties
    log4j: Hierarchy threshold set to [ALL].
    log4j: Parsing for [root] with value=[INFO, NA].
    log4j: Level token is [INFO].
    log4j: Category root set to INFO
    log4j: Parsing appender named "NA".
    log4j: Parsed "NA" options.
    log4j: Finished configuring.
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Connecting to t3://localhost:7009 with userid weblogic ...
    This Exception occurred at Sun Apr 10 14:17:03 UTC 2011.
    javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested excep
    tion is:
            java.lang.ClassNotFoundException: Failed to load class com.msl.security.providers.SessionPrincipal]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:673)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:466)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
    ... 48 more
    Problem invoking WLST - Traceback (innermost last):
    File "/web/10.2/user_projects/domains/dom/shutdown.py", line 1, in ?
    File "<iostream>", line 22, in connect
    WLSTException: 'Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7009 Use dumpStac
    k() to view the full stacktrace'
    Thanks a lot for your time.
    Manish

    Hi Manish,
    It seems that you are using a custom security provider and the weblogic server is not able to find the class / jar file that contains the class.
    java.lang.ClassNotFoundException: Failed to load class com.msl.security.providers.SessionPrincipal]
    Make sure you have all the required jar files in the server classpath.
    You can use the JarScan utility to find the jar that contains the class.
    Refer the below link regarding the jarScan.
    http://weblogic-wonders.com/weblogic/2011/01/26/finding-jar-files-using-jarscan/
    Regards,
    Anandraj
    http://weblogic-wonders.com

  • Problem in Interacting with Weblogic JMS through Informatica ETL server

    Hi All,
    We are trying to configure Informatica PowerCenter server to interact with JMS queues created on Weblogic 11gR1 server. We have copied the necessary
    jar file - wlfullclient.jar to the classpath of the Informatica server.
    Now when i try to read contents of a JMS queue created on Weblogic server through Informatica, i get this error:-
    Failed to get the Queue Connection Factory [weblogic.jms.common.DestinationImpl]. Reason: Failed to look up object [While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms'Exception Stack: javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms']; remaining name 'common/DestinationImpl'
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:464)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:272)
         at weblogic.jndi.internal.ServerNamingNode_1211_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:418)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at com.informatica.powerconnect.jms.server.common.JNDIConnection.getJNDIObject(JNDIConnection.java:84)
         at com.informatica.powerconnect.jms.server.common.PlginJMSConnection$PlginJMSQueueConnection.createConnection(PlginJMSConnection.java:363)
         at com.informatica.powerconnect.jms.server.common.PlginJMSConnection.<init>(PlginJMSConnection.java:90)
         at com.informatica.powerconnect.jms.server.common.PlginJMSConnection$PlginJMSQueueConnection.<init>(PlginJMSConnection.java:352)
         at com.informatica.powerconnect.jms.server.common.PlginJMSConnection.create(PlginJMSConnection.java:115)
         at com.informatica.powerconnect.jms.server.reader.JMSReaderSQDriver.createPartitionDriver(JMSReaderSQDriver.java:557)
    Caused by: javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'
    I have checked that this class file exists in the above said location :- "weblogic/jms/common/DestinationImpl.class" within the wlfullclient.jar but still the
    code is not able to access the class. Similar error came initially while doing JNDI connection using "weblogic.jndi.WLInitialContextFactory" class but it vanished,
    when i explicitly named the jar file on classpth, instead of just the folder containing the jar file.
    To all the users/experts/moderators of Weblogic - Could you please help me understand why Weblogic is not able to look up subcontext 'common'
    for the class - "weblogic.jms.common.DestinationImpl" ??
    Thanks & Regards
    Raj
    Edited by: user8931188 on May 17, 2012 7:39 AM

    You are experiencing a NameNotFoundException, not ClassNotFoundException so it seems there is something wrong about the client connection code or WebLogic config.
    Can you share your client connection connection config/code?

  • JMS error: weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub

    hi weblogic users,
    i have a problem in sending jms messages
    across two different weblogic host/domain.
    the configuration is:
    jms client:
    -JAX-WS webservice web app
    -deployed in WebLogic Server Version: 10.3.1.0
    -host: 192.168.30.133:7011
    -domain: ChSoaAdminServer1
    -can access server's console: http://192.168.1.22:6001/console
    server:
    -jms server, jms module, cf, queue configured
    with subdeployment targeted to the jmsserver
    -deployed in WebLogic Server Version: 10.3.2.0
    -host: 192.168.1.22:6001
    -domain: soa_domain
    -cannot access client's console: http://192.168.30.133:7011/console
    i use standard lookup method in my java client code:
    String settingJmsServer="t3://192.168.1.22:6001";
    String settingCF="jms/adminduk/cf";
    String settingQueue="jms/adminduk/queue/central";
    env=new Hashtable();
    env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
    env.put(Context.PROVIDER_URL, settingJmsServer);
    ctx = new InitialContext( env );
    System.out.println("-- Destination");
    ds = (Destination) ctx.lookup(settingQueue);
    System.out.println("-- ConnectionFactory");
    cf = (ConnectionFactory) ctx.lookup(settingCF);
    but it's getting exception
    when looking up the connection factory (look at the bottom of my post):
    ok now, how to solve this problem?
    -i tried to change the server to another host with WL 10.3.1.0 installed (so
    it's the same version with the client) and its ok (receiving messages)
    -i tried to deploy the WS client to the same host as the jms (WL 10.3.2.0), so no
    remote lookup needed (java lookup code adjusted), it's ok
    -based on the stack trace:
    "Could not find dynamically generated class:
    'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub
    (class not found) ..."
    -does it mean do i've to use the same version of WL installed in the client side ??
    -is WL 10.3.2.0 compatible with WL 10.3.1.0 ?
    -is it possible to use a different version of weblogic (in the client/server)
    in using the jms feature ?
    -do the jms server must have access to client's port (7011) for it to work ?
    thanks,
    any info/hints/helps will be appreciated :)
    ---------- start error ---------
    ####<Mar 23, 2010 4:24:51 PM ICT> <Error> <com.sun.xml.ws.server.sei.EndpointMethodHandler>
    <coolpie> <ChSoaAdminServer1> <[ACTIVE] ExecuteThread: '1' for queue:
    'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1269336291921> <BEA-000000>
    <***** ASSERTION FAILED *****[ Could not find dynamically generated class:
    'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub' ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not find dynamically
    generated class: 'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub' ]
         at weblogic.utils.classfile.utils.CodeGenerator.generateClass(CodeGenerator.java:78)
         at weblogic.rmi.internal.StubGenerator.hotCodeGenClass(StubGenerator.java:775)
         at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:759)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:779)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
         at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:213)
         at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:207)
         at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.jms.client.JMSConnectionFactory.readExternal(JMSConnectionFactory.java:382)
         at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1031_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:400)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at
    weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:194)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at siak.model.MessageManager.init(MessageManager.java:101)
         at siak.ws.SiakWS.sendEvent(SiakWS.java:37)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:101)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:83)
         at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:152)
         at
    com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:264)
         at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
         at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
         at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
         at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
         at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
         at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:249)
         at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:453)
         at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:250)
         at
    com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
         at
    weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:298)
         at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:211)
         at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:297)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:87)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java
    :227)
         at
    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletConte
    xt.java:3588)
         at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at
    weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
         at
    weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.ClassNotFoundException: weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub
         at
    weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
         at
    weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
         at
    weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:55)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
         at
    weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
         at
    weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:36)
         at
    weblogic.utils.classloaders.FilteringClassLoader.findClass(FilteringClassLoader.java:100)
         at
    weblogic.wsee.util.JAXWSClassLoaderFactory$1.findClass(JAXWSClassLoaderFactory.java:45)
         at
    weblogic.utils.classloaders.FilteringClassLoader.loadClass(FilteringClassLoader.java:85)
         at
    weblogic.utils.classloaders.FilteringClassLoader.loadClass(FilteringClassLoader.java:80)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:247)
         at
    weblogic.utils.classloaders.GenericClassLoader.defineCodeGenClass(GenericClassLoader.java:516
         at weblogic.utils.classfile.utils.CodeGenerator.generateClass(CodeGenerator.java:73)
         at weblogic.rmi.internal.StubGenerator.hotCodeGenClass(StubGenerator.java:775)
         at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:759)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:779)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
         at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:213)
         at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:207)
         at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.jms.client.JMSConnectionFactory.readExternal(JMSConnectionFactory.java:382)
         at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1031_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:400)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at
    weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:194)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at siak.model.MessageManager.init(MessageManager.java:101)
         at siak.ws.SiakWS.sendEvent(SiakWS.java:37)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:101)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:83)
         at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:152)
         at
    com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:264)
         at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
         at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
         at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
         at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
         at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
         at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:249)
         at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:453)
         at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:250)
         at
    com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
         at
    weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:298)
         at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:211)
         at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:297)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:87)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java
    :227)
         at
    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletConte
    xt.java:3588)
         at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at
    weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
         at
    weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    ---------- end error ---------

    1 - A class-not-found is an odd exception to get on a server. Did you perhaps try to add client-only jars to the server classpath? The server classpath is already setup properly to act as a client.
    2 - Its usually not a good practice to create contexts in client code (instead of simply using the Servlet context in your case), or to hard code URLs, dests, and CF references into the code. It works, but can be hard to maintain and inefficient.
    3 - See:
    [ Enhanced Support for Using WebLogic JMS with EJBs and Servlets |  http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/j2ee.htm#g1329180 ]
    and
    [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/interop.htm#JMSPG553 ]
    and the cross-domain advice in
    [ Integration and Multi-Domain Best Practices |
    http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACFBCHB ]
    Hope this helps,
    Tom

  • WebLogic JMS client frozen during JMS connection stopping (race condition)

    Hello,
    Our application is using the WebLogic 10.3.1 JMS client generated with wlfullclient5.jar.
    We have sometimes a race condition when the WebLogic server is stopped.
    In about 10% of the cases where the server is stopped, the client application is frozen in the "stop" call (see stack trace #1 below).
    Our understanding is that each JMS API call by the application is translated by a request-response message on the TCP connection to the JMS server. The JMS library sends the request and then wait for the response. From our observations, it looks like there is no local timeout in the JMS library. This means that if the WebLogic server is being stopped just after receiving the "stop" request, it will never send the "stop" response, which means that the application will be stuck forever.
    The same problem also occurs when using JMS bridges between 2 JMS servers (see stack trace #2 below).
    How can we activate a local timeout for all JNDI/JMS calls ?
    Regards,
    metatech
    "AppThread" prio=3 tid=0x0000000100117800 nid=0x2 in Object.wait() [0xffffffff7befe000]
    java.lang.Thread.State: WAITING (on object monitor)
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:485)
    at weblogic.messaging.dispatcher.DispatcherWrapperState.triggerPeerGoneAndWait(DispatcherWrapperState.java:607)
    - locked <0xffffffff7509aee8> (a weblogic.messaging.dispatcher.DispatcherWrapperState)
    at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:349)
    at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
    at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:252)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
    at weblogic.jms.client.JMSConnection.stop(JMSConnection.java:758)
    - locked <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
    at weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
    at AppSession.closeJMSSession(ConnectorSession.java:499)
    "[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.jms.client.JMSXASession@1d363e4 WAITING
    java.lang.Object.wait(Native Method)
    java.lang.Object.wait(Object.java:485)
    weblogic.jms.client.JMSSession.waitForState(JMSSession.java:4778)
    weblogic.jms.client.JMSSession.stop(JMSSession.java:1310)
    weblogic.jms.client.JMSConnection.stop(JMSConnection.java:773)
    weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
    weblogic.jms.adapter.JMSBaseConnection.closeInternal(JMSBaseConnection.java:570)
    weblogic.jms.adapter.JMSBaseConnection.access$000(JMSBaseConnection.java:85)
    weblogic.jms.adapter.JMSBaseConnection$2.run(JMSBaseConnection.java:552)

    Hi Tom,
    Thanks for looking at the issue.
    I tried to post the full thread dump as an attachment, but it is not allowed by the forum, so you find it hereunder.
    Regards,
    metatech
    =================
    2010-05-28 12:33:19
    Full thread dump Java HotSpot(TM) 64-Bit Server VM (14.2-b01 mixed mode):
    "Attach Listener" daemon prio=3 tid=0x0000000100c5b800 nid=0x24 waiting on condition [0x0000000000000000]
    java.lang.Thread.State: RUNNABLE
    "ExecuteThread: '0' for queue: 'JmsAsyncQueue'" daemon prio=3 tid=0x0000000100759800 nid=0x23 in Object.wait() [0xffffffff643ff000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:485)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
         - locked <0xffffffff6f4ed828> (a weblogic.kernel.ServerExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
    "Timer-0" daemon prio=3 tid=0x000000010078c800 nid=0x21 in Object.wait() [0xffffffff647ff000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         - waiting on <0xffffffff6f4ee2c0> (a java.util.TaskQueue)
         at java.lang.Object.wait(Object.java:485)
         at java.util.TimerThread.mainLoop(Timer.java:483)
         - locked <0xffffffff6f4ee2c0> (a java.util.TaskQueue)
         at java.util.TimerThread.run(Timer.java:462)
    "weblogic.timers.TimerThread" daemon prio=3 tid=0x00000001008e0000 nid=0x20 in Object.wait() [0xffffffff649ff000]
    java.lang.Thread.State: TIMED_WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
         - locked <0xffffffff6f4e75d0> (a weblogic.timers.internal.TimerThread)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=3 tid=0x0000000100709000 nid=0x1e waiting for monitor entry [0xffffffff65afe000]
    java.lang.Thread.State: BLOCKED (on object monitor)
         at weblogic.jms.client.JMSConnection.stateChangeListener(JMSConnection.java:1413)
         - waiting to lock <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:682)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=3 tid=0x000000010055c800 nid=0x1d in Object.wait() [0xffffffff65cff000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:485)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
         - locked <0xffffffff6f427a80> (a weblogic.kernel.ServerExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=3 tid=0x000000010055c000 nid=0x1c in Object.wait() [0xffffffff65eff000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:485)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
         - locked <0xffffffff6f427da0> (a weblogic.kernel.ServerExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=3 tid=0x00000001006fa800 nid=0x1b in Object.wait() [0xffffffff660ff000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:485)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
         - locked <0xffffffff6f4280c0> (a weblogic.kernel.ServerExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
    "StateHolder" daemon prio=3 tid=0x0000000100584800 nid=0x1a waiting on condition [0xffffffff66aff000]
    java.lang.Thread.State: TIMED_WAITING (sleeping)
         at java.lang.Thread.sleep(Native Method)
         at StateHolder.run(StateHolder.java:80)
         at java.lang.Thread.run(Thread.java:619)
    "Thread-1" daemon prio=3 tid=0x0000000100554000 nid=0x18 waiting on condition [0xffffffff66cff000]
    java.lang.Thread.State: TIMED_WAITING (sleeping)
         at java.lang.Thread.sleep(Native Method)
         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:104)
    "Low Memory Detector" daemon prio=3 tid=0x00000001003d3800 nid=0x16 runnable [0x0000000000000000]
    java.lang.Thread.State: RUNNABLE
    "CompilerThread1" daemon prio=3 tid=0x00000001003cf000 nid=0x15 waiting on condition [0x0000000000000000]
    java.lang.Thread.State: RUNNABLE
    "CompilerThread0" daemon prio=3 tid=0x00000001003cd800 nid=0x14 waiting on condition [0x0000000000000000]
    java.lang.Thread.State: RUNNABLE
    "Signal Dispatcher" daemon prio=3 tid=0x00000001003cb800 nid=0x13 runnable [0x0000000000000000]
    java.lang.Thread.State: RUNNABLE
    "Finalizer" daemon prio=3 tid=0x00000001003a4800 nid=0x12 in Object.wait() [0xffffffff680ff000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
         - locked <0xffffffff6f4c7670> (a java.lang.ref.ReferenceQueue$Lock)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
         at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
    "Reference Handler" daemon prio=3 tid=0x00000001003a3000 nid=0x11 in Object.wait() [0xffffffff682ff000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:485)
         at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
         - locked <0xffffffff6f401370> (a java.lang.ref.Reference$Lock)
    "Worker" prio=3 tid=0x0000000100117800 nid=0x2 in Object.wait() [0xffffffff7befe000]
    java.lang.Thread.State: WAITING (on object monitor)
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:485)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.triggerPeerGoneAndWait(DispatcherWrapperState.java:607)
         - locked <0xffffffff7509aee8> (a weblogic.messaging.dispatcher.DispatcherWrapperState)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:349)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:252)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         at weblogic.jms.client.JMSConnection.stop(JMSConnection.java:758)
         - locked <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
         at weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
         at ConnectorSession.closeJMSSession(ConnectorSession.java:499)
         at ConnectorSession.receiveRequest(ConnectorSession.java:617)
         at ConnectorSession.processRequest(ConnectorSession.java:341)
         at Worker.mainApplication(Worker.java:127)
         at Worker.mainMethod(Worker.java:298)
         at Worker.main(Worker.java:163)
    "VM Thread" prio=3 tid=0x000000010039c800 nid=0x10 runnable
    "GC task thread#0 (ParallelGC)" prio=3 tid=0x000000010011b000 nid=0x3 runnable
    "GC task thread#1 (ParallelGC)" prio=3 tid=0x0000000100121000 nid=0x4 runnable
    "GC task thread#2 (ParallelGC)" prio=3 tid=0x0000000100122800 nid=0x5 runnable
    "GC task thread#3 (ParallelGC)" prio=3 tid=0x0000000100126000 nid=0x6 runnable
    "GC task thread#4 (ParallelGC)" prio=3 tid=0x0000000100127800 nid=0x7 runnable
    "GC task thread#5 (ParallelGC)" prio=3 tid=0x0000000100129000 nid=0x8 runnable
    "GC task thread#6 (ParallelGC)" prio=3 tid=0x000000010012b000 nid=0x9 runnable
    "GC task thread#7 (ParallelGC)" prio=3 tid=0x000000010012c800 nid=0xa runnable
    "GC task thread#8 (ParallelGC)" prio=3 tid=0x000000010012e000 nid=0xb runnable
    "GC task thread#9 (ParallelGC)" prio=3 tid=0x000000010012f800 nid=0xc runnable
    "GC task thread#10 (ParallelGC)" prio=3 tid=0x0000000100131800 nid=0xd runnable
    "GC task thread#11 (ParallelGC)" prio=3 tid=0x0000000100133000 nid=0xe runnable
    "GC task thread#12 (ParallelGC)" prio=3 tid=0x0000000100134800 nid=0xf runnable
    "VM Periodic Task Thread" prio=3 tid=0x00000001003d5800 nid=0x17 waiting on condition
    JNI global references: 818

  • Weblogic.messaging.dispatcher.DispatcherException!!??

    Hi,
    I have the following piece of code extract which creates a JMS Session. I am looking up a queue from a WLS1032 to a WLS1033 (SOA Suite 11g) and publish messages to it.
    if (remoteCtx == null || remoteJmsConnection == null || remoteQueue == null) {
         setupRemoteJMSResources();
    session = remoteJmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
    sender = session.createProducer(remoteQueue);
    private void setupRemoteJMSResources() throws NamingException, JMSException {
              Hashtable<String, String> env = new Hashtable<String, String>();
              env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
              env.put(Context.PROVIDER_URL, soaProviderUrl);
              env.put(Context.SECURITY_PRINCIPAL, username);
              env.put(Context.SECURITY_CREDENTIALS, password);
              remoteCtx = new InitialContext(env);
              QueueConnectionFactory connectionFactory = (QueueConnectionFactory) remoteCtx.lookup(jmsRemoteCFName);
              remoteJmsConnection = connectionFactory.createQueueConnection();
              remoteQueue = (Queue) remoteCtx.lookup(remoteQueueName);
    It has been working fine the last month but yesterday started to throw the following exception at the createSession() line.
    I cannot find the cause of this exception and I would like to prevent it in the future. It is running on a WLS1032 in a SLSB.
    Could anybody provide a hint of what could have caused this? Start/Stop of the application resolved the problem but I would like to further investigate it.
    weblogic.messaging.dispatcher.DispatcherException: weblogic.messaging.dispatcher.DispatcherException: java.lang.Exception: Connection not found     at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:116)     at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)     at weblogic.jms.client.JMSConnection.setupJMSSession(JMSConnection.java:520)     at weblogic.jms.client.JMSConnection.createSessionInternal(JMSConnection.java:488)     at weblogic.jms.client.JMSConnection.createSession(JMSConnection.java:474)     at weblogic.jms.client.WLConnectionImpl.createSession(WLConnectionImpl.java:553)     at
    Thank you in advance,
    Petros

    Check the soa_prod_a1:soa_a2 logs during the timestamp Oct 21, 2014 5:55:54 PM  issue occured.
    The below error message tells us the remote JVM is down and inaccessible.
    java.rmi.ConnectException: This RJVM has already been shutdown
    Check if the below port numbers are listening on the below ipaddresses
    172.28.164.137: 21801,
    172.28.164.139: 21811:
    Thanks,
    Vijaya

  • Unable to resolve 'weblogic.messaging.dispatcher.S:null'

    We have a WLS 10.3 cluster with 1 admin server and 2 managed servers. Each managed server hosts JMS queues so we have a distributed queue environment. Applications periodically report an issue that prevents messages from being dropped onto the queues. The frequency of the issue is weekly and sometimes multiple times during the week. We have found that un-targeting and re-targeting the JMS Servers seems to resolve the problem (at least in the short term). The message producer applications are using the weblogic.jar and an xa connection factory. I've included the stack trace below. I'm hoping that someone can help uncover the root cause of the issue.
    Stack Trace:
    Caused by: weblogic.jms.common.JMSException: No failover destination.
    at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
    at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
    at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
    at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
    at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
    at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
    at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
    at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)
    at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:574)
    at org.springframework.jms.core.JmsTemplate$4.doInJms(JmsTemplate.java:551)
    at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
    ... 8 more
    Caused by: weblogic.jms.common.JMSException: No failover destination.
    at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
    at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
    at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
    at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
    at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
    at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
    at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
    at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
    at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
    at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
    ... 9 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
    ... 14 more

    Hi,
    I would suggest you to go through these 2 links which you give all the details about UDD
    Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
    http://middlewaremagic.com/weblogic/?p=3747
    Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
    http://middlewaremagic.com/weblogic/?page_id=1976
    Tips to solve UDQ issues
    - Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
    - Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
    - All the managed servers are in the same cluster.
    - If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
    - Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
    Hope this helps you.
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

  • Weblogic JMS Client App fails creating queue connection

    Using the example provided from installation: ...\bea\wlserver_10.0\samples\server\examples\src\examples\jms\queue\QueueBrowse.java
    I can successfully connect and display the queue when this test app runs on the local Weblogic Server. When I run the test app on a remote server (not the Weblogic server), I get the following error:
    Exception in thread "main" weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
         java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
         java.lang.NullPointerException
         at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:258)
         at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
         at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
         at com.lodestarcorp.custom.QueueBrowse.init(QueueBrowse.java:53)
         at com.lodestarcorp.custom.QueueBrowse.main(QueueBrowse.java:129)
    Caused by: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
         java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
         java.lang.NullPointerException
         at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:91)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:332)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
         at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreateRequest(Unknown Source)
         at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224)
         ... 4 more
    Caused by: java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
         java.lang.NullPointerException
         at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:118)
         at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:89)
         at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:55)
         at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:41)
         at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:194)
         at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
         at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceSmartStubInfo(RemoteObjectReplacer.java:116)
         at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:102)
         at weblogic.rmi.utils.io.InteropObjectReplacer.replaceObject(InteropObjectReplacer.java:62)
         at weblogic.utils.io.ChunkedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:40)
         at weblogic.utils.io.ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:141)
         at java.io.ObjectOutputStream.writeObject0(Unknown Source)
         at java.io.ObjectOutputStream.writeObject(Unknown Source)
         at weblogic.messaging.dispatcher.DispatcherWrapper.writeExternal(DispatcherWrapper.java:152)
         at weblogic.jms.frontend.FEConnectionCreateRequest.writeExternal(FEConnectionCreateRequest.java:98)
         at java.io.ObjectOutputStream.writeExternalData(Unknown Source)
         at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
         at java.io.ObjectOutputStream.writeObject0(Unknown Source)
         at java.io.ObjectOutputStream.writeObject(Unknown Source)
         at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:614)
         at weblogic.rjvm.MsgAbbrevOutputStream.writeObjectWL(MsgAbbrevOutputStream.java:605)
         at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:38)
         at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:87)
         ... 8 more
    Caused by: java.lang.NullPointerException
         at weblogic.rmi.internal.BasicRuntimeDescriptor.createSkeletonClass(BasicRuntimeDescriptor.java:272)
         at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:158)
         at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:140)
         at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:110)
         ... 30 more
    FYI: I did create the wlfullclient.jar from the installation.
    Could the problem be related to a proxy issue? It's not a DNS problem (I've tested with the IP address).
    Thanks,
    Brian

    I had this very same issue, in a project I was importing directly individual jars:
         <classpathentry kind="lib" path="lib/javax.jms_1.1.1.jar"/>
         <classpathentry kind="lib" path="lib/weblogic.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.identity_1.1.2.1.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager.ja_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.transaction_2.7.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client.ja_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.wls_1.0.0.0_6-1-0-0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.full_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security_1.0.0.0_6-1-0-0.jar"/>
         <classpathentry kind="lib" path="lib/wlclient.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.classloaders_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.management.core_2.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.descriptor_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.logging_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.timers_1.7.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.socket.api_1.2.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.digest_1.0.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.lifecycle_1.4.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.store_1.7.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.common.security.api_1.0.0.0_6-1-0-0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.wrapper_1.4.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.messaging.kernel_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.expressions_1.4.0.0.jar"/>
    and everything was working;
    in another project I was importing the "Weblogic System Libraries" libraries, and I was getting the NullPointerException...
    I have the sensation that there is room for improvement in the way libraries are managed.

  • Failed to lookup connection factory weblogic.jms.XAConnectionFactory

    when i deploy any service with jms protocol (write to queue) using sbconsole i face this error
    "Failed to lookup connection factory weblogic.jms.XAConnectionFactory"
    any suggestion?
    Thanks

    weblogic.jms.XAConnectionFactory is the default XA connection factory class. You wont see this in any JMS modules in Weblogic server. It should be available by default.
    Can you once check the JNDI tree of your servers if this JNDI name exists. (in Weblogic Administration console go to Servers, click on any server and there will be a link for JNDI tree on the server's page)
    Also, try creating a new connection factory in Weblogic console and using that in your service. Although it is highly unlikely that a new connection factory will work since all custom XA connection factories are dependent on the default connection factory class you mentioned.

  • Weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal UsernameToke

    Hello,
    I'm developing an web service client and I have an error when I call the web service :
    *<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<faultcode>wsse:InvalidSecurity</faultcode>*
    *<faultstring>weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken</faultstring>*
    *</env:Fault>*
    The wsdl has the following policy set:
    *<WL5G3N1:Policy WL5G3N2:Id="ws-policy">*
    *<sp:SupportingTokens>*
    *<wsp:Policy>*
    *<sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">*
    *<wsp:Policy>*
    *<sp:HashPassword/>*
    *<sp:WssUsernameToken10/>*
    *</wsp:Policy>*
    *</sp:UsernameToken>*
    *</wsp:Policy>*
    *</sp:SupportingTokens>*
    *</WL5G3N1:Policy>*
    *<wsp:UsingPolicy WL5G3N0:Required="true"/>*
    And the SOAP header of my request is as follows :
    *<S:Header>*
    *<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">*
    *<wsse:Username>user</wsse:Username>*
    *<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">pVK3p4MC0YJ/qGeb/lMGrrNQBwQ=</wsse:Password>*
    *<wsse:Nonce>NjkwMjk2Mzgw</wsse:Nonce>*
    *<wsse:Created>2012-02-22T14:59:10Z</wsse:Created>*
    *</wsse:UsernameToken></wsse:Security>*
    *</S:Header>*
    Do you know what might be the cause of the error?
    Thank you.
    Edited by: 916856 on Feb 24, 2012 8:39 AM
    Edited by: 916856 on Feb 24, 2012 8:40 AM

    Hello,
    I'm developing an web service client and I have an error when I call the web service :
    *<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<faultcode>wsse:InvalidSecurity</faultcode>*
    *<faultstring>weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken</faultstring>*
    *</env:Fault>*
    The wsdl has the following policy set:
    *<WL5G3N1:Policy WL5G3N2:Id="ws-policy">*
    *<sp:SupportingTokens>*
    *<wsp:Policy>*
    *<sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">*
    *<wsp:Policy>*
    *<sp:HashPassword/>*
    *<sp:WssUsernameToken10/>*
    *</wsp:Policy>*
    *</sp:UsernameToken>*
    *</wsp:Policy>*
    *</sp:SupportingTokens>*
    *</WL5G3N1:Policy>*
    *<wsp:UsingPolicy WL5G3N0:Required="true"/>*
    And the SOAP header of my request is as follows :
    *<S:Header>*
    *<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">*
    *<wsse:Username>user</wsse:Username>*
    *<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">pVK3p4MC0YJ/qGeb/lMGrrNQBwQ=</wsse:Password>*
    *<wsse:Nonce>NjkwMjk2Mzgw</wsse:Nonce>*
    *<wsse:Created>2012-02-22T14:59:10Z</wsse:Created>*
    *</wsse:UsernameToken></wsse:Security>*
    *</S:Header>*
    Do you know what might be the cause of the error?
    Thank you.
    Edited by: 916856 on Feb 24, 2012 8:39 AM
    Edited by: 916856 on Feb 24, 2012 8:40 AM

  • Can I turn off weblogic JMS in 5.1

              All,
              Is there a way to turn off JMS in wl51. We are using another 3rd party product
              and would like to optimize the wl51 vm by removing everything from memory that
              we can.
              Regards,
              Todd
              

    <strong response>
              Hi Todd,
              The WL 6.0+ JMS team also has messaging experience.
              We have written multiple queuing products -
              perhaps even some of the same ones you used in the "early 90s". This team
              has many years of experience, plus a dependable company to back them up. We
              have seen competitor products fall-over quite spectacularly in internal testing
              (without much effort). Evaluating scalability, robustness, and features is worth
              a second careful look, and a third -- there are many hidden twisty passages all
              alike in this arena, as you may be aware.
              We aren't even afraid to air our dirty laundry in this very public newsgroup. (Note
              that we know that other vendors track this newsgroup carefully, so now you know, that
              we know, that they know, that we know). :-)
              Note that the vendors you mention don't even support transactions (at least not until
              very recently), so to call them "enterprise" level may be a stretch. (To be fair here,
              Sonic
              is getting there, and we have worked with them directly on this. You can even search
              this newsgroup for some of their posts on the topic.)
              I think we will have to agree to disagree here, but I will of course admit there is
              always
              room for improvement.
              Tom
              P.S. Just to make things clear, I'm a BEA employee.
              </strong response>
              Todd Flora wrote:
              > Tom,
              >
              > Thanks for your reply. I will look at this so maybe I need to do nothing.
              >
              > As far as your BEA Plug goes. We looked at wl6.1 JMS and quite frankly it fell
              > far short of an enterprise solution. Take it from someone that has been working
              > with messaging products since the early 90's BEA's JMS is just mediocre. (Can't
              > spell) I don't know about ver 7.0 haven't looked at it. We are currently using
              > SpiritSoft Wave and what a great product. SonicMQ and Fiorano also had nice products.
              >
              > Regards,
              >
              > Todd
              > Tom Barnes <[email protected]> wrote:
              > >I know very little about WL 5.1 particulars. But, most JVMs do not load
              > >classes into
              > >memory until they are needed. There is usually a JVM option to see what
              > >classes it is
              > >loading. See the white-paper
              > >"Small Footprint Client Options for BEA WebLogic Server" at
              > >http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
              > >(WebLogicThinClient.zip)
              > >for a little info on this option.
              > >
              > >Seriously consider WL JMS version 6 or 7. This has a robust,
              > >scalable, fast JMS written (and maintained) by a team that has had experience
              > >developing
              > >multiple enterprise level queuing products, (biased BEA plug.)
              > >
              > >Tom
              > >
              > >Todd Flora wrote:
              > >
              > >> OK Thanks for your reply.
              > >>
              > >> I have not weblogic.jms entries in the property file but the server
              > >is still listening
              > >> for JMS Messages on port 7001. So I don't believe I have succeeded
              > >in reclaiming
              > >> that memory.
              > >>
              > >> Thx.
              > >>
              > >> Todd
              > >> Michael Young <[email protected]> wrote:
              > >> >Hi.
              > >> >
              > >> >I believe all you need to do is comment out all jms related properties
              > >> >(weblogic.jms.*) in the weblogic.properties file. You may also want
              > >> >to comment
              > >> >out any connection pool used to persist jms messages.
              > >> >
              > >> >HTH,
              > >> >Michael
              > >> >
              > >> >Todd Flora wrote:
              > >> >
              > >> >> All,
              > >> >>
              > >> >> Is there a way to turn off JMS in wl51. We are using another 3rd
              > >party
              > >> >product
              > >> >> and would like to optimize the wl51 vm by removing everything from
              > >> >memory that
              > >> >> we can.
              > >> >>
              > >> >> Regards,
              > >> >> Todd
              > >> >
              > >> >--
              > >> >Michael Young
              > >> >Developer Relations Engineer
              > >> >BEA Support
              > >> >
              > >> >
              > >
              [att1.html]
              

  • Failed to unmarshal interface java.util.Set

    I am trying to get all mbeans using getAllMBeans() method after
    getting MBeanHome successfully. The method fails with the following
    error.
    Any clues ?
    Thanks
    karthik
    >>>>
    weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception -
    with nested exception:
    [java.rmi.UnmarshalException: failed to unmarshal interface
    java.util.Set; nested exception is:
         java.io.InvalidClassException: javax.management.MBeanAttributeInfo;
    local class incompatible: stream classdesc serialVersionUID =
    7043855487133450673, local class serialVersionUID =
    8644704819898565848]
         at weblogic.management.internal.AdminMBeanHomeImpl_WLStub.getAllMBeans(Unknown
    Source)

    I am trying to get all mbeans using getAllMBeans() method after
    getting MBeanHome successfully. The method fails with the following
    error.
    Any clues ?
    Thanks
    karthik
    >>>>
    weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception -
    with nested exception:
    [java.rmi.UnmarshalException: failed to unmarshal interface
    java.util.Set; nested exception is:
         java.io.InvalidClassException: javax.management.MBeanAttributeInfo;
    local class incompatible: stream classdesc serialVersionUID =
    7043855487133450673, local class serialVersionUID =
    8644704819898565848]
         at weblogic.management.internal.AdminMBeanHomeImpl_WLStub.getAllMBeans(Unknown
    Source)

Maybe you are looking for