Error in Applet reading a JMS topic

I have an applet trying to read a JMS topic. It connects fine, but as
          soon as a message is written into the topic (that the applet is
          subscribed to), I get the following error on the server:
          <Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
          response for: '-1'>
          The applet shows the following stacktrace:
          <Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
          rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          oid: '257', implementation:
          'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          generate the Skeleton on the server for:
          weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
               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)
          >
          <Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          oid: '2', implementation:
          'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          generate the Skeleton on the server for:
          weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
               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.Kernel.execute(Kernel.java:235)
               at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
               at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
               at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
               at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
               at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
               at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
               at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
               at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
               at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          <Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          oid: '2', implementation:
          'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          generate the Skeleton on the server for:
          weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
               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.Kernel.execute(Kernel.java:235)
               at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
               at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
               at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
               at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
               at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
               at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
               at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
               at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
               at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          Thanks in advance for suggestions/help.
          Raj

Is it with 7.0 GA or beta?
          Do you know whether the classpath servlet is open or not?
          Can you run this url from a browser and update this issue please.
          http://host:port/bea_wls_internal/classes/weblogic/jms/dispatcher/Dispatcher
          Impl_WLSkel.class
          You should get a downloaded file to be saved. Otherwise your server need to
          open the classpathservlet.
          use -Dweblogic.servlet.ClasspathServlet.disableStrictCheck=true to open the
          classpath servlet.
          Attach the applet code, so that it will help us to nail down the issue.
          Cheers,
          ..maruthi
          "theist" <[email protected]> wrote in message
          news:[email protected]...
          > I have an applet trying to read a JMS topic. It connects fine, but as
          > soon as a message is written into the topic (that the applet is
          > subscribed to), I get the following error on the server:
          >
          > <Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
          > response for: '-1'>
          >
          >
          > The applet shows the following stacktrace:
          >
          > <Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
          > rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
          >
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
          7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          > oid: '257', implementation:
          > 'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
          > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          > generate the Skeleton on the server for:
          > weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
          scriptor.java:296)
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
          tor.java:309)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          > at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          > at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >
          > <Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          > rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          >
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
          7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          > oid: '2', implementation:
          > 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          > generate the Skeleton on the server for:
          > weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
          scriptor.java:296)
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
          tor.java:309)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          > at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          > at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.Kernel.execute(Kernel.java:235)
          > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
          > at
          weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
          a:42)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >
          > <Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          > rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          >
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
          7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          > oid: '2', implementation:
          > 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          > generate the Skeleton on the server for:
          > weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
          scriptor.java:296)
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
          tor.java:309)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          > at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          > at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.Kernel.execute(Kernel.java:235)
          > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
          > at
          weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
          a:42)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >
          >
          >
          > Thanks in advance for suggestions/help.
          > Raj

Similar Messages

Concurrent nodes reading from JMS topic (cluster environment)

Hi.
Need some help on this:
Concurrent nodes reading from JMS topic (cluster environment)
Thanks
Denis

After some thinking, I noted the following:
1 - It's correct that only one node subscribes to a topic at a time. Otherwise, the same message would be processed by the nodes many times.
2 - In order to solve the load balancing problem, I think that the Topic should be changed by a Queue. This way, each BPEL process from the node would poll for a message, and as soon as the message arrives, only one BPEL node gets the message and take if off the Queue.
The legacy JMS provider I mentioned in the post above is actually the Retek Integration Bus (RIB). I'm integrating Retek apps with E-Business Suite.
I'll try to configure the RIB to provide both a Topic (for the existing application consumers) and a Queue (an exclusive channel for BPEL)
Do you guys have already tried to do an integration like this??
Thanks
Denis

How to read JMS Topic in Oracle E-Bussiness suite R12

We have to read JMS Topic in Oracle E-Bussiness suite R12. JMS Topic is created by SOA and name of JNDI and connection factory details are provided by SOA. Please let me know the steps to read the JMS Topic.

Hi,
SOA and Weblogic documentation can be found at (Search for JMS):
Documentation for Oracle SOA Suite
http://www.oracle.com/technology/products/soa/soasuite/collateral/documentation.html
Oracle WebLogic Server Documentation
http://download.oracle.com/docs/cd/E14571_01/wls.htm
Thanks,
Hussein

OSB(11.1.1.4) errors when ServiceProxy configured to AQ JMS Topic(not Q)

