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

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 does not recover from error

Hello everyone,
We are noticing some strange behavior with the JMS adapter, and would like your help. We have messages coming into XI from WebSphere MQ. We have configured a Sender Comm channel (MQ_SENDER) with the appropriate JMS adapter, with a specified queue name (TEST.Q) . We have installed the appropriate MQ-JMS libraries for v6.0.
Here's the problem scenario... initially the application sending the messages to the specified queue was putting an incorrectly formatted MQRFH2 structure in the message. Predictably, this caused our comm channel to fail, and it shows up on the adapter monitor in the failed state with the message "MQJMS1050: The MQRFH2 header has an incorrect format Code: MQJMS1050". This in itself is not a problem, we realized that the application was sending a malformed message. The problem occurs when we fixed the sending application to completely strip out the MQRFH2 header altogether. When the new message is sent, the comm channel seems "stuck" on the previous error, and does not even pick up the new message from the queue. The adapter monitor continues to show the same error for the comm channel. Now when we modified the comm channel to read from a DIFFERENT queue (TEST2.Q) , the comm channel got out of the error state and is able to successfully process new messages coming into that queue. However, when we revert the comm channel back to the original queue (TEST.Q) it reverts back to the original MQJMS1050 error, and does not pick up new messages on the queue.
Any assistance would be greatly appreciated...

Hi,
1) Try to refresh the metadata
2) Check the Queue status
3) Once again check the Queue name. try to make the Sender JMS adapter inactive .save it..again make it active and save it and activate the object.
4) Refresh the Cache :
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

JMS Adapter - Queue Message Loss

Hi Folks,
I am working on MQ - to - File Scenario, working fine. But some Cases message is fail in SMQ1 & SMQ2, I am not able to re-process that message because of that messages are System Error.
So My Problem was, Once JMS Adapter is pick the Data from MQ, no more data in MQ, some cases message is fail, We can't re-process that message, So i dont want to lose that data.
How can i recover that MQ Data...
Thanks for help,

Hi S R,
What is the error detail in SMQ1,SMQ2?
Did you try to reprocess them from execute luws? try to change the status to recorded if possible.then execute again.
thanks

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

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 adapter for MQSeries: Changing from MQ5.3 to 6.X libraries

Hi,
Can someone point in the direction of documentation as to how I would migrate/update a BPEL 10.1.3.5.0 environment using JMS adapters for MQSeries 5.3 to use new libraries for MQSeries 6.x.
In a test env I have located the following, but I am not sure now to proceed.
[bpel@omv2rrm2 5.3]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3
[bpel@omv2rrm2 5.3]$
[bpel@omv2rrm2 5.3]$ ls -l
total 2124
-rwx------ 1 bpel dba 352652 Apr 17 2008 com.ibm.mq-5.3.jar
-rwx------ 1 bpel dba 1798896 Apr 17 2008 com.ibm.mqjms-5.3.jar
[bpel@omv2rrm2 5.3]$
...and...
[bpel@omv2rrm2 config]$ pwd
/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/config
[bpel@omv2rrm2 config]$ cat server.xml
<?xml version="1.0"?>
<application-server xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/application-server-10_1.xsd" localhostIsAdmin="true"
application-directory="../applications"
check-for-updates="adminClientOnly"
deployment-directory="../application-deployments"
connector-directory="../connectors"
schema-major-version="10" schema-minor-version="0" >
<shared-library name="global.libraries" version="1.0" library-compatible="true">
<code-source path="../applib"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>
<shared-library name="oracle.mqseries" version="5.3">
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mqjms-5.3.jar"/>
<code-source path="/opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/oc4j_soa/shared-lib/oracle.mqseries/5.3/com.ibm.mq-5.3.jar"/>
<import-shared-library name="oracle.ws.jaxrpc"/>
</shared-library>

Just upgrade your SOA to 10.1.3.5.0 and then point to the newer MQ jars in those 2 files.

Converting QoS from EO to EOIO in Receiver JMS Adapter

Hello All -
We are currently working with SAP XI 3.0 SP12. Our scenario is something like this:
IDoc -> XI (BPM) -> JMS Adapter
The BPM splits up the incoming IDoc into multiple JMS messages.
The problem is that when the BPM sends the message to the JMS adapter the QoS changes from EOIO to EO. This essentially means that when the messages are written to the JMS Queues, there is no gurantee that they would be written in exactly the same order in which they are produced.
The requirement is to write the messages in exactly the same order in the target queues.
One solution is to capture the transport level acknoledgements and then send the next message from the BPM only on the receipt of the acknoledgement which takes a lot of time.
Is there any other mechanism to ensure the messages going out in an EOIO fashion.
Ashish

