JMS sender communicaton channel error

Hi,
The JMS sender communication channel throws the following error in Communication Channel monitoring in RWB.
<b>Channel started but Inactive</b>
<b>"Channel removed; check whether channel was deleted or moved to another Adapter Engine"</b>
But the channel is active and a copy object of the same channel works succesfully.
Has anyone faced such an issue?
Thanks,
Ambili

Hi Abhishek,
Thanks for ur reply.
1. Already tried it, but still the same status.
2. Yes, i can see the channel in sxi_cache.
3. Tried this several times, same message.
The issue is just for this channel and as I mentioned before, a copy object of the same channel works perfectly fine.
Thanks,
Ambili
Edited by: Ambili Jose on Jan 19, 2010 7:30 AM

Similar Messages

JMS Sender Communication Channel problem

Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
Thanks

HI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup

JMS sender communication channel content conversion

Hi,
I struck with the content conversion in the JMS Sender communication channel.
I have configured the communication channel with the filed fixed lengths. (Simple type)
The field fixed lengths i have given are 10,2,3,11
The contents in the file 1000000072 230 111
but, in the input xml after conversion iam getting 100000007 in the first field and 2 in the second field 23 in the third field.
I have configured the sender communication channel as in the document in SDN.
Even, i configured several communication channels. I didn't get this strange error any time.
I have gone through SDN to fix this issue, but i didn't get solution.
If anyone got rectified this kind of error, please answer your solution to me
Thanking you,
Regards,
Krishnaraju.

Hi,
Thanks for all your support. The issue got resolved.
The issue is due to the file, In the file the special characters are appearing. We are not able to see these characters in the notepad, wordpad, text editor.
But, these characters are appearing in th syn text editor. So, we removed those characters and processessed the file. Now, it is successfull.
Regards,
Krishnaraju.

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

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

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

Content conversion at JMS sender communication channel

Hi friends,
I have to convert fixed length flat structure to xml message.Therefor i have to do content conversion at the JMS sender comm channel.Can someone please explainthe procedure?
data in the queue would be like as follows.
9999000000124646q12233appej500rc11147822zord

Hi Manikandan,
The structure conversion can handle files containing rows with different structures. In
each row there is a key field to identify the structure. The rows with identical key fields of
course have identical structures.
Let us assume that we have a sample file with four rows. Each row has a two-byte key
field; the first row has a second field with ten bytes; the structure of the second and third
rows is the same and comprises two additional fields with three bytes each; the last row
has a second field with five bytes:
AA1234567890
BBABCABC
BBXYZXYZ
CC12345
The configuration for the conversion could look like this:
Module Configuration
Module Key Parameter Name Parameter Value
Plain2XML Transform.Class com.sap.aii.messaging.adapter.Conversion
Plain2XML Transform.ContentType text/xml;charset=utf-8
Plain2XML xml.conversionType StructPlain2XML
Plain2XML xml.processFieldNames fromConfiguration
Plain2XML xml.documentName MyDocument
Plain2XML xml.documentNamespace http://xi.com/test
Plain2XML xml.recordsetName MyRecordset
Plain2XML xml.recordsetStructure NameA,1,NameB,*,NameC,1
Plain2XML xml.keyFieldName MyKey
Plain2XML xml.keyFieldType CaseSensitiveString
Plain2XML xml.NameA.fieldNames MyKey,field-nameA
Plain2XML xml.NameA.fieldFixedLengths 2,10
Plain2XML xml.NameA.keyFieldValue AA
Plain2XML xml.NameB.fieldNames MyKey,field-nameB1,field-nameB2
Plain2XML xml.NameB.fieldFixedLengths 2,3,3
Plain2XML xml.NameB.keyFieldValue BB
Plain2XML xml.NameC.fieldNames MyKey,field-nameC
Plain2XML xml.NameC.fieldFixedLengths 2,5
Plain2XML xml.NameC.keyFieldValue CC
In xml.recordsetStructure, you add a name for each different structure followed by the
number of occurrences or an asterisk for unbounded occurrences. For each structure
name, you configure the structure separately in a separate namespace such as
xml.NameA.fieldNames and so on.
If your source file is a CSV file, replace each xml.XXX.fieldFixedLengths with
xml.XXX.fieldSeparator.
the result of this conversion looks like this:
<ns:MyDocument xmlns:ns="http://xi.com/test">
<MyRecordset>
<NameA>
<MyKey>AA</MyKey>
<field-nameA>1234567890</field-nameA>
</NameA>
<NameB>
<MyKey>BB</MyKey>
<field-nameB1>ABC</field-nameB1>
<field-nameB2>ABC</field-nameB2>
</NameB>
<NameB>
<MyKey>BB</MyKey>
<field-nameB1>XYZ</field-nameB1>
<field-nameB2>XYZ</field-nameB2>
</NameB>
<NameC>
<MyKey>CC</MyKey>
<field-nameC>12345</field-nameC>
</NameC>
</MyRecordset>
</ns:MyDocument>
Regards,
Vinod.

