Error in JMS Sender Adpater

Hi
I am doing Weblogic-PI-File scenario
when i try to pick the XML file from Weblogic JMS queues its giving the follwing error
Error occurred while processing message: 552eec87-b6c3-4035-2675-cc3cd57b5487. Detailed error (if any): com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_File_Sender xmlns:ns0="urn:XXXXXXXX.com:JMSReciever"><SalesOrderDetails><MRNNumber>1234</MRNNumber><FirstName>ABC</FirstName><LastName>CDE</LastName><SocialSecurity>1234567890</SocialSecurity></SalesOrderDetails></ns0:MT_File_Sender> to XI message for message: 552eec87-b6c3-4035-2675-cc3cd57b5487: TransportException: No MIME header found
Edited by: S V on Jan 27, 2009 1:08 AM

Hi I am using Weblogic JMS Queues ..
and the connection parameters i am using :
JNDI LOOKUP NAME FOR QUEUE CONNECTION FACTORY:
mm.jms.VendorConnectionFactory
JNDI LOOKUP NAME OF JMS QUEUE: mm.jms.PIOutboundTestQueue
NAME OF JNDI INITIAL CONTEXT: weblogic.jndi.WLInitialContextFactory
JNDI SERVER ADDRESS : t3://vendor.xxx.xxxxxxx.com:6107
JNDI LOGON USER : xxxxxx
JNDI LOGON PWD : XXXXXX
did i miss anything ... or do i have configure anything on JMS sender adpater so that it will convert the text message into Binary

Similar Messages

Error in JMS Sender (CPALookupException)

Hi,
I have a JMS to SOAP Sync scenario, and i'm getting an error while returning answer to JMS.
the error is:
com.sap.aii.af.service.cpa.impl.exception.CPALookupException : Couldn't retrieve binding for the given channelID:
can someone help ?
changing CC name didn't help.
TX
Edited by: Zevik Heinoch on Sep 13, 2010 11:36 AM
Edited by: Zevik Heinoch on Sep 13, 2010 11:40 AM

I will check the CPA,
I think it is important to say that the error shows in the sender CC, but the name given in the error is the receiver JMS CC, the PI can't find the receiver JMS cc to complete the scenario.

Error in SOAP Sender Adpater

hi
I am SOAP to RFC scenario.. when i am testingthe WSDl from Altova it giving me the follwing error
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message bb9025d0-14a1-11de-bd25-001a4b0aa09f(OUTBOUND) expired.
do i have to change any settings
SV

Hi SV,
I am also getting the same error.
Did you get any solution for this?
I will be grateful to you if you can help me.
Please help!
Thanks & Regards
Gopal

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

EOIO JMS Sender Channel in Error

Hi All,
We have a error on JMS sender channels in Pre-Production environment.
Let me explain you the problem.
On Dev and QA there is no cluster environment. On Pre-production we have 3 clusters. We tested this Sender JMS channel on Dev and QA without giving a Cluster ID and it worked.
Now on Pre prod, we had not mentioned the cluster ID and when messages were picked from the Queue, the channel went into a error mode stating the " Channel is locked due to EOIO".
Then when we added the cluster ID to the channel, in RWB the channel goes into inactive mode. The status is " The EOIO channel has been made inactive on Node 206485150"
The node mentioned in channel is 251902150. This means that the other node has been made inactive. That sounds logical as it is not supposed to process the message.
But the node which is mentioned in the channel has also gone into error mode.
" Error creating JMS connection. failed to create MQManager for ' Hostname:Channel name'". An MQException occured: Completion code 2, Reason 2009
MQJE016: MQ queue managerclosed channel immediatly during connect. Closure reason= 2009, and erro code as MQJMS2005
After this all other sender JMS channels have gone into the same error mode on this node.
We have stopped the JMS service and started it. We also restarted the XI server but no change was encountered.
Please let us know whether JMS sender with EOIO works with cluster ID as I'm not able to find any document which says that JMS with EOIO works succesfully.
Please also let us know how to overcome the error on this node.
Thank you.
Regards,
Sarvesh Desai

