PI 7.1: Weblogic (JMS adapter) - Connectivity & MONITORING!!

Hi ALL
WE have a requirement to integrate PI with Weblogic server using JMS adapter.
However, we would like to host the JMS queues in PI, so that we have end to end monitoring capability.
We do not want Weblogic Server to host these queue, instead want PI 7.1 to maintain these quese ... so that we can monitor these interfaces end -to- end.
Please, let us know if anybody has done this Weblogic integration with JMS queue monitoring within PI 7.1.
So, the main GOAL is to have JMS Queue monitoring in PI, where we have visibility to how many queues are running and the no.of messages in sent in each queue and failures if any.
Also, is there any Queue monitoring under /nwa adminstration; where we can see the queue created in PI
So, if anyone has implemented this in PI 7.1, please let us know.
Your help is greatly appreicated!!
Thank you,
Patrick.
Edited by: Patrick Jones on Sep 25, 2009 6:24 PM
Edited by: Patrick Jones on Sep 25, 2009 8:58 PM
Edited by: Patrick Jones on Sep 26, 2009 12:09 AM
Edited by: Patrick Jones on Sep 26, 2009 10:04 PM
Edited by: Patrick Jones on Sep 28, 2009 2:28 AM

Hi Patrick,
We've done something similar but with PI 7.0 & Weblogic hosting the queue so I'm not sure how useful this will be to you...
Firstly, great move to have the queue/s hosted in PI (in my opinion), for several reasons:
- You won't have to keep investigating whether or not Weblogic actually put the message on the queue/s or not.
- It makes monitoring a bit easier.
- For some reason on PI 7.0, when Weblogic or stops the queue services then PI stops polling for messages although we have green lights in RWB communication channel monitoring. If we stop & start the comm channel/s then the JMS Adapter starts picking up messages off the queue. A couple of SAP notes point to a known Weblogic issue with the way Weblogic works with initial contexts. Hosting the queues in PI would take care of this problem.
Currently we are using HermesJMS to monitor all JMS queue/s with number of messages & possible message backlog in the queues. We are also working on setting up Business Processing Monitoring that can do full end-to-end monitoring of a business process across the landscape not just in within PI. I'm also curious to see what's available in PI 7.1 for JMS queue monitoring.
Regards, Trevor

Similar Messages

PI7.1 JMS Adapter - connect to NW6.40

Hello,
We are facing following problem on SAP PI:
We have a scenario where PI (version 7.1) is connecting to another SAP NetWeaver system (version 6.40). There is an application that reads/puts messages from/to JMS Queues running on this system. PI has to connect the JMS Provider of 6.40 system and read/put these messages from/to these JMS Queues.
This scenario worked fine till we used XI 3.0 (NW6.40). We configured sender JMS channel with link to remote JMS Server and parameter "force_remote".
After installation of new PI7.1 we noticed some issues:
1.the connection is unstable. Sending JMS messages from PI to NW6.40 queue works a while but then we get error like this:
Adapter Framework caught exception: Unable to write new JMS message body for message: 00237d29-13fc-02ed-ba85-01d046631592: ConnectorException: Connector for ConnectionProfile of channel: EON_CC_jms_rcv_omsmessageon node: 922834950 having object id: 70855b1c6c483e869982ea2fe9787b36 was unable to create a new javax.jms.TextMessage message: javax.jms.IllegalStateException: Session is closed.
2. we cannot read messages from JMS Queue of NW6.40 at all. The messages are there in queue, communication channel is running and succesfully connected to queue but no message is processed and no error shows in communication channel monitoring.
Has anybody solve similar problem with connection between 7.1 and 6.40 NetWeaver?
I think the problem can be backward incompatibility of 7.1 SAP JMS libraries against 6.40. If this is true then the question is whether it is possible to deploy old libraries and run them simultaneously with native 7.1 libraries?
Thanks

problem sorted - factory property settings were not configured correctly in JMS Adapter connection pool

Error with the Receiver JMS Adapter (Connection On-Demand feature)

Hi,
In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
The message status was set to WAIT.
Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
Any idea?
PI 7.1 EHP1
Thanks,
Martin
/people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

Female Mini Display Port Adapter - Connect Monitor to Non Mini Display Port

