Creating a secured DISTRIBUTED JMS topic.

I need create a secured DISTRIBUTED JMS topic. That is, client should have the correct security credentials in order to access the topic.
Please help.

Similar Messages

Problems using distributed JMS topic

          I'm having problems using a distributed topic. I'm running WebLogic 8.1 (SP1)
          with two managed servers in a cluster. I created a new distributed topic using
          the console, and used auto deploy to target the distributed topic to the cluster
          and create members on both servers. I deployed three message-driven EJBs (listening
          on the distributed topic) to both servers.
          After initial deployment, the topic works as expected - I post a message to the
          distributed topic, and it is received by all six EJBs. When I re-start the system
          (both managed servers and the admin server), however, the results are different.
          When I post a message to the distributed topic, it is only received by the three
          EJBs on the first server (the log shows that all EJBs have deployed successfully).
          Under Deployments/EJB Modules/Monitoring, the EJBs on the second server show "JMSConnection
          Alive" as false, while the others are true.
          Under Monitoring/"Monitor all Active JMS Destinations..." for the member topics,
          there are three consumers listed when there should be six.
          If remove and re-create the member topics, or the distributed topic, exceptions
          appear in the log saying that one or both of the member topics are "suspended".
          Is there additional configuration that needs to be done for this scenario? Are
          there any known problems related to distributed topics?
          Thanks,
          Richard


Hi Richard,
          There are no 8.1SP1 problems that I know of.
          Check your logs for Warnings and Errors - distributed topics
          members often log an explanatory message
          when they fail to contact their fellow members.
          Also make sure that you have configured so that
          the following are true:
          All WL servers are named differently.
          All JMS servers are named differently.
          All JMS stores are named differently.
          All distributed topic members within a distributed topic are named
          differently.
          Also make sure that your cluster is coming up
          properly in the first place. If you have
          trouble doing so, you can post
          to the clustering newsgroups for info.
          Tom
          Richard Killen wrote:
          > I'm having problems using a distributed topic. I'm running WebLogic 8.1 (SP1)
          > with two managed servers in a cluster. I created a new distributed topic using
          > the console, and used auto deploy to target the distributed topic to the cluster
          > and create members on both servers. I deployed three message-driven EJBs (listening
          > on the distributed topic) to both servers.
          >
          > After initial deployment, the topic works as expected - I post a message to the
          > distributed topic, and it is received by all six EJBs. When I re-start the system
          > (both managed servers and the admin server), however, the results are different.
          > When I post a message to the distributed topic, it is only received by the three
          > EJBs on the first server (the log shows that all EJBs have deployed successfully).
          >
          > Under Deployments/EJB Modules/Monitoring, the EJBs on the second server show "JMSConnection
          > Alive" as false, while the others are true.
          >
          > Under Monitoring/"Monitor all Active JMS Destinations..." for the member topics,
          > there are three consumers listed when there should be six.
          >
          > If remove and re-create the member topics, or the distributed topic, exceptions
          > appear in the log saying that one or both of the member topics are "suspended".
          >
          > Is there additional configuration that needs to be done for this scenario? Are
          > there any known problems related to distributed topics?
          >
          > Thanks,
          > Richard
          >

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

Clustering a JMS Topic