Check if there is any unprocessed message stuck in the queue:
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework

JMS sender communicaton channel error

Hi,
The JMS sender communication channel throws the following error in Communication Channel monitoring in RWB.
<b>Channel started but Inactive</b>
<b>"Channel removed; check whether channel was deleted or moved to another Adapter Engine"</b>
But the channel is active and a copy object of the same channel works succesfully.
Has anyone faced such an issue?
Thanks,
Ambili

Hi Abhishek,
Thanks for ur reply.
1. Already tried it, but still the same status.
2. Yes, i can see the channel in sxi_cache.
3. Tried this several times, same message.
The issue is just for this channel and as I mentioned before, a copy object of the same channel works perfectly fine.
Thanks,
Ambili
Edited by: Ambili Jose on Jan 19, 2010 7:30 AM

JMS sender cc error: Error while calling operation 'setChannel' for object

Hi guys,
I'm getting following error in my sender JMS adapter which tries to connect to Websphere MQ:
Error while calling operation 'setChannel' for object '| com.ibm.mq.jms.MQQueueConnectionFactory
it is then followed by connection and system parameters.
Any idea, what could be wrong?
I also doubt about cc's connection parameters:
- transport network protocol: should I use TCP/IP or WebsphereMQ?
- JMS compliant: non-JMS or JMS compliant?
thanks for your help,
olian

Hi Olian,
the configuration of a JMS adapter requires close working with the MQ team. they are best people to tell you what is the correct parameter value.
depending on the "transport protocol" he will be able to help you complete the configuration.
if you have chosen "websphere MQ (non-jms)", the transport/network protocol and Jms-compliance depends on the configuration made on the network and MQ.
Raghu

JMS sender channel error

hi,
i am using pi 731 single stack.
i have a jms sender channel. The jms sender channel is connecting to Webshere MQ version 6.0.2.10.
the error is -
Error creating JMS connection : The JMS provider gave the error message as MQJMS2005:failed to create
MQQueueManager for x.y.com:QMgr1 MQJE001 completion code 2,Reason 2059,and the error code as MQJMS2005
What could be the issue. The JMS drivers are successfully installed.

Hi,
As Indrajit said seems to be a JMS configuration problem. Check this thread in stackoverflow with the same error: java - Always receive MQJE001: Completion Code &#39;2&#39;, Reason &#39;2059&#39;. ERROR - Stack Overflo…
Regards.

JMS sender error in case MQ websphere---Please help

Hi SDN,
I am stuck in configuring JMS sender adapter for MQ series.After creating all objects
I have activated the scenario.I got an exception message in the sender JMS channel.It is :
XI inbound processing failed for message at 2007-05-08|13:30:21.009+0300. JMS and XI identifiers for the message are ID:414d512046494b594d5a2020202020204614d148001e50e2 and 1f7c5fd0-fd4f-11db-ab43-aabfb000d002 respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Exception thrown in method process. The transaction is marked for rollback.
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java(Compiled Code))
at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java(Compiled Code))
at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java(Compiled Code))
Please help. The scenario is MQ ---> SAP.
Regards,
Mansoor

Hi SDN,
This is very important for me. Can anybody resolve the problem.
The scenario is MQ --> SAP. I have configured sender JMS adapter like this.
Transport protocol : WebsphereMQ(nonJms)
QueueConnectionFactory Java Class : com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
IP Address or Server Name: XXXXXXX
Server port: 1421
Queue Manager Name: TestAPI
Channel name : TestAPI
JMS Queue: TestQ
XI settings:
mapping of message: Message payload= JMS payload
Please let meknow if you need any more details.
Regards,
Mansoor

JMS Send Transaction Failing, due to resources could not be assigned

