JMS Adpater Error

Hi all
I configure the JMS receiver Adpater of webSphereMQ
but i got the error as followed:
<b>Receiver channel. Details: MQJMS2005: failed to create MQQueueManager for '172.31.235.100:QM_Test'</b>
I have a doubt:
The XI and MQ are in the same server, should i configure the network of MQ such
as the domain MQM or something else
and i have searched this issue in this forum, but there is no solution
I am eager for your reply
And Thanks in advance

Hi Leo,
have u seen these..
configuration of JMS adapter Using WebSphereMQ
SAP XI and JMS for WebSphere MQ
connection with the JMS provider
cheers,
Prashanth
P.S Please mark helpful answers

Similar Messages

Reciever JMS Adpater Error

Hi Experts,
I am getting following error in Reciever JMS adapter:
I am using transport protocol is Acces JMS provider with JNDI
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=http://168.89.59.82:7005/, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: CC_eRespond_ServiceTicketson node: 8273250 having object id: d72754188a053d43b6aa0dd420346941: javax.naming.CommunicationException
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
Can anyone please tell me what is the cause of this error.
Kind Regards,
Praveen.

Hi Experts,
We are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic server.
Our configuration of JMS receiver Adapter is
JNDI Lookup Name of Queue Connection Factory----
ConnectionFactory
JNDI Lookup Name of JMS Queue----
queue/IntegrationQueue
Name of JNDi Initial Context Factory: -
weblogic.jndi.WLInitialContextFactory
JNDI Server Address:----
weblogic server ip
JNDI Logon User: -
user
JNDI Password: -
password
Could you please help us.
The Error message as follows
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=http://IP:port/, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: CC_eRespond_ServiceTicketson node: 8273250 having object id: d72754188a053d43b6aa0dd420346941: java.lang.NoClassDefFoundError
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
Regards
Praveen

Weblogic Connection with Oracle JMS AQ errors

Hi All,
I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
The steps I followed exactly are this :
1) Created a Database Queue called DemoInqueue using the following scripts :
exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
COMMIT;
exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
COMMIT;
exec dbms_aqadm.start_queue('DemoInQueue');
COMMIT;
2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
QAConnectionFactory but no difference )
Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
are the same....
Are these steps correct ? Am I missing something here.?
I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
Here is the error stack below :
<BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
SOA LOG.....
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.

Thanks for passing along the link.
The part about Oracle's documentation not mentioning the JmsAdapter configuration was a real sticking point for me - I was having the same problem as the original poster until I updated that deployment as the link outlined.
Also, towards the end of that link the author mentions running in to problems getting their composite to successfully bind to the queue definitions that were created in WebLogic.
I attempted post my solution to this on the original site, but I'm not sure if it got through - so I'll add the details of what worked for me here:
Connection Factory:
Local JNDI: aqjms/JMSTest_Connection_Factory
Remote JNDI: XAQueueConnectionFactory
Destination:
Local JNDI: aqjms/JMSTest_Queue
Remote JNDI: Queues/JMSTest_Queue
Outbound Connection Pool:
Name: eis/aqjms/JMSTest_Queue
Connection Factory: aqjms/JMSTest_Connection_Factory
JDeveloper Composite:
Destination Name: aqjms/JMSTest_Queue
JNDI Name: eis/aqjms/JMSTest_Queue
Cheers,
- Nathan

Need suggestion on implementing JMS message error recovery

Hi,
Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
1. Use a persistent TOPIC (this would ensure guaranteed delivery)
2. Configure a error destination on JMS topic e.g a jms queue
3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
A. Are there any issues with the above design which we need to handle?
B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
C. Are there any other recommended design patterns for error recovery of JMS messages
Please advise.
Regards,
Arif

Thanks Tom !
We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
Regards,
Arif

Oracle.jms.AQjmsException: Error creating the db_connection( OSB PS2.)

hi All,
I am beginner in OSB 11g. Please excuse me if I am asking any dumb question.
I am trying to post messages to Oracle AQ by configuring JMS Destination in OSB Alert destination
I have configured AQ JMS in weblogic 10.3.3 ( OSB PS2) following the blog (http://jianmingli.com/wp/?p=2950)
When i invoked my proxy OSB proxy service i am getting following exception. Can you please help if i am missing any kind of setup while configuring the JMS Module.
Caused By: oracle.jms.AQjmsException: Error creating the db_connection
     at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:625)
     at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
     at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
     at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
     at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
     at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
     at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
     at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.getSession(JmsOutboundMessageContext.java:399)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.newMessage(JmsOutboundMessageContext.java:621)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.setRequestMetaData(JmsOutboundMessageContext.java:229)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.access$100(JmsOutboundMessageContext.java:72)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:788)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:551)
     at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:680)
     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 com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy111.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:489)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
     at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
     at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:345)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
     at com.bea.alsb.alert.pipeline.PipelineAlertManager.processAlert(PipelineAlertManager.java:59)
     at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:125)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
     at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:102)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
     at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
     at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
     at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
     at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
     at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
     at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
     at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
     at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
     at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
     at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
     at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
     at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
     at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
     at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
     at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
     at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
     at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
     at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
     at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)

hi All,
Here is the actual exception while posting message into AQ ( AQ JMS) from OSB.
Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
Not sure what is missing in my AQ JMS configuration. Please help.
Regards,
Nagi

JMS adapter error in MQSeries connection

Dear All,
i am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
     at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
     at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
     at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
com.ibm.mq.MQException: Message catalog not found
     at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
     at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
Thanks and Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Jan 29, 2008 2:32 PM
Edited by: RAJEEV GUPTA on Jan 29, 2008 2:39 PM

Hi,
Check this as well [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fjm35210_.htm]
Regards,
Venkata S Pagolu

JMS Internal Error at Server Client Adapter!JMS Service is not started

Hi
Can any one tell me how to trouble shoot for following errors:
Failed to Create Connection! Reason: Response from the server could not be reached.
JMS Internal Error at Server Client Adapter!JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310
We are trying to send the request from SONICMQ JMS to R/3 and trying to post the response to Sonic Queue. but we are facing some problems for JMS adapter .
but in JMS sender and receiver adapter i gave different IP and port for listen the SONIC queue. why it is showing in different IP here? this message got from logviewer.
regards
Rambarki...

Rambarki,
What is the error displayed on the Adapter Monitoring pages?
Generally the correct error descriptions for connectivity issues are found on adapter monitoring UI than any other.
Other possible reasons could be :
<i>JMS Service is not started
The following hosts could not be reached 143:223:221:10:50310</i> This might be issue with your network settings i.e. XI server is unable to reach the specified IP on specified port.
Regards,
Amol

JMS adpater

Dear Expertise,
I have some doubts in JMS Adpater.
1. IS JMS adapter in XI is JMS client?
2. If JMS adaper CC is in sender mode, will XI pull the data(queues) from JMS server or JMS server will send the data to XI.
For IDOC to JMS scenario, what are the steps need to be done in repository framework.
My question is how to send that IDOC data to JMS server. For this, is any message mapping and interface determination required, as I want to send the same IDOC data to JMS server queue.
Advaced Thanks,
Gujjeti

Praveen,
To work on JMS adapter first you need to install the drivers. Check this document on how to install the drivers:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
Once when you do this it is just like your normal scenario. Check this weblog for some help on how to configure your receiver JMS adapter:
/people/kan.th/blog/2007/02/05/exploring-jms-and-sap-xi-jms-adaper
Also check this for some info. on JMS adapter:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
---Satish

Jms Protocol error

Hi ,
I am using Oracle 10g version 10.1.3 and Oracle AS JMS Server
I have a java client that is using the following configuration for JNDI conext.
// set the environment properties
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL,"opmn:ormi://vtun-lap.us.oracle.com:6003:home");
env.put(Context.SECURITY_PRINCIPAL,"oc4jadmin");
env.put(Context.SECURITY_CREDENTIALS,"apps10g");
QueueConnectionFactory queueConnectionFactory =util.getQueueConnectionFactory();
When I execute the following statement
QueueConnection queueConnection = queueConnectionFactory.createQueueConnection();
I am getting the following error:
[PROTOCOL ERROR] JMSRemoteServer[vtun-lap:12601]: "JMS protocol" error, expected "-559,038,735", got
Object Address: 0x529EDEC4
Thank you
Van Sioung