Anyone know of a Female Mini Display Port Adapter, so I can connect the 24 LED Cinema Display to a computer that has DVI connector? Or hook the monitor up to a KVM, so I can use the monitor with multiple computers?
I know Apple doesn't make these, but does a third party?
Monoline appears to be coming out with adapters to hook a mini display port computer to DVI and HDMI, but not a mini display port monitor to DVI or HDMI.

'Mini Display port' is just a smaller version of display port, which is a slightly different version of HMDI.
No. You may be thinking of Mini DVI. Mini DisplayPort is a smaller verion of DisplayPort, which is different from DVI and HDMI.
<http://www.displayport.org/white-papers/whitepapers/DPTech_OverviewEnglish.pdf>
HDMI, display port, mini display port AND DVI are all capable of being 'converted' from one to another.
It is easy to make a Mini DisplayPort (card) to DVI (display) adapter because a DisplayPort card can be set to generate DVI signals. (Dual-link DVI is a bit more complicated since the adapter must sepatate the clock and data.). A DVI card cannot generate DisplayPort signals, so an adapter for a DisplayPort display with a DVI card would be a lot more complicated.
The ONLY thing that you would LOSE in a DVI to display port conversion is an audio signal.
HDMI is DVI video plus digital audio. DisplayPort does not use DVI video.
The point is they are all interchangeable, signal wise.
No. A DisplayPort card can generate DVI signals when a DuisplayPort to DVI adapter is detected, but a DVI cards cannot generate DiusolayPort signals.
But why should Apple make a cheap DVI to female display port when they can make more money on overpriced graphics card upgrades?
They can't make a cheap adapter, but they could have added a DVI port to the display.

Jms Adapter Connection- Deployment Need Help!!!

Hi,
a got a problem when i try to deploy a new Jms Connection with JNDI and OpenJms.
(I use the Visual Administrator-Gui /services/JmsConnection to do this)
I already deployed my OpenJms Libary jar at xi.
And i get this error if i want save the JmsConnection.
Is there something else i must create or import ???
Would be great if someone knows this problem???
Here the error form Xi Visual Administrator:
java.rmi.RemoteException: Cannot deploy application openjms.sf.net/openjms.app..
Reason: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.; nested exception is:
 com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
 at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
 at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
 at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
 at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
 at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
 at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
 at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
 at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
 at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
 at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.<init>(FileInputStream.java:106)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
 ... 35 more
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
 at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
 at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
 at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
 at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
 at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
 at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
 at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
 at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
 at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
 at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.<init>(FileInputStream.java:106)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
 ... 35 more
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:536) at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58) at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289) at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944) at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288) at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400) at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340) at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330) at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287) at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157) at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220) at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803) at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102) at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61) at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
 at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
 at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
 at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
 at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
 at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
 at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
 at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
 at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
 at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
 at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.<init>(FileInputStream.java:106)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
 ... 35 more
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Error parsing XML file /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml.
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:267)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:521)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deployComponent(ContainerImpl.java:1560)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
 at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
 at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
 at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
 at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
 at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
 at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
 at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
 at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
 at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
 at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
 at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.io.FileNotFoundException: /usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/apps/openjms.sf.net/openjms.app/JMSConnector/standaloneapp.xml (No such file or directory)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.<init>(FileInputStream.java:106)
 at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.deploy(ContainerImpl.java:264)
 ... 35 more
 at com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException.writeReplace(BaseDeploymentException.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367) at javax.management.MBeanException.writeObject(MBeanException.java:126) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367) at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:168) at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257) at com.sap.engine.services.jmx.Message.getMsg(Message.java:453) at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1267) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66) ... 9 more

did you solve this problem. if yes can u pls tell me how. i get the exact problem in Web AS Visual Administrator.
thanks
RD

WebLogic JMS client frozen during JMS connection stopping (race condition)

