Error in JMS adapter MQ to PI

Hi,
We are connecting to Websphere MQ using the JMS adapter.
The message coming from MQ is a flat structure. So we have configured the Message Transform Bean to do the conversion from plain to xml structure according to
http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter
But when we test a message we end up with this error:
TransportException: No MIME header found at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
I'm not sure if this is related to the content conversion or general settings in the JMS adapter.
Any inputs are highly appreciated.
Thanks
Shakthi

Hi Shakthi,
Actually, it is the error that tells you where the error took place:
com.sap.aii._adapter.jms_.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
You might also want to refer to this thread: Error in JMS Sender Adpater for a few ideas to solve your problem. In general, it is connected to your adapter configuration. Please review it once again ang you should have the problem fixed.
Hope this helps,
Greg

Similar Messages

Error in JMS adapter 11g

Hi
I have configured a JMS Adapter in Jdev 11.1.1.3.0 to consume message from a queue(JNDI Name as eis/wljms/WLQueue) on a weblogic server(10.3.1) in a different domain and deployed my BPM process to the soa server 11g.
I created a new outbound connection pool (eis/wljms/WLQueue) in Deployments->JMSAdapter->Configuration->Outbound Connection Pools with Connection Pool Interface: oracle.tip.adapter.jms.IJmsConnectionFactory
Also updated the factory properties field for eis/wljms/WLQueue with :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.75.85.151:9021;java.naming.security.principal=weblogic;java.naming.security.credentials=weblogic
And finally updated the deployment plan for JMSAdapter.
However I am getting the following error :
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample JMSMessageConsumer_init: Retrying connection; attempt #1>
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample
BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the
connection factory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:207)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnec
tionFactory(JMSConnectionFactoryFactory.java:86)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:173)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.Sec
urityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialCo
ntextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
67)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.ja
va:183)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:131)
... 26 more
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticat
ed.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServi
ceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Sou
rce)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.jav
a:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173
Anyone has come across this issue? if yes, how do I resolve this?
Thanks

Have you tried cross-domain security or domain trust?

Error in JMS Adapter Configuration.

Hi,
Its regarding JMS receiver adapter for MQ Series.
We have MQ 6.0 installed on PI server. While trying to connect thorough JMS receiver adapter we are getting a connection failure error at communication channel level.
The MQ administrator is of the opinion that as MQ is local to the PI server a channel is not required.
In the MQ server, the administrator has created a Manager and Queue which we are using in the JMS receiver channel.
We have provided the queue connection factory as the default one used for MQ 5.3
class also as the default. (All the extra jar files required for MQ 6.0 is deployed).
The error description says:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.23.86.134:XBEIG_QMGR1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
Any inputs would be very helpful...
Many Thanks,
Rosine.

you can check the SAP Note 856346 - FAQ on JMS adapter it might have some info

Error in JMS Adapter:

Receiving the below error, thought of JMS Drivers problems undeployed and re-deployed several times, but still problem persist in XI.
Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2010-09-09 11:45:21     Error     MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
2010-09-09 11:45:21     Error     Exception caught by adapter framework: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
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: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary..
2010-09-09 11:45:22     Success     The message status set to WAIT.
2010-09-09 11:45:22     Success     The asynchronous message was successfully scheduled to be delivered at Thu Sep 09 11:50:21 CDT 2010.
The JNDI Libraries are available in Visual Admin, not sure what else causing the issue. Any guru's help is appreciated

XI 3.0 SP20
Regarding the note, that only applied below sp4. We are on SP20. The default values appears but those are not working.This seems to be a problem with Dev only, Q and P is working fine at this moment
If i actually delete module processor's from Sender and Receiver channel, things are working fine. But not sure if it is going to break anything. And this needs to be applied in all landscape. But i have to present a reason, why this weird behavior all of a sudden
Sender
    SAP XI JMS Adapter/ConvertJMSMessageToBinary
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Receiver
    SAP XI JMS Adapter/ConvertMessageToBinary
    SAP XI JMS Adapter/SendBinarytoXIJMSService

Error in JMS Adapter Configuration...Pls help..