Hi,
I have a situation as follows:
AQ JMS Topic --> OSB Proxy Service --> Invoke some business service.
I have configured WLS with AQ Foreign JMS server. I know my WLS/AQ configuration is correct as I can publish to AQ topic from OSB(no bpel) business service. But when I try to get an inbound xml(not soap) messages from AQ and let OSB Proxy Service subscribe to the JMS topic(not queue). I get the following message in WLS console
WLS Console Error message:
<Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-3836792044197546800-63c4ae90.12e4efaf8e2.-7fbf was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
Also the messages does not get picked up from AQ topic and when I look at AQ there is no subscriber created to the JMS topic. I did set the subscriber name, XA etc. in the OSB JMS Transport advanced section.
============================================================================
In the console log I get:
<Feb 22, 2011 4:25:07 PM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda is unable to connect to the JMS destination: jms.etBannerFromRMS. The Error was:
oracle.jms.AQjmsException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
Nested exception: java.sql.SQLException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
>
<Feb 22, 2011 4:25:17 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
<Feb 22, 2011 4:25:17 PM CST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda is unable to connect to the JMS destination or bind to JCA resource adapter: jms.etBannerFromRMS. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Feb 22, 2011 4:25:17 PM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda is unable to connect to the JMS destination: jms.etBannerFromRMS. The Error was:
oracle.jms.AQjmsException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
Nested exception: java.sql.SQLException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
>
<Feb 22, 2011 4:25:27 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
<Feb 22, 2011 4:25:37 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
<Feb 22, 2011 4:25:47 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
Thanks,
Prantor

Are you using an IP address for the AQ datasource host instead of a hostname ?
A search on ora-24047 revealed this thread http://kr.forums.oracle.com/forums/thread.jspa?threadID=431416 which states problem could be with using IP address.

Error encountered while collecting the data from JMS topic bus

Iam encountering a problem while collecting the data from JMS topic bus and pushing the data to BAM.On the DesignStudio window, after I click on “update” button in the plan window to run the plan I get the following exception messages:
IMessageSourceReceiver->messageReceive:
javax.naming.CommunicationException: Connection refused: connect
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
     at
com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at
iteration.enterpriselink.sources.JMSConsumer.start(JMSConsumer.java:85)
     at
iteration.enterpriselink.sources.JMSMessageSourceReceiverImpl.jmsConsumerS
tart(JMSMessageSourceReceiverImpl.java:1001)
     at
iteration.enterpriselink.sources.JMSMessageSourceReceiverImpl.messageRecei
ve(JMSMessageSourceReceiverImpl.java:326)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:426)
     at java.net.Socket.connect(Socket.java:376)
     at java.net.Socket.<init>(Socket.java:291)
     at java.net.Socket.<init>(Socket.java:147)
     at
com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnecti
on.java:682)
     at
oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSoc
ketRmiTransport.java:58)
     at
oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java
:78)
     at
oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTr
ansport.java:68)
     at
com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.ja
va:646)
     at
com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientCon
nection.java:190)
     at
com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.jav
a:174)
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
     ... 5 more
[Oracle BAM Enterprise Link error code: 0x75 -- 0x1, 0x75 -- 0x3A]
Error during Message Receive operation.
[Oracle BAM Enterprise Link error code: 0x75 -- 0x1, 0x75 -- 0x3B]

The error msg says that your BAM server cannot connect to your JMS provider. Make sure your configs are all ok, in EL DesignStudio, BAMArchitect EMSdefinition, etc. You can refer to the samples and technotes and tutorials to understand these details. If you are following the steps in the technote etc. pl verify your oc4j container is running, and oc4j version and 'jndi path' is ok. Give the doc name, pg number and step where you are getting this error.

Error :- while accessing JMS topic messages in Design Studio

Hi,
Am getting this error while clicking update button in Design Studio to populate a dataobject using JMS Topic messages sent by oracle Bpel manager.
IMessageSourceReceiver->messageReceive: javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory. Root exception is java.lang.ClassNotFoundException: oracle.j2ee.rmi.RMIInitialContextFactory
Can you tell me where to find the class and how to use it to resolve the problem?
P.S:-
If you can provide any document how oracle BPEL process manager use JMS topic to send message to Oracle BAM and display in reports.
Thanks in advance
Cheers,
Praveen G
iSOFT R& D Pvt Ltd.
[email protected]

