JMSExpiration

Hi
I am reading different things on whether or not you should be able to set the JMSExpiration as art of the OutboundHeader to produce a JMS message. The idea is to set this property of the header, so when the message is on MQ it has a set "timetolive" and does not stay there indefinitely.
In the BPEL Designer it does not show up, as it is not in the jmsAdapterOutboundHeader.wsdl
Has anybody any clue how to dynamically set the Timetolive element. I know it is in the partnerlink.wsdl, but you cannot set that dynamically ?
Thanks

Looking at the implementation it seems than user headers are assimilated to string by default. However if you set directly JMSExpiration in $outbound variable the transport will try to parse it as long.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Similar Messages

HELP!! JBOSS Default Settings (JMSPriority, JMSExpiration)

Hello All,
I'm trying to figure out how to change the default JBoss settings for JMSExpiration, JMSPriority and JMSTimeStamp. I'm new to JBoss and have found that the documentation on this application is lacking and I'm being polite as this is a public forum.
Can anybody out there point me in the right direction or even better yet tell me what file to tweek so I can make my needed changes?
Thanks in advance!
Karl

Hi.
First of all - Jboss's documentation isn't lacking at all. It only costs money, because that's how they make their profit.
Second - I am not sure you can do it the way you want to do it. I do not know that Jboss has a properties file for these kind of parameters.
You'll be better off trying the Jboss forums for this question.
Cheers
Nimo.

Lack of information in JMS based notification message

Hello,
I have configured Watch for server log and related JMS Message Notification.
However, I get only a text like "MapMessage[ID:<589306.1276727319522.0>]" in the JMS message text.
How can I get the original log message by that ID or the JMS message's text can be extended with content WatchData attribute?
Very appreciate any help or direction to place where I can read about it.
Thanks,
Yuriy

I have figured out what is going on.
WLDF notification is written to JMS in the format that WLS Administrative Console can not read it.
However, when I export message to XML I can see all information that I need:
<?xml version="1.0" encoding="UTF-8"?>
<JMSMessageExport>
<mes:WLJMSMessage xmlns:mes="http://www.bea.com/WLS/JMS/Message">
<mes:Header>
<mes:JMSMessageID>ID:<589306.1276788240914.0></mes:JMSMessageID>
<mes:JMSDeliveryMode>PERSISTENT</mes:JMSDeliveryMode>
<mes:JMSExpiration>0</mes:JMSExpiration>
<mes:JMSPriority>4</mes:JMSPriority>
<mes:JMSRedelivered>false</mes:JMSRedelivered>
<mes:JMSTimestamp>1276788240914</mes:JMSTimestamp>
<mes:Properties>
<mes:property name="JMSXDeliveryCount">
<mes:Int>0</mes:Int>
</mes:property>
</mes:Properties>
</mes:Header>
<mes:Body>
<mes:Map>
<mes:name-value name="WatchAlarmResetPeriod">
<mes:String>60000</mes:String>
</mes:name-value>
<mes:name-value name="WatchSeverityLevel">
<mes:String>Notice</mes:String>
</mes:name-value>
<mes:name-value name="WatchRule">
<mes:String>(SUBSYSTEM = 'ousgg.valves')</mes:String>
</mes:name-value>
<mes:name-value name="WatchDomainName">
<mes:String>my_domain</mes:String>
</mes:name-value>
<mes:name-value name="WatchData">
<mes:String>DATE = Jun 17, 2010 11:24:00 AM EDT SERVER = AdminServer MESSAGE = Invalid record ...</mes:String>
</mes:name-value>
<mes:name-value name="JMSNotificationName">
<mes:String>OUSGG-FileValves-Fail-JMS</mes:String>
</mes:name-value>
<mes:name-value name="WatchAlarmType">
<mes:String>None</mes:String>
</mes:name-value>
<mes:name-value name="WatchRuleType">
<mes:String>Log</mes:String>
</mes:name-value>
<mes:name-value name="WatchName">
<mes:String>OUSGG-FileValves</mes:String>
</mes:name-value>
<mes:name-value name="WatchServerName">
<mes:String>AdminServer</mes:String>
</mes:name-value>
<mes:name-value name="WatchTime">
<mes:String>Jun 17, 2010 11:24:00 AM EDT</mes:String>
</mes:name-value>
</mes:Map>
</mes:Body>
</mes:WLJMSMessage>
</JMSMessageExport>
Does anybody know what format the notification is written in?
I'm trying to read it via JMS transport in OSB and it throwing errors no matter what "Request Message Type" I use:
Unexpected type of message received: weblogic.jms.common.MapMessageImpl
Thanks,
Yuriy
Edited by: user736637 on Jun 17, 2010 12:15 PM

Receiver JMS adapter issue in PI 7.1

Hi All,
We are using JMS receiver adapter for one of our scenarios. I'm facing different type of issue in production system
Issues:
If the channel is functioning the messages are successfully delivering to end system. If there are NO messages for long time the channel is not sending any message to end system and messages are getting failed in PI.
If i STOP and START the channel after few minutes channel able to deliver the messages.
I'm not not able to figure out where the issue is causing.
Please assist me to get ride of this issue.
Thanks in advance
- VR

