Error status in JMS adapter - sync / async brigde. Message processed ok
Hi guys
I'm having som trouble with my scenarion. I'm sending sync message from SAP backend to XI using proxy. From XI onwards to JMS adapter async (and the other way around for the response message).
This works OK. However i have a status error in my RWB on the JMS adapter. There is er red exclamation mark and a text saying:
Correlation ID 'XXX' of JMS request message 'ID:yyy' saved that correponds to XI message 'XXX'
How do I get my adapters in status green?
Kind regards
Martin
Hi Kai
Oh - OK
Settings are:
Receiver JMS channel:
Set JMSCorrelation to: XI Message ID (MessageID)
Store JMS CorrelationId of request: Mark
Sender JMS channel:
Set XI Message ID (MessageID) to: GUID (Recommended Value)
Set XI Conversation ID (ConversationID) To: Stored JMS CorrelationId of Request.
Kind regards
Martin
Similar Messages
-
Correlation issue in JMS adapter - SYNC/ASYNC scenario without BPM
Hi,
I am working on a SYNC/ASYNC scenario with JMS adapter without using BPM. My scenario is SOAP<>PI>JMS. I configured the interface as below:
1. SOAP Sender channel
2. JMS Receiver Channel writing to Queue A.
Module used: a. RequestOneWayBean
b. WaitResponseBean
Correlation Settings:
a. Set JMS Correlation ID to "XI Message ID"
b. Store JMS CorrelationID of request (Checked)
c. Set JMS Property to "JMS Correlation Id"
d. Value = "XI MEssage ID"
3. JMS Sender channel reading from queue B ( I am exporting the message from queue A and importing into queue B)
Module used: a. NotifyResponseBean
Correlation Settings:
a. Set XI MEssage Id to "GUID"
b. Set XI Conversation ID to "Stored JMS COrrelationID of Request"
I can see the cid in the message from queue A. But I observed thhat the header format of the message in Queue A is "MQSTR".
ISSUE:
1. While writing the message to queue A, below adapter log details(part b) concerned me:
a. Message '8747a7c2-2b06-11df-8055-005056a70ed6' successfully processed by channel
b. Could not create acknowledgements for message '8747a7c2-2b06-11df-8055-005056a70ed6'
I am not sure why I am receiving the message that " could not create acknowledgements"
2. While reading the message from the sender channel,I consistently get the error message as below:
a. XI message ID corresponding to JMS message with ID 'ID:414d51205341504449442e514d202020c67b954b20005602'
will be created as a new GUID with value '21bca916-424f-41f6-3347-c71090392b58'
b. Error while processing message '21bca916-424f-41f6-3347-c71090392b58'; detailed error description:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
Below are the blogs which I have already gone through:
1. JMS Synchronous Scenario without BPM - Correlation Settings and Transactional JMS Session
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
2. Note: 1086303
3. Sync / Async Bridge without BPM
In the note, they mentioned something about header being "MQRFH2". BUt in our case, the header is "MSSTR". Not sure whether it makes any difference.
Please help.
Edited by: GP on Mar 9, 2010 4:24 AMHi,
detailed error description:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
This error would generally arose when there are multiple messages, got stuck in the outbound queue. Try to stop both the sender and receiver JMS comunication channels and clear both the inbound and outbound queues.
Once all the messages in the queue are cleraed, try posting the message again.
Regards,
Swetha. -
SOAP to JMS using Sync/Async bridge - configuration confirmation needed
Hi group,
Since I'm experincing error in a scenario using sync/async bridge in jms adapter I really would like a confirmation on my configuration.
For a simple SOAP to JMS scenario is it then correct that all I need is;
1) 2 synchronous message interfaces, 1 inbound and 1 outbound
2) 1 Receiver determination
3) 1 Interface determination
4) 1 Receiver agreement (JMS adapter with module configuration)
5) 2 Sender agreements (in my case 1 soap and 1 JMS adapter - the later with module configuration).
6) The sender and receiver JMS adapters point to different MQ queues (request and response queues)
7) The sender agreement for the JMS adapter uses my synchronous, inbound message interface (isn't this really just a "dummy" to actually fetch data from response queue - meaning that the actual utilized business system/service, MI and namespace are unimportant, since the module will make the adapter notify the listening module in the receiver JMS adapter?)
Best Regards,
DanielHi, thanks for your reply.
I'm familiar with the links provided. I believe everything is configured as it should be, but since I get error I would like to have my configuration confirmed. Neither the weblog (or SAP guide) are detailed enough to convince me 100% that my configuration is correct. Surely the problem could be on the MQ side, but before going into that, I want to be sure that its not on XI-side.
So I really would like confirmation on the steps/question that I wrote:-)
Best Regards,
Daniel -
File to JMS Scenario - Error is Receiver JMS Adapter
Hi,
I am working on File to JMS scenario. I have deployed all required jars for MQ 6.0.2 in SDM. Create all MQ related objects. I am getting following error for Receiver JMS adapter in CC Monitoring.
Please let me know if I have missed anything. Is there anything to do in Visiual Administrator->JMS Provider or JMS Connector for these kind of Scenarios?
Thanks in Advance...
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
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 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)Hi,
I have made my Qmanager as default Qmgr. Now the error is :- Socket connection attempt refused
Recv JMS Communication Channel Error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
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
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318) -
JMS adapter transaction. Rollback message to queue.
Hi all !
A have question about jms adapter transaction. My composite application has 3 steps : JMS adapter (listener), mediator, WS adapter. JMS adapter listen queue push message to mediator, mediator invoke web service. If ws not available (server down), mediator try recovery 5 times. After 5 times, reject message from queue. I wont rollback message to queue. I saw examples with JMS + BPEL, but it not help me. Anybody can help me.Hi,
You don’t need to catch a mediator fault – you can let it rollback to the JMS Queue and let the Queue do the retries.
To get the retries working, log in to the weblogic console and navigate to JMS Modules -> Your Module -> Your Queue -> Configuration -> Delivery Failure
Here you will find options for Redelivery Limit. Set this to the number of retries you need.
Then navigate to the connection factory you want and set the redelivery delay.
This should get your desired behaviour, but once the message has failed it will be discarded. If you prefer to put it on an error queue you can create an error queue, and in the original queue’s, goto Delivery Failure, change the expireation policy and set the Error Destination to be your error queue.
Hope that helps!
Robert -
Error in reciever JMS adapter (SENARIO FILE - XI- JMS )
HI everyone,
My previous error is solved (Error in getting initialcontext). I have deployed the required jar files on server.
Thanks to you'll.
Now I am getting the following error in JMS adapter monitoring RECIEVER CHANNEL . NO DETAIL INFORMTION SET.
i AM USING IBM websphere MQ series for recieving JMS messages from XI.
I have made Queue manager,
Queue,
reciever channel.
and have also provided the following details in my communication channel in XI
QueueConnection FactoryJavaClass : com.ibm.mq.jms.MQQueueConnectionFactory
QueueJavaClass : com.ibm.mq.jms.MQQueue
Ip address or server name : <my ip address> since i have installed IBM JMS server on my system.
server port :1415
QueueManagerName :QM_apple
channel name : reciever_channel
jms Queue: Q1
character set id (ccsid): This I have not given , Idont know what to give here
Transport protocol :tcp/ip
Please guide me to go further , I am stucked at the error , No reciever details set. What should i do?Hi Deepak ,
Please refer this forum post .. if this helps.
Reg:Receiver Mail Adapter
Regards,
srinivas -
Error in Inbound JMS adapter(in ESB project)
Hello all,
I am trying out a sample ESB application, where an ESB service is listening on a JMS topic (OEMS database persistence) for new employee notifications. Upon receiving the message, the service will invoke a stored procedure to insert a record in the database.
I am using inbound jms adapter to receive the jms messages from a jms topic, that is configured using Oracle AQ. I made all the necessary changes in oc4j-ra.xml, application.xml, and data-sources.xml files.
But when I send a jms messages, I see the following errors in the oc4j log.xml:
Failed to activate endpoint for Service "DefaultSystem.AQJMStoDB.ListenForNewEmployees". Reason : oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: An unhandled exception has been thrown in the ESB system. The exception reported is: "ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter was unable to activate the endpoint :{} due to the following reason: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
[Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please correct the reported issue and redeploy the BPEL process.
at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:566)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateInboundJcaEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.performEndpointActivation(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateService(Unknown Source)
at oracle.tip.esb.server.service.EsbServiceFactory.activateEsbService(Unknown Source)
at oracle.tip.esb.server.service.EsbServiceFactory.initializeEsbServices(Unknown Source)
at oracle.tip.esb.server.common.RuntimeESBSystem.start(Unknown Source)
at oracle.tip.esb.common.system.SystemFactory.startSystemsForCluster(Unknown Source)
at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListenersForSystems(Unknown Source)
at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListeners(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.startESBListeners(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.setupRuntime(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.initializeESB(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter$PingTester.run(Unknown Source)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
at oracle.tip.adapter.fw.wsdl.WSDLUtils.invokeSetMethod(WSDLUtils.java:763)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setCciSpecParameters(WSDLUtils.java:665)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:465)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:421)
at oracle.tip.adapter.fw.jca.AdapterLocator.findResourceAdapter(AdapterLocator.java:195)
at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:341)
... 20 more
Can anybody provide any inputs on this error?
Thanks,
PramAll,
Problem is solved. I changed the value for the Source directory & the adapter started to poll.
Thanx,
Homiar. -
Hi,
I have an XI 3.0 connected to an MQ via jms adapter in an Adapter Engine
I have this log when sending a message:
15:39:18 (3130): JMS message ID:414d51204d51584944573120202020207a07c64442701b00 sent successfully
15:39:18 (3140): Session commited
15:39:18 (3180): Se produjo un error java.io.IOException: Error during rendering: Missing mandatory element <sap:queueId> for quality of service EOIO
15:39:18 (3190): Session rolled back
I'm trying to discover the mandatory element.
Regards
GonzaloHello Michal,
Yes we need and we are using EOIO, and is not specified in SAP documentation to specify this parameter in the receiver JMS.
The thing is: Why is missing the mandatory element
<sap:queueId> for quality of service EOIO?
I really apreciate any help with this issue.
Thanks,
Regards,
Gonzalo -
Error in Inbound JMS adapter (ESB project)
Hello all,
I am trying out a sample ESB application, where an ESB service is listening on a JMS topic (OEMS database persistence) for new employee notifications. Upon receiving the message, the service will invoke a stored procedure to insert a record in the database.
I am using inbound jms adapter to receive the jms messages from a jms topic, that is configured using Oracle AQ. I made all the necessary changes in oc4j-ra.xml, application.xml, and data-sources.xml files.
But when I send a jms messages, I see the following errors in the oc4j log.xml:
Failed to activate endpoint for Service "DefaultSystem.AQJMStoDB.ListenForNewEmployees". Reason : oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: An unhandled exception has been thrown in the ESB system. The exception reported is: "ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter was unable to activate the endpoint :{} due to the following reason: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
[Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please correct the reported issue and redeploy the BPEL process.
at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:566)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateInboundJcaEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.performEndpointActivation(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.ESBActivationAgent.activateEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateEndpoint(Unknown Source)
at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.activateService(Unknown Source)
at oracle.tip.esb.server.service.EsbServiceFactory.activateEsbService(Unknown Source)
at oracle.tip.esb.server.service.EsbServiceFactory.initializeEsbServices(Unknown Source)
at oracle.tip.esb.server.common.RuntimeESBSystem.start(Unknown Source)
at oracle.tip.esb.common.system.SystemFactory.startSystemsForCluster(Unknown Source)
at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListenersForSystems(Unknown Source)
at oracle.tip.esb.server.bootstrap.RuntimeResourceAdapter.startListeners(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.startESBListeners(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.setupRuntime(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter.initializeESB(Unknown Source)
at oracle.tip.esb.server.bootstrap.ESBBaseResourceAdapter$PingTester.run(Unknown Source)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: ORABPEL-12531
Error while setting JCA WSDL Property.
Property setPassword cannot be set on oracle.tip.adapter.jms.JmsManagedConnectionFactory due to: [Caused by: Can't find bundle for base name oracle.tip.pc.infra.exception.i18n.PCExceptionList, locale en_US]
Please verify the spelling of the property.
at oracle.tip.adapter.fw.wsdl.WSDLUtils.invokeSetMethod(WSDLUtils.java:763)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setCciSpecParameters(WSDLUtils.java:665)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:465)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:421)
at oracle.tip.adapter.fw.jca.AdapterLocator.findResourceAdapter(AdapterLocator.java:195)
at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:341)
... 20 more
Can anybody provide any inputs on this error?
Thanks,
PramAll,
Problem is solved. I changed the value for the Source directory & the adapter started to poll.
Thanx,
Homiar. -
Hi,
We are having a problem in production, there is an interface which runs ok most of the time but sometimes it's throwing exception
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Unable to write new JMS message body for message: 4b4abe9e-24ff-007d-e100-80000a02210b: ConnectorException: Connector for ConnectionProfile of channel: Srv_WMS_VIC_JMSReceiveron node: 6532450 having object id: 966e2f3c527c359fbe4e1a1f902bf7d0 was unable to create a new javax.jms.TextMessage message: java.lang.NullPointerException
Then alert raises and someone has to manually stop and start the channel and resend the message in error.
This has been really annoying the support people and getting serious impact on business.
Does anyone has an idea why it is happening and what can be the resolution for the same.
Regards
RiaRia,
Is the exception throws after the restart of the Queue/ Receiver Server ?
Check - Note 856346
Cheers
Agasthuri -
JMS adapter could not receive message from Tibco EMS topic
I'm trying to consume message from tibco EMS topic using Oracle SOA JMS adapter. Can anyone please let me know the steps to do this. Appreciate your help.
Thanks,
SBIncrease Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..
-
How to set values in JMS Adapter using Adanced specific Message Attributes
Hi Frnds,
in my scenarios i have to add extra header information MQ Message,
using Adanced specific Message Attributes i defined 7 parameters(Transaction,Environment,shema......) all are type Interger.But i have to set values ( Transaction type,Enviroment,shema....).
Where i can set values ??
help me on this...
Regards,
Raja SekharHi Vijay,
Thanks for your replay,as per your input i creted dynamic configuration method,
i taget structure luks like this
<Data>
<Mesage>
<gl_update>
<header>
<ean1>
<ean2>
</header>
<gl_update>
<Message>
i written UDF and mapped to header element gl_update,
but i am getting below error message in MONI
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
<SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
i think there is no prob with UDF,its executing ,giving warning messages
help me on this,
Regaards
Raj -
Error initializing Sender JMS Adapter
Hi,
Has anyone integrated MQSeries 5.3 with XI 3.0? I have placed all the necessary jar files under tech_adapter and in class path.My adapter status is red and the log says that
". ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
at java.lang.Class.getConstructor0(Native Method)
at java.lang.Class.getConstructor(Unknown Source)
at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
at java.lang.Thread.run(Unknown Source)"
please let me know if i am missing something.
Regards
SathyaHi Amol,
Our SLD Accessor service is working properly.i have deployed all the necessary jar files.I am not very confident in my class path settings.So i am sending my class path,
D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\classes12.zip;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqjms.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mq.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\connector.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqbind.jar;D:\usr\sap\BWXI\SYS\global\tech_adapter\server.jar;com.sap.aii.messaging.adapter.AdapterImpl;D:\usr\sap\BWXI\SYS\global\tech_adapter\ejb.jar;
please look into that.
I am sending the log trace for Adapter Configuration so that you can make something out of it.
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Starting adapter engine version 3.0.0318 ($Id: //tc/aii/30_REL/src/_messaging/java/com/sap/aii/messaging/adapter/AdapterImpl.java#7 $, $DateTime: 2004/08/03 11:19:35 $ ) ...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: sync.time: 200411110440
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jdk.version: 1.3.1
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.rel: 30_REL
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: build.date: 2004-11-11 04:58
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: latest.change: 300224
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.server: PWDFM060
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter_base.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: initializing and starting with given Parameters ...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: - Token File token.keystoragenot found
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Reading property file 'adapter_base.properties' for adapter modules configuration...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: adapterID set to Adapter1
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: AdapterMonitor - expects property file 'BaseConfiguration/AdapterMonitor.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module AdapterMonitor
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-0,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleAdapterMonitor' created, version 2.0.1010
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: InfoLogger - expects property file 'BaseConfiguration/InfoLogger.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module InfoLogger
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-1,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleInfoLogger' created, version 2.0.0918
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: IDLogger - expects property file 'BaseConfiguration/IDLogger.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module IDLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module IDLogger
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-2,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleIDLogger' created, version 1.0.0523
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: Initializing new IDLogger object(version 1.0.0523), root directory is 'Data'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module IDLogger
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: IDLogger started
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module IDLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: RtcMonitor - expects property file 'BaseConfiguration/RtcMonitor.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module RtcMonitor
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-3,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleRtcMonitor' created, version 1.0.0819
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: PersistLayer - expects property file 'BaseConfiguration/PersistLayer.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module PersistLayer
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-4,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePersistLayer' created, version 2.0.0929
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: PWtokens - expects property file 'BaseConfiguration/PWtokens.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PWtokens
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module PWtokens
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-5,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePWtokens' created, version 1.0.0724
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Initializing new PWtoken object(version 1.0.0724), root directory is '.'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module PWtokens
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '<!%' set for parameter 'PWD.beginSeparator'
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '%!>' set for parameter 'PWD.endSeparator'
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: SLDaccessor started
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module PWtokens
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: GUIBrowserEngine - expects property file 'BaseConfiguration/GUIBrowserEngine.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module GUIBrowserEngine
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-6,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleGUIBrowserEngine' created, version 3.0.1930
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...saging.adapter.ModuleGUIBrowserEngine [Thread[Thread-6,5,main]] Info: GUIBrowserEngine started
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: HttpServer - expects property file 'BaseConfiguration/HttpServer.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module HttpServer
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module HttpServer
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-7,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleHttpServer' created, version 1.0.0808
Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Initializing new HttpServer object(version 1.0.0808), root directory is '.\Data'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module HttpServer
Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Http server started
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module HttpServer
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: SLDaccessor - expects property file 'BaseConfiguration/SLDaccessor.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module SLDaccessor
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module SLDaccessor
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-9,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleSLDaccessor' created, version 2.0.1010
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module SLDaccessor
Apr 26, 2006 10:08:23... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: Initializing new SLDaccessor object(version 2.0.1010), root directory is '.\Data'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Started module SLDaccessor
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jms_sender2is - no property file specified - try default 'Configuration/jms_sender2is.properties
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jms_sender2is - expects property file 'Configuration/jms_sender2is.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module jms_sender2is
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Created module jms_sender2is
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-11,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleJMS2Transport' created, version 2.0.1626
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Initialized module jms_sender2is
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine startup procedure finished: 9 modules started successfully
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine running...
Apr 26, 2006 10:08:23... com.sap.aii.messaging.adapter.IDLogImpl [Thread[Thread-11,5,main]] Info: Attached persistent hashtable to file 'D:\usr\sap\BWXI\SYS\global\tech_adapter\Data\jms_sender2is_ID.dat'
Apr 26, 2006 10:08:23... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-11,5,main]] Info: Created new ID log file 'jms_sender2is_ID.dat' in folder 'Data' for module 'jms_sender2is'
Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.SenderParty'
Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.ReceiverParty'
Apr 26, 2006 10:08:23... ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
at java.lang.Class.getConstructor0(Native Method)
at java.lang.Class.getConstructor(Unknown Source)
at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
at java.lang.Thread.run(Unknown Source)
Apr 26, 2006 10:08:28... ...duleSLDaccess.createAdapterEntities() [Thread[Thread-9,5,main]] Info: Adapter Entities for AdapterEngine_bwxi_8200 created successfully
Apr 26, 2006 10:08:29... ...duleSLDaccess.createAdapterServices() [Thread[Thread-9,5,main]] Info: Adapter Services for AdapterEngine_bwxi_8200 created successfully
Apr 26, 2006 10:08:29... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: SLDaccessor started
Regards
Sathya -
JMS Adapter is not picking messages from Topic ( AIA Error Notification)
Hi All,
One of my service is not picking messages from topic. This service was working in one environment but not working in this environment.
I am using AIA 2.5 and using AIAErrorNotification.
Service AIAAsyncErrorHandlingBPELProcess is enquing the message but consumer service AIAReadJMSNotificationProcess is not being invoked automatically.
Whenever we are manually invoking this service, then this service is dequing messages from topic.
Is any have any clue for this?
Thanks in Advance.
Edited by: vikky123 on Dec 22, 2010 1:46 PMIncrease Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..
-
Is JMS adapter can handle text message ?
Hi all,
In my scenario we have to take the data from Mainframe, CIS the data will come may in the form of text. If the data comes with text format ,is our JMS (DB2 drivers) can handle the messages in queue if yes is there any explicit configuration need to done. Till now we did message processsing of xml files but if the queue contains text message how to handle if it is not possible what procedure need to do any adpater module we have to write explicitly can some body explain?Hi,
Refer these links
http://static.springframework.org/spring/docs/2.5.x/reference/jms.html
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
http://help.sap.com/bp_bpmv130/Documentation/Planning/XIUnicodeGuide030411.pdf
http://help.sap.com/saphelp_nw04s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a05b2347-01e7-2910-ceac-c45577e574e0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/482aae19-0301-0010-3485-8efd618818d0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/604e2b64-e689-2910-64b3-ffd650f83756
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00982670-748c-2a10-3985-cdd42fb43e50
and also blogs
Triggering XI Alerts from a User Defined Function
How to send any data (even binary) through XI, without using the Integration Repository
Regards,
Surya
Maybe you are looking for
-
Beige G3 drives making me nuts
This is absolutely infuriating. I have a bunch of Beiges that I've been imaging. I have a number of 6GB and 8GB drives. I built a drive image with 9.2.2 and 10.3.9 with XPostFacto onboard. I've imaged several Beiges with it using NetRestore and a fir
-
Error regarding to the configuration of "Data Source" in Struts-config.xml
Hi, Any 1 just help me out. I am using NetBeans 4.1 bundeled with Sun App server 8.1. Now I wanted to make the database connectivity with the front -end using"Data-source" tag in the struts-config.xml file . I am using the Oracle 9i as database.But I
-
HT201210 how can i restore my iphone to a selected OS
how can i restore my iphone using itunes but i want to be able to select which OS to restore to. i have it on my desktop. but when can i select which OS to restore to? i remember vaguely something about right on restore...but i couldnt figure it out.
-
Firefox 4 will take too much time to re-calibrate to how I need to use it.
Firefox 4 seems to have some nice features, but I don't have the better part of a day to track down substitutes for Add-Ons that no longer work with v.4, figure out how to get my toolbars to display in ways that aren't entirely dysfunctional for me,
-
Attachment transfer of PO from SRM to Back end for extended classic scenario
Hi Experts, We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic