JMS topic - deliver a single Durable Subscriber

Similar Questions

• Messages to the JMS OSB topic disappear even when not subscribed

  Hello
  
  We use a service OSB publish xml messages to a weblogic JMS topic. Message is persistent. There is no consumer for the subject. There is no limit set expiration.
  
  We are able to see the message of the OSB reach the subject. He remains in the topic for a few seconds, then disappears.
  
  The status of the message is 'send transaction' on the subject in the weblogic console. And she appears as Message waiting instead of current Message.
  
  Is there a way to make sure that the message remains in the subject, until it is consumed by a Subscriber?
  
  
  Thank you
  Spengler

  Hi Spengler,

  The topic still messages only for subscribers, if there are no subscribers, then it is not necessary keep the message.

  This is the case even for you as well, that there are no subscribers the message is deleted.

  So first of all you must have at least a first Subscriber (a dummy proxy that reads from the topic) and then post on the subject (via your service OSB or hermes jms tool, etc...). If you try to go check out the topic, you will be able to see the message.

  Hope this information helps.

  Thank you
  Patrick

  Published by: Patrick Taylor on May 13, 2011 14:40

• Difference between Oracle EDN and JMS topic

  Hi all

  Can someone explain in detail the difference between Oracle EDN and JMS topic?

  The only difference I see is

  JMS producer must specify the name of the topic to which the message is to go...

  the NDA does not specify where any point of termination (queue or topic), he just publish the event...

  Are there other differences? How to choose when to use Oracle EDN and JMS topics?

  Please, share your ideas...

  Thank you

  Oracle EDN also uses the subject or the database under.

  So there is no difference in low level technology

  However, the NDA is much easier to implement from the subject.

  EDN avoids you having to use create rubrics, create connection factories, creating adapters, update deployments etc. All this is supported internally in the NDA and is available out of the BOX for you. You simply set an EVENT and then publish / subscribe it.

  However, you can use topics when you have other subscribers of third party such as SAP, Siebel, because the NDA is strongly coupled with Oracle SOA, BPEL, mediator components.

• publication and the jms Topic subscription

  Hello
  
  Can someone tell me how to publish and subscribe jms messages in topic using the notion of sustainable text. I use jdeveloper to weblogic 10.3 and 11.1.1.4.0.
  
  Thanks in advance.

  You create a JMS adapter in the exposed Pan Services. Once you select the topic to subscribe, if you provide a subscription ID sustainable static then the listener adapter will be configured as a sustainable topic Subscriber.
  The publication doesn't have the notion of durable subscription (from which the name).

• How to make a leap of JMS Proxy Service subscribed as a synchronous service

  I'm trying to find the right configuration/model of OSB in support of the following.
  
  Use case:
  
  Several messages to a JMS topic. The Java Web Service invoked by the Subscriber of the Service Proxy should cannot have an active instance at a time so that it processes messages syncronously.
  
  Current configuration for OSB:
  
  Topic JMS-> ProxyServiceA-> BusinessServiceA (synchronous Web Service, Java)
  -> ProxyServiceB-> BusinessServiceB (BPEL synchronous Web Service)
  
  Work Manager configured on ProxyServiceA with maxThreadCount = 1 and minThreadCount = 1
  
  Question:
  
  Multiple instances of BusinessServiceA are active at the same time with the above parameters. I am unable to do the ProxyServiceA to act as a synchronous process, so that it will not return until BusinessServiceA has completed.

  A few Questions:

  How many subscribers are there on the subject? You verified this in the admin console.?

  What kind of factory of connection do you use? Is it permissible to XA?

  Try this:
  1 make the transactional proxy service by implementing a XA Factory connection
  2 configure a job manager on the service proxy with a maxthread = 1 constarint
  3. set up a manager of work on business services (java WS) with the constraint maxthread = 1. (we found tests to maintain the original sequence after the restorations of transactions, it is necessary to single thread of business service as well).
  4. in the proxy service, when routing to business defined Quality of Service on $outbound = Exacltly - once.