Hello,
Our application is using the WebLogic 10.3.1 JMS client generated with wlfullclient5.jar.
We have sometimes a race condition when the WebLogic server is stopped.
In about 10% of the cases where the server is stopped, the client application is frozen in the "stop" call (see stack trace #1 below).
Our understanding is that each JMS API call by the application is translated by a request-response message on the TCP connection to the JMS server. The JMS library sends the request and then wait for the response. From our observations, it looks like there is no local timeout in the JMS library. This means that if the WebLogic server is being stopped just after receiving the "stop" request, it will never send the "stop" response, which means that the application will be stuck forever.
The same problem also occurs when using JMS bridges between 2 JMS servers (see stack trace #2 below).
How can we activate a local timeout for all JNDI/JMS calls ?
Regards,
metatech
"AppThread" prio=3 tid=0x0000000100117800 nid=0x2 in Object.wait() [0xffffffff7befe000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at weblogic.messaging.dispatcher.DispatcherWrapperState.triggerPeerGoneAndWait(DispatcherWrapperState.java:607)
- locked <0xffffffff7509aee8> (a weblogic.messaging.dispatcher.DispatcherWrapperState)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:349)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:252)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
at weblogic.jms.client.JMSConnection.stop(JMSConnection.java:758)
- locked <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
at weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
at AppSession.closeJMSSession(ConnectorSession.java:499)
"[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.jms.client.JMSXASession@1d363e4 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.jms.client.JMSSession.waitForState(JMSSession.java:4778)
weblogic.jms.client.JMSSession.stop(JMSSession.java:1310)
weblogic.jms.client.JMSConnection.stop(JMSConnection.java:773)
weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
weblogic.jms.adapter.JMSBaseConnection.closeInternal(JMSBaseConnection.java:570)
weblogic.jms.adapter.JMSBaseConnection.access$000(JMSBaseConnection.java:85)
weblogic.jms.adapter.JMSBaseConnection$2.run(JMSBaseConnection.java:552)

Hi Tom,
Thanks for looking at the issue.
I tried to post the full thread dump as an attachment, but it is not allowed by the forum, so you find it hereunder.
Regards,
metatech
=================
2010-05-28 12:33:19
Full thread dump Java HotSpot(TM) 64-Bit Server VM (14.2-b01 mixed mode):
"Attach Listener" daemon prio=3 tid=0x0000000100c5b800 nid=0x24 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"ExecuteThread: '0' for queue: 'JmsAsyncQueue'" daemon prio=3 tid=0x0000000100759800 nid=0x23 in Object.wait() [0xffffffff643ff000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:485)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
 - locked <0xffffffff6f4ed828> (a weblogic.kernel.ServerExecuteThread)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"Timer-0" daemon prio=3 tid=0x000000010078c800 nid=0x21 in Object.wait() [0xffffffff647ff000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 - waiting on <0xffffffff6f4ee2c0> (a java.util.TaskQueue)
 at java.lang.Object.wait(Object.java:485)
 at java.util.TimerThread.mainLoop(Timer.java:483)
 - locked <0xffffffff6f4ee2c0> (a java.util.TaskQueue)
 at java.util.TimerThread.run(Timer.java:462)
"weblogic.timers.TimerThread" daemon prio=3 tid=0x00000001008e0000 nid=0x20 in Object.wait() [0xffffffff649ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
 - locked <0xffffffff6f4e75d0> (a weblogic.timers.internal.TimerThread)
"ExecuteThread: '3' for queue: 'default'" daemon prio=3 tid=0x0000000100709000 nid=0x1e waiting for monitor entry [0xffffffff65afe000]
java.lang.Thread.State: BLOCKED (on object monitor)
 at weblogic.jms.client.JMSConnection.stateChangeListener(JMSConnection.java:1413)
 - waiting to lock <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
 at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:682)
 at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '2' for queue: 'default'" daemon prio=3 tid=0x000000010055c800 nid=0x1d in Object.wait() [0xffffffff65cff000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:485)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
 - locked <0xffffffff6f427a80> (a weblogic.kernel.ServerExecuteThread)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"ExecuteThread: '1' for queue: 'default'" daemon prio=3 tid=0x000000010055c000 nid=0x1c in Object.wait() [0xffffffff65eff000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:485)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
 - locked <0xffffffff6f427da0> (a weblogic.kernel.ServerExecuteThread)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"ExecuteThread: '0' for queue: 'default'" daemon prio=3 tid=0x00000001006fa800 nid=0x1b in Object.wait() [0xffffffff660ff000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:485)
 at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:91)
 - locked <0xffffffff6f4280c0> (a weblogic.kernel.ServerExecuteThread)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:115)
