Error in JMS channel

Hi ALL,
I am getting the below error in Communication channel monitoring short log of JMS channel.
"Cannot connect because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing; ensure that JMS provider library 'aii_af_jmsproviderlib.sda' contains all required resources"
This error looks like the deployed .sda file dint contain the class specified.Can u let me know where i can find the aii_af_jmsproviderlib.sda file with all required classes in it .
We are on SAP XI 7.0 SP 14 and the MQ version is 7.0.
Kindly let me know if any one had faced the same error.
Regards,
Rajesh

Hi, check this links.
XI to IBM Websphere Default JMS Provider with JNDI
JMS receiver adapter configuration error
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Edited by: Marco Salazar on Dec 9, 2009 5:24 PM

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

  • Sender JMS Channel Error

    Hi all,
    I have been facing with this problem with sender JMS channel, any pointers as to where can be the solution for it
    The error details are as follows
    JMS and XI identifiers for the message are ID:414d512056515933444e41575445202048aa8802235bad01 and a2d32e30-7aae-11dd-ae1c-001125cc0c0c 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
    at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:963)
    at com.ibm.mq.jms.MQMessageConsumer.receiveAsyncQ(MQMessageConsumer.java:2539)
    at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4262)
    Messages are not being placed in the Queue. the Queues are newly created is there something which has been missed out during the creation of the Queues
    Rgds
    Aditya

    Hi Aditya
    Try this way:
    1. uncheck JMS transactional session check box in JMS sender communication channel.
    2. Once it is done, insert new message in JMS queue.
    Thanks
    Sai

  • 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.

  • JMS Channel error

    JMS Channel is thrrowing error with an error code:2007.
    Error code description is  "CharAttrs is not valid. The parameter pointer is not valid, or points to read-only storage for MQINQ calls or to storage that is not as long as implied by CharAttrLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)".
    But i didnt understood this jargon.
    Could anyone help me what i need to do to fix this .
    Thanks in advance.

    Hi Pola,
    I have never faced this error but as in my helping nature here are some pointers:
    CharAttrLength (MQLONG) - input
    Length of character attributes buffer.
    This is the length in bytes of the CharAttrs parameter, and must be at least the sum of the lengths of the character attributes specified in the Selectors array. Zero is a valid value if there are no MQCA_* selectors in Selectors.
    CharAttrs (MQCHAR×CharAttrLength) - input
    Character attributes.
    This is the buffer containing the character attribute values, concatenated together. The length of the buffer is given by the CharAttrLength parameter.
    The characters attributes must be specified in the same order as the MQCA_* selectors in the Selectors array. The length of each character attribute is fixed (see Selectors). If the value to be set for an attribute contains fewer nonblank characters than the defined length of the attribute, the value in CharAttrs must be padded to the right with blanks to make the attribute value match the defined length of the attribute.
    If the CharAttrLength or SelectorCount parameter is zero, CharAttrs is not referred to; in this case, the parameter address passed by programs written in C or System/390 assembler may be null.
    Regards
    joel

  • Error with JMS receiver channel

    Hi,
    We have a scenario in which Order response will be sent from ECC to WebLogic (JMS system) through PI.
    After the restart of JMS, we are facing issues with JMS receiver channel.
    Some of the responses are delivered, and for few we have the error as described below.
    Also, one of the cluster node of the JMS receiver channel has the below error.
    Please anybody throw some light on this.
    Error description:
    " 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: Pending message discovered: dfff2e2b-80f5-94f1-a068-001cc4d99b3e.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling  channel parameter to 'Bypass' and restart the message afterwards.. "
    Thanks in advance.
    Regards
    Bhanu Tiruveedula.

    Hello Bhanu,
    we have been getting this error from long time with JMS channel but no solution except changing the configuration so that it can throw exception and move on.
    we have also noticed that this happens for some time and then gets resolved automatically. so it seems to be some data which is not expectable by jms channel.
    regards,
    Ratna

  • 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

  • JMS Channel error reson code : 2019

    JMS Channel is throwing error with an reason code : 2019.
    Decription for reason code 2019 is : The object handle Hobj is not valid, for one of the following reasons:
    The parameter pointer is not valid, or (for the  MQOPEN  call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
    The value specified was not returned by a preceding  MQOPEN  call.
    The value specified has been made invalid by a preceding  MQCLOSE  call.
    The handle is a shared handle that has been made invalid by another thread issuing the  MQCLOSE  call.
    The handle is a nonshared handle that is being used a thread that did not create the handle.
    The call is  MQGET  or  MQPUT , but the object represented by the handle is not a queue.
    Can any one tell me what is to be done to fix this error.
    Thanks in advance.

    Hi
    Yes this is an MQ Series "Reason Code", Where each reason code for failing is assigned a number. For this one please refer to the following link:
    http://www-01.ibm.com/support/docview.wss?uid=swg21229508
    For all reason codes have a look at:
    http://middleware.its.state.nc.us/middleware/Documentation/en_US/htm/csqzak06/csqzak065m.htm
    Thanks
    Damien

  • 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

  • Zip or unzip a payload in sender JMS channel

    Hi,
    My scenario is to unzip a payload in sender JMS channel and I have configured the sender JMS module in the below format,
    Processing sequence
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    Module Configuration
    Modulekey            Parameter Name                    Parameter Value
    zip                        zip.mode                                unzip
    I have tried this format also,but it is not working
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    (or)
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    While performing testing,it throws the below error in sender JMS channel,
    The detailed error (if any) is :  com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable pattern: NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable 'pattern'at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:185)
    Can someone help me on how to extract a payload in sender JMS channel.
    Also please guide me on how to extract a multiple payloads in one zip file in sender JMS channel.

    Hi,
    Your module sequence seems to be incorrect.
    Try like this,
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    (or)
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    Regards,
    Praveen Gujjeti

  • Unzip a payload in sender JMS channel

    Hi,
    My scenario is to unzip a payload in sender JMS channel and I have configured the sender JMS module in the below format,
    Processing sequence
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    Module Configuration
    Modulekey            Parameter Name                    Parameter Value
    zip                        zip.mode                                unzip
    While performing testing,it throws the below error in sender JMS channel,
    The detailed error (if any) is :  com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable pattern: NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable 'pattern'at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:185)
    Can someone help me on how to extract a payload in sender JMS channel.
    Also please guide me on how to extract a multiple payloads in one zip file in sender JMS channel.

    Hi,
    Your module sequence seems to be incorrect.
    Try like this,
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    (or)
    SAP XI JMS Adapter/ConvertJMSMessageToBinary     Local Enterprise Bean       convert_JMS2Bin
    AF_Modules/PayloadZipBean Local Enterprise Bean    Local Enterprise Bean       zip
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage     Local Enterprise Bean       convert_Bin2XI
    CallSapAdapter                                                         Local Enterprise Bean      call_AF_MS
    Regards,
    Praveen Gujjeti

  • 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

  • JMS channel issue

    Hi
    My XI system is set-up with alerts frame-work and we are able to raise almost all the system generated alerts. But we are facing one issue with JMS channel alerts. Lets me explain the problem.
    We have a JMS channel connected to JMS Server and we are publishing the messages on JMS queue. When JMS server is down, the channel status is not turning into red and it is staying in gree only. If we see the messages in adapter engine (through message monitoring) they are in delivering mode and they are not going into system error state. So either of the things are not triggering any system alerts. So are there any parameters that we can set-up in JMS channel or somewhere so that when JMS server is down, we can raise the system alerts ?? We are using the EMS server for hosting the JMS queues.
    thanks
    kumar

    Hi Moorthy
    yes! as you said, my main problem is..... channel is not turning into red, eventhough my JMS server is down and there by not able to raise the alert in either of the two cases.  (Adapter Engine based standard alerts or CCMS Alerts). Is there any option to set through which when jms server is down, channel will become red ??
    thanks
    kumar

  • Advance selection for source file-Error in communication channel monitoring

    Hi all,
    Referring to the link below:
    <b>/people/mickael.huchet/blog/2006/09/18/xipi-how-to-exclude-files-in-a-sender-file-adapter
    I have developed my scenario in the same way.But due to the values <b><NOTHING></b>
    in Mandatory fields Source Directory and Filename,i am facing problem in Communication Channel Monitoring as it shows an error;even though the end-to-end scenario works successfully.
    Plase note that  our scenario is not to exclude the particular file but to pick the files serially after a certain delay.
    Kindly provide some idea about how can we remove the error from Communication Channel Monitoring.
    Thanks & Regards,
    Sudhir Tiwari

    Sudhir,
    In the sender file adapter, you have an option called <b>"Processing Sequence"</b>.
    By selecting ByName or ByDate you can make files get selected sequentially either ByName ( alphabetically ) or by the creation time stamp of the file.
    In the sender file adapter also make the QOS as EOIO and give the QueueName as any value and the files will be processed sequentially.
    Regards
    Bhavesh

  • File to Proxy Scenario : Error in communication channel monitoring

    Hi,
    I have developed File to Proxy Scenario on PI 7.1 system and it is not working. I see the below error in communication channel monitoring.
    u201CError: com.sap.engine.interfaces.messaging.api.exception.ConfigException: Some of the IS access information is not available. SLDAccess property may be set to true, but SLD is not available.u201D
    File will be picked from the FTP server.
    I have created File system in SLD of type "Third Party", Can this be the issue?
    Please guide me on this.
    Thanks,
    Chandravadan

    Hi!
    Check if the tcode SLDCHECK is ok!
    Check note #764176.
    Also, refer to link below and execute each steps from the links there MANUALLY.
    Wizard-Based Configuration:
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/2e4c1b16bb4aa8e10000000a11466f/frameset.htm
    Regards,
    Caio Cagnani

Maybe you are looking for