Its like this , i ve file -> bpm -> idoc scenario. 've configured EOIO as the QOS for both adapters. file adapter is configured to pick up a pattern , say *.abc.
The picking option is "By Date". Say there are 5 files in the directory before a particular polling interval which has about 5 sec time delay b/w them in their timestamp.
Now the file adpater picks the files in order , delivers it to ccBPM, i can see 5 diff ccBPM instances(diff workitem IDs).
Say, the third file has less data , the transformation happens faster in the 3rd ccBPM instance and so it delivers it to the idoc adapter vefore the 1st or 2nd one completes. So my order is lost.
Now , i tried setting "transport ack" in send step , but didnt help.Is there any other specific setting to be done ?
Thanks
Saravana

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

Problem in JMS-Adapter with CharacterSet Websphere MQ

Hi,
we have the following scenario:
JMS -> PI -> File
We have a local Websphere MQ Queue Manager and the follwoing configuration in our sender adapter:
Transport-Protocol: WebSphere MQ (non JMS)
Message-Protocol: JMS 1.x
ConnectionFactory: com.ibm.mq.jms.MQQueueConnectionFactory
Java-class Queue: com.ibm.mq.jms.MQQueue
CCSID: 819
Transport: TCP/IP
JMS-conform: WebSphere MQ (non JMS)
In the local queue manager the messages (XML-Messages with header <?xml version="1.0" encoding="ISO-8859-1"?>) have characterSet 819 (ISO-8859-1). That's correct. You can open the files with XMLSpy and it works.
When we receive the messages by our JMS Sender Adapter all the character seems to be in UTF-8 and I don't know why. All the special characters are wrong cause the header of the XML-message shows ISO-8859-1 but all the signs are decoded in UTF-8.
In the other direction (JMS Receiver adapter, File -> PI - JMS) we have the same problem.
We create a ISO-8859-1 message in mapping (and it is really ISO-8859-1) and send it via JMS Receiver Adapter to the local message queue. But there the message arrives in UTF-8 encoding. I don't understand this.
Does anybody know what could be the cause for this?
Does the JMS adapter convert the messages from ISO-8859-1 into UTF-8?
Are there any parameters we have to set?
I hope anybody has an idea what's wrong.
Regards
Thorsten
Edited by: Thorsten Hautz on Oct 12, 2010 5:42 PM

Hi,
thanks a lot for your replies.
our driver settings are correct (as I can see).
I removed value 819 from CCSID, but we have the same effect.
The messages in the local queue manager are TextMessages in XML.
Does anybody know, if we need the standard modules (ConvertJMSMessageToBinary and ConvertBinaryToXMBMessage) in this case?
Is it possible to set the CCSID for the message payload anywhere in the configuration?
The CCSID in the Source tab doesn't have any influence to the encoding of the payload message, only to the header data.
Regards
Thorsten

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.

Configuring JMS adapter

We have 3 instance of BPEL process manager - DEV, TEST and PROD. Once development completes in DEV instance, it is moved to TEST for testing and then to PROD.
When the BPEL process is moved from one environment to another, we have to manully change the JMS adapter settings like IP address etc (3rd Party JMS Topic). This sometimes causes error due to human mistake.
Is there any method by which we can maintain a seperate configuration/properties file wherein these details can be maintained and referenced in JMS adapter WSDL so that we need not change the settings of JMS adapter everytime we migrate from one env. to another?
Regards

Just to understand your problem a little better, say you have processes A and B that you promote b/w these 3 environments. Also, say A is a standalone service invokable by external clients; say B is a service that is invokable by an external client and called by A as well.
Now, in this example, both A and B have web-service end points that change from one env to another.
W.r.t process A's caller, it should know the correct endpoint to invoke the service. Now if there is just one external client that is switching b/w the various environments, it has the responsibility of making this switch b/w the various endpoints (dev to test to prod). Now if this external client is an Oracle BPEL process as well, refer to solution below.
As far as process A's implementation goes, yes, it would have to change to invoke process B correctly. So, in dev, A should call B in dev; in stage/prod, A should call B in stage/prod. BPEL PM provides a solution to accomplish this via a customize ant task - refer to the section titled "Deploying to Multiple Environments with Different Configuration Values" in "Oracle® BPEL Process Manager Developer’s Guide 10g (10.1.3.1.0) B28981-03". Nothing changes for B across these three env as it is not invoking any other internal services.

Configuring JMS Adapter (AQJMStoDB)