Hi,
We are using BAM 10.1.3 against BPEL 10.1.2 and we cannot get it to work.
We are also getting the error "javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory...." .
Our startup paramters for Enterprise Source “Oracle (AS JMS and OJMS) looks like this:
JMS*".;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jndi.jar;C:\OracleBAM\OC4J\j2ee\home\oc4j.jar;C:\OracleBAM\OC4J\j2ee\home\oc4jclient.jar;C:\OracleBAM\OC4J\j2ee\home\lib\oc4j-internal.jar;C:\OracleBAM\OC4J\j2ee\home\lib\ejb.jar;C:\OracleBAM\OC4J\j2ee\home\lib\servlet.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jta.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax88.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax77.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmxri.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmx_remote_api.jar;C:\OracleBAM\OC4J\j2ee\home\lib\adminclient.jar;C:\OracleBAM\OC4J\j2ee\home\ojspc.jar;C:\OracleBAM\OC4J\j2ee\home\jazn.jar;C:\OracleBAM\OC4J\opmn\lib\optic.jar;C:\OracleBAM\OC4J\rdbms\jlib\aqapi.jar;"".;c:\TIBCO\JMS\clients\java\tibjms.jar;c:\TIBCO\JMS\clients\java\jms.jar;c:\TIBCO\JMS\clients\java\jndi.jar;c:\TIBCO\JMS\clients\java\jta-spec1_0_1.jar;c:\TIBCO\JMS\clients\java\jcert.jar;c:\TIBCO\JMS\clients\java\jnet.jar;c:\TIBCO\JMS\clients\java\jsse.jar;c:\TIBCO\JMS\clients\java\tibcrypt.jar;"".;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;"".;C:\Program Files\SonicSoftware\SonicMQ\lib\sonic_Client.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\gnu-regexp-1.0.6.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jaxp.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\xerces.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\tools.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\providerutil.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\fscontext.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\sslj.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jsafe.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\certj.jar;"".;C:\bea\weblogic700\server\lib\weblogic.jar;"".;C:\eGate\client\classes\stcjms.jar;C:\eGate\client\JRE\1.3\lib\ext\fscontext.jar;C:\eGate\client\JRE\1.3\lib\ext\providerutil.jar;C:\eGate\client\ThirdParty\sun\jms.jar;C:\eGate\client\ThirdParty\sun\jndi.jar;C:\eGate\client\ThirdParty\sun\jta.jar;"".;C:\JNDI-Directory_WebMethods\fscontext.jar;C:\JNDI-Directory_WebMethods\providerutil.jar;C:\JNDI-Directory_WebMethods\javax.jms.jar;C:\Program Files\webMethods6\Broker\lib\BrokerJMS60.jar;C:\Program Files\webMethods6\common\lib\client60.jar;C:\Program Files\webMethods6\Broker\lib\xerces.jar;"
We are trying to get to our oc4j container on our BPEL server. We have the following settings on our created message sourcein BAM architect:
Initial Context Factory: oracle.j2ee.rmi.RMIInitialContextFactory
JNDI Service Provider URL: opmn:ormi://hostname:6003:OC4J_BPEL
TopicConnectionFactory Name: java:comp/resource/ojms_ipl/TopicConnectionFactories/iplerror
Topic Name: java:comp/resource/ojms_ipl/Topics/iplerror
ojms_ipl refers to the datasource on our BPEL server that is defined in application.xml.
Where is the class located?
Best regards

Invoke Error while inserting consumed JMS Topic msg in table thru DBadapter

Hi All,
To brief abt my requirement, I am integrating Peoplesoft HRMS module with Oracle SOA i.e.,
+
1. PS HRMS module will publish a JMS msg into a JMS Topic
2. I will consume the same msg using JMS adapter consume operation in my SOA project
3. The Payload(msg) is coming into RECEIVE activity and thru ASSIGN activity invoking the DB adapter to insert the msg into a table.
4. INVOKE activity is throwing the below error(along with the error, able to see the payload in INVOKE activity )
<part name="summary"> +
<summary>*Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: Mapping Not Found Exception. The mapping [EMPLID] for descriptor [class insert.Employee] could not be found. The input xml record had an element [Employee/EMPLID]. Most likely the wrong xml input variable (not matching the expected xsd) was passed to this invoke. Make sure that the input xml is valid relative to the xsd and that the mapping exists in the Mappings.xml. If an old version of the descriptor without this mapping has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this attribute/mapping. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. *</summary>
</part>
Please, provide some suggestions.
Regards,
Satya

Hi Satya,
Try replacing the Assign activity with a Transform acitivity.
Also please check the schema that comes of the DB adapter is having the similar sort of definition that you are getting in your input.
What I mean is to check for length of fields, type of the fields etc.
Thanks,
Deepak.
Edited by: DeepakDabbiru on Oct 23, 2012 3:29 AM

ORABPEL-12165 error while publishing a 77KB message payload to a JMS topic

