JMS adapter transaction. Rollback message to queue.

Hi all !
A have question about jms adapter transaction. My composite application has 3 steps : JMS adapter (listener), mediator, WS adapter. JMS adapter listen queue push message to mediator, mediator invoke web service. If ws not available (server down), mediator try recovery 5 times. After 5 times, reject message from queue. I wont rollback message to queue. I saw examples with JMS + BPEL, but it not help me. Anybody can help me.

Hi,
You don’t need to catch a mediator fault – you can let it rollback to the JMS Queue and let the Queue do the retries.
To get the retries working, log in to the weblogic console and navigate to JMS Modules -> Your Module -> Your Queue -> Configuration -> Delivery Failure
Here you will find options for Redelivery Limit. Set this to the number of retries you need.
Then navigate to the connection factory you want and set the redelivery delay.
This should get your desired behaviour, but once the message has failed it will be discarded. If you prefer to put it on an error queue you can create an error queue, and in the original queue’s, goto Delivery Failure, change the expireation policy and set the Error Destination to be your error queue.
Hope that helps!
Robert

Similar Messages

MDB,MDB container or JMS adapter stops processing messages from JMS queue

Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AM

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

JMS Adapter Supports below message

Hi Frnds,
I am working on one scenario i have to read and write RFH2 Message from MQ,we decided to use jms adapter.
JMS Adapter supports below Message to put in MQ,
<Data>
     <MQRFH2>
          <usr>
               <TransactionType>GL_Update</TransactionType>
               <Environment>LIVE</Environment>
               <SourceScheme>EANCM</SourceScheme>
               <SourceApplicationId>5051150003606</SourceApplicationId>
               <DestScheme>EANCM</DestScheme>
               <DestinationRouting>5051150003330</DestinationRouting>
               <OriginalRouting/>
               <MessageRecordCount>1</MessageRecordCount>
               <BusinessTransactionId>20090405193001</BusinessTransactionId>
               <ParentBusTID/>
               <ParentBusId/>
               <EECode>Y</EECode>
          </usr>
          <mcd>
               <Msd>xml</Msd>
          </mcd>
     </MQRFH2>
     <Message>
          <GL_Update>
               <header>
                    <SourceEAN>5051150003606</SourceEAN>
                    <DestinationEAN>5051150003330</DestinationEAN>
               </header>
               <detail>
                    <AuthorisedUser/>
                    <HeaderText/>
                    <HeaderReference/>
                    <PostingItem>
                         <ProfitCentre>7027101000</ProfitCentre>
                         <CostCentre/>
                         <AccountCode>0001413150</AccountCode>
                         <GlobalBusinessIdentifier>AU10</GlobalBusinessIdentifier>
                         <MonetaryAmount>0000000100.00</MonetaryAmount>
                         <GlobalCurrencyCode>AUD</GlobalCurrencyCode>
                         <RunDate>20080725</RunDate>
                         <Description>IV006270M000000000000000000001</Description>
                         <WorkBreakdownStructureElement/>
                         <BudgetRequest/>
                         <TransactionType/>
                         <TransactionNumber/>
                         <PostingKey>50</PostingKey>
                         <SalesTax>
                              <SalesTaxCode/>
                              <SalesTaxAmount/>
                         </SalesTax>
                         <PersonnelNumber/>
                         <Assignment/>
                         <CalculateTaxBase/>
                         <BaselineDate/>
                         <PaymentTerms/>
                         <MedicalReference/>
                    </PostingItem>
                    <PostingItem>
                         <ProfitCentre/>
                         <CostCentre/>
                         <SalesTax>
                              <SalesTaxCode>P3</SalesTaxCode>
                         </SalesTax>
                    </PostingItem>
                    <PostingItem>
                         <ProfitCentre>7022001001</ProfitCentre>
                         <CostCentre/>
                         <AccountCode>0001701001</AccountCode>
                    </PostingItem>
               </detail>
               <trailer>
                    <thisDocumentGenerationDateTime>20090405T072928Z</thisDocumentGenerationDateTime>
                    <thisDocumentIdentifier>20090405T072928Z</thisDocumentIdentifier>
               </trailer>
          </GL_Update>
     </Message>