Hello Rajesh and all,
Below is the error message i'm receiving. This issue is happens when there is no message flow for few hours and when a new message comes adapter channel in RWB through below error message.
Please assist with inputs
Message processing failed. Cause:com.sap.engine.interfaces.messaging.api.exception.MessagingException:Connector for ConnectionProfile of Channel:IN_JMS_xxxx
node:xxxx havingobject id:xxxxxxx encountered error:MQJMSxxx:an internal error has occured. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException:MQJE001:
An MQException occurred:Completion Code 2,Reason 2195 MQJE046:Unsupported codeset:0 in sending to destination queue:///xxxxxx.QUEUE?targetClient=1, the message message:JMS Message class:jms_txt JMSType: null
JMSDeliveryMode:2 JMSExpiration:0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0

MQ - Problems with receiver adapter

Hello experts,
has anybody experience with this kind of MQ error:
Message-Verarbeitung fehlgeschlagen. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: jms_rcv_aleg on node: 517708350 having object id: 336a5d371e443540b9cf6fcdb922228a encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195 MQJE046: Unsupported codeset : 0 in sending to destination queue:///somevalue targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:08c08110-6001-1091-0804-a2873c90c93c JMSDestination: null JMSReplyTo: null JMSRedelivered: false <?xml version="1.0" encoding="UTF-8"?> <ns1:aleg_auftrag_webkarat_rc xmlns:ns1="http://somevalue.de/ka Another 101 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195 MQJE046: Unsupported codeset : 0
Some additional background information: The MQ system is restarted once a day at midnight. The first message after restart always fails. To solve this I configured the receiver channel with the follwing parameters:
Wait After Message Error (msecs): 900000
Wait Before Reconnect (msecs): 600000
Reconnect if Exception Text Starts with: MQJMS2007
Handling of Pending XI Messages: Bypass Pending Warning and Send Message to JMS (Duplicates Possible)
The SAP note 948016 says something about the JMS-Parameter CONNECTION_TEST_POLL=true. After configuration I received an error, that the adapter is not able to create a temporary queue.
Thanks for all help on this topic
Frank

Hi,
Hope these links are useful to you..
configuration of JMS adapter Using WebSphereMQ
connection with the JMS provider
http://www-1.ibm.com/support/docview.wss?uid=swg21180117
http://www-1.ibm.com/support/docview.wss?uid=swg21105655
Thanks,
Satya Kumar..

JMS receiver adapter Error

Hi Experts,
Any idea about this error. We are getting following in JMS receiver adapter in PI 7.1.
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connector for ConnectionProfile of channel: JMS_Receiver_THQPRD2_Slow_Replyon node: 284760550 having object id: cf2f6eb7d6c93902b64b27bfcaad0ba5 encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>' in sending to destination queue:///QR.EAIPRD.THQPRD2.REPLY.SLOW?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:ID:414d5120504c535748353533202020204e6324ae23eb5b2d JMSDestination: null JMSReplyTo: null JMSRedelivered: false XPLOR PIPXSDI2030 45219q00282YSDI2030PROCESS_MQSERIES PLSWH553 Another 12,761 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>'.
Thanks,
Hari

Hello,
The error indicates a JMS driver issue.
Another customer resolved this issue by updating their MQ and the MQ drivers version (in their case to 6.0.2.8.)
You could try contacting IBM for advice on a similar upgrade.
#1086303 XI JMS Adapter and IBM Websphere MQ: FAQ
12)What is the recommended version of MQ drivers for the PI JMS
Adapter - IBM MQ connectivity ?
Kind regards,
Sarah

JMS Receiver Adapter Catching MQ Exceptions

Hi Experts,
We are running into an issue with our JMS receiver adapter failing PI. We are trying to send transactions via the adapter to a MQ Series' queue but it is failing after no transactions have been sent after a period of 3 hours or more. The only way we can flush the queue is to change the setting on the adapter to Bypass, restart the adapter and then resend the message. Once we do this, everything runs fine throughout the day. It seems to be the amount of time between transactions be processed on the queue.   For instance, last night the last transaction processed successfully was at 7:36pm EST. Then around 11:40pm EST we tried sending another and this is when we caught an exception from MQ once again. We have tried everthing that we know of u2013 we thought it might have been a background job running on PI that causes the issue but last night proved that it wasnu2019t the issue since it occurred before midnight. I feel that the issue is between our JMS connection and your MQ. Below is the message log of the transaction:
What course of action should we take next in diagnosing the issue?
Audit Log for Message: 1c728f10-2044-0441-0a04-604e2cf00000
Time Stamp     Status     Description
2009-05-21 22:40:48     Success     Message successfully received by messaging system. Profile: XI URL: http://bus0157:52000/MessagingSystem/receive/AFW/XI Credential (User): PIPISUSER
2009-05-21 22:40:48     Success     Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-05-21 22:40:48     Success     Message successfully put into the queue.
2009-05-21 22:40:48     Success     The message was successfully retrieved from the receive queue.
2009-05-21 22:40:48     Success     The message status set to DLNG.
2009-05-21 22:40:48     Success     Delivering to channel: JMS_IDOC_SPK_RCV
2009-05-21 22:40:48     Success     MP: Entering module processor
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService
2009-05-21 22:46:48     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP
Time Stamp     Status     Description
2009-05-21 22:46:48     Error     Exception caught by adapter framework: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP?targetClient=1 JMSReplyTo:      null JMSRe
2009-05-21 22:46:48     Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP.

