JMS adapter short log
Hi All,
Today morning we had a system restart after an upgrade.
As it is, all the channels were restarted.
The strange thing is one of the JMS does not have any thing written in the short log in RWB->CC monitoring though the channel is green.
Can you please let me know what could be the reason for this?
Regards,
Raghu
Hi Raghu,
There is no specific reason for this kind of behaviour...actually this is unexpected one.
Once the Java stack have restarted the log will be generated for the channels.
The reason behind this would be at the time of restart or shutdown any of the instance of this adapter was in use, so even after the Java stack had been restarted the adapter will not be initialized or be supressed.
I have faced similar kind of thing with even SOAP adapter.
It depends upon the running instances at the time of shutting down.
Normally this could happen with SOAP or JMS adapter, if you observe just refreshing or start/stop activity resolve it to norma behaviour.
I hope this will help you to get some hint.
Thanks
Swarup
Similar Messages
-
Hi All,
Today morning we had a system restart after an upgrade.
As it is, all the channels were restarted.
The strange thing is one of the JMS does not have any thing written in the short log though the channel is green.
Can you please let me know what could be the reason for this?
Regards,
Raghupatch upgrade helped
-
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 -
JMS Adapter: Disabling debug log
Hi All,
we are having trouble with the JMS Adapter. Adapter is showing message in the opmn/default oc4j intance log growing until 15gb or more..
Is there a way to disable the JMS transaction log ?
Log is showing the following lines:
<2010-02-25 13:12:48,244> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_start(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.04.74.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),0) invoked:oracle.tip.adapter.jms.JmsXAResource@121c9d1
<2010-02-25 13:12:48,267> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_end(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d5.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),67108864) invoked:oracle.tip.adapter.jms.JmsXAResource@be22d2
<2010-02-25 13:12:48,268> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_commit(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d5.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),true) invoked:oracle.tip.adapter.jms.JmsXAResource@be22d2
<2010-02-25 13:12:48,269> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_isSameRM(oracle.tip.adapter.jms.JmsXAResource@be22d2) invoked:oracle.tip.adapter.jms.JmsXAResource@be22d2
<2010-02-25 13:12:48,269> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_setTransactionTimeout(10800) invoked:oracle.tip.adapter.jms.JmsXAResource@16d2727
<2010-02-25 13:12:48,269> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_start(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.0b.74.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),0) invoked:oracle.tip.adapter.jms.JmsXAResource@16d2727
<2010-02-25 13:12:48,271> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_end(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d7.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),67108864) invoked:oracle.tip.adapter.jms.JmsXAResource@f03668
<2010-02-25 13:12:48,272> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_commit(Xid( Global Id 17.1b.f0.d9.ff.ff.ff.ff.e1.48.6d.06.27.01.00.00.d7.72.08.00.00.00.00.00, Format Id 1330790740, Branch Id b3.b7.b7.73.00.00.00.00.00.00.00.00.00.00.00.00),true) invoked:oracle.tip.adapter.jms.JmsXAResource@f03668
<2010-02-25 13:12:48,273> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_isSameRM(oracle.tip.adapter.jms.JmsXAResource@f03668) invoked:oracle.tip.adapter.jms.JmsXAResource@f03668
<2010-02-25 13:12:48,273> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> **** JmsXAResource_setTransactionTimeout(10800) invoked:oracle.tip.adapter.jms.JmsXAResource@c99711
Thanks in advance.
Regards,
Marcelo.In fact I think this is a BPEL question. The log level for default.collaxa.cube.ws is controlled from the BPEL console (at least before 11g, I bet it remains more or less the same).
In 10g you would log in to the BPEL console, select "Manage BPEL Domain", select "Logging" and then find the logger named "default.collaxa.cube.ws" in the list. Change the dropdown to a higher log level, for example Warn. Apply the changes and you are done. You may need to restart the instance if it doesn't seem to help.
I can't point to the exact screens in 11g as I don't have it here, but the general procedure should be the same. Good luck! -
Problem with Send using JMS Adapter with Websphere MQ
Hi,
We have two scenarios using JMS Adapter with MQ:
1. File->PI->MQ
This works fine and drop the file in MQ correctly.
2. MQ->PI->File
This gives an error reading from the queue: (see highlighted in the log below). It correctly connects to the queue name. But it fails with the message "Could not begin a AF transaction".
Our PI version is 7.0 SP 13
Websphere MQ Version 6.0.
Any idea what could be wrong?
Cluster Node Administration Information Availability Times
Cluster Node Details for Channel CC_JMS_MQ_Sender
Short Log
In the Last 4 Hours Server 0 15_92786
_Sucessfully connected to destination 'queue:///MMPP.PLM.FGH41? CCSID=37&targetClient=1'_
Line 1 / 1
Processing Details for Cluster Node Server 0 15_92786
Type
Time Stamp
Message ID
Explanation
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d Error while processing message '2e6206f0-7925-11dd-bc02-0003bae50b4d'; _detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ..._
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d XI message ID corresponding to JMS message with ID 'ID:414d512071736431202020202020202047d9462024028b02' will be created as a new GUID with value '2e6206f0-7925-11dd-bc02-0003bae50b4d'
Amith DharmasiriChecked the drivers installed in :
/usr/sap/<SID>/DVEBMGS<SYSNO>
/j2ee/cluster/server0/bin/ext/com.sap
.aii.af.jmsproviderlib
They are available and properly added to aii_af_jmsproviderlib.sda.
The drivers are:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
These were installed per OSS note 747601.
Any other suggestions, why retrieving from MQ doesn't work? -
Unable to get BPEL composite with JMS Adapter running.
Hello All,
I have tried to build a BPEL Composite to use JMS Adapter, by following the link http://blogs.sun.com/malkit/entry/oracle_soa_suite_bpel_to
Steps in WebLogic console:
1. Created a new JMS Server JMSServer-0 (file persistent store) this is targeted to AdminServer
1. Created a new JMS Module SystemModule-0
3. Created a connection factory in this module JNDI jms/SendRecvConnectionFactory
4. Created a queue in this module JNDI jms/ReceiveQueue
5. Created a SubDeployment Subdeployment0 for these two components.
6. Created a new JMSAdapter connection pool JNDI eis/tst/TestJMSConn and set the ConnectionFactoryLocation property to jms/SendRecvConnectionFactory
Next, I created a simple Java client and tested the JMS Queue to work fine. This went well.
Next, used JDeveloper to create a BPEL Composite to use JMSAdapater, and followed the guidelines given in the above URL to create the JCA file.
While deploying this BPEL composite, I hit a warning in SOA diagnostic server:
JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'
As a result of this warning, the BPEL Composite instances do not get created when I send a message from the test client.
Please find herewith the log details.
I am using JDeveloper Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923 and FMW 11g R1 PS3 RC11.
Any help here?
[2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.deployment] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] BPEL Component "default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess" successfully loaded.
[2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.deploy] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] [Deployment] Component: JMSampleProcess was successfully deployed to service engine:implementation.bpel, for composite:JMSSampleProj
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Initializing OutBound_jms.jca
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> OutBound JCAEndpointInteraction::initInteraction - Activating Endpoint Interaction, Endpoint Id='OutBound
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Successfully initialized OutBound_jms.jca
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] EventBus not null
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] component : Component Name: JMSampleProcess[[
implementation: oracle.fabric.composite.component.implementation.BPELImplementation@51db9e4
oracle.fabric.composite.model.ComponentTypeModel@51db9e6
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CubeServiceEngine=> initing default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess
[2011-04-20T08:33:12.458-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Loading InBound_jms.jca ..
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing JCAEndpointActivation::prepareActivation for {PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Locating JCA Binding Component instance: SCA_AS11R1
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:[[
endpoint='InBound'
WSDL location='oramds:/deployed-composites/default/JMSSampleProj_rev1.0/InBound.wsdl'
portType='Consume_Message_ptt'
operation='Consume_Message'
activation properties={PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating endpoint (0) for InBound
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Done preparing JCAEndpointActivation for Service 'InBound'
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Successfully loaded InBound_jms.jca
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Initializing InBound_jms.jca
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::performActivation - Performing JCA Endpoint Activation, Endpoint Id='InBound'
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing endpoint activation (1) for InBound
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj Creating new instance of Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - starting Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_start: Jms Adapter started
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_endpointActivation: Activating endpoint Endpoint_1
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_start: Starting endpoint Endpoint_1
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_run: Calling register...
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - successfully completed endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Successfully initialized InBound_jms.jca
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> :defaultRevisionChanged - updated default revision to default/JMSSampleProj!1.0 for default/JMSSampleProj
[2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21538] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] Removing temporary directory: C:\DOCUME~1\abhatika\LOCALS~1\Temp\1\sar_base_dir_1303306387379.
[2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21557] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CompositeDeploymentServlet-----> completed deploying sca_JMSSampleProj_rev1.0.jar successfully. Time spent: 5.188 sec.
[2011-04-20T08:33:13.036-05:00] [soa_server1] [WARNING] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041fd,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'. Resolved 'jms'Hi,
Try targetting it to soa_server1 instead of admin server. -
Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ
Hi,
I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
I have updated the oc4j-ra.xml with the following inputs:
<connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
<config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="false"/>
<config-property name="isTransacted" value="true"/>
<config-property name="username" value="admin"/>
<config-property name="password" value="welcome"/>
</connector-factory>
But while testing the BPEL process, I get the error:
<remoteFault>
<part name="code" >
<code>null</code>
</part>
<part name="summary" >
<summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
</part>
<part name="detail" >
<detail>null</detail>
</part>
</remoteFault>
Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
Thanks,
JayatuI am experiencing the exact same issue while configuring for Tibco EMS!!!
I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries! -
BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.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.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 moreBPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.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.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 more -
Configuration for sync/async bridge in Jms adapter
Can someone give me a hint what I might be doing wrong?
The scenario is: synchronous proxy to jms.
Integration repository:
Created synchronous outbound interface and synchronous inbound interface, message mapping, interface mapping.
Integration directory:
Created jms receiver communication channel and jms sender communication channel and configured them according "How to correlate jms messages".
Created receiver determination, interface determination and receiver agreement.
No sender agreement necessary for proxy sender.
So far so good, but...
Both the receiver and sender jms adapter have its own queue (the receiving system will get the request in one queue and put the response in another).
<b>How does the waiting jms receiver adapter know where to expect the answer?</b>
When I test this scenario the (outbound) message get the status "Log version" (abap moni) and "To be delivered" (java moni).
PS:
The testing is performed by using the tool rfhutil. With this tool you can read and write directly from/to the MQ queues where the jms adapters are pointing to.
After receipt of the request in the queue of the reveicer jms communication channel, I manually put a message in the queue of the sender jms communication channel with the XI message ID filled in the correlation ID.More information, In the jms adapter the following error appears:
XI inbound processing failed for message at time 2007-06-11|11:12:48.908+0100. JMS and XI identifiers for the message are ID:414d512052545849444556312020202045f55b6c20d73102 and 4e5bff20-1804-11dc-c2b4-00096b6ed15c respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Minimum address data not configured. Field InterfaceNamespace is empty.
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:1516)
at com.ibm.mq.jms.MQMessageConsumer.receiveAsyncQ(MQMessageConsumer.java:2538)
at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4260) -
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. -
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?
ThanksHave you tried cross-domain security or domain trust?
-
Error in JMS Adapter for MQ series
We have configured a JMS Adpater to connect to MQ Serries queue manager running on our local server. The XI Server is a remote server where JMS adapter is deployed.
Upon deployment we see following string in JMS adapter log -
Sender channel. Details: com.ibm.mq.jms.MQQueueConnectionFactory
And the status of Adpater is RED.
The Adpater is configured in sender mode.
We have created a local queue in Queme Manger and a Server Connectio channel which is being used in adpater configuration.
Please suggest what could be the missing link here.
Appreciate if you can provide us link s to any docuemtn which details the steps to configure an MQ JMS adapter.
Thanks,
GarimaHi Garima,
Please check the following:
1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
2. Check the existence of your JMS drivers.
3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
Any of the above solutions should help you solve the problem.
Regards,
Abhy -
JMS adapter: JNDI not able to connect to TIBCO server.
Hi All,
We are facing a strange problem here related to JMS adapter. We are trying to connect to TIBCO using JMS adapter.
We have 3 different Business Services, all the three using JMS channels. All the JMS channels are connecting to the same server on same port 7222. We have every thing same in all the JMS channels except the Que Name and the queue/log on user.
All the channels under 1 particular services are working fine while under the other two are giving below error:
===========================================
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection factoryQueueConnectionFactory, for profile: ConnectionProfile of channel: <Interface name> on node: <server node> having object id:<Object ID>: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to any server at: tcp://<host1>:7222, tcp://<host2>:7222<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:135)<br>
=============================================
Below are the basic JMS configuration:
1. QueueConnectionFactory
2. com.tibco.tibjms.naming.TibjmsInitialContextFactory
We are on PI 7.0 and working with both Sender and Receiver JMS adapters.
Looking for your help.
Regards,
RahulHI,
Please reply me for this question, or to the other one JNDI not able to connect . Both aer one and the other are same.
--Khaleel -
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..
-
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
Maybe you are looking for
-
Is there a way to prevent iTunes from updating apps?
I have recently updated an app that I love to play but the update caused me to lose all my saved data and it's very buggy and crashes all the time. I managed to rescue the old version from the recycle bin and deleted the new version from iTunes and m
-
Retstriction of confirmation dates in past dates in production order
Hi All, I have a issue with dates In our system production orders are created in advance at once in mass...suppose a production order is having start date and end date as 01.08.2014 and 07.08.2014. Now user taking this production order and proceeding
-
Hellow everyone, while opening SAPMMC i got message like "Get process List Failed" Unknown error. How can solve this problem Regards Ganesh
-
Extract trigger DDL from 8i database
Hi All, We are in process of migrating our 8i database's to 11g. for some reason , we excluded triggers while import. now , I need to get all the ddl's from 8i database. I think , dbms_metatadata is not there in 8i. using the following script did not
-
Reg: Reverse engineering from Code to Flowchart -
Hi Experts, I'm facing problems while generating Flowchart from an existing old legacy PL/SQL code. Is there any tool available which can generate that? Oracle SQL Developer, Toad, etc...? I'm quite sure it'll no way be comparable to a flowchart crea