JMS communication channel red

Hi all,
I have configured the JMS sender communication channel in ID. but the status is red. When i configured the JMS Adapter in Decentral adapter engine(with same details),the status is green.
Please help me out.
The error says that " Sender channel : details null"/
What should we do so as to make our communication channel green?
Need clarifications:
Communication channel config happens in central adapter engine....When i use decentral adapter engine, should i define communication channels also....
If yes, then it will be something like we are making use of both adapter engines right.
please correct me if i'm missing something.
Thanks and regards
rahul

Hi Venkat,
I tried the manual process. The document says that the meta-inf and server folder should be maintained in the sda file including the sub files and the path should be maintained for those sub files....But if i save the path info in the zip file, its returning error when i try to deploy(Error: attribute missing,vendor missing).
On removing the path info,i'm able to delpoy but the adapter status is red.
My SDA structure is not same as the one specified in the document.
i am not getting the meta-inf and server folder in that zip file.only the sub files are included.
please correct me if i am wrong.
Regards
rahul

Similar Messages

Error in JMS Communication Channel not raising alert

Processing Errors in JMS Communication Channel are not raising alerts.
The settings on the communication channel retires are set at 3 and 5min interval.
In RWB the JMS communication channel shows processing errors but an alert is not raised.
The alert are configured in our system and we even have a catch all alert rule with * (wildcard). Errors in PI message processing are raising alerts but errors in Comm Channel are not raising alerts.
The message in SXI_MONITOR shows as processed successfully but when we check the RWB and Comm. Channel Monitoring we see processing errors "Channel error occured; detailed error description: JMS error: Connection to the server has been terminated; Linked error: Connection reset, Error Code:null"
Are we missing any configuration? How do we get alerts/notifications if there are errors in Comm. Channel without having to login into RWB and watch it periodically?
Any help is greatly appreciated.
RM

Hi,
What is the staus of Communication channel in RWB when it fails, RED ??if yes then it should genarate alert.
create one more alert for specific to JMS interface and check it out.
Regards,
Raj

How to set errorDelay parameter in sender JMS Communication Channel?

Dear XI/PI Experts,
Do you happen to have a documentation on how to implement the errorDelay parameter and other general parameters in the sender Sender JMS communication Channel? Do you happen to have a step by step guide or pdf that I can use?
I look forward to hearing from you.
Thanks a lot in advance.
Kind regards,
Grace

Hi Thanks for your replies.
What I need to do is to implement this bullet point:
¡ errorDelay
The default value for this parameter is 0.
This parameter determines how long the system waits before processing further messages if an error occurs. In transactional processing, it can make sense to specify a certain time period, for example, because messages with errors remain in the queue following a ROLLBACK.
In which part of the Sender JMS Comm Channel will I implement this?
Should I put this under tab /Parameters/Processing/Error Handling Settings or should this be under /Parameters/Advanced/Additional Paremeters?

JMS ReplyTo Queue Name parameter in the receiver JMS communication channel

Hi All,
Can any please explain the use of JMS ReplyTo Queue Name parameter in the receiver JMS communication channel?
Thanks
Karthik.

Hi karthik,
JMS ReplyTo Queue Name parameter is used for Specify the name of the queue to which the responses are to be sent.
Thanks
Govind.

JMS communication channel

Hi,
We got an error in the JMS comunication channel.
After we got this error, we restarted the java stack. But then the
JMS communication channels did not resume the connectivity automatically.
We had to manually start and stop the channels. Even we tried making it 'Automatic' in the communication channel monitoring tab. But didnt help
Do we have to maintain any other settings?
Please help to rectify this.
Thanks,
John

Hi,
Just create two communication channels one for receiever and other sender message will be received from sender CC and then after mapping will go thru Receiver CC
While configuring the channel remeber to put the details like the channel name and queue from which you need to pick up the message and put the message as in yr case both are different
try to configure like this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
In addition to the below blogs also refer this
Async/Sync Communication using JMS adapter without BPM (SP 19)
Sync/Async communication in JMS adapter without BPM (SP19)
Exploring JMS and SAP-XI JMS Adaper
Check if you have your adapter module configured as said in the following help doc
http://help.sap.com/saphelp_nw70/helpdata/en/4d/a3bc97ff55c742af7faed661635baf/content.htm
Check these on Adapter module dev:
http://help.sap.com/saphelp_nw04s/helpdata/en/96/f04142099eb76be10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/32/43d84072378031e10000000a1550b0/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e21106cc-0c01-0010-db95-dbfc0ffd83b3
Check these Links ---
==>http://help.sap.com/saphelp_nw04s/helpdata/en/a3/63af1bbf09469fa1615c05f0daff6f/frameset.htm
==>http://help.sap.com/saphelp_nw04s/helpdata/en/a3/63af1bbf09469fa1615c05f0daff6f/frameset.htm
Hope These links will be Very Helpful to you...:)
Regards,
Suryanarayana