Ok, would you mind taking a look at my forum question titled "Multiple Message Types into one Websphere Message Queue", it may be an easy one for you since you are already doing this!
Best regards,
Aaron
[Multiple Message Types into one Websphere Message Queue|Multiple Message Types into one Websphere Message Queue]

How to set JMS user property in JMS Adapter.

I am using Jdeveloper and SOA 11g. I want to filter some JMS messages from a topic based on a JMS user property. It is consumed using (JMS Adapter) consumer --> Mediator---> DBAdapter.
My Question is how to define a JMS user property using Jdeveloper 11g.
Thanks
Edited by: user5108636 on 24/06/2010 16:10

In Mediator mplan Assign Values use a property expression in the "to" side like:
jca.jms.JMSProperty.XXX
where XXX is the name of the property you would like to have created and populated. In source it will look like:
<Mediator name="A03QueueWFeedMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
wsdlTargetNamespace="http://www.oracle.com/integration/b2b/A03QueueWFeedFromB2B/">
<operation name="receive" deliveryPolicy="AllOrNothing" priority="4"
validateSchema="false">
<switch>
<case executionType="direct" name="A03QueueWFeedToJMS.Produce_Message">
<action>
<transform>
<part name="$out.body"
function="xslt(xsl/ADT_AXX_To_ADT_AXX.xsl, $in.body)"/>
</transform>
<assign>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Type"
value="$in.property.b2b.documentDefinitionName"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@ID"
value="$in.property.b2b.fromTradingPartnerId"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Name"
value="$in.property.b2b.toTradingPartnerId"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.property.b2b.conversationId"
value="$in.property.b2b.conversationId"/>
<copy target="$out.property.b2b.documentDefinitionName"
value="$in.property.b2b.documentDefinitionName"/>
<copy target="$out.property.b2b.documentProtocolName"
value="$in.property.b2b.documentProtocolName"/>
<copy target="$out.property.b2b.documentProtocolVersion"
value="$in.property.b2b.documentProtocolVersion"/>
<copy target="$out.property.b2b.documentTypeName"
value="$in.property.b2b.documentTypeName"/>
<copy target="$out.property.b2b.fromTradingPartnerId"
value="$in.property.b2b.fromTradingPartnerId"/>
<copy target="$out.property.b2b.fromTradingPartnerIdType"
value="$in.property.b2b.fromTradingPartnerIdType"/>
<copy target="$out.property.b2b.toTradingPartnerId"
value="$in.property.b2b.toTradingPartnerId"/>
<copy target="$out.property.b2b.toTradingPartnerIdType"
value="$in.property.b2b.toTradingPartnerIdType"/>
*<copy target="$out.property.jca.jms.JMSProperty.conversationId"*
value="$in.property.b2b.conversationId"/> <copy target="$out.property.jca.jms.JMSProperty.documentDefinitionName"
value="$in.property.b2b.documentDefinitionName"/>
<copy target="$out.property.jca.jms.JMSProperty.documentProtocolName"
value="$in.property.b2b.documentProtocolName"/>
<copy target="$out.property.jca.jms.JMSProperty.documentProtocolVersion"
value="$in.property.b2b.documentProtocolVersion"/>
<copy target="$out.property.jca.jms.JMSProperty.documentTypeName"
value="$in.property.b2b.documentTypeName"/>
<copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerId"
value="$in.property.b2b.fromTradingPartnerId"/>
<copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerIdType"
value="$in.property.b2b.fromTradingPartnerIdType"/>
<copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerId"
value="$in.property.b2b.toTradingPartnerId"/>
<copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerIdType"
value="$in.property.b2b.toTradingPartnerIdType"/>
</assign>
<invoke reference="A03QueueWFeedToJMS" operation="Produce_Message"/>
</action>
</case>
</switch>
</operation>
</Mediator>
The runtime will see something like:
[2010-09-09T11:48:06.353+10:00] [AdminServer] [TRACE] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@60ddbc76] [userId: weblogic] [ecid: 0000Ifo9olH2zGWjLxmJOA1CY0sg0001jY,0] [SRC_CLASS: oracle.integration.platform.blocks.adapter.fw.log.LogManagerImpl] [APP: soa-infra] [dcid: 02d1ff4621073810:26418f01:12af379c141:-7fd3-0000000000000219] [SRC_METHOD: log] Jms Adapter A03QueueWFeed:A03QueueWFeedToJMS [ Produce_Message_ptt::Produce_Message(body) ] XMLHelper_convertJmsMessageHeadersAndPropertiesToXML: <JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">[[
<JMSInboundHeaders>
<JMSCorrelationID></JMSCorrelationID>
<JMSDeliveryMode>2</JMSDeliveryMode>
<JMSExpiration>0</JMSExpiration>
<JMSMessageID>ID:<911867.1283996886119.0></JMSMessageID>
<JMSPriority>4</JMSPriority>
<JMSRedelivered>false</JMSRedelivered>
<JMSType></JMSType>
<JMSTimestamp>1283996886119</JMSTimestamp>
</JMSInboundHeaders>
<JMSInboundProperties>
<Property name="documentProtocolVersion" value="2.3"/>
<Property name="toTradingPartnerIdType" value="Name"/>
*<Property name="conversationId" value="C0A83C0712AF42D840E0000074BA3CCC"/>* <Property name="documentTypeName" value="ADT"/>
<Property name="tracking_conversationId" value="C0A83C0712AF42D866F0000074BA3CD9"/>
<Property name="tracking_ecid" value="C0A83C0712AF42D866F0000074BA3CDA"/>
<Property name="tracking_compositeInstanceId" value="60019"/>
<Property name="documentProtocolName" value="HL7"/>
<Property name="documentDefinitionName" value="QH_ADT_Generic"/>
<Property name="tracking_parentComponentInstanceId" value="mediator:45E076D0BBB411DFAF05817F5F0DD1A1"/>
<Property name="fromTradingPartnerIdType" value="Name"/>
<Property name="fromTradingPartnerId" value="HOMER"/>
<Property name="toTradingPartnerId" value="Self"/>
<Property name="JMSXDeliveryCount" type="integer" value="1"/>
</JMSInboundProperties>
</JMSInboundHeadersAndProperties>
Edited by: Michael.Czapski on 8/09/2010 18:58