• Limit the number of subscribers on the same JMS subscribe to Message subject

  Hello

  Is it possible or property on Weblogic Console on JMS topic put force that a specific number of Subscriber can subscribe only to this topic

  BPEL (JDeveloper) or at design time items in .jca file?

  Thank you

  Hi momo,.

  Can you give some details on the usage scenario/case you're trying to accomplish?

  There is no option to set a constraint on the number of subscribers. You wouldn't be limited, as is one of the reasons you would use a topic to build a scalable solution, i.e. to have flexibility to introduce additional subscribers without impacting existing publishers or consumers.

  If the intention is to restrict access to the topic, the best way would be to use a SSL based connection. This will allow you to share the credentials to consumers only planned.

  I hope this helps!

  Thank you

  Patrick

• Want JMS adapter to consume the HornetQ section data

  Hi all
  I have a stand-alone hornetQ topic with a durable subscriber. Now I want a BPEL process with adapter to JMS that will consume the hornetQ field data. I have all the hornet associated jar files. I already have all the jar files in the folder of wls. Then set the PRE_CLASSPATH in the setDomainEnv script. But now, JMS adapter, I chose option of third party. After that, it will ask for JMS JNDI connection. What should I enter here? I need to create any JNDI in weblogic console? If yes then please give me steps to that end.
  
  Thanks in advance.

  Hello

  In the 2nd screen it ask the service name and it can be any name and select advance option queues in the display 3.

  If you configure you queue name to the foreign server on the destination tab, and then in the configuration of the card in the screen 7 you will see the queue, select the name and give the correct JNDI name eis/aqjms/queue or ist/aqjms/threads - in case if you use default JNDI names.

  Hope this helps you.

  Kind regards
  Tarak.

• SDS + Jboss JMS authentication

  Hello world!
  
  I use Flex Data Services (2.0.1 und 3 Beta) in JBoss 4.0.5 more Tibco EMS JMS server, which enabled authentication and gets the motions JNDI passed from JBoss.
  
  The Flash application in question must receive text messages JMS with a subject not secure in a non-durable subscription.
  
  She must use an account on th JMS server that has the right to purchase, but is not in the administrator group.
  
  
  I use a tag mx: consumer, who gets initialize in an initApp() function that is called through an event "creationComplete mx:application.
  
  Subscribe to the JMS topic
  consumer1.setRemoteCredentials ("username", "PWD");
  consumer1. Subscribe();
  
  In the config.xml file - messaging, I have the following destination set:
  
  < destination id = "EMSTest-jms" >
  Properties of <>
  < jms >
  javax.jms.TextMessage < message-type > < / message type >
  TopicConnectionFactory < factory connections > - < / factory connections >
  subject of < destination-jndi-name >. EMSTest < / destination-jndi-name >
  > delivery mode < NON_PERSISTENT < / delivery mode >
  DEFAULT_PRIORITY > to the priority of the message < < / priority of the message >
  AUTO_ACKNOWLEDGE < acknowledge mode > < / acknowledge mode >
  false < traded sessions > < / processed sessions >
  < initial-context-environment >
  < property >
  < name > Context.SECURITY_PRINCIPAL < / name >
  user name < value > < / value >
  < / property >
  < property >
  < name > Context.SECURITY_CREDENTIALS < / name >
  pwd < value > < / value >
  < / property >
  < property >
  < name > Context.PROVIDER_URL < / name >
  < value > tibjmsnaming://someip:7222 < / value >
  < / property >
  < property >
  < name > Context.INITIAL_CONTEXT_FACTORY < / name >
  < value > com.tibco.tibjms.naming.TibjmsInitialContextFactory < / value >
  < / property >
  < / initial-context-environment >
  < / jms >
  < / properties >
  <>channels
  < Ref = "my-rtmp" channel / >
  < Channel Ref = "my - amf" / >
  < / channels >
  < Adapter Ref = "jms" / >
  < / destination >
  
  Now, when you launch the application I get following from the JMS server error message:
  
  "password invalid or username"
  
  Because the configured values are valid, it's not supposed, it's why I forwarded the JMS calls through tcpproxy.
  
  Proxy TCP shows three communications by calling consumer.subscribe ():
  
  two JNDI calls on the server (perhaps to get the connection and the subject), who use the name of user and password correct
  
  and a third call (perhaps actually subscribe to this topic) that use the user name = anonymous password as well as other
  
  So in fact the JMS server has every right to complain, but why SDS uses a name of user and password different for the last call?
  
  Where can I configure these values?
  
  In addition, the only place, where a "anonymous" username is configured across the system, is in JBoss as unauthorized in server.xml of default username...
  
  
  Many thanks for any help!
  

  Hello

  I checked with the current adapter to JMS and unfortunately JMS adapter does not support the authentication you need. I opened a request for improvement and will ensure that this configuration will be based for the next version.

  Thanks for reporting the problem.