"StateHolder" daemon prio=3 tid=0x0000000100584800 nid=0x1a waiting on condition [0xffffffff66aff000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
 at java.lang.Thread.sleep(Native Method)
 at StateHolder.run(StateHolder.java:80)
 at java.lang.Thread.run(Thread.java:619)
"Thread-1" daemon prio=3 tid=0x0000000100554000 nid=0x18 waiting on condition [0xffffffff66cff000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
 at java.lang.Thread.sleep(Native Method)
 at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:104)
"Low Memory Detector" daemon prio=3 tid=0x00000001003d3800 nid=0x16 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"CompilerThread1" daemon prio=3 tid=0x00000001003cf000 nid=0x15 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"CompilerThread0" daemon prio=3 tid=0x00000001003cd800 nid=0x14 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Signal Dispatcher" daemon prio=3 tid=0x00000001003cb800 nid=0x13 runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Finalizer" daemon prio=3 tid=0x00000001003a4800 nid=0x12 in Object.wait() [0xffffffff680ff000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
 - locked <0xffffffff6f4c7670> (a java.lang.ref.ReferenceQueue$Lock)
 at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
 at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=3 tid=0x00000001003a3000 nid=0x11 in Object.wait() [0xffffffff682ff000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:485)
 at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
 - locked <0xffffffff6f401370> (a java.lang.ref.Reference$Lock)
"Worker" prio=3 tid=0x0000000100117800 nid=0x2 in Object.wait() [0xffffffff7befe000]
java.lang.Thread.State: WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:485)
 at weblogic.messaging.dispatcher.DispatcherWrapperState.triggerPeerGoneAndWait(DispatcherWrapperState.java:607)
 - locked <0xffffffff7509aee8> (a weblogic.messaging.dispatcher.DispatcherWrapperState)
 at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:349)
 at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
 at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:252)
 at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
 at weblogic.jms.client.JMSConnection.stop(JMSConnection.java:758)
 - locked <0xffffffff7509a640> (a weblogic.jms.client.JMSConnection)
 at weblogic.jms.client.WLConnectionImpl.stop(WLConnectionImpl.java:722)
 at ConnectorSession.closeJMSSession(ConnectorSession.java:499)
 at ConnectorSession.receiveRequest(ConnectorSession.java:617)
 at ConnectorSession.processRequest(ConnectorSession.java:341)
 at Worker.mainApplication(Worker.java:127)
 at Worker.mainMethod(Worker.java:298)
 at Worker.main(Worker.java:163)
"VM Thread" prio=3 tid=0x000000010039c800 nid=0x10 runnable
"GC task thread#0 (ParallelGC)" prio=3 tid=0x000000010011b000 nid=0x3 runnable
"GC task thread#1 (ParallelGC)" prio=3 tid=0x0000000100121000 nid=0x4 runnable
"GC task thread#2 (ParallelGC)" prio=3 tid=0x0000000100122800 nid=0x5 runnable
"GC task thread#3 (ParallelGC)" prio=3 tid=0x0000000100126000 nid=0x6 runnable
"GC task thread#4 (ParallelGC)" prio=3 tid=0x0000000100127800 nid=0x7 runnable
"GC task thread#5 (ParallelGC)" prio=3 tid=0x0000000100129000 nid=0x8 runnable
"GC task thread#6 (ParallelGC)" prio=3 tid=0x000000010012b000 nid=0x9 runnable
"GC task thread#7 (ParallelGC)" prio=3 tid=0x000000010012c800 nid=0xa runnable
"GC task thread#8 (ParallelGC)" prio=3 tid=0x000000010012e000 nid=0xb runnable
"GC task thread#9 (ParallelGC)" prio=3 tid=0x000000010012f800 nid=0xc runnable
"GC task thread#10 (ParallelGC)" prio=3 tid=0x0000000100131800 nid=0xd runnable
"GC task thread#11 (ParallelGC)" prio=3 tid=0x0000000100133000 nid=0xe runnable
"GC task thread#12 (ParallelGC)" prio=3 tid=0x0000000100134800 nid=0xf runnable
"VM Periodic Task Thread" prio=3 tid=0x00000001003d5800 nid=0x17 waiting on condition
JNI global references: 818

Initiate fails in BPEL Console for BPEL process connecting to JMS Adapter