Sharing JMS sender communication channels

Hi all,
We have flatfile interfaces to XI JMS where we would like to share the JMS sender communication channel.
This is normally not possible since you cannot have two sender agreements with the same comm channel.
Are there workarounds for sharing JMS comm channels (we cannot make use of content fields, we do no conversion). is there a way with variables perhaps?
Thanks for any help
Tom

Tom
There is an otption of send a file to multiple receivers.
Therefore use your receiver determination to have multiple receivers and set there some condition.Thus making conditional receivers. Or have two receiver determinations.
This might help you.
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
/people/prasadbabu.nemalikanti3/blog/2006/03/10/bpmsingle-sender-and-multiple-receivers-based-on-synchronous-exchangeswitch-part-1
/people/prasadbabu.nemalikanti3/blog/2006/02/27/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-2
http://help.sap.com/saphelp_nw04/helpdata/en/7d/577941761b070de10000000a1550b0/content.htm
Pls : Reward points if helpful.
Vishal K

2 JMS Sender Communication Channels polling 1 MQ Queue

Hi Experts,
I have a situation where 2 JMS sender communication channels are polling 2 different message type data (via content conversion in JMS) from 1 MQ queue. However adapters are having problem polling the right message from the queue.
Is this something that is not possible?
I know that we can possibly use 2 MQ queues - one for JMS 1 with message type 1 and the other for JMS 2 with message type 2
OR
1 JMS with 1 common message type with 1 MQ queue.
But I want to confirm whether my current situation is suppose to work or not.
Thanks,
Jay

>
Jung Sun Ko wrote:
> Hi Experts,
>
> I have a situation where 2 JMS sender communication channels are polling 2 different message type data (via content conversion in JMS) from 1 MQ queue. However adapters are having problem polling the right message from the queue.
> Is this something that is not possible?
Maintain different queues for different message types.
The adapters else will just pick the message that comes to the queue first based on the polling time irrespective of the message type. It is not intelligent enough
>
> I know that we can possibly use 2 MQ queues - one for JMS 1 with message type 1 and the other for JMS 2 with message type 2
> OR
> 1 JMS with 1 common message type with 1 MQ queue.
>
> But I want to confirm whether my current situation is suppose to work or not.
>
> Thanks,
>
> Jay
Hope the above replies answers your question

Sender Communication Channel Error

Hi all,
iam working on JDBC scenario.For this iam using party and business service.
iam getting following error at jdbc sender communication channel.
Error occurred while sending message: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.
Erlier it worked fine.But now iam getting this problem.
We are having some other channels which r working fine.
any ideas......?
Thanks,
Sreedhar Goud.

1. If you know the user, who having admin rights;
1.Open the VA tool; ex: C:\usr\sap\X67\JC01\j2ee\admin --> click on "go.bat"
2. Click on "New" button ( this is on Logon Dialog box)
3. Enter "Display name"; and select "Direct Connection To a Dispatcher Node".
4. Say "Next"
5. Enter "User Name","Host" and "Port" and Save the data.
6. Select User and click on "Connect"
2. Did you forget the J2EE_ADMIN password? Just follow below steps:
Just follow below steps:
1.Start the Config Tool C:\usr\sap\<SID>\<engine-instance>\j2ee\configtool\configtool.bat
Ex: D:\usr\sap\F02\JC00\j2ee\configtool --> configtool.bat
2. "Switch to configuration mode" for that Click on "Pencil" icon;
3. Click on "Pencil" icon means "Swith to Configuration Edit mode" then say "YES"
4. cluster_data --> server --> cfg --> services -->
click on "Propertysheet com.sap.security.core.ume.service
select properties:
ume.superadmin.activated = True
ume.superadmin.password = <enter password >
then say "OK"
Click on "Pencial ICON.
5. Save & restart Java Engine.
Login with "Administrator"
1. http://<host>:<Port>/useradmin/index.jsp
2. Enter userid / Password as "Administrator / <password>
3. it will ask change password just change it.
Please follow steps one by one. it should resolve your issue.

Reconnect issue with JMS sender Communicatio channel

Hi All,
We need help for JMS sender channel.from last two days we are getting issue with JMS channels.they are looking green but not picking data from Mq ssue to this lot of messages got stuck in MQ queue and its stop writting messsages .
Problem from PI side is JMS communication channels are not showing any issue.even they do not pick data or lost connection with MQ server they are looking green. so its very difficult for PI team to find out correct Comunication channels which stop picking up the data.when we start/stop that CC its start picking data.
Do anybody face this issue.please do let us know permenent solution instead of doing start/stop when user report issue.
Thanks in advance
Best Regards
Monica Bhosale
Edited by: monica bhosale on Mar 8, 2012 8:56 AM

we are using PI 7.11 and this issue was fixed in SP06
until then one of the work around we were using was to schedule the adapter to stop and start every 3 hour or so

Issue with JMS sender Communication Channel