Hi,
My scenario is that FTP->MQ Queue->Local JMS Queue->XI.
MQ Queue has successfully picked up the files from FTP and posted successfully into Local JMS Queue. But XI is unable to pick them up from Local JMS Queue.
It is giving the following error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '153.88.140.28:ESEALMW303'
Here are the details what I enetered in the Sender JMS Adapter Configuration:-
Transport Protocol-> WebsphereMQ(Non JMS)
QueueConnection Factory Java Class-> com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class->com.ibm.mq.jms.MQQueue
IP address:            153.88.140.28
Server port:            1414
Queue Mgr name ESEALMW303
Channel name        MQMA_ESEALMW303_1
JMS queue            EAB_MDMTOCBS_LQ01
Any help would be appreciated

Soumya,
Refer Abhy's reply in the below thread
XI JMS error MQJMS2005 : failled to create MQQueuemanager for ....
raj.

Error in JMS Adapter while communicating with WebSphere MQ 7.5

Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.

Problem solved after removing j2ee.jar file from classpath !

Error with JMS adapter

We are using a JMS adapter with XML input files and we are getting the following error:
:#1.#00144F80C55600310000001A00001BC700DD9B18A4E85181#1288983973313#com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer##com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer.handleRetriesOnException(MessagingException, QueueMessage, MessageController)#J2EE_GUEST#223963##<applicationserver_hostname>_<SID>_623765##8bfba530dea111dfbf9b00144f80c556#MS Queue Worker [JMS_http://sap.com/xi/XI/SystemSend]##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#JMS_http://sap.com/xi/XI/System#com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server#http://<hostname>:50000/sap/xi/engine?type=entry#
One that is interesting is that these errors are occurring on application servers only. Could it be that the Integration Server URL is not fully qualified. In the SLD it's just <hostname>, not <hostname>.test.com (as an example).
Any help is greatly appreciated.

Dear George,
Concerning the issue, in the Integration Engine please try increasing the value of the parameter :
   - icm/HTTP/max_request_size_KB
from the default size of 100MB to e.g., 2GB.
Kindly go through the following link :
- http://help.sap.com/saphelp_nwpi71/helpdata/en/58/108b02102344069e4a31758bc2c810/frameset.htm
for details.
Additionally, it is recommended to setup a large message queue,
i.e.,
add an entry and appropriate value (e.g., 20480 KB) for the TUNING parameter : 'EO_MSG_SIZE_LIMIT'
using
TCODE
   sxmb_adm
    Integration Engine Configuration
      Select Edit mode and Add the TUNING parameter
I Hope this helps.
Best Regards
Nishwanth

Error in JMS Adapter for MQ series

We have configured a JMS Adpater to connect to MQ Serries queue manager running on our local server. The XI Server is a remote server where JMS adapter is deployed.
Upon deployment we see following string in JMS adapter log -
Sender channel. Details: com.ibm.mq.jms.MQQueueConnectionFactory
And the status of Adpater is RED.
The Adpater is configured in sender mode.
We have created a local queue in Queme Manger and a Server Connectio channel which is being used in adpater configuration.
Please suggest what could be the missing link here.
Appreciate if you can provide us link s to any docuemtn which details the steps to configure an MQ JMS adapter.
Thanks,
Garima

Hi Garima,
Please check the following:
1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
2. Check the existence of your JMS drivers.
3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
Any of the above solutions should help you solve the problem.
Regards,
Abhy

Error in reciever JMS adapter (SENARIO FILE - XI- JMS )

HI everyone,
My previous error is solved (Error in getting initialcontext). I have deployed the required jar files on server.
Thanks to you'll.
Now I am getting the following error in JMS adapter monitoring RECIEVER CHANNEL . NO DETAIL INFORMTION SET.
i AM USING IBM websphere MQ series for recieving JMS messages from XI.
I have made Queue manager,
Queue,
reciever channel.
and have also provided the following details in my communication channel in XI
QueueConnection FactoryJavaClass : com.ibm.mq.jms.MQQueueConnectionFactory
QueueJavaClass : com.ibm.mq.jms.MQQueue
Ip address or server name : <my ip address> since i have installed IBM JMS server on my system.
server port :1415
QueueManagerName :QM_apple
channel name : reciever_channel
jms Queue: Q1
character set id (ccsid): This I have not given , Idont know what to give here
Transport protocol :tcp/ip
Please guide me to go further , I am stucked at the error , No reciever details set. What should i do?

Hi Deepak ,
Please refer this forum post .. if this helps.
Reg:Receiver Mail Adapter
Regards,
srinivas

Message "Lost" in a JMS adapter.