How to Set JMS property and Read JMS property in BPEL using JMS adapter

Does any one know how to set or read more than one JMS property in BPEL using JMS adapter. My queue server is Oracle JMS server.
Any help and sample is well appreciated

Hi Van
I have noted that only the attribute "type" is missing. It seems that when you create a "string" property, the attribute "type" is droped from the XML. If you use another type (as "integer" or "double") it stays there.
If you try to read your properties, except for the "type" attribute, you should be successful, as I am. If you need, please tell me your email, I can send you my code.
Source Code:
in ASSIGN activity (process which SENDS the JMS message):
<assign name="TESTES">
<copy>
     <from expression="'string'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@type"/>
</copy>
<copy>
     <from expression="'name'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@name"/>
</copy>
<copy>
     <from expression="'value1'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@value"/>
</copy>
<bpelx:append>
     <bpelx:from>
     <Property name="" type="" value=""
          xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/"/>
     </bpelx:from>
     <bpelx:to variable="HeaderJms" part="outboundHeader"
          query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties"/>
</bpelx:append>
<copy>
     <from expression="'string'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@type"/>
</copy>
<copy>
     <from expression="'name2'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@name"/>
</copy>
<copy>
     <from expression="'value2'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@value"/>
</copy>
</assign>
in ASSIGN activity (process which READS the JMS message)
<assign name="Assign_1">
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@name"/>
<to variable="temp"/>
</copy>
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@value"/>
<to variable="temp"/>
</copy>
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@name"/>
<to variable="temp"/>
</copy>
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@value"/>
<to variable="temp"/>
</copy>
</assign>
Note that I do not try to read the "type" attribute, otherwise it will fail.
Here is the JMS Header Message received:
<inboundHeader>
<JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">
<JMSInboundHeaders>
<JMSCorrelationID>
bpel://localhost/pi_lms-c001e/BpelPiAtualizacaoC001E~1.0/3200025-BpInv0-BpSeq1.6-2
</JMSCorrelationID>
<JMSDeliveryMode>2</JMSDeliveryMode>
<JMSExpiration>0</JMSExpiration>
<JMSMessageID>ID:467DFA1FA1ED459EBF37F51F596C3F12</JMSMessageID>
<JMSPriority>4</JMSPriority>
<JMSRedelivered>false</JMSRedelivered>
<JMSType>com.mercurio.lms.integration.c001eip.c001EIntegrationPoint</JMSType>
<JMSTimestamp>1201552046253</JMSTimestamp>
</JMSInboundHeaders>
- <JMSInboundProperties>
<Property name="JMSXDeliveryCount" type="integer" value="1"/>
<Property name="JMSXRecvTimestamp" type="long" value="1201552046698"/>
<Property name="JMSXUserID" value="lms_dev_int_v1_user"/>
<Property name="JMS_OracleDeliveryMode" value="2"/>
<Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
<Property name="JMS_OracleDelay" type="long" value="0"/>
<Property name="JMSXState" type="integer" value="0"/>
<Property name="IAS_VERSION" value="10.1.3"/>
<Property name="JMS_OracleDeliveryMode" value="2"/>
<Property name="name" value="value1"/> ("type" attribute was droped!!!)
<Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
<Property name="name2" value="value2"/> ("type" attribute was droped!!!)
</JMSInboundProperties>
</JMSInboundHeadersAndProperties>
</inboundHeader>
Regards
Marcelo

PI JMS Adapter - setting of MQMD.Format

I have a requirement whereby I need to set MQMD.Format=u2019MQIMSu2019 on a receiver JMS channel, i.e. when it reaches our MQ / Mainframe from PI we need that format set (PI defaults to u2018MQSTRu2019). Unlike for example ccsid, format it is not a parameter available to be changed on the main JMS screens.
Any ideas on how I can achieve this? SAP has suggested doing some things over on the receiver (MQ) side but I don't want to go there, and don't think I should need to.
We are on PI 7.11 sp 5.
Background: as per IBM documentation (http://webcache.googleusercontent.com/search?
q=cache:Ps4qVR_SbYIJ:www.macyplace.com/macyent/descriptions/MEMQClass.htmMQSERIESOTMAreasonmqims;cd=7&hl=en&ct=clnk&gl=ca), otma-based messages must have a format of 'MQIMS'. Here is an excerpt:
...Messages using the IMS OTMA bridge require an MQMD format of "MQIMS"....
Keith

