WLS 10.3.5 error with JMS

<entry key="java.naming.factory.initial" value="${xyz.JavaNamingFactoryInitial}" />
<entry key="java.naming.provider.url" value-ref="foresightconnectionurl" />
<entry key="java.naming.security.principal" value="" />
<entry key="java.naming.security.credentials" value="" />
</map>
</property>
</bean>
When i use these settings in my local weblogic 10.3.5 server to Listen to a TOPIC - it works fine !!I receive messages
But when the same is deployed in another environment with the same version of weblogic - we dont receive any messages instead the following warning keeps popping up:
org.springframework.jms.listener.DefaultMessageLis tenerContainer - Could not refresh JMS Connection for destination 'JMSModule1!ForeSightJMSUserRequestedData Topic' - retrying in 120000 ms. Cause: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
Strange thing is the same settings worked for Spring 2.5.6 version with out the credentials
<bean id="jndiTemp" class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<map>
<entry key="java.naming.factory.initial" value="${xyz.JavaNamingFactoryInitial}" />
<entry key="java.naming.provider.url" value-ref="foresightconnectionurl" />
</map>
</property>
</bean>
Note : in spring 2.5.6 we did not provide pricipal and credentials.But if i try the same with 3.05 release i get the following error.
<Apr 16, 2012 7:29:29 PM MDT> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: :org.springframework.beans.PropertyBatchUpdateExce ption:Failed properties: Property 'bus' threw exception; nested exception is org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name 'xyzTopicConnectionFactory' defined in class path resource [org/ihc/idea/ccc/consentwrapper/appcontext.xml]: Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER, Administrators]; Property 'transportIds' threw exception; nested exception is org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name 'foreSightTopicConnectionFactory' defined in class path resource [org/ihc/idea/ccc/consentwrapper/consentwrapper.xml]: Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER, Administrators]
at org.springframework.beans.AbstractPropertyAccessor .setPropertyValues(AbstractPropertyAccessor.java:1 02)
USER is my user ID .
Is this because our DEV environment WLS does not allow anonymous access?
What should be done to make WLS to allow anonymous access?
Edited by: 928049 on Apr 16, 2012 8:49 PM

You have two options:
OPTION 1: Enable Anonymous Admin Lookup
We have an option in WebLogic Server Security Configuration called AnonymousAdminLookupEnabled (Domain > Security > General). By default this is diabled. You can check the flag to enable it.
For further information,
http://docs.oracle.com/cd/E23943_01/web.1111/e13707/domain.htm#i1174143
OPTION 2: Pass the username and password credentials. OR setup cross-domain security.
Check the below documentation
http://docs.oracle.com/cd/E23943_01/web.1111/e13707/domain.htm#i1176046
Arun