Our BPEL process reports the above exception when we tried to publish a 23 line PO to a JMS topic with the default partner link settings (on a dev workstation using the OC4J JMS provider). We do not see the above errror manifest itself on smaller size purchase orders (1-6 line orders). The stack trace from the domain long is shown below:
<2006-04-05 16:28:13,390> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> XMLHelper_setJmsMessageHeadersAndPropertiesFromXML: No headers/properties set because element is null
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsProducer_execute: A resource exception occured while producing message
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
ORABPEL-12165
ERRJMS_PROVIDER_ERR.
Could not produce message due to JMS provider error.
Please examine the log file to determine the problem.
     at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:209)
     at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:114)
     at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:195)
     at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:154)
     at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:458)
     at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:647)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:448)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335)
     at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
Caused by: javax.jms.JMSException: storeMessage(ID:Oc4jJMS.Message.OCS1PC.737371:10a6c2453eb:-8000.352,c0:a7:7:1f:24:2c:0:0:29:0:0:0:0:0:0:0:0:2a:1:a:6c:2b:84:11)
     at com.evermind.server.jms.JMSUtils.makeJMSException(JMSUtils.java:1844)
     at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1860)
     at com.evermind.server.jms.ServerStore.storeMessage(ServerStore.java:757)
     at com.evermind.server.jms.ServerStore.enq(ServerStore.java:157)
     at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:464)
     at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:97)
     at com.evermind.server.jms.JMSProvider.enqMessage(JMSProvider.java:574)
     at com.evermind.server.jms.EvermindSession.send(EvermindSession.java:1099)
     at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:409)
     at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:201)
     at com.evermind.server.jms.EvermindTopicPublisher.publish(EvermindTopicPublisher.java:77)
     at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:195)
     ... 30 more

look into the jms.log - can be found @ $BPEL_HOME/integration\orabpel\system\appserver\oc4j\j2ee\home\log
maybe this gives some more information..
hth clemens

How to configure a error queue for weblogic jms topic

Hi guys.
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration Policy: Redirect
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
Any suggestions for this topic? Can anyone provide some helps or any useful links.
Thanks in advance.
Mingzhuang

Mingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj

Messages in JMS Topic Error destination

Hi,
I have a JMS Topic with an error destination queue configured. Now, In our scenario , there are two subscribers of topic for the same message. Suppose for a message published to topic, subscriber1 is able to processes message successfully but subscriber2 throws errors when processing the same message.
1. Once the redelivery limit is reached and subscriber2 continues to throw exception, Will the message get en queued to Error Destination (in spite of the fact that subscriber 1 has processed the same message successfully) ?
2. For a consumer (e.g MDB) listening to Error destination and consuming error messages, Is it possible to determine which topic subscriber was unable to process the message ?
Please let me know
Regards,
Arif

Here it depends on the state of the message, if the message is visible then the message would be available for consumption, else it is not. In case the subscriber 2 failed to consume the message and the message is still visible then a retry would be made, else the message would not be retried.
In case the message is visible then the message would be move to the error queue based on the configured redelivery attempts.
Additionally, an MDB can find the destination using the getJMSDestination() call. But as per my understanding we will only be able to get the name of the last destination which in this case would be error queue:
http://docs.oracle.com/javaee/1.4/api/javax/jms/Message.html#getJMSDestination%28%29

OSB 11g - poll JMS topic on OAS 10.1.2

Hi everybody,
We are going to create OSB 11g proxy service that will poll JMS topic located on Oracle Application Server 10.1.2. I think that the first step is to set up foreign JMS server, connection factory and destinations in the Weblogic server, am I right?
I've never set up that before and l looking for any guides on how to set up OAS 10.1.2 topic as foreign destination in Weblogic 10.3.3.
Any help will be appreciated
Best regards,
Dmitry

Ok, finally I found this guide http://www.oracle.com/technetwork/middleware/bam/technote-bam-connectingoc4jjms-129297.pdf and set up foreign JMS server, connection factory and topic. These foreign JMS objects are included in weblogic JNDI tree, and I could successfully deploy OSB Proxy Service that is intended to poll foreign JMS topic. The following error appeared in the weblogic server log file after deployment:
<Aug 24, 2010 1:21:44 PM MSD> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: RequestEJB-4249293316140669267--703a
3e3e.12aa2c85115.-7fcd is unable to connect to the JMS destination: jms.oc4jUDC_IDENTITY_TOPIC. The Error was:
[EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The error was:
javax.jms.JMSException: Unable to create a connection to "/0.0.0.0:12,601" as user "null".
Linked exception: java.net.ConnectException: Connection refused.
javax.jms.JMSException: Unable to create a connection to "/0.0.0.0:12,601" as user "null".
at com.evermind.server.jms.JMSUtils.makeJMSException(JMSUtils.java:1898)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1914)
at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:114)
at com.evermind.server.jms.EvermindTopicConnection.<init>(EvermindTopicConnection.java:63)
at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicConnection(EvermindTopicConnectionFactory.java:91)
at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicConnection(EvermindTopicConnectionFactory.java:83)
at weblogic.ejb.container.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:503)
at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1969)
12601 is JMS port of remote OC4J instance, I can connect to this port from weblogic server though telnet.
I do not know why 0.0.0.0 is printed as IP address, and why user is "null" ..
Any ideas on that?