Hi All,
Merry Christmas!
I think I am reopening the below previous thread but I really am stuck.
Re: Can ESB JMS adapter read and write from/to Oracle AQ
I am trying to wrap up the AQJMStoDB example in
Oracle® Application Server Adapters for Files, FTP, Databases, and Enterprise Messaging User’s Guide 10g Release 3 (10.1.3.1.0)...
I completed all the necessary steps and when I execute the Send command I am getting the below error...
C:\ESBSamples\AQJMStoDB\tools>java Send JMSDEMO_TOPIC
OEMS.155 - simple JMS Send / JMS 1.02 / Database AQ / no JNDI
Connection factory = oracle.jms.AQjmsTopicConnectionFactory@f72617
Created connection = oracle.jms.AQjmsConnection@3bb2b8
Created session = oracle.jms.AQjmsSession@c2ff5
started connection
Got topic = JMSUSER.JMSDEMO_TOPIC
started session = oracle.jms.AQjmsSession@c2ff5
destination: JMSUSER.JMSDEMO_TOPIC
message :
<?xml version = '1.0' encoding = 'UTF-8'?>
<db:InputParameters xmlns:db="http://xmlns.oracle.com/pcbpel/adapter/db/DBAPP/AD
DEMPLOYEES/">
<EMPS>
<EMPS_ITEM>
<FNAME>John</FNAME>
<MIDDLE>W</MIDDLE>
<LNAME>Doe</LNAME>
<ADDR>
<STREET>100 Oracle Parkway</STREET>
<CITY>Redwood Shores</CITY>
<STATE>CA</STATE>
<ZIP>94065</ZIP>
</ADDR>
</EMPS_ITEM>
</EMPS>
</db:InputParameters>
message was sent with ID=null
Can you help me identify the problem.
I am using XE database and jdk 1.4.12_16.
Please let me know if you need more information on the setting and stuff.
Thanks,
Kalyan.

Just to understand your problem a little better, say you have processes A and B that you promote b/w these 3 environments. Also, say A is a standalone service invokable by external clients; say B is a service that is invokable by an external client and called by A as well.
Now, in this example, both A and B have web-service end points that change from one env to another.
W.r.t process A's caller, it should know the correct endpoint to invoke the service. Now if there is just one external client that is switching b/w the various environments, it has the responsibility of making this switch b/w the various endpoints (dev to test to prod). Now if this external client is an Oracle BPEL process as well, refer to solution below.
As far as process A's implementation goes, yes, it would have to change to invoke process B correctly. So, in dev, A should call B in dev; in stage/prod, A should call B in stage/prod. BPEL PM provides a solution to accomplish this via a customize ant task - refer to the section titled "Deploying to Multiple Environments with Different Configuration Values" in "Oracle® BPEL Process Manager Developer’s Guide 10g (10.1.3.1.0) B28981-03". Nothing changes for B across these three env as it is not invoking any other internal services.

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

If you want to use JMS with AQ as datastore then there is some configuration you need to do to enable this. This is outside SOA Suite per sa, e.g. no adapter required.
If you want to connect to the AQ direct then use the AQ adapter.
this blog may be of some help understand the configuration
http://biemond.blogspot.com/2008/01/oracle-jms-with-esb-and-bpel.html
cheers
James

Accessing Tibco-EMS queue from XI(using JMS adapter)

Hi All,
I am currently working on a Tibco Integration scenario with XI thru JMS(Sender) adapter. I have gone through some of our SDN forum threads and come to know that we have to deploy some TIBCO specific jar files to the fetch data from TIBCO-EMS queues. But still have the following query on
1. what are all the JAR files(TIBCO JMS libraries) needed to be installed in SAP J2EE engine? I have got the following JAR files from TIBCO guys...
tibcrypt.jar
tibjms.jar
tibjmsadmin.jar
tibjmsapps.jar
tibrvjms.jar
regards,
Raks

Hi Raks,
Check this note for JNDI configuration..
802754
"If a 3rd party JMS provider should be used then usually the "Name of JNDI initial context factory" must be adjusted. I.e. com.sap.engine.services.jndi.InitialContextFactoryImpl must be replaced by some.other.vendor.jms.jndi.InitialContextFactory In addition it is necessary to deploy the jar that contains the some.other.vendor.jms.jndi.InitialContextFactory with the aii_af_jmsproviderlib.sda SDA file. In addition, you must extend the server/provider.xml deployment descriptor in the relevant way. Refer to Chapter 11 of the XI 3.0 Configuration Guide for more information"
You need to find out class "Name of JNDI initial context factory" for tibco as mentoned in the note and deploy the corresponding JAR file.
Also check this link for JNDI configuration parameters in the JMs adapter..
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Regards
Anand

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

Similar Messages

Maybe you are looking for