I am trying to get a transaction of a JMS send to work where the origination of the send occurs in domain A and the message queue is hosted in domain B. I have been able to get this to work; however, this issue has shown up in recent tests. I haven't changed anything other than the version of the Oracle database client that is being used. I don't see any relationship between that and the persistent store.
Both domains are hosted on the same computer and both domains are simple development domains. Trust is established between the domains using 'global trust'.
I'm running Weblogic Server 10.3.4..
I'm not sure how to get around this issue. I can't find any documentation...
My suspicion is that there needs to be some special configuration for the transaction, since I'm using the default persistence store. The warnings seem to indicate the problem. The AdminServer is hosted on domain A and the AuditAdminServer on domain B...
Any assistance will be greatly appreciated!
Thanks in advance...
Here is the stacktrace:
<Apr 11, 2013 11:17:05 AM MDT> <Warning> <JTA> <BEA-110405> <Resource WLStore_audit_domain__WLS_AuditAdminServer was not assigned to any of these servers: AdminServer AuditAdminServer >
<Apr 11, 2013 11:17:25 AM MDT> <Warning> <JTA> <BEA-110405> <Resource WLStore_audit_domain__WLS_AuditAdminServer was not assigned to any of these servers: AdminServer AuditAdminServer >
<Apr 11, 2013 11:19:47 AM MDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB gov.va.med.datasharing.core.ServiceBusImpl.processInbound(java.lang.String,java.lang.Object)],Xid=BEA1-003FA101855115C0DB45(13340960),Status=Rolling Back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: WLStore_audit_domain__WLS_AuditAdminServer],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=183,seconds left=22,XAServerResourceInfo[DefaultXADataSource_vhie_domain]=(ServerResourceInfo[DefaultXADataSource_vhie_domain]=(state=rolledback,assigned=AdminServer),xar=DefaultXADataSource,re-Registered = false),XAServerResourceInfo[WLStore_audit_domain__WLS_AuditAdminServer]=(ServerResourceInfo[WLStore_audit_domain__WLS_AuditAdminServer]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[WLStore_vhie_domain_VhieFileStore]=(ServerResourceInfo[WLStore_vhie_domain_VhieFileStore]=(state=rolledback,assigned=AdminServer),xar=WLStore_vhie_domain_VhieFileStore1316539,re-Registered = false),SCInfo[vhie_domain+AdminServer]=(state=rolledback),SCInfo[audit_domain+AuditAdminServer]=(state=rolling-back),properties=({weblogic.transaction.name=[EJB gov.va.med.datasharing.core.ServiceBusImpl.processInbound(java.lang.String,java.lang.Object)]}),local properties=({weblogic.jdbc.jta.DefaultXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+192.168.1.120:7001+vhie_domain+t3+, XAResources={WLStore_vhie_domain_VhieFileStore, SDSDataSource_vhie_domain, DefaultXADataSource_vhie_domain, eis/jms/WLSConnectionFactoryJNDIXA, WSATGatewayRM_AdminServer_vhie_domain},NonXAResources={})],CoordinatorURL=AdminServer+192.168.1.120:7001+vhie_domain+t3+): weblogic.transaction.RollbackException: Aborting prepare because the following resources could not be assigned: WLStore_audit_domain__WLS_AuditAdminServer
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1881)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:345)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:625)
     at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:49)
     at weblogic.ejb.container.internal.BaseRemoteObject.__WL_postInvokeTxRetry(BaseRemoteObject.java:444)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:53)
     at gov.va.med.datasharing.core.ServiceBus_r6xnti_ServiceBusImpl.processInbound(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
     at $Proxy89.processInbound(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
     at $Proxy91.processInbound(Unknown Source)
     at gov.va.med.datasharing.web.ServiceBusDelegate.processInbound(ServiceBusDelegate.java:43)
     at gov.va.med.datasharing.web.adc.PatientServiceImpl.changeADCStatus(PatientServiceImpl.java:58)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:69)
     at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:97)
     at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:81)
     at org.springframework.expression.spel.ast.SpelNodeImpl.getTypedValue(SpelNodeImpl.java:102)
     at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:98)
     at org.springframework.binding.expression.spel.SpringELExpression.getValue(SpringELExpression.java:84)
     at org.springframework.webflow.action.EvaluateAction.doExecute(EvaluateAction.java:75)
     at org.springframework.webflow.action.AbstractAction.execute(AbstractAction.java:188)
     at org.springframework.webflow.execution.AnnotatedAction.execute(AnnotatedAction.java:145)
     at org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:51)
     at org.springframework.webflow.engine.support.ActionTransitionCriteria.test(ActionTransitionCriteria.java:82)
     at org.springframework.webflow.engine.support.TransitionCriteriaChain.test(TransitionCriteriaChain.java:71)
     at org.springframework.webflow.engine.Transition.canExecute(Transition.java:195)
     at org.springframework.webflow.engine.Transition.execute(Transition.java:211)
     at org.springframework.webflow.engine.impl.FlowExecutionImpl.execute(FlowExecutionImpl.java:393)
     at org.springframework.webflow.engine.impl.RequestControlContextImpl.execute(RequestControlContextImpl.java:214)
     at org.springframework.webflow.engine.TransitionableState.handleEvent(TransitionableState.java:119)
     at org.springframework.webflow.engine.Flow.handleEvent(Flow.java:555)
     at org.springframework.webflow.engine.impl.FlowExecutionImpl.handleEvent(FlowExecutionImpl.java:388)
     at org.springframework.webflow.engine.impl.RequestControlContextImpl.handleEvent(RequestControlContextImpl.java:210)
     at org.springframework.webflow.engine.ViewState.handleEvent(ViewState.java:232)
     at org.springframework.webflow.engine.ViewState.resume(ViewState.java:196)
     at org.springframework.webflow.engine.Flow.resume(Flow.java:545)
     at org.springframework.webflow.engine.impl.FlowExecutionImpl.resume(FlowExecutionImpl.java:258)
     at org.springframework.webflow.executor.FlowExecutorImpl.resumeExecution(FlowExecutorImpl.java:169)
     at org.springframework.webflow.mvc.servlet.FlowHandlerAdapter.handle(FlowHandlerAdapter.java:183)
     at org.springframework.webflow.mvc.servlet.FlowController.handleRequest(FlowController.java:174)
     at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
     at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)
     at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)
     at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:915)
     at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:822)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:796)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:180)
     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: WLStore_audit_domain__WLS_AuditAdminServer
     at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:1153)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2200)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:279)
     ... 77 more