JMS Topic Write throws JMSClientException:055143: Destinati must be a queue

Hi,
1) created JMS Server
2) created JMS module
3) Created JMS Topic, created Subdeployment and associated queue to the subdeployment
4) Created JMS Queue and associated Queue to the subdeployment
5) created connection factory and associated connection factory to the subdeployment
6) Created JMS Adapter connection pool.
7) Associated JMS Adapter connection pool and connection factory.
8) Redeployed JMS Adapter.
In my BPEL process i consumed JMS Adapter as a partner link.
If I try to write in JMS queue created above, BPEL process works fine.
But if I try to write in JMS Topic, i am getting following exception
Any solution for the following.
===============================================================
ERRJMS_ERR_CR_QUEUE_PROD.
ERRJMS_ERR_CR_QUEUE_PROD.
Unable to create Queue producer due to JMSException.
Please examine the log file to determine the problem.
     at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:711)
     at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:642)
     at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:180)
     at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:337)
     at oracle.tip.adapter.jms.WLSJmsInvoker.invoke(WLSJmsInvoker.java:109)
     at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:166)
     at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:140)
     at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:311)
     at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:548)
     at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeAsyncJcaReference(JCAInteractionInvoker.java:508)
     at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performAsynchronousInteraction(JCAEndpointInteraction.java:491)
     at oracle.integration.platform.blocks.adapter.AdapterReference.post(AdapterReference.java:247)
     at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost(AsynchronousMessageHandler.java:142)
     at oracle.integration.platform.blocks.mesh.MessageRouter.post(MessageRouter.java:197)
     at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.java:214)
     at sun.reflect.GeneratedMethodAccessor937.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy293.post(Unknown Source)
     at oracle.fabric.CubeServiceEngine.postToMesh(CubeServiceEngine.java:806)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:258)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1059)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
     at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74)
     at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
     at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1165)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4361)
     at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:555)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
     at sun.reflect.GeneratedMethodAccessor1034.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
     at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
     at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
     at sun.reflect.GeneratedMethodAccessor900.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
     at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
     at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy276.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
     at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Caused by: weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055143]Destination must be a queue, PocJmsModule!PocJmsTopic
     at weblogic.jms.common.Destination.checkDestinationType(Destination.java:112)
     at weblogic.jms.client.JMSSession.setupJMSProducer(JMSSession.java:2830)
     at weblogic.jms.client.JMSSession.createProducer(JMSSession.java:2858)
     at weblogic.jms.client.JMSSession.createSender(JMSSession.java:2605)
     at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:698)
     ... 87 more
[2011-07-19T06:56:33.927-04:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.invoke.pool-4.thread-3] [userId: <anonymous>] [ecid: 4c1276542546757f:14f086aa:131000ef8b1:-8000-00000000001abc77,0:1:100079473] [APP: soa-infra] [composite_name: JMSQueueWrite_Composite] [component_name: queueWrite_bpel] [component_instance_id: 103412] JCABinding=> [default/JMSQueueWrite_Composite!1.0*soa_c000666f-6301-48aa-805d-d92a5e62a021.TopicWriteJMSAdapter]:Produce_Message One-way operation Produce_Message() failed
[2011-07-19T06:56:33.929-04:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.invoke.pool-4.thread-1] [userId: <anonymous>] [ecid: 4c1276542546757f:14f086aa:131000ef8b1:-8000-00000000001abc76,0:1:100079475] [APP: soa-infra] [composite_name: JMSQueueWrite_Composite] [component_name: queueWrite_bpel] [component_instance_id: 103413] JCABinding=> JMSQueueWrite_Composite:TopicWriteJMSAdapter [ Produce_Message_ptt::Produce_Message(opaque) ] Could not invoke operation 'Produce_Message' against the 'JMS Adapter' due to: [[
BINDING.JCA-12137
===============================================================
Thanks
Ajay

6) Created JMS Adapter connection pool.Did you set IsTopic attribute here for the outbound connection pool to true...
Instead of creating custom connection pools, easiest approach would be to use eis/wls/Queue as the jndi name in the partner Link for queues and      eis/wls/Topic for topics.

Connectivity to the JMS Topic for the server synchronization information

Hi,
I am gettign below error, Can any body knows it, Please help
ProcessService 'GoYar/2011-09-16 20:21:38-04:00' created successfully.
Session initialized for participant User1 (User1 User1) with roles [ADMIN, CHECK_USER:US, APPR_USER:US, MOD_USER:US, WORK_ADMIN]
Unreachable Engine Tolerance (seconds):
by default: 0
to be used: 0
This papi client will not cache exceptions which imply that an engine could not be reached.
The connection to the JMS Topic engine was completed successfully.
Starting Fuego PAPI News Listener [cddbpdvg_dev] Service [GoYar/2011-09-16 20:21:38-04:00:46354487:29112942]
Topic Lookup topicFactoryLookupName: XATopicCF
topicLookupName: NewsTopic
The connectivity to the JMS Topic for the server synchronization information has been temporarily interrupted.
Details:
Error looking up Topic Connection Factory 'XATopicCF'.
Details:
javax.naming.NameNotFoundException: Unable to resolve 'XATopicCF'. Resolved ''; remaining name 'XATopicCF'
Caused by: Unable to resolve 'XATopicCF'. Resolved ''
fuego.papi.impl.j2ee.JMSTopicLookUpException: Error looking up Topic Connection Factory 'XATopicCF'.
Details:
javax.naming.NameNotFoundException: Unable to resolve 'XATopicCF'. Resolved ''; remaining name 'XATopicCF'
at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:741)
at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:620)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'XATopicCF'. Resolved ''; remaining name 'XATopicCF'
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.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:732)
... 1 more

Could this be a CLASSPATH issue?
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)

Problem having a MDB connect to a remote JMS Topic (WLS 6.1 sp3)

          Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
          scenario:
          > Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they are
          not part of a cluster......both are independent servers
          > One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and the
          second one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
          target is Server1})
          > In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xml
          file):
          <JMSServer Name="EventServicesJMSServer"
          Store="ESJMSServerFileStore" Targets="Server1">
          <JMSTopic JNDIName="jms/EventServicesTopic7001"
          Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
          </JMSServer>
          > In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xml
          file):
          <JMSServer Name="EventServicesJMSServer"
          Store="ESJMSServerFileStore" Targets="Server1">
          <JMSTopic JNDIName="jms/EventServicesTopic8001"
          Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
          </JMSServer>
          > An MDB is deployed on WLSDomain1/Server1 with the following elements in its
          weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
          the relevant info):
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>1</max-beans-in-free-pool>
          <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
          </pool>
          
          <destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
          <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
          <provider-url>t3://localhost:8001</provider-url>
          <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          > An MDB is deployed on WLSDomain2/Server1 with the following elements in its
          weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
          the relevant info):
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>1</max-beans-in-free-pool>
          <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
          </pool>
          
          <destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
          <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
          <provider-url>t3://localhost:7001</provider-url>
          <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          > After starting both the WLS servers, I've verified that they have made connections
          to each other; the Topics are defined in the JNDI tree of the respective servers;
          and the MDBs have been deployed in their respective servers. But the MDBs can't
          see/connect to their respective JMS destination. Here's the error message and
          stack trace from one the WLS server's trace file:
          <Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
          common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
          the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
          attempt to
          re-establish the connection with the JMS server. This warning may occur during
          WebLogic Cluster start-up if the JMS destination is located on another server.
          When the JMS server connection is re-established, the Message-Driven EJB will
          again receive JMS messages.
          The Error was:
          weblogic.jms.common.JMSException: Connection not found
          at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
          at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
          at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
          at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
          at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
          at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
          at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
          at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
          at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
          at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
          at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
          9)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Have you run into a similar problem? Any suggestion?
          Thanks,
          Farook