Your client is using old OC4J JMS classes - you need to set up your client's class-path to point to the .jar files that came with 10.1.3. The exact set of .jar files required for looking up and using OC4J JMS connection factories and destinations over RMI is covered in the 10.1.3 version of the Services Guide - in the JMS Chapter.

JMS Deserialization Error

Hi,
I am encountering the JMS Exception 'Error deserializing object'. I do not have
the stack trace. The same code works perfectly fine 99% of the time. It throws
exception at random very rarely.
Can anyone help me with the possible causes of this exception.
Thanks in advance.

Hi Gordon,
I'm getting the EXACT same problem . were you able to resolve this problem . please let me know what the soln is
thanks
mantish

JMS communication error

Hi,
I have deployed JMS application on Oracle 9i Application Server. I have made the necessary configurations in jms.xml(eg., Setting the queue connection factory and the name of the queue). Now when I try to run the client application I get the following error.
JMS communication error = Unable to connect to JMSServer (localhost/127.0.0.1:9127)
The JMS server is running on port 9127....
The rmi server is running on port 23791...
Can anyone help me out as to how this problem could be resolved ?
Sirisha

Hi
Did you try changing jms.xml to point to the real ip instead of host="localhost" ?
sometimes it works.
g'day
nimo

JMS receiver error

Hello,
I have maintained a JMS receiver adapter to an existing MQ system (IBM WebSphere 6.0)
After deploying the modules to PI (7.11) the adapter goes green but allways says "Sucessfully disconnected from destination".
When sending a message through this adapter I get the error message:
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: No transition found from state: STARTING, on event: process_commence for DFA: JMSReceiver_ATLAS_MQ:4b9d8e8dfe883ebeb7ab5af79e59cdf6"
I can not find out where the problem can be....I played arrounf with the several options for QM Manasger, channels.....
I do not use any "Advanced Adapter options"
Anybody who can help me????
best regards
Werner

I still have checked all the notes and blogs....
But nothing helps, I still have the same problem.
The problem can be, that I am not a MQ specialist, but I have access to the MQ and I can see the settings.
Do I have to use adapter specific atributes???
I only use QManager, Chanell, queue....
ANd there is somehting other really strange.
I have create several components for different scenarios.
When I create an Adapter in one component, I get the error I listed before.
But in some components I get the error:
"Channel Has Internal Error" in the RWB overview and in the node
"Adapter had not provided any status infomration about this channel"
I tried with Creating new channel, copy channel between the components....
but allways the same...in some components I get this error
in other components I get the message "Successfully discponnected from destination"
Werner
Edited by: Werner Magerl on Sep 28, 2010 1:59 PM

Messages in JMS Topic Error destination

Hi,
I have a JMS Topic with an error destination queue configured. Now, In our scenario , there are two subscribers of topic for the same message. Suppose for a message published to topic, subscriber1 is able to processes message successfully but subscriber2 throws errors when processing the same message.
1. Once the redelivery limit is reached and subscriber2 continues to throw exception, Will the message get en queued to Error Destination (in spite of the fact that subscriber 1 has processed the same message successfully) ?
2. For a consumer (e.g MDB) listening to Error destination and consuming error messages, Is it possible to determine which topic subscriber was unable to process the message ?
Please let me know
Regards,
Arif

Here it depends on the state of the message, if the message is visible then the message would be available for consumption, else it is not. In case the subscriber 2 failed to consume the message and the message is still visible then a retry would be made, else the message would not be retried.
In case the message is visible then the message would be move to the error queue based on the configured redelivery attempts.
Additionally, an MDB can find the destination using the getJMSDestination() call. But as per my understanding we will only be able to get the name of the last destination which in this case would be error queue:
http://docs.oracle.com/javaee/1.4/api/javax/jms/Message.html#getJMSDestination%28%29

ALERT triggering slow in case of adpater errors