We have a BPEL process picking up data from JMS Queue of TIBCO EMS server. When we try to run this process from BPEL Console Initiate tab, we get following error dump :
Oracle BPEL Process Manager Full Cycle
An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
Attachments:
Build Information:
Oracle BPEL Server version 10.1.3.1.0
Build: 0
Build time: Mon May 15 06:39:46 PDT 2006
Build type: release
Source tag: PCBPEL_SOABETA_GENERIC_060515.0600
Exception Message:
[javax.servlet.ServletException]
The system encounters errors while running as the authenticated identity.
Exception Trace:
javax.servlet.ServletException: The system encounters errors while running as the authenticated identity.
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:416)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:622)
     at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:161)
     at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:50)
     at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:98)
     at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
     at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:103)
     at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:395)
     at displayProcess.jspService(_displayProcess.java:857)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:590)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:514)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:392)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:406)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:622)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
     at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:260)
     at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:50)
     at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:194)
     at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:199)
     at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:131)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
     at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:392)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:406)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:620)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:869)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:449)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:233)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:847)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Also the BPEL process containing JMS adapter is not able to pick up data from JMS queue.
The same adapter was used in ESB service as well, which is working fine. There are no issues in ESB JMS Adapter connecting to JMS Queue of TIBCO EMS server.
Your help is appriciated.

Try the BPEL / SOA forum, you'll get more help there.
-steve-

Inbound JMS adapter with MapMessage