Similar Messages

  • 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

  • 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 with jms receiver communication channel

    I am new to jms adapter
    I am getting ERROR:"Error connection due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Please ensure that all needed resources are present in the JMS provider library: com.sap.aii.adapter.lib.sda".
    How to resolve this issue?
    Please help to me
    Thanks
    Swathi

    Hi,
    Check all the jar files in aii_af_jmsproviderlib.sda
    See the list of files from below link
    http://help.sap.com/saphelp_nw70/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    or install the drives again i suppose som of jar files are missing on PI box or not deployed correctly.
    chirag

  • Server Error with JMS

    I have installed..WSAD5.1.2 with 5.0 Test Environment and IBM WebSphere MQ 5.3.
    I have created a PointToPoint Messaging Client. with a QueueConnectionFactory n Queue JNDI name.
    I am getting following problems during the server startup...
    *** Starting the server ***
    ************ Start Display Current Environment ************
    WebSphere Platform 5.0 [BASE 5.0.2 ptf2M0325.01] running with process name localhost\localhost\server1 and process id 2088
    Host Operating System is Windows 2000, version 5.0
    Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20030711a (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
    was.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
    user.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
    Java Home = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\java\jre
    ws.ext.dirs = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/ext;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/web/help;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.2/runtime/worf.jar
    Classpath = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/bootstrap.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/j2ee.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/lmproxy.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wteServers.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wasToolsCommon.jar
    Java Library path = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/jre/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;.;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;C:\IBM\WebSphere MQ\Java\lib;C:\dev\MKS\IntegrityClient\bin;c:\dev\Perl\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\dev\cygwin\bin;C:\dev\4NT302;C:\dev\apache-ant-1.5.4\bin;C:\dev\jdk1.3.1_08\bin;C:\dev\jakarta-tomcat-4.1.30\bin;C:\dev\mksscripts\src;C:\tbs\bin;C:\Program Files\IBM\WebSphere MQ\WEMPS\bin;c:\dev\MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;C:\IBM\WebSphere MQ\bin;;C:\IBM\WebSphere MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;.;C:\dev\NMake;C:\dev\ZipUnzip;
    ************* End Display Current Environment *************
    [6/7/04 11:59:06:000 IST] 4eee356d ManagerAdmin I TRAS0017I: The startup trace state is *=all=disabled.
    [6/7/04 11:59:06:516 IST] 4eee356d AdminInitiali A ADMN0015I: AdminService initialized
    [6/7/04 11:59:07:500 IST] 4eee356d Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
    [6/7/04 11:59:07:547 IST] 4eee356d SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
    [6/7/04 11:59:07:641 IST] 4eee356d SecurityCompo I SECJ0309I: Java 2 Security is disabled.
    [6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
    [6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0240I: Security service initialization completed successfully
    [6/7/04 11:59:09:797 IST] 4eee356d JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
    [6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0051I: Queue Manager open for business
    [6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0052I: Starting the Broker
    [6/7/04 11:59:11:297 IST] 4eee356d SystemErr R MQJE001: Completion Code 2, Reason 2085
    [6/7/04 11:59:11:297 IST] 4eee356d BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
    [6/7/04 11:59:11:328 IST] 4eee356d JMSService E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
    at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1527)
    at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1579)
    at com.ibm.ws.messaging.BrokerManager.attachToMQ(BrokerManager.java:439)
    at com.ibm.ws.messaging.BrokerManager.startBroker(BrokerManager.java:234)
    at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:194)
    at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
    at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
    at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
    at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    Please let me know what is the problem and how to solve it. This is urgent. Tnx

    Did you go into Websphere MQ and set up the queue you are using? Defining the queue in JNDI is not enough.
    Broker Manager unable to attach to Queue Manager - unknown Queue

  • WLS 5.1 not error with jdk 1.4 ???

    Hi,
    Ive just upgrading the jdk from 1.3 to 1.4 and got alot of errors.
    Im using the Bea Weblogic Server 5.1!
    Just at startup I got a VerifyError.
    And som other exception I got is: java.lang.NoClassDefFoundError: com/sun/java/util/collections/ArrayList
    Is WLS5.1 not compatible with J2SE (ver 1.4) ??
    When I change back to 1.3 everything is going fine.
    Error 1:
    java.lang.VerifyError: class weblogic.iiop.IIOPOutputStream overrides final method

    This is the platform support page and 1.4 is not listed for any Weblogic version...
    http://www.weblogic.com/platforms/index.html
    So if you want 1.4 you'll have to wait for a version that supports it.
    There was a guy that posted a link to a document on how to run 6.x with 1.4 but it's still unsupported so
    it's not recommended.
    --dejan
    John wrote:
    Hi,
    Ive just upgrading the jdk from 1.3 to 1.4 and got alot of errors.
    Im using the Bea Weblogic Server 5.1!
    Just at startup I got a VerifyError.
    And som other exception I got is: java.lang.NoClassDefFoundError: com/sun/java/util/collections/ArrayList
    Is WLS5.1 not compatible with J2SE (ver 1.4) ??
    When I change back to 1.3 everything is going fine.
    Error 1:
    java.lang.VerifyError: class weblogic.iiop.IIOPOutputStream overrides final method

  • [EJB:010112] - error with WLI8.1 Event Generator for foreign JMS/MQ provider

    I'm getting following error in weblogic server log when starting a JMS Event generator
    to a foreign JMS(MQ5.3) Queue.
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect
    every 10 seconds. This log message will repeat every 600 seconds until the condi
    tion clears.>
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. The Error was:
    [EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted, but the pro
    vider defined in the EJB is not transacted. Provider should be transacted if onM
    essage method in MDB is transacted.>
    My WLI8.1.2 is patched with CR131686_812.zip to support event generator for foreign
    JMS destinations. The foreign JMS/MQ provider is configured properly. QueueSend/Receive
    were tested fine with JMS java code using local JNDI names of foreign JMS objects.
    So we know that foreign Queue is active and accessiable from webLogic.
    Anyone run into this? Solution?
    Thanks,
    Scott

    Hi Scott,
    I need a transaction from the MDB since I am not using an EJb to pursue the action.
    Hence I need to retain the <trans-attribute>Required</trans-attribute> at the
    MDB.
    Have any answers?
    Pradip
    "Scott Yen" <[email protected]> wrote:
    >
    It's resolved.
    The MDB automatically created by JMS Event Generator defaults to be deployed
    with
    “transacted”. That requires the foreign JMS provider to be “XA”.
    The deployment descriptor is created as <domain-directory>/WLIJmsEG_<event_gen_name>.jar
    e.g. C:\bea812\user_projects\domains\jmsInterop\WLIJmsEG_mqQueueEventGen.jar
    Since MQ in the localhost and remote SLUDV18 are not XA-enabled, we had
    to manually
    change the <container-transaction> section in ejb-jar.xml:
    From :
    <trans-attribute>Required</trans-attribute>
    To:
    <trans-attribute>NotSupported</trans-attribute>
    "Scott Yen" <[email protected]> wrote:
    I'm getting following error in weblogic server log when starting a JMS
    Event generator
    to a foreign JMS(MQ5.3) Queue.
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. Connection failed after 2 attempts. The MDB will attempt to
    reconnect
    every 10 seconds. This log message will repeat every 600 seconds until
    the condi
    tion clears.>
    <May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    EJ
    B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
    JMSQueue. The Error was:
    [EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted,
    but the pro
    vider defined in the EJB is not transacted. Provider should be transacted
    if onM
    essage method in MDB is transacted.>
    My WLI8.1.2 is patched with CR131686_812.zip to support event generator
    for foreign
    JMS destinations. The foreign JMS/MQ provider is configured properly.
    QueueSend/Receive
    were tested fine with JMS java code using local JNDI names of foreign
    JMS objects.
    So we know that foreign Queue is active and accessiable from webLogic.
    Anyone run into this? Solution?
    Thanks,
    Scott

  • Error with the Receiver JMS Adapter (Connection On-Demand feature)

    Hi,
    In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
    Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
    Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
    The message status was set to WAIT.
    Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
    Any idea?
    PI 7.1 EHP1
    Thanks,
    Martin
    /people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
    Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

    Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

  • Activate change list received Communication with JMS server failed errors

    Hello XI Gurus,
    The first time when we tried to activate the change list in Integration Repository (Design) or Integration Directory(Configuration) we received an error message below.
    "Communication with JMS server failed
    Repeat the last action. If the problem continues to occur after multiple attempts, contact your system administrator to check the availability of the JMS provider service."----
    However, the second time went through, but the changes will not effected unless we do a refresh CACHE in order to see the changes.
    This happened on any of the interfaces in Repository and Directory.
    NW 7.0 SPS9
    Greatly appreciate for any helps!
    Dave

    Hi David,
    Logon your SAP J2EE Visual Administrator,
    go to 'Serverxxx"->Services
    ->JMS Connector
    and
    ->JMS Provider
    Ensure that everything is running smoothly, no red cross. If so, restart the service
    If you need to redeploy the JMS, go to 'Deploy', select 'Container' and navigate to the JMS connector to do the redeployment.
    Cheers,
    Aaron

  • Activate change lists error - Communication with JMS server failed

    Hi,
    I have this error message prompted when I try to activate my design object in Integration Builder :-
    <i>Communication with JMS server failed Repeat the last action. If the problem continues to occur after multiple attempts, contact your system administrator to check the availability of the JMS provider service.</i>
    Anyone knows where should I fix the errors ? Many Thanks in Advance.
    regards

    Hi,
      I think you should check the JMS Provider service in the Visual Administrator.
    Have a look at those help pages:
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/90/57849e5e3e45d784afc4e3bfa8136f/frameset.htm">JMS Administration</a>
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/a9/ad3d9ef22e4b2ea9752de8d98db5a4/frameset.htm">JMS Provider Service</a>
    Best regards,
    Manuel

  • Weblogic: problem with JMS foreign server and Transaction

    Hello everyone,
    I am working with an enterprise application with Web Application Server Logic 10.3. L 'application uses the following components:
    1) MDB 2.0
    2) FOREIGN JMS SERVER -> WebSpereMQ
    3) EJB SESSION
    L 'MDB calls the session bean which uses in its ejb-jar.xml using a Wrapper for JMS QueueConnectionFactory with res-ref:
    <resource- ref>
    <res-ref-name> jms / iss / QCFIXP </ res-ref-name>
    <res-auth> Container </ res-auth>
    <res-sharing -scope> Shareable </ res-sharing-scope>
    <resource- ref>
    The MDB is CMT
    <transaction-type> Container </ transaction-type>
    while the session bean is BMT
    <transaction-type> Bean </ transaction-type>
    to call the QCFIXP in its transaction.
    The QCFIXP ii an XA resource
    When there is a rollback operation in SessionBean also in 'MDB
    There 'an operation setRollbackOnly:
    getMessageDrivenContext (). setRollbackOnly ();
    After this operation on the MDB I do a JNDI look up the QueueConnectionFactory but sending the message on a queue I get the following exception:
    javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA:
    But if not using the "wrapper jms" in the session bean I did not take any exception and the application don' t have any error.
    My doubt is :
    Why if I use the JMS wrapper I get an error javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA?
    Thanks in advance.
    Michele
    Edited by: user3501731 on 11-mag-2011 3.16

    Hi Tom,
    Thanks very much for your responses and careful analysis you've done.
    Following the source code of the MDB where error occurs.
    Marked In bold the line where the exception is thrown.
         public void onMessage(Message msg) {
    //          Utility.logger(AP.DEBUG, "Partito MDB 2");
              processa(msg);
              protected void processa(Message msg) {
              Utility.logger(
                   AP.DEBUG,
                   "IXPReceiverMDB7.processa(Message msg) partito");
              try {
                   long start = System.currentTimeMillis();
    /*               Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB.processa(Message msg) effettuo lookup");*/
                   ejb = myEjbLocalHome.create();
                   // individuo l'identificativo del messaggio in ricezione
                   String msgid = msg.getJMSMessageID();
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa(Message msg) elaboro messaggio:"
                             + msgid);
                   String charset = msg.getStringProperty("JMS_IBM_Character_Set");
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa Charset:" + charset );
                   // invoco il processo di ricezione
                   boolean commitRequested = ejb.processa(ctlReq, encoding, msg);
                   // il valore di ritorno del processo di ricezione identifica o meno
                   // la necessita' di effettuare il rollback dell'intero processo
                   if (!commitRequested) {
                        getMessageDrivenContext().setRollbackOnly();
                   if (ctlReq) {
                        Utility.logger(
                             AP.INFO,
                             "IXPReceiverMDB7.processa(Message msg) spedisco il messaggio pilota del 'cleaning' con JMSCorrelationID = '"
                                  + msgid
                                  + "'");
                        msg.setJMSCorrelationID(msgid);
                        // Viene creata la QueueConnection
                        QueueConnectionFactory factory =
                             JmsFactoryDispenser.getSingleton().getFactory();
                        QueueConnection connection = factory.createQueueConnection();
                        // Viene ottenuta la 'session'
                        QueueSession session =
                             connection.createQueueSession(
                                  false,
                                  Session.AUTO_ACKNOWLEDGE);
                        // spedisco il messaggio sulla coda abbinata al processo di 'cleaning'
                        // della coda di controllo
                        IXPMessageManager msgManager = new IXPMessageManager(session);
                        msgManager.spedisci(msg, AP.PILOTQUEUE, "J", AP.STD_MESSAGE);                    session.close();
                        connection.close();
                   long end = System.currentTimeMillis();
                   Long durata = new Long (end - start);
                   Utility.logger(
                        AP.INFO,
                        "IXPReceiverMDB7 Tempo totale elaborazione messaggio: " +
                        msgid + " " +
                        durata.toString() + " mill" );
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa(Message msg) terminato");
              } catch (Throwable e) {
                   getMessageDrivenContext().setRollbackOnly();
                   try {
                        Utility.myExceptionHandler(
                             "E",
                             "1",
                             "4028",
                             "IXPReceiverMDB.onMessage()",
                             e);
                   } catch (Throwable ex) {
                        ex.printStackTrace();
    Thanks in advance.
    Edited by: serpichetto on 16-mag-2011 1.24

  • Dynamic queue name with JMS Queue XML?

    Hi,
    Is it possible to use dynamic queue name with JMS Queue XML?
    I tried using a variable in the JNDI URL, and supply the value in a package. I specified the following in the JNDI URL in the Topology:
    e.g.
    <JMS_RESOURCE>?d=<DTD_FILE>&s=<SCHEMA>&JMS_DESTINATION=#PROJECT_NAME.dest_var
    I declared and set the variable in a package, then tried to load data from the above data server to database. But executing this package gave me the following error:
    7000 : null : java.sql.SQLException: javax.jms.JMSException: Cannot find the target in JNDI (#PROJECT_NAME.dest_var)
    java.sql.SQLException: javax.jms.JMSException: Cannot find the target in JNDI (#PROJECT_NAME.dest_var)
         at com.sunopsis.jdbc.driver.bg.executeQuery(bg.java)
         at com.sunopsis.jdbc.driver.bh.executeQuery(bh.java)
         at com.sunopsis.jdbc.driver.l.f(l.java)
         at com.sunopsis.jdbc.driver.l.executeUpdate(l.java)
         at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execSrcOrders(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.g.y(g.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Unknown Source)
    Am I doing it wrongly?
    Thanks!

    hi,
    as it's not in Adapter-Specific Message Properties
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
    looks like you cannot do it with jms adapter in standard
    use proxy or your own adapter instead
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • 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

  • 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

  • Java client for OSB proxy with JMS Transport

    Hi,
    I am trying to call OSB proxy with JMS Transport. I am generating the client through ant task clientgen and following this article
    http://www.oracle.com/technetwork/articles/murphy-soa-jms-092653.html
    The osb proxy is req-response and is simply routing to BS which return a string value.
    When I run my client, it get stuck and does not return at all. Has any one trying java client in such scenario?
    What I may be missing?
    Below is snipped of client code:
    String url = "http://localhost:7021/sbresource?PROXY/MySample/MyJMSProxyService";
    CreditLoanApprovalServiceSoapBindingQSService service = new CreditLoanApprovalServiceSoapBindingQSService_Impl(url);
    MyPortType port = service.getCreditLoanApprovalServiceSoapBindingQSPort();
    LoanStruct in = new LoanStruct(); //populated the data structure
    String loanResult = port.processLoanApp(in); // Stuck here without any error
    System.out.println("LoanResult--> " + loanResult);
    Thx
    /Ashwani

    http://localhost:7021/sbresource?PROXY/MySample/MyJMSProxyService is the WSDL URL of the proxy.
    Transport is is picked by the client from wsdl.
    As far as the documentation of client generation is there, there is no change.
    But meanwhile I have started working on sending the message directly to queue. JMSProxy is getting called. May be I will first run the proxy this way and then try troubleshooting the java client.
    Regards
    Ashwani

Maybe you are looking for

  • Can't connect 2TB Time Capsule to my home network

    I can't seem to get my new 2TB Time Capsule to show up in Airport Utility on my MacBook Pro. I started out trying to connect wirelessly, then with an Ethernet cable directly between the Time Capsule and my MacBook. Still, the new device does not appe

  • Performance with txkWfClone.sh

    Hi list, According to Note: "Autoconfig Performance Issue Running txkWfClone.sh After Applying ATG_PF.H Rollups [ID 458443.1]" there is a performance problem with script txkWfClone.sh. Right now, I am running "perl adcfgclone.pl appsTier" command in

  • T_Code 1KEK - Transferring Receivables and Paybles to PCA

    Hi SAPients, We normally do the transfer of Receivables and Paybles to PCA through T-code 1KEK as a period end closing process. Now something strange is happening which was never before. While transferring the Receivables and Paybles through 1KEK, al

  • How can I change a audio podcast into a video podcast?

    Hello, I'm currently using the lastest version of iTunes and have successfully imported all my music, movies, home videos, books, etc. I'm having an issue with iTunes U and Podcasts. The reasons is because I don't actually use them for the real purpo

  • How do i change the font, save in messages i'm reading in ipad 3?

    how do i change the font, save in messages i'm reading in ipad 3?