Hi Forum,
I have made a alert category to receive alerts from a particular scenario, and added all the available standard container variables SXMS_MSG_GUID,SXMS_ERROR_CAT, SXMS_ERROR_CODE, SXMS_FROM_PARTY, SXMS_FROM_SERVICE, SXMS_FROM_NAMESPACE, SXMS_FROM_INTERFACE, SXMS_TO_PARTY, SXMS_TO_SERVICE, SXMS_TO_NAMESPACE, SXMS_TO_INTERFACE, SXMS_TO_ADAPTER_TYPE, SXMS_TO_ADAPTER_ERRTXT,
hence when the scenario runs i receive all kind of errors, but the problem is whenever there is an error in the Adpater (communication channel), i receive the error very late, otherwise for mapping errors etc. the alert is triggered instantaneously, (i check these error in tcoe ALRTDISP),
what can be the problem?
also, the job SXMSALERT_PROCESS_DATA_GET is scheduled to run evry 5 minutes

Hi,
For ur defined mapping error u can rasie it thorugh Function module.
refer the below link:
Triggering XI Alerts from a User Defined Function
Triggering XI Alerts from a User Defined Function
For triggering Adapter engine n integration related error u can either create the alert rule in RWB and raise it.
Triggering alert by configuring a rule from RWB.
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/d5b54020c6792ae10000000a155106/content.htm
Did u look at the below link using BPM:
Triggering from BPM.
The specified item was not found.
Simple Steps to Get Descriptive Alerts from BPM in XI
chirag

JMS Adapter Error

Hi Experts,
               We are havingone problem in Sender JMS Adapter. From Sender (SeeBeyond) xml files are getting posted into Remote Queue in MQ, then it has been sent to Local Queue of MQ, and then finally from Local MQ Queue PI is picking up the data and sending it to SNC system.
               The problem lies in PI itself. While coming into PI, the value in the incoming payload where special characters(say, swedish character) are coming, are coming into PI as a garbage value. Whereas, in Sender (SeeBeyond), MQ and in PI Character set is ISO 8859_1. We have stopped the Sender JMS channel in PI, and checked the payload in MQ and in SeeBeyond, in both of the cases it's fine, only when coming into PI, data are getting corrupted.
                For this we have done some investigation like below,
1) We had changed the CCSID from 00819 (ISO 8859_1) to 1208 (UTF-8), 1200 (UTF 16), but no luck.
2) We had added th below mentioned modules into Sender JMS in Processing Sequence with the existing modules,
AF_Modules/MessageTransformBean                                              Local Enterprise Bean               ContentType
(ii) AF_Modules/TextCodepageConversionBean                                   Local Enterprise Bean               codepageConversion
But yet we are getting the same error in encoding in the payload while coming into PI.
Can anybody help me out with it, or probably let me know if I am missing something in my investigation.
//BR
Soumya

Hi Stefan,
             Sorry for the late reply. We were testing in different cases in PI, and here what I have found. In Sender JMS adapter we had put the module "AF_Modules/MessageTransformBean" with Module Key "Transform". And the configuration of this Module Key is as follows:-
Transform     Transform.ContentType      text/plain;charset="UTF-8"
And we changed the CCSID to 1208 (UTF-8). Now when we saw the payload in SXI_MONITOR in PI, we have found that the special character is being distorted whereas in View Sourse the payload is fine including special character also. That means there might be some display problem in SXI_MONITOR.
             Now, the Sender sends the data in XML iin ISO 8859-1nto MQ, MQ send the same as a string in PI, from PI it's going to SCM system (R/3, Supply Chain Management), where we could see ABAP.APPLICATION Error. We tested the interface in SCM system by running SPROXY and found that it's not able to recognise ISO 8859-1, since it's a Non-Unicode System, it will only understan UTF-8 and hence the error. Now manually we have changed the XML Header into UTF-8 and tested at SCM side, and this goes fine.
           So, we could see the changing of XML Header from ISO 8859-1 to UTF-8 would be running fine at receiver end (SCM). Since SCM is a Non-Unicode System, the XML header cannot be changed to UTF-8, is there any possibility in PI that we can change the XML Header from ISO 8859-1 to UTF-8.
           For your information, we are using Sender JMS adapter to receive the File from Sender and we are using Receiver XI adapter to post the file into SCM system.
What's your suggestion Stefan, how can we change the XML Header from ISO 8859-1 to UTF-8 in PI?
Many Thanks
Soumya

JMS Adpater Error

Similar Messages

Maybe you are looking for