JMS adapter - reciever error

Hi All,
I configured File to JMS scenario. For this, I have installed JMS drivers in XI to connect to WebsphereMQ 6.0, I deployed all the necessary jar files for this version.
This scenario is absolutely working fine for WebsphereMQ5.x version, however the same scenario is not working for WebsphereMQ6.0. The error it throws is An exception occured, completion code 2, reason 2059.
I crosschecked with MQ team, the details provided for Queuename, userid n pwd are correct. Eventhen I am getting the above error only for MQ6.0 only.
Please help me out if any extra conf need to be done.
Thanks
Satish.

Hi,
Thanks for replies
I checked all these and i m connecting with ipaddress but not with host.
however the ipaddress with hostname is entered correctly in etc/hosts
satish

Similar Messages

JMS Adapter configuration error

Hi All
      My scenario is file to jms.i configured the webspher MQ and i created queues manager and channals.I done JMS receiver like this,
1)Transport protocol:WebspherMQ JMS provied
2)Message porotocol:JMS x.1
3)Adapter Enigen:   Integration Server
4)QueueConnecation Factery Java           Class:com.ibm.mq.jms.MQQueueConnectionFactory
5)Queue Java Class:com.ibm.mq.jms.MQQueue
6)IP Address or server name:Localhost
7)Server port:1414
8)Queue Mannager Name:QM_sapxi
9)channal name:CHANNAL1
10)JMS queue:MQCONN.OUT
11)Transport/netwrok protocol:TCP/IP
12)JMS compliant:WebSpherMQ(non jms)
13)Deliver mode of message Producer:Persist JMS Messages in the JMS provider
14)mapping of the message:Entier message=JMS Payload
finaly i checked my Adapters status,it was red and i got the error Receiver channel. Details: (No detail information set. so pls help me .pls suggest me
thanking u
regards ,
ramesh

Hello Ramesh,
I assume you deployed your jms libraries via SDM.
You can check a successfull deployment in the libraries of the server node via the J2EE Admin tool.
To get a more detailed log, you can augment the log level to debug for destinations
com.sap.aii.af.service.jms & com.sap.aii.adapter.jms. You can do so in the logConfigurator of the J2EE Admin tool.
Afterwards reactivate your comm channel in the configuration. (Just change the short text, so you can change and reactivate.)
When you then go to the defaultTrace file via the logViewer, you should see more details on the error.
Greetings,
Bart

JMS Adapter Consumption Error

Hi All,
We are getting the below error while trying to consume the JMS Message from the queue. The instance itself is not created.
The Error Message is as follows:
+"Non Recoverable System Fault :+
+Failed to create Translator. Expected "startsWith" or "lookAhead" with "lookFor" at <element name="ODErrorLogger">, but not found. Must specify "startsWith" or "lookAhead" with "lookFor" at <element name="XXXXX">, because this particle is within "choice" model group."+
When i click on the payload viewing option in the error message i get the boxes and some special symbols.
Kindly do help us resove the same.
Regards,
Balaji R

Hi,
You have a XSD for translating native format... The translator is not able to understand your xsd...
What's your message format, xsd and expected result?
Cheers,
Vlad

MQ6 Drivers for JMS Adapter throwing error

Per note 747601 of SAP, we got the jar files for MQ6.
MQ 6.0 with SAP XI 3.0 JAR files needed
We prepared the .sda file
When we try to deploy it through SDM, we are getting errors:
Summary:
========
There were 1 archives selected.
0 archives successfully loaded.
   Loading of 1 archives failed.
Details:
========
1) Error loading archive
    C:\aii_af_jmsproviderlib.sda
    (server side name is: C:\aii_af_jmsproviderlib.sda)
    com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component
found in the SDA C:\aii_af_jmsproviderlib.sda is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation is missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
Please advise.
Thanks,
Bhaskar
Here is how this got resolved:
We added drivers for MQ6 in the sda file.
Then isntalled MQ client on the XI server (I am not sure why we need to do this).
Then in the Communication Channel provided the User ID and PAssword for the MQ Server box (the windows log in information). It took us a while (a couple fo weeks) to find this out.
I am not sure if this is the real solution, but it is working fine for us now.
So thoguht of posting this here.
Thanks,
Bhaskar

not sure about this but i guess Craig is a better person to let you know !!!
Contact - [email protected]

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 JMS adapter 11g