.>

It turns out that those packages are, indeed, in extra.
I didn't think to look there, since I assumed that everything needed by base would be in [core].
I assumed wrong.

Error in File sender Adapter

Hi All,
I am currently getting the following error in the communication channel monitoring for Sender adpater, when it is trying to get the files from the server.
Could not process due to error: java.lang.NullPointerException: while trying to get the length of an array loaded from local variable 'dirList'
Please let me know if anyone has come across this issue before.
- Venkat

Hi,
I am not doing any file content conversion. Its just a pass through interface.
It picks file from one server and places it on the other
Let me know
- Venkat

Need help about setting up a JMS sender channel

I just started to play with PI for a few weeks and I'm trying to setup a simple JMS sender channel to read stuff from a WebSphere MQ.
I've someone installed JMS adaptor for me, but we never know it is correctly installed or not. First question is "Is there any way we can verify JMS adapter is correctly installed or not?"
In the Design: integration builder, I've a very defined a very simple data type(src_dt) which is a string and a message type(src_mt) which uses resp_dt. Finally I created a message interface (test_mia_out) that contains src_mt. At this point of time, I don't need message mapping so I didn't configurate this section.
Then I went to Configuration: Integration builder and created a new communcation channel with the following setting:
Parameter section:
Adapter Type: JMS
Transport Protocol: WebSphereMQ (Non-JMS) <- if i don't use this option, i can't enter MQ connection detail in the Source section.
Message Protocol: JMS 1.x
Adapter Engine: Integration Server
Source section:
QueueConnectionFactory Java Class: com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
...MQ connection detail...(IP, Port, Queue Manager, Channel and Queue Name )
Transport Protocol: TCP/IP <- this is consists to server side setting
JMS-Compliant: JMS-Compliant
Since I only want a very simple working sample, again I didn't change the content in receiver determination, interface determaintion and sender agreement.
Now when I active this change and I saw the following error in the channel monitor:
Short Log - Channel has internal error
Admin Info - Exception: Channel with Status Unknown or Not Registered
I did stop and start the service, refresh CPA cache and even restart the entire PI server, I always see this message and cannot find any more detail description about what is causing this problem.
My PI Server version is 7.0 and MQ version is 5.3
There's very limited resource about how to setup to read MQ message in PI and I'm stuck now. Therefore, I need a help from some experienced people to tell me if I have did something wrong or missed some steps?
And if possible, could people mind to post a step by step go through how you setup it up?
Edited by: Robert Fu on Jan 10, 2008 6:51 AM