Errors on JMS communication Channel sonicMQ JMS Provider netweaver2004s

After deploying supplier specific jar's Sonic_Client.jar into aii_af_jmsproviderlib.sda.
I get the following error in the communication channel monitoring.
Channel CC_SONIC_RECEIVER is errornous, hence it cannot be started. See error messages ( Error during channel initialization; exception trace: java.lang.ClassCastException
 at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:372)
 at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 ...) before. Reconfigure it or restart the JMS service!
Any suggestions about the cause...

yes the drivertool.bat does it for me
<?xml version="1.0" encoding="UTF-8"?>
<provider-descriptor>
 <display-name>com.sap.aii.af.jmsproviderlib</display-name>
 <component-name>com.sap.aii.af.jmsproviderlib</component-name>
 <major-version>7</major-version>
 <minor-version>0</minor-version>
 <micro-version>6</micro-version>
 <provider-name>sap.com</provider-name>
 <references>
 <reference type="library" strength="weak">jms</reference>
 <reference type="library" strengh="weak">com.sap.aii.messaging.runtime</reference></references>
 <jars>
 <jar-name>sonic_Client.jar</jar-name><jar-name>sonic_XA.jar</jar-name></jars>
<
At this moment i am receiving the following error on the communication channel
Exception caught by adapter framework: The JMS channel with channel ID f055fe2451203cd5b39d81c7647b281e is errornous. Details:Error during channel initialization; exception trace: javax.jms.JMSException: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:2600 at progress.message.jimpl.JMSExceptionUtil.createJMSException(Unknown Source) at progress.message.jimpl.Connection.(Unknown Source) at progress.message.jimpl.QueueConnection.(Unknown Source) ... [104] progress.message.client.ENetworkFailure: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:260

SOAP over JMS Sender Communication Channel - How to?

Hello folks,
I have an async. scenario in which a SOAP message is posted to a JMS queue, then SAP PI picks up the SOAP message, extracts the payload and maps it into an IDOC to SAP.
Couple of questions...
1. Does the JMS adapter supports SOAP over JMS?
2. Can I get the entire SOAP envelope in SAP PI (just like the "do no use SOAP envelope" function works in the SOAP adapter) ?
3. Is the above scenario possible? Given the fact that my scenario (i.e. ccBPM, mappings, etc..) is expecting a SOAP envelope as input?
Thanks,
Rob

Ok, then I think I am on the right track, but still I cannot get this scenario to work.
JMS (SOAP)-> SAP PI(ccBPM) --> IDOC
I put SOAP messages on the sender queue, those messages dissapear from that queue, so I would expect that I can see them back in PI, but no trace is left behind in the monitoring area... It is like they've never been read from the input queue.
What is happenning with those messages? The definition of the SOAP envelope has been uploaded as an external definition and linked to a message interface in the repository.
JMS Communication channel checked but it is also fine.
Any clues where to look?
Thanks.

Error in JMS Input channels

Dear all,
We have observed a peculiar issue.
Some of the JMS Input channels are throwing this error:-
"Error establishing JMS connection; error message: MQJMS2005: failed to create MQQueueManager for <IP>:<QM Manager>> MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009; error code: MQJMS2005"
Other JMS channels with the same configurations are working fine. But some JMS channels have this error.
If any one has faced a similar issue, kindly share the steps to resolve the same.
Thanks in advance,
Younus

Please ask the MQ Team to restart the MQ queue.I mean to stop and start again.
We faced similar kind of issues and we even tried to restarting the JMS communication channel and MQ Queue.This solved our problem.
As only one JMS channel is not working,there might be connectivity issues with JMS Queues..
Try to restart the JMS Queue and JMS communication channel and see.