Hi Keith,
I am trying to do the same thing. Set the MQMD Format to MQIMS using the JMS_IBM_Format but that does not work and gives the following error:
Message processing failed. Cause: com.sap.aii.adapter.jms.api.connector.ConnectorException: Connector for ConnectionProfile of channel: CC_NIAE_DO_NOT_TOUCH_JMS_RECEIVERon node: 3721650 having object id: 484b71b77f4c38debe12a87b7a961905 encountered error: MQJMS2007: failed to send message to MQ queue. in sending to destination queue:///SYSTEM.DEFAULT.LOCAL.QUEUE?targetClient=1, the message message: JMSMessage class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1311715458427 JMSCorrelationID: 0892080c-b00b-2c01-0e08-f0c02012c708 JMSDestination: queue:///SYSTEM.DEFAULT.LOCAL.QUEUE?targetClient=1 JMSReplyTo: null JMSRedelivered: false JMSXDeliveryCount: 0 JMS_IBM_Encoding: 785 JMS_IBM_Format: MQIMS <?xml version="1.0" encoding="UTF-8"?> <SCSMSG><SCS-MSG-LENGTH>000001663</SCS-MSG-LENGTH><SCS-APP-RE ...: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue.
A JMS error occurred while processing message: 0892080c-b00b-2c01-0e08-f0c02012c708. The JMS provider gave the error mesage as MQJMS2007: failed to send message to MQ queue. MQJE001: Completion Code '2', Reason '2148'., and the error code as MQJMS2007.
I talked with one of the MQ Team here and they said you might want to have 3 spaces after MQIMS because the MQMB.Format field is 8 Characters and I tried but still the same error.
Also tried putting MQIMS is single and double quote lile "MQIMS " and 'MQIMS ' but it takes the quote as a character and does not create a MQ Message with format MQIMS.
Did you try it and had it working?
Thanks
-Saumitra

Weblogic Message Bridge Producing Duplicate JMS Messages

We have a message bridge that we use to integrate with TIBCO. The message bridge is deployed on a WL cluster. We see duplicate JMS messages produced by the bridge when it is deployed on the cluster. We don't see this behavior when only one ManagedServer in the cluster is active,.
TIBCO version: 4.4.3 V5
WLS: 10.3.3 with patch for bug BUG8732539 (BQC6)
java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2121-linux-x86_64, compiled mode)
We are also seeing a lot of exceptions related to
<May 27, 2011 4:11:57 PM PDT> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
However the bridge is active. We are monitoring the message-out count on TIBCO and we observed that we see duplicates whenever there a message is re-delivered. We opened a case with Oracle support and they suggested patch 10258751 which didn't help. The next suggestion was a patch for "Bug 11852771 - [WLS10.3.2]MISSING AND DUPLICATE IN JMS QUEUE MESSAGE MONITORING" but I don't think it will help since our JMS consumers are getting duplicate messages and this is not just a UI issue.
Here is the message behavior when we send a single message:
Timelines
11:34:17 --> Message sent to TIBCO EMS queue
11:34:17 --> WL MS3 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:17 --> WL MS1 says it got the message and committed the transaction
11:34:17 --> Message is visible in the JMS queue in the admin console
11:34:17 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:31 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS2 says it got the message and committed the transaction
11:34:31 --> WL MS1 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are two messages in the JMS queue)
11:34:31 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:54 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS4 says it got the message and committed the transaction
11:34:31 --> WL MS2 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are three messages in the JMS queue)
11:34:31 --> TIBCO EMS receives an ACK from WL for the message
MS04
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-6A59E8FE76C4FC4CA149
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <MS04> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<193654.1306521294611.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
MS03
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257342> <BEA-000000> <Bridge MessageBridge1 Successfully got connection to the target destination>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1: both source and target adapters support XA = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 supportsMDBTX = false supportsXA = true async = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 WorkMode = Exactly-once>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntimeVerbose> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 Entering processMessages() ------ >
####<May 27, 2011 11:34:17 AM PDT> <Error> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-3AA29116A4CA622834EA> <> <1306521257343> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:200)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
... 8 more
).>
####<May 27, 2011 11:34:17 AM PDT> <Warning> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257344> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>
MS02
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271386> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-679AF074F381152F047C
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271392> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<196075.1306521271386.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Error> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:225)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
... 2 more
).>
####<May 27, 2011 11:34:54 AM PDT> <Warning> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
MS01
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257536> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: false
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-72BC818FE2BB8C2655C6
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257542> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<195581.1306521257536.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Error> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
... 1 more
).>
####<May 27, 2011 11:34:31 AM PDT> <Warning> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>