</Data>
please help me on this
it possible to achieve using JMS adapter or not?? what is the alternative solution ??
Regards,
raj

Hi RSR,
JMS is the better way to connect sonic MQ.below iam attaching you few points while using JMS.
1.for the JMS adapter an external driver is needed (java archive)
2.this archive is provided by the respective provider of the queuing system
3.the driver has to be deployed via SDM , see XI configuration guide for details
4.Routing rules and sender has to be specified as for any other channel in the directory
    object model
5.the message header information is determined from the appropriate sender
   agreement for the communication channel
6.the communication channel defined must be used in exactly one sender agreement
7.at least the interface name and the sender service must be qualified in the
    sender agreement ,other fields are optional
Depending on the transport protocol selected, specify the following :
8.For Sonic MQ JMS Provider :
·        Java class QueueConnectionFactory
·        Java class queue
·        IP address or server name
·        Server port
·        JMS queue
9.JNDI JMS Provider Lookup
·        JNDI name of QueueConnectionFactory
·        JNDI name of JMS queue
·        Name of JNDI Initial Context Factory
·        Address of JNDI server
·        JNDI users
·        JNDI password with confirmation
10.
For WebSphereMQ (MQ Series) JMS Provider
·        Java class QueueConnectionFactory
·        Java class queue
·        IP address or server name
·        Queue manager name
·        Channel name
·        JMS queue
·        Character set for non-ASCll names
·        Transport/network protocol
·        Target client
11.
JMS Provider Administered Objects via File
   File name of serialized object QueueConnectionFactory
   File name of serialized object Queue
With Rgds,
MF.Haq

Restrict message volume through JMS adapter (not individual message size)

Hi, does anyone know of a way to restrict the flow of messages through a JMS adapter? For example, If I wanted to only allow up to 1000 messages to be sent in an hour to a particular system. The rest should just be queued in the Adapter Engine until the next hour begins in order to smooth out the load on the recieving system.
I know this is poor design but there is a system that is getting overwhelmed and cannot be easily changed right away. I'd like a way to control this from the middleware using standard PI (no ccBPM).
Any ideas?
Thanks in advance,
Aaron

Stefan, thank you for the idea, that is a good one.
I'm going to assume there is nothing specific we can do in the SAP JMS adapter to control the flow, and look to a solution in the queueing software like you suggested or the 3rd party application.
-Aaron

JMS adapter with complex messages

Each of our MQ Series messages contain several transactions. Our standard format is:
<Message>
<RecordSet(1..n)>
HeaderRecord
Item Record(1..n)
</RecordSet>
</Message>
Does anyone have an example for how this would be done in XI 3.0? I have seen how this can be done with the file adapter, but with the JMS adapter do I need to use BPM?
Thanks,
Andrew

Each of our MQ Series messages contain several transactions. Our standard format is:
<Message>
<RecordSet(1..n)>
HeaderRecord
Item Record(1..n)
</RecordSet>
</Message>
Does anyone have an example for how this would be done in XI 3.0? I have seen how this can be done with the file adapter, but with the JMS adapter do I need to use BPM?
Thanks,
Andrew

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

Distributed topic - JMS adapter consuming duplicate messages

We have distributed topic thats consumed by a composite (JMSadpter in mediator).
We see for every one message sent the composite consumes the message twice. (With forwarding policy set to partitioned)
Is this an expected behavior? and how do we make the consumer (JMS adapter) consume only once per message
Thanks
Vijay