I'm trying to create a distributed JMS topic using the wlconfig ant task (MBean).
I can create a topic on a single server fine, but I can't figure out how to create a distributed topic that I could access on any server in the cluster.
This is what I have so far, which seems to run, but I can't lookup the topic under the JNDI name in the server,
<wlconfig url="t3://${JEE_HOST}:7001/" username="${JEE_USER}" password="${JEE_PASSWORD}">
<query domain="mydomain" type="Cluster" name="*" property="cluster"/>
<query domain="mydomain" type="Server" name="server1" property="server1"/>
<query domain="mydomain" type="Server" name="server2" property="server2"/>
<query domain="mydomain" type="Server" name="server3" property="server3"/>
<create type="JMSConnectionFactory" name="EmployeeTopicConnectionFactory">
<set attribute="JNDIName" value="jms/EmployeeTopicConnectionFactory"/>
<set attribute="XAServerEnabled" value="false"/>
<set attribute="Targets" value="${cluster}"/>
</create>
<create type="JMSServer" name="EmployeeJMSServer1">
<set attribute="Targets" value="${server1}"/>
</create>
<create type="JMSServer" name="EmployeeJMSServer2">
<set attribute="Targets" value="${server2}"/>
</create>
<create type="JMSServer" name="EmployeeJMSServer3">
<set attribute="Targets" value="${server3}"/>
</create>
<create type="JMSDistributedTopic" name="EmployeeTopic">
<set attribute="JNDIName" value="jms/EmployeeTopic"/>
<set attribute="LoadBalancingPolicy" value="Random"/>
<set attribute="Targets" value="${cluster}"/>
</create>
</wlconfig>
This produces the following in the config.xml
<jms-server>
<name>EmployeeJMSServer1</name>
<target>server1</target>
</jms-server>
<jms-server>
<name>EmployeeJMSServer2</name>
<target>server2</target>
</jms-server>
<jms-server>
<name>EmployeeJMSServer3</name>
<target>server3</target>
</jms-server>
<migratable-target>
<name>server1 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>server1</user-preferred-server>
<cluster>employee-cluster</cluster>
</migratable-target>
<migratable-target>
<name>server2 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>server2</user-preferred-server>
<cluster>employee-cluster</cluster>
</migratable-target>
<migratable-target>
<name>server3 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>server3</user-preferred-server>
<cluster>employee-cluster</cluster>
</migratable-target>
<jms-interop-module>
<name>interop-jms</name>
<sub-deployment>
<name>EmployeeTopicConnectionFactory</name>
<target>employee-cluster</target>
</sub-deployment>
<sub-deployment>
<name>EmployeeTopic</name>
<target>employee-cluster</target>
</sub-deployment>
<descriptor-file-name>jms/interop-jms.xml</descriptor-file-name>
</jms-interop-module>
and the jms interop xml
<connection-factory name="EmployeeTopicConnectionFactory">
<jndi-name>jms/EmployeeTopicConnectionFactory</jndi-name>
<transaction-params>
<xa-connection-factory-enabled>false</xa-connection-factory-enabled>
</transaction-params>
</connection-factory>
<distributed-topic name="EmployeeTopic">
<jndi-name>jms/EmployeeTopic</jndi-name>
<load-balancing-policy>Random</load-balancing-policy>
</distributed-topic>

You might want to post this to the JMS forum:
http://forum.java.sun.com/forum.jspa?forumID=29

How to resolve JMSExceptions:045032 when creating a JMS Topic

I am using Weblogic 12c (12.1.1.0). I have created a new managed server. I have created a JMS server targeted to the new managed server. I have created a JMS module targeted to the new managed server. I have created a JMS Subdeployment which targets both the new managed server and the new JMS server. I've created a JMS connection factory which targets the JMS Subdeployment.
Now everything I've done so far has worked fine. No problems. The problem happens when I try to create a JMS Topic. I select to create a new regular Topic; I target the new JMS Subdeployment, and after selecting the Subdeployment Weblogic refreshes the page and shows the JMS server. So this all seems OK. When I try to finish and create the JMS Topic, I get the following error: [JMSExceptions:045032]While attempting to create destination [TOPIC_NAME] in module [MODULE_NAME] the JMS server [MANAGED_SERVER_NAME] could not be found.
Any thoughts on this? I've googled around but haven't found anything useful.

I replicated this at my end. This is caused by Subdeployment target to both the new managed server and the new JMS server.
Please try creating a new Subdeployment and target it to JMS Server only, as described in the document below.
https://docs.oracle.com/cd/E24329_01/web.1211/e24385/best_practice.htm#JMSAD633
"Populate the subdeployment only with JMS servers - not WebLogic servers. Only include the JMS servers that you wish to host destinations. This ensures that when the JMS resources are configured, they are targeted to the correct JMS servers. For modules that support non-distributed destinations, the subdeployment must only reference a single JMS Server. If you have a mix of distributed and non-distributed destinations, use two modules each with its own subdeployment."
Best Regards
Luz

JMS Distributed Destination Topic - how to avoid MDB to recieve duplicates

HELP!!
          I have spent a lot of time looking for an option to move jms on a cluster, finally I can do this using distributed destination, I have two memmbers(Topic) in the distributed destination topic, but when both of them are active, the Message Driven Bean which is deployed on cluster recieves 2 messages instead of 1, anyone please help me to change this to have only one message instead of 2 !!!!!