Communication channel parameters are not tranported in CTS+ transport

Hi,
My scenario is MDM to jms.
we have configured the cts+ transport in our system.
We transported the ESR and ID objects from development to Quality.
But in the sender mdm communication channel the everything is getting transported except Repository password.
when i checked in the quality system the Repository password was blank.
And receiver jms communication channel details are in
dev system
IP Address or server Name:135.12.14.12
server port                          :3321
Queue manange name       :RRTYRKB
channel name                  :KDIEKE.MDM
Quality System
IP Address or server Name:localhost
server port                        :1414
Queue manange name       :QM_hostname
channel name                    :S_hostname
i want know whether this is the case when we do the cts+ transport?
if it is the case should i edit the objects in the Quality sysem(which i don't want to do).
Thanks.
Regards,
Muniyappan.

Hi,
>>>if it is the case should i edit the objects in the Quality sysem(which i don't want to do).
communication channel attrubites always get reset in the new env - TEST, PRD, etc.
and you always need to fill them once more - this is the normal way
otherwise - would you like to use DEV parameters on PRD system ?
maintaining the channel attributes is a typical task on all landscapes
Regards,
Michal Krawczyk

Communication Channel Monitor status using UDF

I am writing a UDF to get the JMS adapter type status from "communication channel monitor"..
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey dkey = DynamicConfigurationKey.create(
"http://sap.com/xi/XI/System/JMS", "DCJMSCorreleationID" );
From here I don't how to get the status of JMS communication channel status, cluster node status and also the processing details..
I am also thinking, is there any I can get the JMS payload and parse it to get the required elements..
I badly need ur suggestion..
Thanks-GS

Hello Sreeram ,
Thanks for the Reply.I am working on PI 7.0 SP06 in a SAP Note I have read that
it is from PI 7.0 SP8 i think because of the lower SP level iam not getting the
Communication Channel Monitor displayed.
Note 1000528 - FAQ: XI 3.0 / PI 7.0 Adapter and Channel Monitoring
Regards
Prasad
Message was edited by:
prasad chintala

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.

JMS (Sender Communication Channel) and MQ in Mainframe (Legacy) System

Hi All,
Can we use JMS Sender Communication Channel in XI that runs on Windows 2003 server to DIRECTLY poll messages from MQ in Mainframe (Legacy) system??
I understand that we can install MQ on XI server and have mainframe push the messages to XI MQ so that JMS can poll but wanted to see if there is a way to do this without having MQ on XI server.
If you know of any documentation regarding this, can you please post it?
Thanks,
Jay

Jung,
Are you looking for this help:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Also check this sap help:
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
---Satish

Mail to File Integration(Mail Sender Communication channel status RED)

Hi all,
I am doing Email to File Integration Scenario, XI is reading mails from an particular exchange server mail id & putting it in to a file. now all IR & ID configuration is done.
But in RuntimeW Bench -> Adapter Monitreing The Sender Mail Communication Channel is RED with error occured: exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 00KC NO The requested item could not be found

We check the Exchange Server login Acess through TELNET ,as suggested from SAP Service marketplace
and login is successfull, with details available of Inbox
but in TENET when we try to execute the IMAP Status command error message comes
" expected space not found" .
Since XI is not able to read the inbox mail, so Sxmb_moni is blank.....
can any body suggest that this issus is related to that IMAP Status..........or some thing else..
our URL is correct.
Regards,
Ashutosh

the URL path was wrong...
it should end with .......exchange/Inbox/
the sender channel was having error RED ,but it was showing green status intially because delay update .....
Regards
Ashutosh

Sender JMS Synchronous communication channel not picking up files from JMS

Hello,
One of our Sender JMS synchronous communication channel (used Sync/Async bridge in the module section to make it Synchronous) is not picking up files from JMS system though the channel looks to be active (greeen).
When I am trying to stop the channel, it is giving error as "1 of 1 administered and selected channels have not been stopped", and after this when I start the cannel again it shows green but not picking up any files.
if anyone is haivng any solution for this, please reply back.
Thanks in advance.

Messages available in JMS system? please check queue's if message were there and it is not picking up then some thing wrong with cc.
simple solution create new communication channel with same details and try to use the same.

JMS communication channel red

Similar Messages

Maybe you are looking for