From the documentation (provided here: http://download.oracle.com/docs/cd/E21764_01/integration.1111/e10231/adptr_jms.htm)
The JMS API specifies three types of acknowledgments that can be sent by the JMS publisher:
- DUPS_OK_ACKNOWLEDGE, for consumers that are not concerned about duplicate messages
- AUTO_ACKNOWLEDGE, in which the session automatically acknowledges the receipt of a message
- CLIENT_ACKNOWLEDGE, in which the client acknowledges the message by calling the message's acknowledge method
Could you check in the weblogic-ra.xml what acknowledge mode has been configured:
<property>
<name>AcknowledgeMode</name>
<value>AUTO_ACKNOWLEDGE</value>
</property>
...Note that when DUPS_OK_ACKNOWLEDGE is used it can happen that a message is consumed more than once.
Are you also sure that the message is not produced twice?
Seminar on Cloud Computing - http://middlewaremagic.com/weblogic/?p=7387

JMS adapter(MQSeries): Authorization check for queue access

Hi All,
We are getting the same error as mentioned in the note no.749743 now we are following the note but we are not able to figure out what specific SP level we need to apply as it is very generalised.
And From where we can get a newer version of the JMS Adapter.
How can we test our configuration directory object? I cant see any test configuration option under tools menu.
Please help me out.
Thanks in Advance
Regards
rahul

Rahul
Since you are using transport protocol as WebSphereMQ(Non-JMS)you have to provide some of the JMS Provider specific settings as mentioned in:
http://help.sap.com/saphelp_nw04s/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
---Mohan

Oracle JMS Adapter - Bpel Pick message from AQ based on the correlationId?

Hello,
I'm experiencing an issue during pricking the messages from AQ based on the JMSCorrelationID in Asynchronously.
I've developed asynchronous BPEL services, which will post messages in AQ (Inbound), the same service will liston response from Out queue.
Currently my service is consuming all messages, i want to consume only relevant response message based on the correlation Id.
Could you please advise me?
Regards,
Paddy.

Thanks MaShek for your replay,
During process invocation I've generated guid and set this value to JMSCorrelationID property which will set as message corrlationID, same JMSCorrelationID coming in response as well, I've set on message property same JMSCorrelationID which I set in invocation.
If same message response comes then the pick activity is working fine that means consumed message and correlation correctly, but other messages also consuming and then rejecting message. I want to restrict this.
Only relevant correlationid messages need to pick and process.
If any suggestions appreciated.
Note: I'm using Jdev11.1.15,
Regards,
Paddy

JMS Sender Adapter EOIO with different messages in Queue to RFC

Dear Colleague,
In one of my scenarios i am using JMS Sender Adapter and Websphere MQ series.
In my MQ Series Queue i get different Messages with Different Structures.
for e.g in my MQ Series Queue Q1 i have M1, M2, M3 coming in Order.
Now i need to doa Mapping of M1 to a Standard BAPI B1 call through RFC at the reciever side.
Now i need to doa Mapping of M2 to a Standard BAPI B2 call through RFC at the reciever side.
Now i need to doa Mapping of M3 to a Standard BAPI B3 call through RFC at the reciever side.
We are aware that on Receiver side we can have multiple Recievr Determinations.so i can send it to 3 different BAPIs.
Question:
But how do i split the Messges which are coming out of MQ series Q from JMS to 3 different Mapping Structures as we knwo that we do not 'Multiple Sender Interface Determinations' from Determined based on the Message which is coming in.
Hope i have been clear in making myself understand about the problem given above.
I have alos given below the same in a bit Graphical Form.
MQ Series --> M3, M2, M1(Messages) --> JMS Adapte(EOIO) --> M1(Message) -> RFC -> B1(Bapi)
--> JMS Adapte(EOIO) --> M2(Message) -> RFC -> B2(Bapi)
--> JMS Adapte(EOIO) --> M3(Message) -> RFC -> B3(Bapi)
Is it possible to achieve the above result. Answers fo the solution are most welcome. These can be also from the new Netweaver Release Versions. If we have the solution to these in New version we will implment the New Netweaver Releases.
Thanks & Warm Regards
Venugopal

Dear Kai,
if i have 3 MQ series Queues then how are we going to maintain the flow of the Messages in the same order in which has come into MQ series queues.
this mesans to say that all the Message come in Parallel out from JMS or MQ side and will be mapped onto Reciever side.
But in my case i wil need to have M1 first M2 second and M3 third.
This means to say that M1 recived and acknowledged then M2 should come and acknowledged and then M3 should be acknowledged.
How this will be possible with your solution of making 3 MQ series Queues.
Please do let me know.
Thanks
Venugopal

Mediator Resequencer,JMS Adapter: queue consumers increase from PS2 to PS4

Hi,
We have an environment using SOA Suite and Mediator Resequencer, it is using a FIFO approach. It has been running fine in SOA Suite version 11.1.1.3.
We are using a JMS Adapter, consuming the messages from the UDD queues as we have a SOA cluster of two managed servers.
Well we are now doing some test for upgrading to PS4 (11.1.15) and we have noticed some differences after the upgrade in terms of # consumers on the UDD queues.
In 11.1.1.3 eache member of the UDD was showing just 1 consumer. Looks like this is the right configuration when using and mediator resequencer FIFO approach, as they say you need to have a single-threaded approach to avoid unpredictible result.
After upgrade that, we have noticed that in 11.1.1.5 each UDD member shows 2 consumers, we have not changed anything, we just follow the upgrade guide to do that. To be honest we are not sure wheter it is a problem or not.
Can anybody advise about that? If it is an issue, How and where can configure it to get back to 1 consumer connected to UDD member?
Thanks a lot!

The Bridge is configured to use the MQ CF and destination directly without the foreign JMS wrapper. Does this make any difference to the bridge's transactional behaviour with MQ?
Even with the foreign jms wrapper, the local jndi name of the MQ CF is still mapped to com.ibm.mq.jms.MQXAQueueConnectionFactory class. So I think there is no wrapper classes are used from foreign JMS perspective. But if a bridge is configured to lookup local jndi, does it add any wrapper classes which handles the XA interactions with MQ in a different way ?
I am trying to see if introducing a foreign server resolves the problem. Not sure if its worth to take this path.
Thanks in advance.
Regards,
Atheek

Processing messages from MQ by JMS adapter

Hi,
I have a JMS adapter which reads messages from MQ and invokes a real time service.
I am facing a problem.
Suppose after processing my 3rd message fails , i get the error
com.acta.adapter.sdk.RecoverableOperationAdapterException: JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERATION TO CONTINUE.
Now ideally the error messages should go into an error queue and the remaining messages should be processed.
But the remaining messages are also not getting processed.All subsequent messages after erroneous message also get into error q.
I have set continue after error property(In operations configuration) to True.
I am using Get operation for JMS adapter.
Any idea what could solve this issue?

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

Dequeue jms messages using JMS adapter

Hi,
I have created jms server, modules, queue from console-messaging-jms modules.
I am trying to create a soa composite to consume message from this queue.
In JMS adapter wizard - step 7 - i have selected the destination queue. In this step, what should be the jndi name?
do i need to update weblogic-ra.xml file?
Can someone please point me to the steps/doc to create jms adapter to consume message from Oracle Weblogic JMS? (basically configure deployment descriptor)
Thanks
Ganesh

By passing username/password in the outbound connection pool, i was able to connect to the secured weblogic jms..
This was my config for eis/wls/Queue connection pool..
     AcknowledgeMode     java.lang.String     AUTO_ACKNOWLEDGE
     ConnectionFactoryLocation     java.lang.String     weblogic.jms.XAConnectionFactory
     FactoryProperties     java.lang.String
     IsTopic     java.lang.Boolean     false
     IsTransacted     java.lang.Boolean     false
     Password     java.lang.String     weblogic123
     Username     java.lang.String     weblogic
After making the change ( remember to hit enter after modifying password and username fields, else change wont persist) , i saved it with a new deployment plan and updated the deployment with the new plan. Then redeployed the composite containing the jms adapter and I am able to see a consumer created for the queue.

JMS-Adapter with persistent Queues (DB): ORABPEL-12166

Hi,
does anybody know what the error:
file:/C:/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/Provisioning/tmp/.bpel_SenderProvisioning_1.0_bb735430814144c8f5f279c73842c3d4.tmp/JMS_Provisiong_A.wsdl [ Produce_Message_ptt::Produce_Message(Request) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_ENQUEUE_ERR.
Die Nachricht konnte aufgrund von folgender Fehlerbedingung nicht in die Queue gestellt werden:.
; nested exception is:
ORABPEL-12166
ERRJMS_ENQUEUE_ERR.
Die Nachricht konnte aufgrund von folgender Fehlerbedingung nicht in die Queue gestellt werden:.
Weitere Informationen hierzu finden Sie in der Log-Datei.
means?
Where can i find the logs?

This is most likely caused by a nonexistent or misconfigured queue.
For a JMS adapter, make sure your AQ queue/topic is set up as JMSType. Make sure you've spelled everything correctly.
To find the logs for ESB go to:
$ORACLE_HOME/j2ee/oc4j_soa/log/oc4j see log.xml
For BPEL go to
$ORACLE_HOME/bpel/domains/default/logs see domain.log
You may also find errors in the OPMN logs:
$ORACLE_HOME/opmn/logs
see default_group~oc4j_soa~default_group~1.log
You will have to turn up log levels to "FINE" or "FINER" for ESB or DEBUG for BPEL to get anything close to a meaningful message. For my most recent error on ESB the "FINER" setting yielded the following message for this error:
</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[ORABPEL-12166
ERRJMS_ENQUEUE_ERR.
Could not enqueue message due to the following error condition:.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:237)
at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:143)
at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:197)
at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:156)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:485)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:736)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:497)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:430)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:447)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:184)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:112)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:106)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:85)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:105)
at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:273)
at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:212)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:197)
at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:82)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:69)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(ESBListenerImpl.java:369)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(ESBListenerImpl.java:295)
at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:293)
at oracle.tip.adapter.jms.inbound.JmsConsumer.doSend(JmsConsumer.java:571)
at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:507)
at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:353)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:274)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.UnsupportedOperationException: publish is called without a valid Topic
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1252)
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:215)
... 34 more
Hope that helps. See the SOA admin guide for help with setting log levels:
Here's where you can find all App Server books for SOA Suite:
http://download-west.oracle.com/docs/cd/B31017_01/nav/docindex.htm
Peace,
G.