FAQ. Naming conflict. To interop between domains make sure:
          All WL Servers are named differently.
          All JMS Servers are named differently.
          All JMS Stores are named differently.
          Tom
          Farook Wadia wrote:
          > Hi, I am having problem making an MDB listen to a remote JMS Topic. Here's the
          > scenario:
          >
          >
          >>Two Weblogic servers (6.1 sp3) running on the same machine (W2K) - they are
          >
          > not part of a cluster......both are independent servers
          >
          >
          >>One WLS is listening on port 7001 (Domain=WLSDomain1; Target=Server1) and the
          >
          > second one on 8001 (Domain=WLSDomain2; Target=Server1 {This is not a typo, the
          > target is Server1})
          >
          >
          >>In WLSDomain1/Server1, I have a JMS Topic defined as follows (in its config.xml
          >
          > file):
          >
          > <JMSServer Name="EventServicesJMSServer"
          > Store="ESJMSServerFileStore" Targets="Server1">
          > <JMSTopic JNDIName="jms/EventServicesTopic7001"
          > Name="jms/EventServicesTopic7001" StoreEnabled="true"/>
          > </JMSServer>
          >
          >>In WLSDomain2/Server1, I have a JMS Topic defined as follows (in config.xml
          >
          > file):
          >
          > <JMSServer Name="EventServicesJMSServer"
          > Store="ESJMSServerFileStore" Targets="Server1">
          > <JMSTopic JNDIName="jms/EventServicesTopic8001"
          > Name="jms/EventServicesTopic8001" StoreEnabled="true"/>
          > </JMSServer>
          >
          >>An MDB is deployed on WLSDomain1/Server1 with the following elements in its
          >
          > weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
          > the relevant info):
          >
          > ..
          > <message-driven-descriptor>
          > <pool>
          > <max-beans-in-free-pool>1</max-beans-in-free-pool>
          > <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
          > </pool>
          > 
          > <destination-jndi-name>jms/EventServicesTopic8001</destination-jndi-name>
          > <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
          > <provider-url>t3://localhost:8001</provider-url>
          > <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
          > </message-driven-descriptor>
          > ...
          >
          >
          >>An MDB is deployed on WLSDomain2/Server1 with the following elements in its
          >
          > weblogic-jar.xml file (I haven't included the entire weblogic-jar.xml file, only
          > the relevant info):
          >
          > ..
          > <message-driven-descriptor>
          > <pool>
          > <max-beans-in-free-pool>1</max-beans-in-free-pool>
          > <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
          > </pool>
          > 
          > <destination-jndi-name>jms/EventServicesTopic7001</destination-jndi-name>
          > <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
          > <provider-url>t3://localhost:7001</provider-url>
          > <connection-factory-jndi-name>weblogic/jms/ConnectionFactory</connection-factory-jndi-name>
          > </message-driven-descriptor>
          > ...
          >
          >
          >>After starting both the WLS servers, I've verified that they have made connections
          >
          > to each other; the Topics are defined in the JNDI tree of the respective servers;
          > and the MDBs have been deployed in their respective servers. But the MDBs can't
          > see/connect to their respective JMS destination. Here's the error message and
          > stack trace from one the WLS server's trace file:
          >
          > <Apr 17, 2003 4:58:25 PM GMT> <Warning> <EJB> <The Message-Driven EJB: com.manu.
          > common.server.objectServices.CSMEventListenerMDB_8001 is unable to connect to
          > the JMS destination: jms/EventServicesTopic8001. The EJB container will automatically
          > attempt to
          > re-establish the connection with the JMS server. This warning may occur during
          > WebLogic Cluster start-up if the JMS destination is located on another server.
          > When the JMS server connection is re-established, the Message-Driven EJB will
          > again receive JMS messages.
          > The Error was:
          > weblogic.jms.common.JMSException: Connection not found
          > at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
          > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
          > at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
          > at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
          > at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
          > at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:522)
          > at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:418)
          > at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:348)
          > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
          > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
          > at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
          > 9)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          >
          > Have you run into a similar problem? Any suggestion?
          >
          > Thanks,
          >
          > Farook

Distributed JMS Topic consumer reconnection... How???

