Sensor publish to jms topic

I am getting following error on server console . It works fine if i use "database" instead of jms topic in sensor action.
<2005-07-12 10:33:31,504> <ERROR> <default.collaxa.cube.sensor> <PCException::<init>> Reports Error.
<2005-07-12 10:33:31,506> <ERROR> <default.collaxa.cube.sensor> <PCException::<init>> A problem occurred while
processing reports data.
<2005-07-12 10:33:31,507> <ERROR> <default.collaxa.cube.sensor> <PCException::<init>> Please examine the log file to determine the problem.
<2005-07-12 10:33:31,512> <ERROR> <default.collaxa.cube.sensor> <QueuePublisher::publish> Reports Error.
<2005-07-12 10:33:31,513> <ERROR> <default.collaxa.cube.sensor> <QueuePublisher::publish> A problem occurred while processing reports data.
<2005-07-12 10:33:31,515> <ERROR> <default.collaxa.cube.sensor> <QueuePublisher::publish> Please examine the log file to determine the problem.
<2005-07-12 10:33:31,517> <ERROR> <default.collaxa.cube.sensor> <PCException::<init>> Data Publisher failed.
<2005-07-12 10:33:31,519> <ERROR> <default.collaxa.cube.sensor> <PCException::<init>> The Reporting Data Publisher JMSQueue of type jms/demoTopic failed.
<2005-07-12 10:33:31,521> <ERROR> <default.collaxa.cube.sensor> <PCException::<init>> Please examine the log file for more details.
<2005-07-12 10:33:31,523> <ERROR> <default.collaxa.cube.sensor> <DefaultDataRouter::send> Data Publisher failed.
<2005-07-12 10:33:31,524> <ERROR> <default.collaxa.cube.sensor> <DefaultDataRouter::send> The Reporting Data Publisher JMSQueue of type jms/demoTopic failed.
<2005-07-12 10:33:31,526> <ERROR> <default.collaxa.cube.sensor> <DefaultDataRouter::send> Please examine the log file for more details.
Which log will have more details? what setup is required?

Hi,
<2005-07-12 10:33:31,519> <ERROR> <default.collaxa.cube.sensor> <PCException::<init>> The Reporting Data Publisher JMSQueue of type jms/demoTopic failed.
The Above line suggests that you have configured your sensor for JMS Queue while the target you have provided is of JMS Topic.
Please provide the follwing for the Sensor Action configuration if you want to use JMS Topic.
Publish Type : JMS Topic
JMS Connection Factory : jms/TopicConnectionFactory
Publish Target : jms/demoTopic
HTH
Dhaval

Similar Messages

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

JMS Topic - Can there be multiple pubs/subs

          I belive JMS Topic supports multiple publishers, subscribers
          for the same topic right? I am sure about the multiple subsicriber part because
          I have done it before (with one publisher). However, I am changing my
          design to have multiple publishers now as well. Is this possible?
          Thanks


Ashique wrote:
          > I belive JMS Topic supports multiple publishers, subscribers
          > for the same topic right?
          Yes.
          > I am sure about the multiple subsicriber part because
          > I have done it before (with one publisher). However, I am changing my
          > design to have multiple publishers now as well. Is this possible?
          >
          Yes.
          >
          > Thanks

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

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

Jms adapter not polling messages from jms topic

Hi
We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
<adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
      
      <property name="PayloadType" value="TextMessage"/>
      
      <property name="UseMessageListener" value="true"/>
      <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
    </activation-spec>
</endpoint-activation>
</adapter-config>
If we remove Durable subscriber and message selector properties,its able to poll messages.
Any pointer will help
thanks in advance
Baji

After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
<property name="UseMessageListener" value="false"/>
But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
<property name="DurableSubscriber" value="XYZ"/>
If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
Thanks
Baji

Newbie question about JMS topic and OSB