Configuration for sync/async bridge in Jms adapter

Can someone give me a hint what I might be doing wrong?
The scenario is: synchronous proxy to jms.
Integration repository:
Created synchronous outbound interface and synchronous inbound interface, message mapping, interface mapping.
Integration directory:
Created jms receiver communication channel and jms sender communication channel and configured them according "How to correlate jms messages".
Created receiver determination, interface determination and receiver agreement.
No sender agreement necessary for proxy sender.
So far so good, but...
Both the receiver and sender jms adapter have its own queue (the receiving system will get the request in one queue and put the response in another).
<b>How does the waiting jms receiver adapter know where to expect the answer?</b>
When I test this scenario the (outbound) message get the status "Log version" (abap moni) and "To be delivered" (java moni).
PS:
The testing is performed by using the tool rfhutil. With this tool you can read and write directly from/to the MQ queues where the jms adapters are pointing to.
After receipt of the request in the queue of the reveicer jms communication channel, I manually put a message in the queue of the sender jms communication channel with the XI message ID filled in the correlation ID.

More information, In the jms adapter the following error appears:
XI inbound processing failed for message at time 2007-06-11|11:12:48.908+0100. JMS and XI identifiers for the message are ID:414d512052545849444556312020202045f55b6c20d73102 and 4e5bff20-1804-11dc-c2b4-00096b6ed15c respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Minimum address data not configured. Field InterfaceNamespace is empty.
     at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:1516)
     at com.ibm.mq.jms.MQMessageConsumer.receiveAsyncQ(MQMessageConsumer.java:2538)
     at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4260)

JMS adapter transaction. Rollback message to queue.

Similar Messages

Maybe you are looking for