Hi
I have configured a JMS Adapter in Jdev 11.1.1.3.0 to consume message from a queue(JNDI Name as eis/wljms/WLQueue) on a weblogic server(10.3.1) in a different domain and deployed my BPM process to the soa server 11g.
I created a new outbound connection pool (eis/wljms/WLQueue) in Deployments->JMSAdapter->Configuration->Outbound Connection Pools with Connection Pool Interface: oracle.tip.adapter.jms.IJmsConnectionFactory
Also updated the factory properties field for eis/wljms/WLQueue with :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.75.85.151:9021;java.naming.security.principal=weblogic;java.naming.security.credentials=weblogic
And finally updated the deployment plan for JMSAdapter.
However I am getting the following error :
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample JMSMessageConsumer_init: Retrying connection; attempt #1>
<May 24, 2010 10:08:29 AM GMT+05:30> <Warning> <oracle.soa.adapter> <BEA-000000>
<JMSAdapter sample
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 neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:207)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnec
tionFactory(JMSConnectionFactoryFactory.java:86)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:173)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
Caused by: javax.naming.AuthenticationException [Root exception is java.lang.Sec
urityException: User: weblogic, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialCo
ntextFactoryDelegate.java:681)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
67)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.ja
va:183)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionF
actory(JMSConnectionFactoryFactory.java:131)
... 26 more
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticat
ed.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServi
ceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Sou
rce)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.jav
a:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173
Anyone has come across this issue? if yes, how do I resolve this?
Thanks

Have you tried cross-domain security or domain trust?

Error in JMS Adapter Configuration.

Hi,
Its regarding JMS receiver adapter for MQ Series.
We have MQ 6.0 installed on PI server. While trying to connect thorough JMS receiver adapter we are getting a connection failure error at communication channel level.
The MQ administrator is of the opinion that as MQ is local to the PI server a channel is not required.
In the MQ server, the administrator has created a Manager and Queue which we are using in the JMS receiver channel.
We have provided the queue connection factory as the default one used for MQ 5.3
class also as the default. (All the extra jar files required for MQ 6.0 is deployed).
The error description says:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.23.86.134:XBEIG_QMGR1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
Any inputs would be very helpful...
Many Thanks,
Rosine.

you can check the SAP Note 856346 - FAQ on JMS adapter it might have some info

Error in JMS Adapter:

Receiving the below error, thought of JMS Drivers problems undeployed and re-deployed several times, but still problem persist in XI.
Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2010-09-09 11:45:21     Error     MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
2010-09-09 11:45:21     Error     Exception caught by adapter framework: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary..
2010-09-09 11:45:22     Success     The message status set to WAIT.
2010-09-09 11:45:22     Success     The asynchronous message was successfully scheduled to be delivered at Thu Sep 09 11:50:21 CDT 2010.
The JNDI Libraries are available in Visual Admin, not sure what else causing the issue. Any guru's help is appreciated

XI 3.0 SP20
Regarding the note, that only applied below sp4. We are on SP20. The default values appears but those are not working.This seems to be a problem with Dev only, Q and P is working fine at this moment
If i actually delete module processor's from Sender and Receiver channel, things are working fine. But not sure if it is going to break anything. And this needs to be applied in all landscape. But i have to present a reason, why this weird behavior all of a sudden
Sender
    SAP XI JMS Adapter/ConvertJMSMessageToBinary
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Receiver
    SAP XI JMS Adapter/ConvertMessageToBinary
    SAP XI JMS Adapter/SendBinarytoXIJMSService

Adapter Status Error : Error in creating message ID map for JMS message:

Currently in the SAP XI 3.0 JMS Adapter, I am receiving the following error
Error in creating message ID map for JMS message:
ie. Error while processing message 'de8265f6-c864-4479-1137-9bab17b78b3b'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in creating message ID map for JMS message: ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:103)
Although I am receivng this error, when I check the details of the message processing, all steps are successful and the message is set to status : DLVD
Audit Log for Message: de8265f6-c864-4479-1137-9bab17b78b3b
Time Stamp     Status     Description
09.06.2009 13:27:24     Success     New JMS message with JMS message ID ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 received. The XI message ID for this message is de8265f6-c864-4479-1137-9bab17b78b3b
09.06.2009 13:27:24     Success     JMS message converted to XI message format successfully
09.06.2009 13:27:24     Success     RRB: entering RequestResponseBean
09.06.2009 13:27:24     Success     RRB: suspending the transaction
09.06.2009 13:27:24     Success     RRB: passing through ...
09.06.2009 13:27:24     Success     RRB: leaving RequestResponseBean
09.06.2009 13:27:24     Success     Transform: using Transform.Class: com.sap.aii.messaging.adapter.Conversion
09.06.2009 13:27:24     Success     Transform: transforming the payload ...
09.06.2009 13:27:24     Success     Transform: successfully transformed
09.06.2009 13:27:24     Success     Application attempting to send an XI message synchronously using connection JMS_http://sap.com/xi/XI/System.
09.06.2009 13:27:24     Success     Trying to put the message into the call queue.
09.06.2009 13:27:24     Success     Message successfully put into the queue.
09.06.2009 13:27:24     Success     The message was successfully retrieved from the call queue.
09.06.2009 13:27:24     Success     The message status set to DLNG.
09.06.2009 13:27:25     Success     The application sent the message synchronously using connection JMS_http://sap.com/xi/XI/System. Returning to application.
09.06.2009 13:27:25     Success     The message was successfully transmitted to endpoint http://sapxia.swets.nl:8000/sap/xi/engine?type=entry using connection JMS_http://sap.com/xi/XI/System.
09.06.2009 13:27:25     Success     The message status set to DLVD.
Not sure why this is occurring.......