Make it a Queue or don't deploy the MDB to the cluster. You are seeing
          expected behavior. I have the same situation with a Topic and I deploy my
          MDB to one node in the cluster and have it configured to consume the local
          physical Topic.
          Bill
          "Manav Sehgal" <[email protected]> wrote in message
          news:18024883.1107530318601.JavaMail.root@jserv5...
          > HELP!!
          > I have spent a lot of time looking for an option to move jms on a
          > cluster, finally I can do this using distributed destination, I have two
          > memmbers(Topic) in the distributed destination topic, but when both of
          > them are active, the Message Driven Bean which is deployed on cluster
          > recieves 2 messages instead of 1, anyone please help me to change this to
          > have only one message instead of 2 !!!!!

Creating JMS Topic using JMX/MBeans Interface

Hello,
I'm trying to create a JMS Topic using MBeans. For this, I first
create a JMSTemplateMBean, then I create a JMSServerMBean (do
setTemporaryTemplate() and addTarget() on the latter) and finally
create JMSTopicMBean. On the JMSTopicMBean, I do setJNDIName() and
jmsServerMBean.addDestination(topicMBean).
Problem is that when I look in the console, I see only the JMS
Template and JMS Server (JMS Topic is NOT there). But if I try to
rerun my program, it gives 'InstanceAlreadyExistsException' on the
JMSTopic. Also, when I print out all the MBeans, the JMSTopic MBean is
there i.e. its been created. So why won't it show up in the Console ?
Any ideas are appreciated.
Thanks
-PG