So here is what I want to achieve:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. The way I picture this is that a producer will invoke a proxy to publish a message. The subscriber will (asynchronously) invoke another proxy to pickup the message.
Is this possible and how do I go about doing this?
thanks
Edited by: user10341230 on Apr 28, 2010 8:49 AM

Hi there,
user10341230 wrote:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. > it's not really clear what you want to achieve here.
you say
user10341230 wrote:
The way I picture this is that a producer will invoke a proxy to publish a message.you need a proxy with whatever inbound protocol you like (http, file, mail...), which through a jms business service push the message to the Topic.
you say
user10341230 wrote:
The subscriber will (asynchronously) invoke another proxy to pickup the messagethe subscriber can be either asyncrhnous, in which case you need a proxy service with inbound protocol jms. or as you probably need a synchronous one
in which case you need another proxy with whatever inbound protocol you like whch once called in its pipeline calls some pojo class to read from this topic synchrnously (you need a durable subsciber).
Regards,
Tony
ps: have a look http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/jms/design_best_practices.html#wp1058694

How to express application metadata for a JMS topic?

Hi there,
I would like to be able to provide application specific metadata associated with messages for an entire topic. I'd be interested in learning of methods to do this in a JMS way i.e. avoiding something implementation specific.
I'm using MapMessage objects to send XML payloads. The name in the name/value pair is the XML element name. An example pair name might be:
/j:FeatureCollection/@id... which means that the value of the name/value pair relates to the id attribute of the XML node named "j:FeatureCollection".
I'd like to be to associate metadata with my message so that I may declare the XML namespaces and schema locations.
One thought that I had was to use message properties e.g.:
message.setStringProperty(
"xmlns:j",
"http://www.classactionpl.com/gml/journeyFeatures");My concern though is that property information will be conveyed with each message sent and thus consume bandwidth, perhaps unnecessarily. Consumers are typically only going to be interested in the metadata at the start of the subscription to resolve XML namespace mappings.
Ideally, given that my metadata relates to information published on the topic as a whole, it'd be great to have the metadata associated with the topic instead. Can this be achieved?
FYI: I'm presently using ActiveMQ 4.1 and may also use IBM's Websphere MQ in the future.
Thanks for any help.
Kind regards,
Christopher

Thanks for your reply.
I really want to keep the metadata associated with the data. It seems like the properties of a message can help me here. I'm not sure that it is necessarily beyond the scope of JMS.
Any further thoughts?
Cheers,
-C

Publishing message to Topic from a standalone application.

Hi,
I have a standalone Java program which will publish a message to the TOPIC. I have found the code to publish to the topic. Please anyone of you can tell me, if I can do it from the standalone application and if yes then how, please provide a code example if possible. We need to specify JNDI's, so tell me where we configure these JNDIs and how would my standalone program would connect to it.