@Tom, thanks for your hints and sorry for my delayed response. Here are my answers to your queries…
-- Does messaging work, without any exceptions, when only one bridge is active?
It works fine when only one node of the cluster is active. -- I'm not familiar with Tibco monitoring, but I suspect that the "message-out count on TIBCO" stat doesn't always imply that there's a duplicate message. It could mean that an initial message delivery attempt failed, it's transaction rolled back, and the message was redelivered. Redelivery after a failure is normal - the original delivered message, if one actually made it onto a WebLogic queue, should be discarded by WebLogic when its failed transaction eventually rolls back (before its ever handed to a consumer application).
You are absolutely right. The mismatch in count was due to redelivery attempts. We could see that as soon as we turned on trace in TIBCO-- The posted stack traces look like they may be JVM stdout/stderr scrapes, which are often automatically truncated, for example, see the "... 8 more" listed at the bottom of one of the stack traces below. There might be more information in the full stack trace for the "Resource manager is unavailable" exception. Full traces are logged in each WebLogic Server's log files.
I tried redirecting the output and even set "stdout Stack Trace Depth:" to -1 but I am not albe to see the complete trace.-- The setTransactionTimeout NullPointerException error message looks like it is collateral damage from the original reported "Resource manager is unavailable" exception that's thrown earlier during the enlistResource() step. If you are truly getting duplicates, then I think this is a clue that the bridge is somehow (stupidly) trying to proceed with forwarding the message despite the fact that there's no current transaction on the thread... 
I have a case open with Oracle support and we have extensive debugging turned on. Here is what the engineer came back with. There is an issue with XA transactions in JCA adapter when it talks to third party providers like TIBCO. Since the resource names are not unique across the cluster, a XA transaction is started on multiple nodes in the cluster for the same message. All transactions abort but the message is persisted and TIBCO redelivers the message since the connection is severed when the transaction aborts. We were able to reproduce this scenario at will with our setup and Oracle was able to reproduce the issue too.  -- Can you check the state of the message on the WebLogic Q? The fact that a message is shown on the WL console doesn't necessarily mean that the state of the message is visible (it could be waiting for the transaction to commit - something that apparently never happens). On the console: Services -> Messaging -> JMS Modules -> [module name] -> [destination name]. 
Our consumer was getting duplicate messages. This confirms that the console was not giving us incorrect information. The console showed that 2/3/4 messages were in "current" state when we expected only one message. -- Make sure that the bridge's Tibco destination is a Tibco queue not a Tibco topic (it's happened). 
Yeah we made sure it was a Queue. -- Can you post your bridge and destination stanzas from your config.xml?  
Will try to do this shortly but have to strip out lot of information. -- I vaguely recall that there was a problem with untyped connection factories in Tibco at one point (not sure). You might want to try changing the Tibco configuration to spin-up "XA Queue Connection Factory" instead of just an "XA Connection Factory" (plus modify the bridge configuration accordingly). 
We tried this but it didn't eliminate this issue. One thing we did notice however was that the number of rollbacks were greatly reduced. 
Here is the workaround that Oracle is suggesting: Create pinned destinations and assign it to a distributed queue. This will keep the transactions local and hence eliminate the duplicate transactions and rollback. We tried it and it eliminated the dups issue. However I discovered another bug during my testing. Our cluster messaging mode is "Unicast" and message forwarding from zero consumer queues to queues with consumers fails. We have four/five nodes in the cluster and two consumer threads. I observed that the zero consumer queues always forward to one queue in the cluster that has consumers. The forwarding stalls when I bring down the node that has consumers. Again, we were able to reproduce this issue at will and Oracle has acknowledged that it is a bug. They've reported that Unicast fails without any warning whereas Multicast fails with a warning in the log. We have observed this message forwarding stalling even with UDQs.
I have another case open for an issue where our message bridges that transfer messages from TIBCO to WLS stalls after sometime. The status is shown as active but it is not doing anything. The server instance shows stuck threads trying to roll back a message. TIBCO logs indicate that it is receiving a request to rollback a transaction but it is not finding the transaction to rollback. The only way to recover from this condition is to restart the cluster. I am fairly confident that he root case for this issue is again the XA transaction issue. I changed our UDQ to pinned destination in one environment and we are no longer seeing dups or bridge stalling there. Hopefully Oracle can resolve the message forwarding issue.Thanks again….

JMS unable to connect MQ after idling for 10 min

Hi,
I have come up with a working Async/Sync interface which is MQ->XI->RFC->CRM and CRM->RFC->XI->MQ again.
I sent several messages to create tickets in CRM and CRM created the tickets successfully and sent back reponses back to MQ. MQ received the reponses messages.
The problem is that after sending the messages, I waited for 10min or so and I started to send messages to create tickets in CRM. The tickets are again created successfully and tried to send the reponses messages to the receiver MQ but in the Communication Channel Monitoring, error is shown:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: MQ_XML_Receiver_CC2on node: 74922450 having object id: 05e949939d4c3a649aa55b273caa390b encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///MCLCT.INVESTIGATION.XML.01?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1192218203185 JMSCorrelationID:470bb330-f40a-01ab-0000-000081b0b8e9 JMSDestination: queue:///MCLCT.INVESTIGATION.XML.01?targetClient=1 JMSReplyTo: null JMSRedelivered: false JMSXDeliveryCount:0 <?xml version="1.0" encoding="UTF-8"?> <InvestigationUpdateXML_DT><INVESTIGATION_UPDATE><LW_INVEST_N Another 162 character(s) omitted: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
So I have to stop the particular JMS channel and start it again in order to send messages over to the receiver MQ.
Anyone has an idea why is it so? Is it a MQ problem or JMS adapter problem existing on the XI part?
Appreciate if someone can give some acruate info to solve the hassle of restarting communication channel everytime.
Thanks in advance.