I'm having exact same problem, except I'm trying to go through the weblogic.Admin command-line tool. (I'm working with version 6.1) First I create a JMSServer and set its Targets property. It shows up in console and I see the entry in config.xml. Then I create a new JMSTopic and set its JNDIName (I can't see this new topic from console, but an entry is made in config.xml and I can't create the topic again.) Then I invoke the addDestination method on the JMSServer MBean and pass in my new topic. The method returns "false", with no futher explanations or exceptions. If I try to go through the setDestinations property of the JMSServer MBean, the same thing happens: a silent failure.
I have no idea what to do! Is this a bug? Has anyone ever succeeded in doing this sort of thing?

Why 9 connections are automatically created per one jms topic?

Why 9 connections are automatically created per one jms topic?
Is it possible for one topic to have one connection, rather nine connecions?
If so, any drag concerning having one connection of one topic?
Let me know asap, it would be really appreciated.
<code>
public void connectJMS() {
try {
if (RTConst.getInstance().getConnectMode() != RTConst.NOTCONNECT) {
targetTCF = ServerDelegate.getTopicFactoryComm();
targetT = ServerDelegate.getTopicNameComm();
connection = targetTCF.createTopicConnection();
session = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
topicSubscriber = session.createSubscriber(targetT);
topicSubscriber.setMessageListener(this);
connection.start();
System.out.println("[CommJMSReceiver] Common Topic Connection successed");
} catch (Exception ex) {
System.out.println("[CommJMSReceiver] Common Topic Connection failed");
ex.printStackTrace();
</code>
Message was edited by:
PaulSheldonII_Screen

Why 9 connections are automatically created per one jms topic?
Is it possible for one topic to have one connection, rather nine connecions?
If so, any drag concerning having one connection of one topic?
Let me know asap, it would be really appreciated.
<code>
public void connectJMS() {
try {
if (RTConst.getInstance().getConnectMode() != RTConst.NOTCONNECT) {
targetTCF = ServerDelegate.getTopicFactoryComm();
targetT = ServerDelegate.getTopicNameComm();
connection = targetTCF.createTopicConnection();
session = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
topicSubscriber = session.createSubscriber(targetT);
topicSubscriber.setMessageListener(this);
connection.start();
System.out.println("[CommJMSReceiver] Common Topic Connection successed");
} catch (Exception ex) {
System.out.println("[CommJMSReceiver] Common Topic Connection failed");
ex.printStackTrace();
</code>
Message was edited by:
PaulSheldonII_Screen

Messages could not persist in jms Topic

Hi,
I implement JMS Topic in a SOA project in a cluster (two nodes) environment.
The problem is,
1. The jms topic service executes twice (because of 2 nodes in my cluster) and the message is also replicates but shows as a single message.
To overcome the above issue, I use "singleton" property in composite as well as EM console.
Then above problem has been resolved but creates below issue.
2. The issue is, in my case 2 servers in my cluster, if first server comes first to running state and jms Topic produces messages to first server.. then messages
persists pretty good.
But if first server comes first to running state and jms Topic produces messages on to 2nd server then messages are deleted immediately when they produced.
and vice-versa for 2nd server comes first to running state.
Friends, please help me on this.
Regards,
Venkat
Edited by: Pasagad on Mar 20, 2013 6:11 AM

What type of topic have you created ? Try not to create a distributed topic instead create topics for each managed server with same local jndi name.
see this blog: http://soa-street.blogspot.com/2010/08/subscribing-to-distributed-topic-within.html

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.

JNDI Lookup for JMS Topic issue.......!

Hi,
          Our application is deployed on two nodes (MS1 and MS2 in a cluster) and I created JMSServer on MS1, JMS ConnectionFactory and Distributed Topic are targeted on both MS1 and MS2 i.e on entire cluster.
          We have the JMS Code in postStart() method of starup class which extends ApplicationLifecycleListener which would create the JMS Subcriber and set the message listener on to it.
          code snippet:
               System.out.println("createSubscriber called");
               subSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
               // Lookup for the Topic
               Topic cadTopic = (Topic) ctx.lookup("JMSTopicLog4j");
               System.out.println("Topic is: " + cadTopic.getTopicName());
               // Create JMS Subscriber.
               cadSubscriber = subSession.createSubscriber(cadTopic);
               // Set the listener to Subscriber.
               cadSubscriber.setMessageListener(new CADMessageListener());
               topicConnection.start();
          When I start the cluster (managed Servers MS1 and MS2) for the first time and deploy the application on them (entire cluster) it works well i.e. message listener is active and able to receive messages published by publisher but when I try to stop and start MS2 it gives the following exception during server startup
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''; remaining name 'JMSTopicLog4j'
          at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1123)
          at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:250)
          at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
          at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:204)
          at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:267)
          at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
          Note: I thought my application context is getting started before JNDI tree is loaded but I could see that it is able to lookup the ConnectionFactory and throws the given exception when it comes to lookup code of JMS Topic.
          is there any configuration issue or am I missing something? Please help me in this regard.
          Thanks in advance.
          Kris.

Very interesting, I mean in the sense that we have the same setup, but instead of topic we are using the queues.
          And our problem is exactly the same,deployment works but after restart same javax.naming.NameNotFoundException happens on server 2.

JMS topic-cache topic is not getting broadcasting in other managed servers

Hi All,
Please give me some idea in fixing the issue that im facing.
I have created the JMS topic in my weblogic console server which has 2 managed servers.
I have a feature in my application which is kept in a cache that will be used by my JMS topic. If my request hits managed 1 server im able to see the newly created feature.
But the same feature is not working when i make the request hit managed 2 server.
It means the JMS topic is not getting broadcasted properly in other managed server. I dont want to go for a server recycle which will resolve the issue.
Please let me know if im not clear enough.
Below is the description provided by my partner on the same issue in his words..
"The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.
The same problem is observed in Production as well. Let us know if there is anything wrong in the way the JMS Topic is created or any other configuration is missing, that is not allowing the proper functioning of the Topic."
fyi...i have all my firewall enabled between the managed servers.And multicast property is also declared correctly only.

Please let me know if im not clear enough.No. Please explain again.
The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.Is it a distributed topic? Or does it mean a topic message doesnt get delivered to all subscribers?
ram.

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)

JMS Topic - Deliver to only one Durable Subscriber

Hi,
Is it possible to put a message onto a topic but only have it delivered to a single durable subscriber?
I realise this breaks the rules of what a topic is but this is for a scenario where a single subscriber has errored when processing the original message from the topic. I am putting a user interaction process to recover it and if the user selects ‘resubmit’ I want to put the message back on the topic but only deliver it to the one subscriber that failed to process the message.
My ways to achieve this (in order of preference) would be.
1.     JMS Adapter
2.     Writing Java to use JMS API
If neither of these are possible than:
3.     Create a System Resubmit queue and have every composite look for message on the resubmit queue (with their client ID) as well as the normal topic they use
Of course I would like to avoid 3 as it introduces a complication into every process we create that takes messages from a JMS Topic.
Thanks for your help.
Robert

I could suggest a (dirty) trick:
all subscribers subscribe to the topic using a filter (message selector, http://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncer)
SUBSCRIBER1 uses:
destination = ALL OR SUBSCRIBER1
SUBSCRIBER2 uses:
destination = ALL OR SUBSCRIBER2
etc
The first message has the property destination set to ALL, so all subscribers will process it.
The resubmitted message will have destination = SUBSCRIBER<N>, where N is the failed subscriber

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

Creating a secured DISTRIBUTED JMS topic.

Similar Messages

Maybe you are looking for