[http://www.google.com/search?q=jms+publish+standalone+example|http://www.google.com/search?q=jms+publish+standalone+example]
Edited by: jtahlborn on Sep 4, 2008 9:07 PM

Receive asynchronous message from JMS topic over web service

Hi,
I have a JMS topic and I want to expose it as a web service so that clients can
make durable subcription to the topic and receive messages asynchronously. What
is the best way of doing this ? Is there a portable (to other containers) way
of do this ? If not, is there a web logic specific way of doing this ?
Thanks,
Siva

So you expect clients to be receiving SOAP messages over HTTP? In this
case, the clients are really servers that are capable of servicing SOAP
requests, correct? And how about the senders: are they also using
SOAP/HTTP to send messages that are delivered to the receivers?
It should be possible to write this yourself using JMS not as the
transport, but as a mechanism for distributing the message to a set of
clients. You'll need to implement a Web Service for publishing to a
topic, an operation for registering an end point to recieve messages,
and an MDB (or other form of JMS subscriber) executing on the server to
relay the message to the end point.
Siva wrote:
Hi,
I have a JMS topic and I want to expose it as a web service so that clients can
make durable subcription to the topic and receive messages asynchronously. What
is the best way of doing this ? Is there a portable (to other containers) way
of do this ? If not, is there a web logic specific way of doing this ?
Thanks,
Siva

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 Topics translate to Queues behind the scenes?

Hi There:
In discussing JMS implementation with coworkers I found someone mention that even if we created topics and have users subscribed to those topics, those topics get translated into individual queues per topic per user. So the queue in affect gets subscribed to the topic and the user is actually subscribed to the queue. While I can imagine that this kind of implementation makes sense for reliable delivery, I find it hard to believe that this is the way JMS implements topics internally.
Can someone throw some lite on this please?

RajMap wrote:
Well the content gets replicated to the queues when it is not necessary to do that. If I am not doing reliable delivery, then the message that is published to the topic is delivered to the users that are subscribed to the topic at the point in time, and to do that I do not see the need to implement it via queues. Like I mentioned before for reliable delivery it makes sense to implement them to queues.
And secondly it might lead to an explosion of queues internally. Consider for e.g. if we have say 5000 topics and about 10-15 subscribers for each topic, it will result in up to 75000 queues. I am not sure if that is a big number for queues, but it feel larger than what I designed for because in my mind I am thinking 4000-5000 topics.you are making a lot of conjectures based on entirely abstract concepts. what is a "queue"? what is a "topic"? these are just abstract ideas used by the jms spec. the words "queue" and "topic" define a bunch of behavior, but say nothing about how you need to implement that behavior. is 75000 queues a lot of queues? who knows, depends how i choose to implement a queue. is the data "replicated" to each queue in a topic? who knows, depends how i choose to store data. you can't make any of these statements outside of a specific implementation of the jms spec.

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.

Messages posted to JMS Topic from OSB disappear even when not subscribed

Hi,
We are using an OSB service to publish xml messages to a weblogic JMS Topic. Message is persistent. There are no consumers for the Topic. There is no expiration limit set.
We are able to see the message from OSB reach the Topic. It stays in the Topic for a few seconds and then disappears.
The State of the message shows up as "send transaction" on the Topic in the weblogic console. And it shows up as Message Pending instead of Message Current.
Is there a way to ensure that the message stays in the Topic till it is consumed by a subscriber?
Thanks,
Senthil

Hi Senthil,
The topic persists messages only for subscribers, if there is no subscribers, then it is not necessary to persist the message.
This is the same case for you as well, as there are no subscribers the message gets deleted.
So first you need to have atleast one subscriber first (A dummy proxy that is reading from the topic) and then post to the topic (through your OSB service or hermes jms tool, etc .. ) . Then if you try to go and check the topic you will be able to see the message.
Hope this information helps.
Thanks,
Patrick
Edited by: Patrick Taylor on May 13, 2011 2:40 PM

JMS Topic Sample Needed

Hi,
Can someone point me to a doc which explains how to develope a sample JMS application using standalone oc4j.
And also what are the properties that are used to create the InitialContext for the oc4j JMS Directory service.
i. e
Properties env = new Properties( );
env.put(Context.SECURITY_PRINCIPAL, "");
env.put(Context.SECURITY_CREDENTIALS, "");
env.put(Context.INITIAL_CONTEXT_FACTORY,"");
env.put(Context.PROVIDER_URL,"");
InitialContext jndi = new InitialContext(env);
It will be of great help if u can share a sample for the above.
Thx,
Siddhardha.

Ashique wrote:
          > I belive JMS Topic supports multiple publishers, subscribers
          > for the same topic right?
          Yes.
          > I am sure about the multiple subsicriber part because
          > I have done it before (with one publisher). However, I am changing my
          > design to have multiple publishers now as well. Is this possible?
          >
          Yes.
          >
          > Thanks

Sensor publish to jms topic

Similar Messages

Maybe you are looking for