No, not using correlation id.
I was able to resolve the issue on this queue by changing the following setting
Under the PROCESSING tab, under XI SETTINGS
Time period for Duplicate Check for EO(IO) (secs) it was set to 86400
I have changed this to 300 seconds and the adapter has now gone green.
BUT......
That said, I have the exact scenario on another sender JMS channel set to 300 seconds and it exhibits the same issue.
correlation settings:
Set XI message id to = GUID
Set Xi conversation

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

JMS adapter does not recover from error

Hello everyone,
We are noticing some strange behavior with the JMS adapter, and would like your help. We have messages coming into XI from WebSphere MQ. We have configured a Sender Comm channel (MQ_SENDER) with the appropriate JMS adapter, with a specified queue name (TEST.Q) . We have installed the appropriate MQ-JMS libraries for v6.0.
Here's the problem scenario... initially the application sending the messages to the specified queue was putting an incorrectly formatted MQRFH2 structure in the message. Predictably, this caused our comm channel to fail, and it shows up on the adapter monitor in the failed state with the message "MQJMS1050: The MQRFH2 header has an incorrect format Code: MQJMS1050". This in itself is not a problem, we realized that the application was sending a malformed message. The problem occurs when we fixed the sending application to completely strip out the MQRFH2 header altogether. When the new message is sent, the comm channel seems "stuck" on the previous error, and does not even pick up the new message from the queue. The adapter monitor continues to show the same error for the comm channel. Now when we modified the comm channel to read from a DIFFERENT queue (TEST2.Q) , the comm channel got out of the error state and is able to successfully process new messages coming into that queue. However, when we revert the comm channel back to the original queue (TEST.Q) it reverts back to the original MQJMS1050 error, and does not pick up new messages on the queue.
Any assistance would be greatly appreciated...

Hi,
1) Try to refresh the metadata
2) Check the Queue status
3) Once again check the Queue name. try to make the Sender JMS adapter inactive .save it..again make it active and save it and activate the object.
4) Refresh the Cache :
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

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

Error in JMS adapter MQ to PI

Hi,
We are connecting to Websphere MQ using the JMS adapter.
The message coming from MQ is a flat structure. So we have configured the Message Transform Bean to do the conversion from plain to xml structure according to
http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter
But when we test a message we end up with this error:
TransportException: No MIME header found at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
I'm not sure if this is related to the content conversion or general settings in the JMS adapter.
Any inputs are highly appreciated.
Thanks
Shakthi

Hi Shakthi,
Actually, it is the error that tells you where the error took place:
com.sap.aii._adapter.jms_.core.channel.filter.ConvertBinaryToXiMessageFilter.filter
You might also want to refer to this thread: Error in JMS Sender Adpater for a few ideas to solve your problem. In general, it is connected to your adapter configuration. Please review it once again ang you should have the problem fixed.
Hope this helps,
Greg

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,
Pram

All,
Problem is solved. I changed the value for the Source directory & the adapter started to poll.
Thanx,
Homiar.

Sender JMS adapter error

Hi All,
I'm trying out a scenario which sends data from a Message Queue to SAP.
For this I need to configure JMS adapter in the sender side. here i am getting the error in the sender communication channel like below
Can not access because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing; ensure that JMS provider library 'aii_af_jmsproviderlib.sda' contains all required resources.
Can any please help me on this?
Thanks
Govinda.

You need to deploy the MQ JMS library to your PI system first.
Please check sap note 1138877 for detail.
The numbers and names of the IBM libraries change depending on the MQSeries version you are using. Currently, we know the following names:
MQSeries 5.2
u2022     com.ibm.mq.jar
u2022     com.ibm.mqjms.jar
MQSeries 5.3
u2022     com.ibm.mq.jar
u2022     com.ibm.mqbind.jar
u2022     com.ibm.mqjms.jar
u2022     connector.jar (this file can also be retrieved from the SAP J2EE server directory)
MQSeries 6.0
u2022     CL3Export.jar
u2022     CL3Nonexport.jar
u2022     com.ibm.mq.jar
u2022     com.ibm.mqjms.jar
u2022     connector.jar
u2022     dhbcore.jar
u2022     rmm.jar

JMS adapter - reciever error

Similar Messages

Maybe you are looking for