Hi,
I have identified that the problem lies with sending messages to remote queue.
For local queue, I am able to send messages anytime. Eg. sending 10 messages, wait for 30 min and send another 5. The JMS communication channel works fine.
For remote queue, I sent 10 messages and wait for just 5 min and sent another 1. The communication channel again threw out such error message again. In short, it is unable to put the message in MQ. I have to restart the com channel again, in order to send the message over to MQ.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: MQ_XML_Receiver_CC2on node: 74922450 having object id: 05e949939d4c3a649aa55b273caa390b encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///MCLCT.INVESTIGATION.XML.01?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1192218203185 JMSCorrelationID:470bb330-f40a-01ab-0000-000081b0b8e9 JMSDestination: queue:///MCLCT.INVESTIGATION.XML.01?targetClient=1 JMSReplyTo: null JMSRedelivered: false JMSXDeliveryCount:0 <?xml version="1.0" encoding="UTF-8"?> <InvestigationUpdateXML_DT><INVESTIGATION_UPDATE><LW_INVEST_N Another 162 character(s) omitted: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
So is there any way to configure the JMS adapter to connect the MQ as it wish with success and send the messages anytime of the day? The MQ queue admin has decided to use remote queue and it's hard to convince them to switch to local queues and I am not an expert on MQ technologies, I can't list out the pros and cons of having local queues.
Regards.
Chee Nam
PS: Appreciate if anyone can give some pointers.

JMS Message Expiry Period (msecs) in Synchronous JMS scenario

Hi,
I've configured a Proxy->JMS synchronous scenario using Sync/Async Bridges in the Receiver JMS adapter. All is well when the reply queue is working but when the reply queue is down, the waiting time in the JMS receiver adapter is too long. It can be up to a minute or more. We want to shorten the wait time for the reply. On the receiver adapter, I've tried using 'JMS Message Expiry Period (msecs)' in the JMS setting but it doesn't seem to have any effect. Then I tried switching on the 'JMS Message Expiration' under Adapter-Specific Mesage Attribute. However I get the following error:
Dynamic record/records: DCJMSExpiration,DCJMSTimestamp, that correspond to the JMS property/properties: JMSExpiration,JMSTimestamp, respectively is/are either missing from the message: deacb6f9-56e0-3bf1-af90-00145e6880b6, or have invalid types specified in the channel configuration
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Dynamic header records are missing/incorrect specified in message: deacb6f9-56e0-3bf1-af90-00145e6880b6. Erroneous/Unspecified headers are:[ DCJMSExpiration DCJMSTimestamp ]
Any one has an idea? Thanks in advance.

Hi,
When queue down normally JMS Receiver Communication channel tries 3 times to send message to Queue,when it tries 3 times the retrievel time its not possible to predict,may be you need to chnage the setting at basis level for retry interval.
check with basis team.
Regards,
Raj

Message-driven bean CMT can not be supported

Hi,
I�m trying to use IBM MQSeries 5.3 with S1AS7. The AS and MQ run under W2K SP3. At first I had no problem with deploying and running samples. I used C:\Sun\AppServer7\samples\ejb\mdb\simple\
I was able to put a test message into MQSeries queue and I saw it was processed by the MDB
Then I decided to change <transaction-type> from �Bean� to �Container� and I added <assembly-descriptor> where I set <trans-attribute> as �Required�.
Here is my new ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>

<ejb-jar>
<display-name>SimpleMessageJAR</display-name>
<enterprise-beans>
<message-driven>
<display-name>SimpleMessageEJB</display-name>
<ejb-name>SimpleMessageEJB</ejb-name>
<ejb-class>samples.ejb.mdb.simple.ejb.SimpleMessageBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
     <container-transaction>
          <method>
               <ejb-name>SimpleMessageEJB</ejb-name>
               <method-name>onMessage</method-name>
               <method-params>
                    <method-param>javax.jms.Message</method-param>
               </method-params>
          </method>
          <trans-attribute>Required</trans-attribute>
     </container-transaction>
</assembly-descriptor>
</ejb-jar>
In this case I have the following server.log
[15/Dec/2002:15:29:00] FINE ( 1700): Requesting Server Session at: 1039955340843
[15/Dec/2002:15:29:00] FINE ( 1700): Got Server Session at: 1039955340859(1039955340843)
[15/Dec/2002:15:29:00] INFO ( 1700): CORE3282: stdout: In SimpleMessageBean.SimpleMessageBean()
[15/Dec/2002:15:29:00] FINEST ( 1700): Thread[MQQueueAgent (MYASQUEUE),5,RMI Runtime]: got session: com.sun.enterprise.jms.SessionWrapperBase@3c9616 from com.iplanet.ias.ejb.containers.IASServerSessionImpl@3508c0
[15/Dec/2002:15:29:00] INFO ( 1700): CORE3282: stdout: In SimpleMessageBean.setMessageDrivenContext()
[15/Dec/2002:15:29:00] INFO ( 1700): CORE3282: stdout: In SimpleMessageBean.ejbCreate()
[15/Dec/2002:15:29:00] FINEST ( 1700): start(): calling notify... com.iplanet.ias.ejb.containers.IASServerSessionImpl@3508c0
[15/Dec/2002:15:29:00] FINEST ( 1700): run(): after wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@3508c0
[15/Dec/2002:15:29:00] FINEST ( 1700): Thread[Thread-28,5,RMI Runtime]: run(): calling Session.run() ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@3508c0
[15/Dec/2002:15:29:00] FINEST ( 1700): Thread[Thread-28,5,RMI Runtime]: message-driven bean container onMessage :
JMS Message class: jms_text
JMSType: null
JMSDeliveryMode: 1
JMSExpiration: 0
JMSPriority: 0
JMSMessageID: ID:414d5120514d5f636c6f7564202020200628fc3d2000020f
JMSTimestamp: 1039955340820
JMSCorrelationID:null
JMSDestination: null
JMSReplyTo: null
JMSRedelivered: false
JMS_IBM_PutDate:20021215
JMSXAppID:C:\WINNT\system32\mmc.exe
JMS_IBM_Format:MQSTR
JMS_IBM_PutApplType:11
JMS_IBM_MsgType:8
JMSXUserID:alex
JMS_IBM_PutTime:12290082
JMSXDeliveryCount:1
111111111111111111
[15/Dec/2002:15:29:00] FINEST ( 1700): beforeMessageDelivery() not called
[15/Dec/2002:15:29:00] INFO ( 1700): MDB00040: [mdb-simple:SimpleMessageEJB]: Message-driven bean CMT can not be supported.
[15/Dec/2002:15:29:00] SEVERE ( 1700): MDB0008: Session.run() throws Exception [Message-driven bean CMT can not be supported.]
[15/Dec/2002:15:29:00] SEVERE ( 1700): MDB0009: Session.run() throws Exception
java.lang.RuntimeException: Message-driven bean CMT can not be supported.
     at com.sun.enterprise.jms.SessionWrapperBase.run(SessionWrapperBase.java:200)
     at com.iplanet.ias.ejb.containers.IASServerSessionImpl.run(IASServerSessionImpl.java:191)
     at java.lang.Thread.run(Thread.java:536)