Hi All,
We are tying to connect to IBM WebSphere MQ system from SAP PI and pickup messages thru sender JMS adapter.
This is WebSphere MQ -> PI -> Proxy Async scenario. We deployed the required sda file in SDM. We could connect to MQ system message queue, and pick messages from PI development system.
But, when we are trying to do it from PI test system, we get the following error in Comm Channel monitoring:
Error while processing message 'b000f150-15cf-4484-24ec-d8ad10acb685'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Exception in method process.: BaseEJBException: Exception in method process. at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
The patch levels (ABAP & Java) are the same for both the PI systems.
sda file is also deployed successfully for both systems. Comm Channel config is exactly the same for both the systems.
But, still we get the above error.
We did full cache refresh, CPA cache refresh, stopped/started comm channel, restarted the adapter, java stack, and whole PI system after deployment. But, still we get the same error.
Can you please tell me if i am missing something here?
Thanks,
Chandra

Hi,
>>>MessageFilterException
my exp with this error on JMS
a) delete the channel in ID
b) recreate it and active and it works ....
at least with activemq jms
Regards,
Michal Krawczyk

Sender File channel error

Hi Experts,
We are getting the below error in the File sender channel.
Error: com.sap.engine.interfaces.messaging.api.exception.MessagingException:24
This error we are getting for one specific File Channel. Other File channels are working fine. 1 message is also picked up by this channel but everytime it shows the same message id and the error.
Please let me know how to fix this.
Regards,
Shaibayan

Hi Shaibayan,
Kindly check for detailed logs in NWA for this channel.
Also if possible try to collect logs from XPI Inspector tool, more details can be found in below OSS note:
1514898 - XPI Inspector for troubleshooting XI
Regards
VJ

SOAP over JMS Sender Communication Channel - How to?

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

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

JDBC Sender Communication Channel Error

Hi,
We are facing the below error in Sender JDBC communication channels:
The JDBC driver returned the following error message: 'java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]No ResultSet set was produced.'
We are getting this error in channels which are using stored procedures but not in channels using direct sql query statements.
The database is not having any data currently.
So is the above error because of no data or some other issue?
Any ideas?
I have searched the sdn but didnt find anything appropriate.so posting a new thread.
Thanks,
Anu.

Can you try again after filling in few records in the DB? I am suspecting the way SP has been written ... check if it is required to return value from SP?

File sender communication channel error

Hi gurus please help me on the below issue ,suddenly my file(sender)communication channle is showing error status stated below error ,it is just simple scenario like file to proxy upto one hour back it is working fine suddenly it is showing below error plz give me the reply im in production suport
Error: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name localejbs/ModuleProcessorBean, cannot resolve object reference. [Root exception is javax.naming.NamingException: Error occurs while the EJB Object Factory trying to resolve JNDI reference Reference Class Name: Type: clientAppName Content: sap.com/com.sap.aii.af.app Type: interfaceType Content: local Type: ejb-link Content: ModuleProcessorBean Type: jndi-name Content: ModuleProcessorBean Type: local-home Content: com.sap.aii.af.lib.mp.processor.ModuleProcessorLocalHome Type: local Content: com.sap.aii.af.lib.mp.processor.ModuleProcessorLocal com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.aii.af.app; nested exception is: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5106] The application [sap.com/com.sap.aii.af.app] will not be started, because of the server state is [STARTING]. at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315) at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106) at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:144) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:63) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:77) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:228) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283) at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:394) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:223) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:242) at javax.naming.InitialContext.lookup(InitialContext.java:351) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:83) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:51) at com.sap.aii.adapter.file.File2XI.send(File2XI.java:3451) at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1332) at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:622) at com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:500) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182) at com.sap.engine.core.thread.impl3.SingleThread.run

Hi Thank for your reply Nbendu and sorry for late reply .
My issue was now resolved but i want to know why this is happend i am getting this issue when ever there is any Basis maintaenance Happens.
If it is due to Basis maintnance then with same combination we have 2 more interfaces is there it is not affecting the other .
Any thoughts.
Regards
Madhu

Receiver JMS Adapter Communication channel Error

Hi Experts,
The Error is given below
Cannot connect because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing: ensure that JMS Provider library 'aii_af_jmsproviderlib.sda' contains all required resources.
when i searched SDN , i found the MQ JMS Library need to deployed in XI/PI . For clarification check SAP NOTE 1138877 is given .
What should I do ?
pls advice
Regards,
Jude

Hello Experts,
I am encountering the same error that you faced. I am using PI 7.0 and MQ adapter 6.0. I would like to know where to get the following jar files:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
I know that I am supposed to add the above files to aii_af_jmsproviderlib.sda on the PI server. As I not a basis person, it'll be great if you could direct me to some detailed instructions. I am trying to follow SAPNote: 747601.
Please correct me if I am wrong.
Thanks,
Bhanu.

JMS sender communicaton channel error

Similar Messages

Maybe you are looking for