• &lt; error &gt; &lt; security &gt; &lt; BEA-000000 &gt; &lt; validation events is not available because no JMS Transport is available. The remote L2 caches will be out of sync. &gt;

  I'm trying to set up a cluster, I installed my SQL server DB and Weblogic Portal 10.3.2 on two different machines and each thing is correctly configured according to my knowledge.

  but when I am trying to start my node managed on a remote machine, out of sync error continually as shown below

  < 6 sep, 2014 16:42:02 IST > < error > < security > < BEA-000000 > < validation events is not available because no JMS Transport is available. The remote L2 caches will be out of sync >

  < 6 sep, 2014 16:42:07 IST > < error > < security > < BEA-000000 > < validation events is not available because no JMS Transport is available. The remote L2 caches will be out of sync >

  < 6 sep, 2014 16:42:13 IST > < error > < security > < BEA-000000 > < validation events is not available because no JMS Transport is available. The remote L2 caches will be out of sync >

  < 6 sep, 2014 16:42:18 IST > < error > < security > < BEA-000000 > < validation events is not available because no JMS Transport is available. The remote L2 caches will be out of sync >

  < 6 sep, 2014 16:42:24 IST > < error > < security > < BEA-000000 > < validation events is not available because no JMS Transport is available. The remote L2 caches will be out of sync >

  NOTE: I can connect to my DB using java utils.dbping [MSSQLSERVER4 |] MSSQLSERVERB] < db username > < db and user password > DB_Host:Port / Db_name on two physical machines.

  is there no work around for this problem, as I am not able to get around this error and is unable to start my managed computer node.

  Thank you

  Punishes

  Hello

  Notes on MOS:

  It is an issue that occurs because the RDBMS security store configuration problem. In order to synchronize the RDBMS security store data, WLS uses the JMS topic for transport, which is not met in this case and therefore this error. The solution is to configure the JMS topic according to the above reference documentation. However this post ideally is not an error but a simple warning message. Thus, in the context of the code fix, we delivered a patch for WLS, to change the gravity of this message of 'ERROR' to 'WARNING '. This patch can be downloaded using My Oracle Support Portal using:

  Bug number: 13459424

  Patch ID: NF9G

  Emmanuel

• OSB 11 g acting as a Proxy of JMS

  I was hoping someone can clear my understanding of the OSB, and how it interacts with JMS.
  
  I created a server, the connection and the JMS topic in WLS. It works very well. I am able to subscribe and publish from a java client and an OSB business service.
  
  Our use case is to use OSB as a "front end" for JMS if you want. We want JMS to you clients to connect to the OSB and you subscribe to our (sustainable) JMS topic. Is it possible to subscribe to a JMS client proxy service? How can I do?
  
  The next thing we will try to do is have a process of OSB listen our JMS topic and call a web service when a new message is posted. Guides on that?
  
  Thank you very much
  Sam

  We want JMS to you clients to connect to the OSB and you subscribe to our (sustainable) JMS topic. Is it possible to subscribe to a JMS client proxy service? How can I do?

  I don't think that a proxy service subscribers are possible. Instead create a separate waiting (or other storage), queue for your client application and inform the OSB pull the message from the source queue and send it to target storage (may be a different queue JMS)

  The next thing we will try to do is have a process of OSB listen our JMS topic and call a web service when a new message is posted. Guides on that?

  This approach is quite similar to what I mentioned above. Just create a proxy service to let JMS consume messages from the subject and create a Business Service (web service WSDL based) to call the web service target. In the flow of of proxy JMS messages, you can have the transformation if necessary and then forward the message to business that finally delivers the message to target web services.

  Kind regards
  Anuj

• Queries on JMS

  Hello
  I learn from JMS, and I have the following questions which have been curious to me:
  1. How can I associate one or more queues/topics with a single connection factory, so that they can be accessed only through this connection factory and not others?
  2. How can I provide security to name of user and password to a JMS connection factory and a JMS queue?
  
  I would really appreciate any guidance or insight in this case.

  The wrong forum. You need a forum of Weblogic. I do not see often specific questions server get answered here.

• error of JMS weblogic 10.3

  # < 25 August 2009 11:39:07 AM MST > < WARNING > < EJB > < ddczxspsdb1 > < devM2 > < ExecuteThread: '2' for the queue: 'weblogic.kernel.System' > < < < > WLS Kernel > > < BEA-010061 > < The Message - Driven EJB: FileLoadBeanEJBImpl is unable to connect to the JMS destination: JMSTopic. The error was:
  [EJB:011010] The JMS destination with the JNDI name: JMSTopic was not found. Please ensure that the JNDI name in the weblogic-ejb - jar.xml is correct, and the JMS destination has been deployed. >
  # < 25 August 2009 11:39:17 AM MST > < WARNING > < EJB > < ddczxspsdb1 > < devM2 > < ExecuteThread: '12' to the queue: 'weblogic.kernel.Default' > < < < > WLS Kernel > > < BEA-010096 > < The Message - Driven EJB: AmgenFileLoadBeanEJBImpl is unable to connect to the JMS destination: JMSTopic. The connection failed after 2 attempts. The MDB will attempt to reconnect every 10 seconds. This log message repeats every 600 seconds until that condition clears. >
  # < 25 August 2009 11:39:17 AM MST > < WARNING > < EJB > < ddczxspsdb1 > < devM2 > < ExecuteThread: '12' to the queue: 'weblogic.kernel.Default' > < < < > WLS Kernel > > < BEA-010061 > < The Message - Driven EJB: AmgenFileLoadBeanEJBImpl is unable to connect to the JMS destination: JMSTopic. The error was:
  [EJB:011010] The JMS destination with the JNDI name: JMSTopic was not found. Please ensure that the JNDI name in the weblogic-ejb - jar.xml is correct, and the JMS destination has been deployed. >
  
  is the error due to the jms topic name.
  I gave the name of jms as jmsDevTopic topic in the administration console and we test the jms connectivity from the client.
  
  
  In addition, under the heading JMS-> monitor-> durable subscribers, I see the following message
  
  
  
  Can't find the execution of this JMS destination information.
  
  There are many reasons why the system cannot find the destination runtime. Here are some common causes:
  
  * This destination is not targeted to a JMS server
  * This destination caters to a JMS server, but the Server JMS is not targeted to a server or a migratable target
  * the JMS destination module is not targeted to a server or a cluster
  * all target entities above are not enabled
  
  
  but I targeted factories connection and subject to the JMS server with a deployment under and targeted jms server with the managed server.
  
  
  can you help me with this
  
  
  Thank you

  In the stack trace that is provided, the first exception seems thrown by the application com.amgen code and has nothing directly to do with WebLogic. Specifically, the code has been impossible to find a properties file:

  Caused by: com.amgen.util.config.ConfigException: cannot load jmsdevTopic.properties file property
  to com.amgen.util.config.PropertyConfig. (PropertyConfig.java:32)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
  at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
  at com.amgen.util.config.ConfigManager.getConfig(ConfigManager.java:43)
  at com.amgen.util.config.ConfigManager.getConfig(ConfigManager.java:24)
  at com.amgen.jms.ServiceLocator.getTopicConnectionFactory(ServiceLocator.java:61)