Hi!
          I'm trying to develop a JMS consumer that is connected to a distributed topic located in a 2-machine cluster. The client knows the address of the two servers, so the idea is to catch the JMSException (JMS destination shutdown) with a ExceptionListener (or something like that) if one server fails, and then try to connect to the other one...
          I've been browsing Weblogic docs but I didn't find any example for this.
          How do I implement my consumer? Is there any other approach to my problem?
          Thanks a lot!
          Jorge Granado


          Hi Tom:
          Finally I've been able to reconnect my consumer. I took a "clean" one (mine was
          getting too complicated :-) and it worked. I took the TopicReceive sample from
          bea samples and added a "reconnect" method following your recommendations about
          reusing existing ConnectionFactory. I'm beginning to think I was forgetting to
          start the connection, but anyway now it works great. Thanks a lot!
          BTW, could you explain to me how can I change (if possible) in "real-time" the
          MessageSelector properies for an existing consumer? Suppose that I have a consumer
          connected to a topic with a selector like "priority >=2" and I'd like to change
          it to "priority >=3" without restarting the application... Is it possible??
          Thanks again
          Jorge
          Tom Barnes <[email protected].bea.com>
          wrote:
          >Seems like your following the recipe correctly. :-)
          >
          >Could you try this on a platform other than AIX?
          >
          >Are you using the same version of WL jars for client and server?
          >
          >Are you using the new 8.1 "thin client" jars for the client? If
          >so try using weblogic.jar instead (don't put both kinds
          >of jars in your classpath).
          >
          >
          >"Jorge Granado" jorge.granadoATatosorigin.com wrote:
          >
          >> Hi again!
          >>
          >> Well, maybe there's something I don't get, but what I'm trying to do
          >is:
          >>
          >> -Create a topic consumer and connect it to the distributed topic (standard
          >process...)
          >> -Shutdown the server where the consumer is connected...
          >> -Capture the exception
          >> -Close the topic connection
          >> -Create a new one reusing existing topic connection factory (as you
          >told me there's
          >> no need to make a lookup again...)
          >> -Create a topic session over the new topic connection
          >> -Create a subscriber
          >> -Read messages... :-)
          >>
          >> But in 5th step what I get is a new Exception... "Error creating connection
          >to
          >> the server"
          >>
          >> I'm sure I've misunderstood something... :-(
          >>
          >> Thanks again for your patience :-)
          >>
          >> Jorge
          >>
          >> Tom Barnes <[email protected].bea.com>
          >> wrote:
          >>
          >>>No, I don't know what is happening. I wonder if you are
          >>>somehow multi-threading the session? Try closing
          >>>the old connection before reconnecting. And note that
          >>>there is no need to lookup up the CF again, as the old CF
          >>>should work fine (it is a clusterable RMI reference,
          >>>so it can survive failures).
          >>>
          >>>"Jorge Granado" jorge.granadoATatosorigin.com wrote:
          >>>
          >>>>Now I've created a consumer, and when catching the session exception
          >>>
          >>>and try to
          >>>
          >>>>reconnect to another WL instance, when I make the JNDI lookup to my
          >>>
          >>>connection
          >>>
          >>>>factory, instead of getting a weblogic.jms.client.JMSConnectionFactory
          >>>
          >>>what I
          >>>
          >>>>get is an weblogic.jms.frontend.FEConnectionFactory_812_WLStub_812_WLStub.
          >>>
          >>>>This causes a ClassCastException and I can't connect to it. Any idea
          >>>
          >>>what is happening?
          >>>
          >>>>Thanx again :-)
          >>>>
          >>>> Jorge
          >>>>
          >>>>BTW, I'm using WL 8.1 SP2 (AIX platform)
          >>>>
          >>>>Tom Barnes <[email protected].bea.com>
          >>>>wrote:
          >>>>
          >>>>
          >>>>>Hi Jorge,
          >>>>>
          >>>>>Registering exception-listeners and retrying on failure
          >>>>>seems like the right approach. I'm not sure what you
          >>>>>are looking for in an example.
          >>>>>
          >>>>>For more information on JMS clustering, I recommend reading
          >>>>>the JMS Performance Guide white-paper on dev2dev:
          >>>>>
          >>>>>http://dev2dev.bea.com/technologies/jms/index.jsp
          >>>>>
          >>>>>Tom, BEA
          >>>>>
          >>>>>P.S. One thing to realize is that WebLogic distinguishes between
          >>>>>"session" exceptions and "ccnnection" exceptions. Shutting
          >>>>>down JMS without shutting down a client connection's WL
          >>>>>server only generates session exceptions, as the connection
          >>>>>is still valid. To monitor session exceptions, register
          >>>>>a session exception listener (see the weblogic.jms.extensions
          >>>>>package).
          >>>>>
          >>>>>Jorge Granado wrote:
          >>>>>
          >>>>>
          >>>>>
          >>>>>>Hi!
          >>>>>>
          >>>>>>I'm trying to develop a JMS consumer that is connected to a distributed
          >>>>>
          >>>>>topic located in a 2-machine cluster.
          >>>>>
          >>>>>
          >>>>>>The client knows the address of the two servers, so the idea is
          >to
          >>>>>
          >>>>>catch the JMSException (JMS destination shutdown)
          >>>>>
          >>>>>with a ExceptionListener (or something like that) if one server fails,
          >>>>>
          >>>>>and then try to connect to the other one...
          >>>>>
          >>>>>
          >>>>>>I've been browsing Weblogic docs but I didn't find any example for
          >>>>>
          >>>>>this.
          >>>>>
          >>>>>
          >>>>>>How do I implement my consumer? Is there any other approach to my
          >>>
          >>>problem?
          >>>
          >>>>>>Thanks a lot!
          >>>>>>
          >>>>>> Jorge Granado
          >>>>>
          >>
          >

Error in Applet reading a JMS topic

Similar Messages

Maybe you are looking for