hi to all,
i need to connect XI to IBM Websphere MQ, using JMS adapter.
I did it well, i can exchange the message perfectly, but i have a strange behavior when websphere send message(XML) on queue with same_msgId for all message.
In this case i receive just the first of a series of message, and i "loose" the other, i know that the problem is the unique msgId of MQ, but how can i catch the error in jms adapter?
or how can i keep persistent the message in queue?
i've check the flag 'Transactional JMS session' to keep it persistent.
I wold like that mine JMS adapter answer with an error or don't consume the message keeping it in the queue.
thanks in advance
Claudio.

Hi Prateek,
i dont think by adapter module in this scenario you can raise an alert......because the problem is with uniqueness of msgID.........but every msg has a msgID so your adapter module will process every msg in the sameway.........but since the msgID is same, then only the first msg will be processed and the other msgs when they will try to store their msg processing data in XI database, they will fail because already the first msg processing data has that msgID, so the remaining msgs will be rollbacked by XI.............
Hi Claudio,
you will have to find a way in MQ to stop this thing of multiple msgs being generated by same msgID......i think there may be some property in MQ which will decide how and when a new msgID should be generated........just see this thing in MQ.............there should be a way in MQ which shall generate a unique msgID for each msg.........
Thanks,
Rajeev Gupta

JMS Adapter problem

Hi,
I am getting this error in JMS adapter when I am trying to send messages from XI to Weblogic server. Can somebody help on this?
Receiver channel. Details: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
Thanks
Kalyan

Kalyana
The error states it cannot instantiate the class WLInitialContextFactory which creates initial contexts for accessing the WebLogic naming service. So go through the below url for more info. on this and configure accordingly.
http://edocs.bea.com/wls/docs70/javadocs/weblogic/jndi/WLInitialContextFactory.html
Also just try to configure accroding to:
http://help.sap.com/saphelp_nw2004s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
Configure the JMS settings according to:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
---Satish

Unable to deploy JMS adapter

hi
i have an problem when I finish to create an JMS adapter, JDEV display an message error
unable to get deployment file
i don't khow why??

Hi
its an error when i finished to create an JMS adapter, i was refereced to the topic of the JMS adapter
http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28994/adptr_jms.htm#BABCCBFB
i realised all step for creating an JMS adapter but when i "clicked" finish he give me this error so JMS adapter doesnt create.
thanks

JMS Adapter timeout property

How do I set timeout property for JMS adapter in BPEL in SOA Suite 10g ?
Scenario :
In one of the business scenarios, a JMS message in enqueued to WebLogic JMS queue from BPEL process.
There is a asyncronus invoke activity to the JMS adapter partner link.
This invoke activity to the JMS adapter took 15 mins in one of the invocations and hence giving timeout to the bpel client.
Query :
Is there any way I could set the timeout for this invocation, either at partner link level or a JMS adapter connection factory level.

Hi,
This is supposed to solve ERRJMS_PROVIDER_ERR error for JMS adapter.
Please refer metalink NOTE:393468.1.
I am not sure if it works for 10.1.2.0.2 version but probably it works on 10.1..3.X version.
Regards,
Ved

JMS Adapter UseMessageListener property...

What is the use of the 'UseMessageListener' property that needs to be set as true / false while configuring an Inbound JMS Adapter Service. What difference does the true / false value make to the runtime working of the Service? Thanks in advance.

Hi,
This is supposed to solve ERRJMS_PROVIDER_ERR error for JMS adapter.
Please refer metalink NOTE:393468.1.
I am not sure if it works for 10.1.2.0.2 version but probably it works on 10.1..3.X version.
Regards,
Ved

Error status in JMS adapter - sync / async brigde. Message processed ok

Hi guys
I'm having som trouble with my scenarion. I'm sending sync message from SAP backend to XI using proxy. From XI onwards to JMS adapter async (and the other way around for the response message).
This works OK. However i have a status error in my RWB on the JMS adapter. There is er red exclamation mark and a text saying:
Correlation ID 'XXX' of JMS request message 'ID:yyy' saved that correponds to XI message 'XXX'
How do I get my adapters in status green?
Kind regards
Martin

Hi Kai
Oh - OK
Settings are:
Receiver JMS channel:
Set JMSCorrelation to: XI Message ID (MessageID)
Store JMS CorrelationId of request: Mark
Sender JMS channel:
Set XI Message ID (MessageID) to: GUID (Recommended Value)
Set XI Conversation ID (ConversationID) To: Stored JMS CorrelationId of Request.
Kind regards
Martin

Error in JMS adapter MQ to PI

Similar Messages

Maybe you are looking for