• consumption of the Subscriber for CDC ODI

  Hello
  
  I use DCC (relaxation one) in a workflow running several interfaces and I would like to know if there is a way to avoid creating a single separate Subscriber for each interface? because in my package, I have 40 interfaces (actually 5 separate interfaces that run 8 times with a variable which take 8 different values).
  
  I was thinking of a LKM option as for the consumption of JMS message, but there is no option like this...
  
  If someone has an idea, I'd be really interested.
  
  
  Thanks in advance.
  
  You
  Micropole.

  heheheh right now, we are at 28 ° c. This weekend I plan to go to the beach, there is a good one to 150 KM from the city, I am now...

  If at any time you decide to visit us, tell me and I can give you some tips on the best places... :D

  I hope that the solution works...

• About JMS transfers the JMS Messages

  Hello
  
  In my organization, we have implemented weblogic 10.2.5, suddenly our JMS topics stopped before messages to subscribers, no idea?
  
  your help is very appreciated.
  
  Mansoor
  
  Kind regards.

  The problem might be a network, application, client or server problem. Your primary investigative tool includes your server log (look for the errors & warnings), thread dumps client & server (glance for blocked threads) and all the exceptions that can be thrown to your customers.

  A few questions that might help to refine the question:

  Several areas are involved?

  Do you use distributed topics?

  What is the maximum size of your messages?

  HTH,

  Tom

• Written about JMS lift JMSClientException:055143: audio must be a queue

  Hello
  
  (1) Server JMS
  (2) created JMS module
  (3) created JMS topic, created Subdeployment and associated with the queue to the subdeployment
  (4) created the JMS queue and queue associated with the subdeployment
  (5) created the connection factory and connection associated with the subdeployment
  (6) connection JMS adapter created pool.
  (7) associated with JMS connection pool and connection factory adapters.
  (8) redeployed JMS adapter.
  
  In my BPEL process, I used JMS adapter as a link partner.
  If I try to write to the queue created above JMS, BPEL process works very well.
  But if I try to write in the JMS topic, I'm special suite
  Any solution for that.
  
  ===============================================================
  ERRJMS_ERR_CR_QUEUE_PROD.
  ERRJMS_ERR_CR_QUEUE_PROD.
  Cannot create the queue due JMSException producer.
  Please review 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)
  to $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)
  to 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)
  to $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)
  to java.util.concurrent.ThreadPoolExecutor$ Worker.runTask (ThreadPoolExecutor.java:886)
  to 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)
  ... more than 87
  
  ]]
  [2011 07-19 T 06: 56:33.927 - 04:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.invoke.pool - 4.thread - 3] [username: < anonymous >] [ecid: 4c1276542546757f:14f086aa:131000ef8b1:-8000-00000000001abc77, 0:1:100079473] [APP: soa-infra] [composite_name: JMSQueueWrite_Composite] [name of the component: queueWrite_bpel] [component_instance_id: 103412] JCABinding = > [by default/JMSQueueWrite_Composite! 1.0 * soa_c000666f-6301-48aa-805-d-d92a5e62a021.] TopicWriteJMSAdapter]: Produce_Message Produce_Message() one-way operation failed
  [2011 07-19 T 06: 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] [name of the component: 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: []
  LIAISON. JCA-12137
  
  ===============================================================
  
  Thank you
  Ajay

  (6) connection JMS adapter created pool.

  You assign IsTopic attribute here for the connection pool outgoing true...

  Instead of creating custom connections pools, the simplest approach would be to use the EIA/wls/queue as the jndi name in the partner liaison for queues and eis/wls/theme for the subjects.