[15/Dec/2002:15:29:00] FINEST ( 1700): Thread[Thread-28,5,RMI Runtime]: in run(): return object com.iplanet.ias.ejb.containers.IASServerSessionImpl@3508c0 to pool ...
[15/Dec/2002:15:29:00] FINEST ( 1700): run(): before wait ... com.iplanet.ias.ejb.containers.IASServerSessionImpl@3508c0
If I use internal AS JMS I don�t have any trouble. Everything works fine.
Why it is possible to use MDB CMT with internal AS JMS provider?
What should I do to create MDB CMT with IBM MQSeries?
Alexei Gladkov

Hi Alexei,
Sun ONE Application Server 7 does not support CMT MDBs with 3rd party JMS providers. (As you note, BMT MDBs work with MQSeries and Sun ONE App Server).
With the advent of the next J2EE CA spec version (1.5) and J2EE 1.4, a standard means of hooking JMS providers into app servers and MDBs will be made available. Shortly after J2EE 1.4 is released, you'll see this support in Sun ONE App Server.
From the J2EE 1.4 spec: "The Connector API now supports integration with asynchronous messaging systems, including the ability to plug in JMS providers."
Thanks,
Chris

Error in JMS communicatin channel while deleivering to WMQ server

How to check whether a node in Adapter engine is having messaging service active?
I am having one of the JMS receiver node having error :
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_Americas_EDI_Receiveron node: 101565650 having object id: #MSGid# encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException in sending to destination queue:///NASB.UPXI.EDI.INBOUND.AQ, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:3258af50-24e0-11dd-bc98-3c2ac1cacf6e JMSDestination: null JMSReplyTo: null JMSRedelivered: false ReceiverId: ### SenderId:### ISA00 00 124165122352 *08 080 5180935U00401 Another 478 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException"
The second Line for same mssg id provides follwing info:
""JMS error occurred while processing message 'MSGIDe'; error mesage: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException null; error code: MQJMS1016"
Can anyone suggest what can be a fix over this. We have tried restyrting j2ee also but the still persists.
Expect points for sure.
Regards,
Nipun

Hey All,
Following is the solution for the above mentioned JMS receiver channel problem whilst connecting to MQ Series Server.
I assume you are connecting to a MQ series server with version less then 7.xx, or MQ Server 5.xx,
Cause of Problem: The problem appears when you try to send a message through JMS Receiver Adapter channel to a such MQ server and at that particular moment, the server do not accepts the message i.e. the connection with MQ Server drops out; resulting in a Java null pointer error, as the MQ fails to assign the pointer back to the same message, { again until its transferred to MQ.} therefore MQ JMS 2003, MQJMS2007 and MQJMS1016 error appears.
Possible configuration at XI/PI:
1. Add a Advanced additional JMS parameter Connection_Test_Poll = True
2. For XI settings from the drop down of field "Handling of Pending XI messages" select "Bypass Pending Warning and Send Message to JMS(Duplicates possible)" . This will probably cause duplicates at MQ series Server side, make sure you are ready to encounter it there!!
3. If the error still appears, choose In the Error Handling settings, Reconnection if Exception text Starts with provide the error number which the message is currently experiencing. eg. MQJMS1016 or MQJMS2007 or MQJMS2003. Restart the communication channel and restart such message..
After applying the above settings if you still experience errors MQJMS2007, 2003 and MQJMS1016, when connecting and processing messages to MQ server, Then you should try upgrading the MQ Series server! You cannot do much in the XI/PI system else you will create duplicates in the MQ system.
Please Note this error has more to do with the compatibility issue of MQ Series server with PI's JMS adapter.
Do let me know if you have any more queries on this.
Regards,
NIPUN

JMSExpiration

Similar Messages

Maybe you are looking for