I'm sharing the following problem and solution with using the OEP inbound message adapter because it may be
a common situation occurring to other users.
Recently was using the inbound JMS adapter with its default (OEP internal) converter from JMS MapMessage
messages to OEP events. The inbound adapter was receiving MapMessage messages but it was not assigning
values to the corresponding attributes in the specified input event instance.
The problem was that I was not properly creating the MapMessage messages in the JMS producer client.
I was using method setStringProperty() instead of method setString(), which is what is needed to set name/value
pairs of type String, and similarly with other primitive Java data types. Here's a code snippet for building and sending
a MapMessage on the client side:
 try {
 mapm = qsess.createMapMessage();
 mapm.setString("valueType1", "value1");
 mapm.setString("valueType2", "value2");
 mapm.setInt("valueType3", 5);
 producer.send(mapm);
 } catch (JMSException jmse) {
 jmse.printStackTrace(System.err);
 System.exit(0);
Regards,
Mauricio

OSB JMS config:
<queue name="RequestQ">
<sub-deployment-name>wlsbJMSServer</sub-deployment-name>
<jndi-name>RequestQ</jndi-name>
</queue>
<queue name="ResponseQ">
<sub-deployment-name>wlsbJMSServer</sub-deployment-name>
<jndi-name>ResponseQ</jndi-name>
</queue>
Business service in OSB from where message is sent to the "ResponseQ" which is consumed by CEP.
Jms Inbound CEP Config:
<jms-adapter>
<name>jmsAdapterInbound</name>
<jndi-provider-url>t3://10.227.145.164:7005</jndi-provider-url>
<connection-jndi-name>weblogic.jms.XAConnectionFactory</connection-jndi-name>
<destination-jndi-name>ResponseQ</destination-jndi-name>
<user>weblogic</user>
<password>weblogic123</password>
<work-manager>JettyWorkManager</work-manager>
<concurrent-consumers>1</concurrent-consumers>
<session-transacted>false</session-transacted>
</jms-adapter>

JMS Adapter timeout property

How do I set timeout property for JMS adapter in BPEL in SOA Suite 10g ?
Scenario :
In one of the business scenarios, a JMS message in enqueued to WebLogic JMS queue from BPEL process.
There is a asyncronus invoke activity to the JMS adapter partner link.
This invoke activity to the JMS adapter took 15 mins in one of the invocations and hence giving timeout to the bpel client.
Query :
Is there any way I could set the timeout for this invocation, either at partner link level or a JMS adapter connection factory level.

Hi,
This is supposed to solve ERRJMS_PROVIDER_ERR error for JMS adapter.
Please refer metalink NOTE:393468.1.
I am not sure if it works for 10.1.2.0.2 version but probably it works on 10.1..3.X version.
Regards,
Ved

WebLogic JMS high memory usage and frequent full GCs

Hi Team,
            We have below set up in production (and all the lower environment).
1. WLS: 10.3.6 (64 bit)
2. Java: HP JDK 1.7.0.06 (64 bit)
3. Two Manage server instances in cluster with one Migratable target
4. one JMS server with Persistence store targeted to Migratable target
5. Messages are persisted in DB
6. about 37 distributed queues/topics are hosted on one JMS server
7. .Net JMS clients and WebLogic JMS clients connect to respective JMS distributed Queues/topics to either produce message or consume.
Since last month, we see that WebLogic Manage server hosting JMS server keeps on chewing memory "even with small (of the order of 28 messages in 4/5 days) load", GC indicates that objects are shifted from PSYoung space to ParOldGen during minor GCs but ParOldGen space keeps on filling up in smaller chunks. After x number of days (where x ranges from 5-7 days), even Full GC is not able to bring down memory significantly and that's when frequent full GCs start with long pauses making JMS highly unstable.
We don't have JMS Quotas configured but I think something else going on as it is not high on load. Any additional hints or troubleshooting steps is much appreciated?
Here is first and last GC log just to give an idea...
Heap after GC invocations=661 (full 0):
{Heap before GC invocations=1 (full 0):
PSYoungGen      total 1225728K, used 1050624K [9fffffff09c00000, 9fffffff5f400000, 9fffffff5f400000)
eden space 1050624K, 100% used [0x9fffffff09c00000,0x9fffffff49e00000,0x9fffffff49e00000)
from space 175104K, 0% used [0x9fffffff54900000,0x9fffffff54900000,0x9fffffff5f400000)
to   space 175104K, 0% used [0x9fffffff49e00000,0x9fffffff49e00000,0x9fffffff54900000)
ParOldGen       total 2797568K, used 0K [0x9ffffffe5f000000, 0x9fffffff09c00000, 0x9fffffff09c00000)
object space 2797568K, 0% used [0x9ffffffe5f000000,0x9ffffffe5f000000,0x9fffffff09c00000)
PSPermGen       total 49152K, used 47453K [0x9ffffffe1f000000, 0x9ffffffe22000000, 0x9ffffffe5f000000)
object space 49152K, 96% used [0x9ffffffe1f000000,0x9ffffffe21e57630,0x9ffffffe22000000)
2014-12-24T09:04:45.118-0700: 15.651: [GC [PSYoungGen: 1050624K->118221K(1225728K)] 1050624K->118293K(4023296K), 0.32600
15 secs] [Times: user=0.07 sys=0.00, real=0.33 secs]
{Heap before GC invocations=661 (full 0):
PSYoungGen      total 1367168K, used 1364256K [9fffffff09c00000, 9fffffff5f400000, 9fffffff5f400000)
eden space 1333376K, 100% used [0x9fffffff09c00000,0x9fffffff5b220000,0x9fffffff5b220000)
from space 33792K, 91% used [0x9fffffff5d300000,0x9fffffff5f128030,0x9fffffff5f400000)
to   space 33664K, 0% used [0x9fffffff5b220000,0x9fffffff5b220000,0x9fffffff5d300000)
ParOldGen       total 2797568K, used 2654825K [0x9ffffffe5f000000, 0x9fffffff09c00000, 0x9fffffff09c00000)
object space 2797568K, 94% used [0x9ffffffe5f000000,0x9fffffff0109a5c0,0x9fffffff09c00000)
PSPermGen       total 151552K, used 147591K [0x9ffffffe1f000000, 0x9ffffffe28400000, 0x9ffffffe5f000000)
object space 151552K, 97% used [0x9ffffffe1f000000,0x9ffffffe28021cd8,0x9ffffffe28400000)
2014-12-29T08:18:08.798-0700: 429216.418: [GC [PSYoungGen: 1364256K->33632K(1329792K)] 4019081K->2752791K(4127360K), 0.8
254362 secs] [Times: user=0.10 sys=0.00, real=0.83 secs]
Regards,

Thanks Luz. I have been collecting gclogs and heap dumps (whenever app server is high on memory and frequent GCs with long pauses are seen). So far heap dumps haven't revealed anything specific (may be I am not able to read heap dumps properly ) but looking at GC confirms that app server is consuming allocated heap.I was following Oracle WebLogic server support Patter as you have indicated. I thought about opening a ticket with HP but on high level JVM is doing what is suppose to do i.e allocating memory space as needed and performing GC therefore didn't go that path.
Any other suggestions that might be useful. One of the things I forgot to mention ( and I will add it to original message), that one of the .Net consumers is not asynchronously connecting to its queue (to consume messages) rather it is synchronously connects and then if it doesn't find messages it disconnects and process goes on every few seconds. I was reading somewhere that frequent JNDI look ups should be avoided. Can this cause memory issue if so then it is strange as this same set up has been there over a year and we never has problem then?
Regards,

Problem with JMS Adapter after upgrade to 7.1

Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PM

does following JAR files in place in aii_af_jmsproviderlib.sda.
●      com.ibm.mq.jar
●      com.ibm.mqbind.jar
●      com.ibm.mqjms.jar
●      connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag

XI JMS adapter after JMS provider reboot

Hi All,
I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.
After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.
In JMS adapter we have folloving settings and we are connected straight into queue:
Transport Protocol = SonicMQ JMS Provider
General JMS Settings:
Transactional JMS Session is in use
Delivery Mode of Message Producer = Persist JMS messages..
+ Queue user & pw
Error Handling Settings:
Wait After Message Error(msecs) = 60000
Wait Before Reconnect(msecs) = 60000
Does anyone ran into this earlier?
Thanks in advance.
-Kimmo

Hi Saravana,
It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory
It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.
We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.
We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.

Problem testing JMS adapter

I have create and configure JMS resource but still i am getting this exception
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'sendMessage' failed due to: ERRJMS_ERR_CR_QUEUE_PROD. ERRJMS_ERR_CR_QUEUE_PROD. Unable to create Queue producer due to JMSException. Please examine the log file to determine the problem. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Fault
BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'sendMessage' failed due to: ERRJMS_ERR_CR_QUEUE_PROD. ERRJMS_ERR_CR_QUEUE_PROD. Unable to create Queue producer due to JMSException. Please examine the log file to determine the problem. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Kindly help

This is how I configured
Configure the JMS Queue Resource (Jndi name=>>> jms/demoMsgQueue)
Configured the JMS Connection Factory Resource
configured the demoCF JMS connection factory
Created a JMS Adapter Connection Pool
Associate the Connection Pool with the Connection Factory
Redeployed the JMS Adapter with the New Resources
How I can do bouning app server?

PI unable to connect via JMS adapter to Weblogic

Hello All,
We have implemented JMS adapter on PI 7.11 for the first time in our landscape which connects to Weblogic server. When i test my scenario i get this Error on JMS Communication Channel. Could some one help me out .. where things are going wrong?
Am using Transport protocol as : Access JMS Provider with JNDI
CASE 1 :
284272 A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with
environment: {java.naming.provider.url=t3s://usdatlpc64m----
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427250 having object id: 035dd91446303f17bf0e7ad9a4dbd564: RuntimeException: Exception occurred while reading the license file. at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65) ...
CASE2:
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=----
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427251 having object id: 035dd91446303f17bf0e7ad9a4dbd564: javax.naming.NamingException: String index out of range: -1 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65) ...

Hi ,
Were you able to resolve the issue?
We are facing similar issue when trying to integrate (SOAP over JMS) with WebSphere 7.x server to read JMS messages. We are using SAP PI 7.1 version and after providing the JNDI connection factory as "com.ibm.websphere.naming.WsnInitialContextFactory".....the error returned is :
======
Channel error occurred. Detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=iiop://10.60.5.115:2809, java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory, java.naming.security.principal=admin, java.naming.security.credentials=admin}for profile: ConnectionProfile of channel: JMSSender_MESon node: 8649950 having object id: a8c808c859f33b40a41d0ced2088fb18: javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65) ...
=====
Thanks in Advance
-Naveen

PI 7.11 JMS adapter using JNDI weblogic server issue

Hi SAP experts,
I have a scenario to integrate to a application using JMS adapters. we use SAP PI 7.11 version.
We have deployed JMS drivers successfully and We face issue here to connect to weblogic server
We are using JMS adapter using JNDI to connect to weblogic server version 10.3.
Can anyone help with the exact format to be used in JMS properties table and additional parameters table in JMS communication channel. Your quick help will be appreciated.
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up destination: AccrualDetailsQueue for profile: ConnectionProfile of channel: CC_SND_JMS on node: 3010950 having object id: 673696a9fe8c39fdab32213f0930afb3: javax.naming.NameNotFoundException: Unable to resolve 'AccrualDetailsQueue'. Resolved '' at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination(JndiConnectorImpl.java:168)<br

Hi Padmini,
Refer to the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
It was very helpful to me, for configuring the additional parameters in the communication Channel JMS.
I leave you some screenshots of the settings that I did.
I seize the opportunity to ask you, where do I can get the drivers (.Jar) for Weblogic?
Regards.
Rodrigo.

PI 7.1: Weblogic (JMS adapter) - Connectivity & MONITORING!!

Similar Messages

Maybe you are looking for