Before you use the JMS, you need to deploy some drivers related to specific MQseries, Kindly ensure that proper driver are deployed....
If you use MQSeries 53x.xxx, you must enter the following JAR files in aii_af_jmsproviderlib.sda.
com.ibm.mq.jar, com.ibm.mqbind.jar, com.ibm.mqjms.jar, connector.jar (use the JAR file from the J2EE client directory)
check this link it will give you more inofmration
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
check this to get the condifuration the JMS
How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Ref How To Use the Content Conversion Module in JMS Adapter - https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000582377&

JMS Sender Communication Channel problem

Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
Thanks

HI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup

JMS sender communication channel content conversion

Hi,
I struck with the content conversion in the JMS Sender communication channel.
I have configured the communication channel with the filed fixed lengths. (Simple type)
The field fixed lengths i have given are 10,2,3,11
The contents in the file 1000000072 230 111
but, in the input xml after conversion iam getting 100000007 in the first field and 2 in the second field 23 in the third field.
I have configured the sender communication channel as in the document in SDN.
Even, i configured several communication channels. I didn't get this strange error any time.
I have gone through SDN to fix this issue, but i didn't get solution.
If anyone got rectified this kind of error, please answer your solution to me
Thanking you,
Regards,
Krishnaraju.

Hi,
Thanks for all your support. The issue got resolved.
The issue is due to the file, In the file the special characters are appearing. We are not able to see these characters in the notepad, wordpad, text editor.
But, these characters are appearing in th syn text editor. So, we removed those characters and processessed the file. Now, it is successfull.
Regards,
Krishnaraju.

NameNotFoundException in JMS Sender Adapter

Hi,
I am doing JMS to File Scenario.
In the JMS Sender Adapter, I am getting the following error.
Channel error occurred. Detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection factoryQueueConnectionFactory, for profile: ConnectionProfile of channel: JMS_Senderon node: 215438950 having object id: 8a69f5589d733e01b34a6dd53c6c4acf: javax.naming.NameNotFoundException: QueueConnectionFactory in QueueConnectionFactory not found at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:134)
Can someone let me know why this error is happening and the solution ?
Thanks in advance,
Neena

Hi Neena,
What JMS server are you using?
This seems the parameter settings in JMS sender is incorrect. check this link for vendor specific details
http://help.sap.com/saphelp_nw04/Helpdata/EN/c1/739c4186c2a409e10000000a155106/content.htm
Hope the JMS drivers were installed properly!!!
Regards
Suraj

Error in JMS Sender Adpater

Similar Messages

Maybe you are looking for