Monitoring the jms connection - normal behaviour

Hi all,
-> We have a SNMP agent on a managed server and is targeted to the same.
-> We have not created any gauge monitor,String monitor or counter monitor, its all blank.
Question:
Considering the above setup, If there is a new jms connection should SNMP call the jmx to get the reference of the jms connection.??
Is this the normal behaviour of weblogic with no monitor attributes specified?
/SR

Enable the JMX on domain by adding below JVM Options to domain.xml, then from the JDK/bin use JConsole, this very light weight and gives all the info of JVM.
-Dcom.sun.management.jmxremote - this will allow the IS to use the same MBeanServer as the VM instead of starting a new one
-Dcom.sun.management.jmxremote.port=18010 - the port the MBeanServer listens on
-Dcom.sun.management.jmxremote.authenticate=false - no security
-Dcom.sun.management.jmxremote.ssl=false - no SSL either
Raghu

Similar Messages

HOw to test the jms connection?

HI all,
how to test the jms connection in xi?
regards
kish

HI,
We can see the JMS sender or reciver side .. in RWB .. see communicaiton channel mononitoring,., also..
We can access it through browser.. it depends upon the proocol type .. like sonic or webspeare MQ..or ...
see below links
http://help.sap.com/saphelp_nw04/helpdata/en/cf/886a3c3a860657e10000000a114084/frameset.htm
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
content conversion https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/97171dd3-0401-0010-5195-b43f556e6ce9
Chilla

Error in looking up the JMS Connection Factory

 Hi,
 I am using weblogic6.1. I created a JMS Connection factory from administrator
 console with the name QueueConnectionFactory..But when i restart the server and
 try to look up that factory its giving an NameNotFoundException...This is the
 entry of the factory in config.xml
 <JMSConnectionFactory JNDIName="QueueConnectionFactory"
 Name="QueueConnectionFactory" Targets="myserver"/>
 But if i change reapply the target server to myserver from admin console whenever
 restart the server it works fine..
 I dont know where is the problem..Can u please update me on the problem if u people
 have any idea.
 The trace of the exceptions i got is as below:
 java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to
 resolve QueueConnectionFactory. Resolved
 : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
 java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to resolve
 QueueConnectionFactory. Resolved: '' Unr
 esolved:'QueueConnectionFactory' ; remaining name ''
 Thanx
 Regards,
 Narayan


 Hi Zach,
 No, I dont think ur interpretation is right..Once the entry corresponding
 to JMS Connection Factory is there in config.xml, the server should automatically
 bind it at the time of booting.. right. Why should this administrator server come
 into the picture.
 Thanx
 "Zach" <[email protected]> wrote:
 >Don't know. Sounds like the admin server is not notifying JMS of the
 >changes under certain situations. You might post in the management.console
 >newsgroup.
 >
 >_sjz.
 >
 >"Narayan" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Hi,
 >> I am using weblogic6.1. I created a JMS Connection factory from
 >administrator
 >> console with the name QueueConnectionFactory..But when i restart the
 >server and
 >> try to look up that factory its giving an NameNotFoundException...This
 >is
 >the
 >> entry of the factory in config.xml
 >>
 >> <JMSConnectionFactory JNDIName="QueueConnectionFactory"
 >> Name="QueueConnectionFactory" Targets="myserver"/>
 >> But if i change reapply the target server to myserver from admin console
 >whenever
 >> restart the server it works fine..
 >> I dont know where is the problem..Can u please update me on the problem
 >if
 >u people
 >> have any idea.
 >> The trace of the exceptions i got is as below:
 >> ****************
 >> java.rmi.RemoteException: javax.naming.NameNotFoundException:
 >Unable to
 >> resolve QueueConnectionFactory. Resolved
 >> : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
 >> java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable
 >to
 >resolve
 >> QueueConnectionFactory. Resolved: '' Unr
 >> esolved:'QueueConnectionFactory' ; remaining name ''
 >>
 >> **********************
 >>
 >> Thanx
 >> Regards,
 >> Narayan
 >>
 >>
 >
 >

Why do JMS connections stay connected after Flex clients close?

Hello,
I am using AMF_Polling and the JMS Adapter to receive discardable messages on a topic from Fiorano JMS. It works very well except for one thing. When the Flex client goes away because the browser closed, the JMS connection to FIorano is still there. It seems to stay there for a very long time and may never timeout and go away.
Questions:
1. Is this normal behavior for the JMS adapter?
2. Is there a way to force these unused connections to close between the JMS server and the Flex JMS adapter?
3. Is the JMS adapter continuing to receive messages after the Flex client goes away?
4. If so, are messages stacking up in memory which will eventually fill up and cause problems?
Thanks,
Chris Shafer, George Weiss Associates

To answer the question about the forwarding of messages from one queue to another myself: As mentioned at http://forums.bea.com/thread.jspa?threadID=400000611, the forwarding for queues does only work if all queue consumers are attached to the same queue. This means that our setup is OK.
But the main question is still unanswered: why do the number of active JMS connections increase? I forgot to mention that
- all messages arrive at the clients and that no exceptions are visible in the log
- if you kill the client, the connections are still visible in the Weblogic console!?
Please help as this problem is very urgent.
Peter
Edited by: pkeller on 24.10.2008 09:06
Edited by: pkeller on 24.10.2008 09:10

Getting the below error while using the JMS server.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

Maximum JMS Connections

 Hi,
 I would like to know what is the maximum JMS connections weblogic server can
 handle anytime. And where do we set this parameter? we have a group of Message
 Listeners listening to a Queue on weblogic by opening JMS connections at the same
 time. So I was wondering how many JMS clients can Weblogic handle?? And also does
 it impact the performance of weblgic server.
 Thanx,
 Sankas


 Thanks for the information guys. It was very helful.
 -Sankas
 Tom Barnes <[email protected]> wrote:
 >Each remote JVM to the WL server multiplexes network calls over a single
 >socket
 >connection, and each remote JVM may have many JMSConnections into the
 >WL server. A
 >single server can support thousands of remote JVMs, and tens of thousands
 >of
 >JMSConnections -- even with the default thread-pool sizes. Clustering
 >and
 >distributed destinations can help one scale higher. Of course, performance
 >and
 >scalability are highly application and hardware dependent, and the best
 >thing to do
 >is create a benchmark that emulates your particular apps characteristics
 >and see
 >how it scales...
 >
 >Tom, BEA
 >
 >Sankas wrote:
 >
 >> Shean,
 >> I did not have anything in mind. But if you see the weblogic console
 >there
 >> is a default parameter "JMS Thread Pool Size = 15" under the Server
 >section in
 >> the services/JMS Tab .
 >> I thought this was the JMSConnections count in the server.
 >> Well I think it would be good to know how far can we go
 >> with the JMS connections thing.
 >>
 >> Thanx,
 >> Sankas
 >>
 >> "Shean-Guang Chang" <[email protected]> wrote:
 >> > It will depend on the memory resource you used for the JVM (both
 >WLS
 >> >server
 >> >and client). There is no design limit for this. Do you have a number
 >> >in
 >> >mind?
 >> >"Sankas" <[email protected]> wrote in message
 >> >news:[email protected]...
 >> >>
 >> >> Hi,
 >> >> I would like to know what is the maximum JMS connections weblogic
 >> >server can
 >> >> handle anytime. And where do we set this parameter? we have a group
 >> >of
 >> >Message
 >> >> Listeners listening to a Queue on weblogic by opening JMS connections
 >> >at
 >> >the same
 >> >> time. So I was wondering how many JMS clients can Weblogic handle??
 >> >And
 >> >also does
 >> >> it impact the performance of weblgic server.
 >> >>
 >> >> Thanx,
 >> >> Sankas
 >> >
 >> >
 >

Getting error to access the JMS resouce.

I have confabulated 4 managed servers (des1, des2,des3 and des4) with JMS servers in a cluster on WebLogic 9.2. The servers des1 and des2 are located on same host of admin server installed(e.g. the hostname is adminhost). The servers des3 and des4 are located on anther host (remotehost). I have confabulated the JMS Connection Factory and Uniform Distributed Topic and target them to the cluster by using a subdeployment. I started the admin server on adminhost:7001.
I set the JMS provider URL to t3://adminhost:5010,adminhost:5020,remotehost:5010,remotehost:5020 in my java code to look up my JMS topic.
I can get the JMS topic from the adminhost's servers (des1 and des2). But on the remote host, if I don't start adminhost:5010, the server will get got error when try to get the JMS topic.
javax.naming.NameNotFoundException: While trying to lookup 'peoplesoft.crm.omk.jms.omkBroadcastTopic'
didn't find subcontext 'peoplesoft'. Resolved ''; remaining name 'peoplesoft/crm/omk/jms/omkBroadcastTopic'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
The remote server will only can get the JMS topic when the adminhost:5010 is up and running, which is the first one listed in the JMS provider URL.
Can any one give me the idea that:
Q1: Why only the admin server's managed servers can access the JMS topic?(because the des2 does not rely on if the server on adminhost:5010 running).
Is there any way I can make it work on remote host?
Q2: Why only the first server is recognized in the JMS provider URL?
Q3: Why the JSM provider is singleton fail point?
Thank you in advance!
Lucy
Edited by: user710140 on Feb 20, 2009 3:27 PM

Here are my config.xml and jms.xml. Thank you for help!
config.xml
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml http://www.bea.com/ns/weblogic/90/security/xacml.xsd http://www.bea.com/ns/weblogic/90/security http://www.bea.com/ns/weblogic/90/security.xsd http://www.bea.com/ns/weblogic/920/domain http://www.bea.com/ns/weblogic/920/domain.xsd http://www.bea.com/ns/weblogic/90/security/wls http://www.bea.com/ns/weblogic/90/security/wls.xsd">
<name>omk</name>
<domain-version>9.2.0.0</domain-version>
<security-configuration>
<name>omk</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{3DES}DCrNeNp+kXrDhSu/xl1jSPlzzeCAUak9MRuA+ZvX8Ih/gYhSJAhEXNBeX92iiOAFcusvheIQMuMPAtQfFmG7UOSiq8Rm3q8s</credential-encrypted>
<node-manager-username>system</node-manager-username>
<node-manager-password-encrypted>{3DES}sDP3fr4NSp2l89H2BtwOoA==</node-manager-password-encrypted>
</security-configuration>
<server>
<name>crm9</name>
<ssl>
<name>crm9</name>
<enabled>true</enabled>
<hostname-verification-ignored>true</hostname-verification-ignored>
<listen-port>444</listen-port>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<server-private-key-alias>rfas010</server-private-key-alias>
<identity-and-trust-locations>KeyStores</identity-and-trust-locations>
</ssl>
<log>
<name>crm9</name>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<execute-queue>
<name>weblogic.kernel.Default</name>
<thread-count>50</thread-count>
</execute-queue>
<listen-port>7001</listen-port>
<web-server>
<name>crm9</name>
<web-server-log>
<name>crm9</name>
<file-name>./logs/PIA_access.log</file-name>
<logging-enabled>false</logging-enabled>
</web-server-log>
<https-keep-alive-secs>120</https-keep-alive-secs>
</web-server>
<iiop-enabled>false</iiop-enabled>
<listen-address></listen-address>
<staging-directory-name>./stage</staging-directory-name>
<upload-directory-name>./upload</upload-directory-name>
<staging-mode>nostage</staging-mode>
<graceful-shutdown-timeout>30</graceful-shutdown-timeout>
<msi-file-replication-enabled>true</msi-file-replication-enabled>
<custom-identity-key-store-file-name>keystore/pskey</custom-identity-key-store-file-name>
<custom-identity-key-store-type>JKS</custom-identity-key-store-type>
<custom-trust-key-store-file-name>keystore/pskey</custom-trust-key-store-file-name>
<custom-trust-key-store-type>JKS</custom-trust-key-store-type>
</server>
<server>
<name>proxyServer</name>
<ssl>
<enabled>false</enabled>
<listen-port>5011</listen-port>
</ssl>
<machine>rhas001</machine>
<listen-port>5010</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.120.154</listen-address>
</server>
<server>
<name>des1</name>
<ssl>
<enabled>false</enabled>
<listen-port>5011</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rfas010</machine>
<listen-port>5010</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.121.100</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des1</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>des2</name>
<ssl>
<enabled>false</enabled>
<listen-port>5021</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rfas010</machine>
<listen-port>5020</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.121.100</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des2</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>des3</name>
<ssl>
<enabled>false</enabled>
<listen-port>5011</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rtas043</machine>
<listen-port>5010</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.123.106</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des3</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>des4</name>
<ssl>
<enabled>false</enabled>
<listen-port>5021</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rtas043</machine>
<listen-port>5020</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.123.106</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des4</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<cluster>
<name>PsftOmkCluster</name>
<multicast-address>239.192.0.0</multicast-address>
<multicast-port>7009</multicast-port>
<multicast-ttl>2</multicast-ttl>
<number-of-servers-in-cluster-address>4</number-of-servers-in-cluster-address>
</cluster>
<embedded-ldap>
<name>omk</name>
<credential-encrypted>{3DES}6Sr2wTwijurtQum4aELROj7jVGCnAucX5/41CQo4NNw=</credential-encrypted>
</embedded-ldap>
<configuration-version>9.2.0.0</configuration-version>
<app-deployment>
<name>crm9</name>
<target>PsftOmkCluster</target>
<module-type>ear</module-type>
<source-path>applications/crm9</source-path>
<sub-deployment>
<name>/DCS</name>
<target>PsftOmkCluster</target>
</sub-deployment>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>proxyServer</name>
<target>proxyServer</target>
<module-type>war</module-type>
<source-path>C:\Temp\wlst\proxyApp.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlnav</name>
<target>crm9</target>
<module-type>war</module-type>
<source-path>D:\lucy\wlnav.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<machine>
<name>rhas001</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>rhas001.us.oracle.com</listen-address>
<listen-port>5556</listen-port>
</node-manager>
</machine>
<machine>
<name>rfas010</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>rfas010.us.oracle.com</listen-address>
<listen-port>5556</listen-port>
</node-manager>
</machine>
<machine>
<name>rtas043</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>rtas043.us.oracle.com</listen-address>
<listen-port>5556</listen-port>
</node-manager>
</machine>
<jms-server>
<name>PsftOmkJMSServer1</name>
<target>des1</target>
</jms-server>
<jms-server>
<name>PsftOmkJMSServer2</name>
<target>des2</target>
</jms-server>
<jms-server>
<name>PsftOmkJMSServer3</name>
<target>des3</target>
</jms-server>
<jms-server>
<name>PsftOmkJMSServer4</name>
<target>des4</target>
</jms-server>
<migratable-target>
<name>des1 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des1</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<migratable-target>
<name>des2 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des2</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<migratable-target>
<name>des3 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des3</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<migratable-target>
<name>des4 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des4</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<jms-system-resource>
<name>PsftOmkJMSModule</name>
<target>PsftOmkCluster</target>
<sub-deployment>
<name>PsftOmkClusterSubdeployment</name>
<target>PsftOmkCluster</target>
</sub-deployment>
<descriptor-file-name>jms/psftomkjmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>crm9</admin-server-name>
</domain>
jms
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<connection-factory name="omkBroadcaster">
<sub-deployment-name>PsftOmkClusterSubdeployment</sub-deployment-name>
<jndi-name>jms.connection.omkConFactory</jndi-name>
<load-balancing-params>
<server-affinity-enabled>false</server-affinity-enabled>
</load-balancing-params>
</connection-factory>
<uniform-distributed-topic name="omkBroadcastTopic">
<sub-deployment-name>PsftOmkClusterSubdeployment</sub-deployment-name>
<jndi-name>peoplesoft.crm.omk.jms.omkBroadcastTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
</weblogic-jms>
Edited by: user710140 on Feb 23, 2009 8:54 AM

Error in looking up JMS connection factory in cluster

          Hi,
          We have setup a JMS connection factory targeted to clustered servers. We currently
          have two physical servers defined in the cluster.
          When the clustered servers first comes up, we can't see the JMS connection factory
          in the JNDI tree of any of the clustered servers. We can see in the server log
          that factory is actually being started. Binding to the JNDI tree is not happening.
          Through Management console when we move the target of connection factory back
          and forth, then the problem is gone.
          Any pointers to the problem are welcome.
          P.S. We are using WL 7.0.1
          Thanks
          Nishchit


          Hi,
          We have setup a JMS connection factory targeted to clustered servers. We currently
          have two physical servers defined in the cluster.
          When the clustered servers first comes up, we can't see the JMS connection factory
          in the JNDI tree of any of the clustered servers. We can see in the server log
          that factory is actually being started. Binding to the JNDI tree is not happening.
          Through Management console when we move the target of connection factory back
          and forth, then the problem is gone.
          Any pointers to the problem are welcome.
          P.S. We are using WL 7.0.1
          Thanks
          Nishchit

Cannot create more JMS connection

Hi,
I got the following error:
WARNING: RAR5117 : Failed to obtain/create connection from connection pool [ jms/batchExecutorMDBConnectionFactoryPool ]. Reason : com.sun.appserv.connectors.internal.api.PoolingException: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.I have cleared all messages in the queue, redeployed my application. But somehow the connections still existed in the connection pool and therefore i always see this error appearing whenever i re-launch my application.
I created JMS connection locally and close it immediately after sending message as suggested out there to avoid connection leaking.
Could you help me how to clear all connections in order to re-run my application. Then slowly i can find out where the connection leaking is?
I am using glassfish 3.1.2 with the setting 500 maximum connection in the jms connection factory
thanks,
-CM

CardM wrote:
Could you help me how to clear all connections in order to re-run my application. Then slowly i can find out where the connection leaking is?
I am using glassfish 3.1.2 with the setting 500 maximum connection in the jms connection factoryErrr, reboot the server?
Glassfish questions should go in the glassfish forum: http://www.java.net/forums/glassfish/glassfish

Monitor Secondary DB connection in SOLMAN

Hi
We have a requirement for monitoring the secondary DB connection to HANA system .
Is it possible to monitor the DB connection in solution manager ? If so , please let me know the steps and procedure .
Regards
Bala

Dear Bala,
You can monitor DBA Cockpit connection.
With best regards,
Alexander

How to find if I have lost my jms connection?

Is there a way to find if my client has lost its connection to the JMS service?

believe only approach is optimistic: expect success,
react on fail
try/catch for JMSException: send() producer-side,
receive() consumer-side
on exception: retry by close() Connection/Session,
recreate Connection/Session, and reattempt actionYes. Plus: set an ExceptionListener at the JMS connection and act properly when onException is called. The ExceptionListener is the hook where JMS providers usually report a connection lost.
-- Andreas

Why do the number of active JMS connections increase?

Problem
- Number of active JMS connections and current JMS messages increases until the Weblogic instances crash with an OutOfMemory exception
Setup
- Weblogic v9.2.3, Cluster with 4 Nodes
- A JMS Message is sent from a MDB in Weblogic to a distributed queue which has a member on each of the 4 Weblogic nodes. The session is created as follows session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE), the message delivery mode is set programmatically to persistent and the delivery mode override of the queue setup is set to persistent too
- Standalone JMS client processes: each one is attached to all 4 nodes. Each one uses a unique JMS message selector so that we have more than one queue consumer for one queue but every message is exactly dedicated to one queue consumer. We us weblogic.jar for the clients.
- Use of Weblogic auto reconnect feature. JMS client code:
Connection connection = this.connectionFactory.createQueueConnection();
final WLConnection wlconnection = (WLConnection)connection;
wlconnection.setReconnectPolicy(JMSConstants.RECONNECT_POLICY_ALL);
wlconnection.setTotalReconnectPeriodMillis(-1);
wlconnection.setReconnectBlockingMillis(-1);
Remarks and Questions
- There are no pending JMS messages which is good
- In our setup, each JMS client is connected to all 4 nodes as the messages are not distributed to all nodes: if a message is put to Queue A but the client is only connected to Queue B, the message is NOT transfered from Queue A to Queue B. We set the parameter "Forward Delay" to 5 seconds with no effects. Is this the normal behavior?
- Not all JMS clients are visible in the Weblogic console under JMS Services -> JMS Servers -> [Server] -> Monitoring -> Active Connections. Which one are visible? Which one are not visible? There are also clients where the number of connections is not zero but stays constant; we know that as several independent clients on different hosts are started and the IP adress is visible in the Weblogic console. Why....?
- What reasons can lead to increasing connections? Is this due to client or server problems? Do we have to acknowledge the message in the onMessage(Message) method of the client JMS consumer? So far as I know, we don't have to.
- Are the increasing number of current messages due to the increasing number of JMS connections?
- May the RECONNECT_POLICY_ALL policy produce this problem?
Any hint is appreciated.
Peter
Edited by: pkeller on 23.10.2008 17:08

To answer the question about the forwarding of messages from one queue to another myself: As mentioned at http://forums.bea.com/thread.jspa?threadID=400000611, the forwarding for queues does only work if all queue consumers are attached to the same queue. This means that our setup is OK.
But the main question is still unanswered: why do the number of active JMS connections increase? I forgot to mention that
- all messages arrive at the clients and that no exceptions are visible in the log
- if you kill the client, the connections are still visible in the Weblogic console!?
Please help as this problem is very urgent.
Peter
Edited by: pkeller on 24.10.2008 09:06
Edited by: pkeller on 24.10.2008 09:10

Iphone 5 is taking too long to download through EDGE why????????Please help i just wnat to confirm that it is the normal behaviour or it is some kind of problem please help

iphone 5 16 gn black my iphone is taking too long to download apps from apps to download on my iphone so please help from overcoming this problem
i just want to know this is the normal behaviour or it is some kind of problem

You have to turn on 3G/4G/LTE and be in a coverage area for such to happen.
Or connect to wifi.
Normal behavior for Edge is very very slow.

My MBP Retina doesn't allow the use of two Thunderbolt to DVI adapters. It only works with one TB - VGA adapter and one TB - DVI adapter. However now the color on the VGA connected monitor is slightly different.

The monitors are Viewsonic VA2406m-LED. The Display preferences show all three monitors but one monitor always says "No Signal" if they are both connected TB -> DVI.
The Color on the VGA connected one is slighly off. It seems like I should be able to connect two DVI monitors not sure why this is stopped. Does it have something to do with the Graphics card?

The problem was with the newEgg adapter. I just went to the Apple Store and bought an Apple adapter and the monitor now displays correctly.
For future reference, in case anyone experiences this problem:
the newEgg adapter is part number 9SIA1PU0P88920, described as a Thunderbolt Mini Displayporrt Display Port DP to DVI Adapter for APPLE Macbook Pro Air and the full description says it works for macbook pro, etc.
when this adapter is used, the macbook pro recognizes the monitor, but the monitor displays nothing.
When the apple adapter (MB507Z/B Mini Display Port to DVI Adapater) is used, the monitor displays correctly.
Of course, the individual newEgg part might simply be defective, but I doubt it. moral -- spend the extra $$ and buy the Apple adapter.

Weblogic Server 9.2 Crashes when using the JMS Wrapped Connection Pooling.

===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 01:05:05 on Thu Sep 16 18:27:36 2010
Additional information is available in:
E:\obopay\servers\EWP_9.2_Domain\jrockit.4516.dump
E:\obopay\servers\EWP_9.2_Domain\jrockit.4516.mdmp
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error Message: Illegal memory access. [54]
Exception Rec: EXCEPTION_ACCESS_VIOLATION (c0000005) at 0x0095065F - memory at 0x00740060 could not be read.
Minidump : Wrote mdmp. Size is 567MB
SafeDllMode : -1
Version : BEA JRockit(R) R27.2.0-131-78843-1.5.0_10-20070320-1457-windows-ia32
GC Mode : Garbage collection optimized for throughput
GC Strategy : Generational Parallel Mark & Sweep
: Current OC phase is: not running. YC is not running.
: GC strategy for GC 36 was genparpar
: GC strategy for GC 37 was genparpar
: GC strategy for GC 38 was genparpar
: GC strategy for GC 39 was genparpar
: GC strategy for GC 40 was genparpar
: mmHeap->data = 0x00C00000, mmHeap->top = 0x10C00000
: The nurserylist starts at 0x01BE75E8 and ends at 0x0CB52440
: mmStartCompaction = 0x00C00000, mmEndCompaction = 0x01C00000
: References are 32-bit.
CPU : Intel Pentium III/Pentium III Xeon SSE SSE2 SSE3 SSSE3 EM64T
Number CPUs : 2
Tot Phys Mem : 3451408384 (3291 MB)
OS version : Microsoft Windows XP version 5.1 Service Pack 3 (Build 2600) (32-bit)
Thread System: Windows Threads
State : JVM is running
Command Line : -Djava.library.path=E:\bea\jrockit90_150_10\bin;E:\bea\jrockit90_150_10\jre\bin;E:\bea\weblogic92\server\native\win\32;E:\bea\weblogic92\server\bin;E:\bea\weblogic92\server\native\win\32\oci920_8 -Dweblogic.management.discover=false -Dplatform.home=E:\bea\weblogic92 -Dwls.home=E:\bea\weblogic92\server -Dwli.home=E:\bea\weblogic92\integration -Dweblogic.Name=myserver -Dweblogic.management.username=weblogic -Dweblogic.management.password=weblogic -Dweblogic.ext.dirs=E:\bea\patch_weblogic901\profiles\default\sys_manifest_classpath\weblogic_patch.jar Djava.security.auth.login.config=E://workspace/Bhopal/LoginModulesConfig/ewp_loginmodules.config -Djava.naming.factory.initial.ewp.remote=weblogic.jndi.WLInitialContextFactory -Dcom.ewp.proxy.is_remote=false -Djava.naming.provider.url.ewp.remote=t3://localhost:7001 -Dweblogic.webservice.verbose=true -Dweblogic.log.Log4jLoggingEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true Xdebug -Xnoagent -Dcom.sun.management.jmxremote -Xms256m -Xmx1024m -Dsun.java.launcher=SUN_STANDARD weblogic.Server
java.home : E:\bea\jrockit90_150_10\jre
JAVA_HOME : <not set>
JAVAOPTIONS: <not set>
PATH : E:\bea\jrockit90_150_10\jre\bin;E:\oracle\product\10.2.0\client_1\bin;C:\Program Files\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\TortoiseSVN\bin
C Heap : Good; no memory allocations have failed
StackOverFlow: 0 StackOverFlowErrors have occured
OutOfMemory : 0 OutOfMemoryErrors have occured
Registers (from ThreadContext: 0x4B29E378 / OS context: 0x4B29E764):
eax = 00740060 ecx = 00740060 edx = 45a45ba0 ebx = 08c953b8
esp = 4b29ea30 ebp = 00000000 esi = 4b29ea60 edi = 4b29efb4
es = 00000023 cs = 0000001b ss = 00000023 ds = 00000023
fs = 0000003b gs = 00000000
eip = 0095065f eflags = 00010206
Stack:
(* marks the word pointed to by the stack pointer)
4b29ea30: 00981099* 08c953b8 008ab310 4b29eb34 09e5c308 009810ea
4b29ea48: 4b29ead8 0098ecd2 4b29ea60 4b29ea90 48bd8960 48bd8960
4b29ea60: 00000001 45aa0278 45a45ba0 00000007 00000000 08c953b8
4b29ea78: 08512180 4b29ef60 00000000 09d56368 09d563b0 4b29efb4
Code:
(* marks the word pointed to by the instruction pointer)
0095062c: 5e5f0cc4 c35bc033 01b85e5f 5b000000 ccccccc3 0424448b
00950644: a5f06ca3 ccccc300 cccccccc 04244c8b 01a8018b e0830774
0095065c: 8bc88bfe* 40788301 44408b03 af0f0a75 c0830841 f8e08317
00950674: ccccccc3 cccccccc cccccccc 0424448b 00f4888b 158b0000
Loaded modules:
(* denotes the module causing the exception)
00400000-0040ffff E:\bea\jrockit90_150_10\bin\javaw.exe
7c900000-7c9b1fff C:\WINDOWS\system32\ntdll.dll
7c800000-7c8f5fff C:\WINDOWS\system32\kernel32.dll
7e410000-7e4a0fff C:\WINDOWS\system32\USER32.dll
77f10000-77f58fff C:\WINDOWS\system32\GDI32.dll
77dd0000-77e6afff C:\WINDOWS\system32\ADVAPI32.dll
77e70000-77f02fff C:\WINDOWS\system32\RPCRT4.dll
77fe0000-77ff0fff C:\WINDOWS\system32\Secur32.dll
77c10000-77c67fff C:\WINDOWS\system32\MSVCRT.dll
76390000-763acfff C:\WINDOWS\system32\IMM32.DLL
00820000-00a9cfff *E:\bea\jrockit90_150_10\jre\bin\jrockit\jvm.dll
76b40000-76b6cfff C:\WINDOWS\system32\WINMM.dll
71ab0000-71ac6fff C:\WINDOWS\system32\WS2_32.dll
71aa0000-71aa7fff C:\WINDOWS\system32\WS2HELP.dll
7c340000-7c395fff E:\bea\jrockit90_150_10\bin\MSVCR71.dll
5dac0000-5dac7fff C:\WINDOWS\system32\rdpsnd.dll
76360000-7636ffff C:\WINDOWS\system32\WINSTA.dll
5b860000-5b8b4fff C:\WINDOWS\system32\NETAPI32.dll
76bf0000-76bfafff C:\WINDOWS\system32\PSAPI.DLL
6d700000-6d70bfff E:\bea\jrockit90_150_10\jre\bin\verify.dll
6d370000-6d38cfff E:\bea\jrockit90_150_10\jre\bin\java.dll
6d2f0000-6d2f7fff E:\bea\jrockit90_150_10\jre\bin\hpi.dll
6d720000-6d72efff E:\bea\jrockit90_150_10\jre\bin\zip.dll
6d520000-6d527fff E:\bea\jrockit90_150_10\jre\bin\management.dll
6d530000-6d542fff E:\bea\jrockit90_150_10\jre\bin\net.dll
71a50000-71a8efff C:\WINDOWS\system32\mswsock.dll
662b0000-66307fff C:\WINDOWS\system32\hnetcfg.dll
71a90000-71a97fff C:\WINDOWS\System32\wshtcpip.dll
41c00000-41c26fff C:\WINDOWS\system32\DNSAPI.dll
41c30000-41c37fff C:\WINDOWS\System32\winrnr.dll
41c40000-41c6bfff C:\WINDOWS\system32\WLDAP32.dll
41c80000-41c85fff C:\WINDOWS\system32\rasadhlp.dll
68000000-68035fff C:\WINDOWS\system32\rsaenh.dll
769c0000-76a73fff C:\WINDOWS\system32\USERENV.dll
438b0000-438b8fff E:\bea\jrockit90_150_10\jre\bin\nio.dll
41ba0000-41ba9fff E:\bea\jrockit90_150_10\jre\bin\jmapi.dll
41bb0000-41bbdfff E:\bea\weblogic92\server\native\win\32\wlfileio2.dll
43ce0000-43cf8fff C:\WINDOWS\system32\iphlpapi.dll
43d10000-43d27fff C:\WINDOWS\system32\MPRAPI.dll
77cc0000-77cf1fff C:\WINDOWS\system32\ACTIVEDS.dll
43d30000-43d54fff C:\WINDOWS\system32\adsldpc.dll
43d60000-43d70fff C:\WINDOWS\system32\ATL.DLL
43d80000-43ebcfff C:\WINDOWS\system32\ole32.dll
43ec0000-43f4afff C:\WINDOWS\system32\OLEAUT32.dll
43f50000-43f5dfff C:\WINDOWS\system32\rtutils.dll
71bf0000-71c02fff C:\WINDOWS\system32\SAMLIB.dll
43f60000-44052fff C:\WINDOWS\system32\SETUPAPI.dll
44060000-44064fff E:\bea\weblogic92\server\native\win\32\wlntio.dll
44540000-44545fff E:\bea\jrockit90_150_10\jre\bin\rmi.dll
4d010000-4d122fff E:\bea\jrockit90_150_10\jre\bin\dbghelp.dll
"[STANDBY] ExecuteThread: '21' f" id=87 idx=0xf0 tid=4208 lastJavaFrame=0x4B29EB4C
Stack 0: start=0x4B260000, end=0x4B2A0000, guards=0x4B263000 (ok), forbidden=0x4B261000
Thread Stack Trace:
at _mmGetPossibleMovedObjectSize+15()@0x0095065F
at _refIterInit+393()@0x00981099
at _refIterInit+474()@0x009810EA
at _trProcessLocksForThread+66()@0x0098ECD2
at _javalockCouldBeLock+1047()@0x008AB417
at _javalockConvertThinToFat+42()@0x008AC13A
at RJNIjrockit_vm_Locks_convertThinLockedToFatLocked@8+15()@0x00986B1F
-- Java stack --
at jrockit/vm/Locks.convertThinLockedToFatLocked(Ljava/lang/Object;)V(Native Method)
at jrockit/vm/Locks.createMonitorAndConvert(Ljava/lang/Object;Z)Ljrockit/vm/ObjectMonitor;(Unknown Source)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:474)
at weblogic/common/CompletionRequest.getResult(CompletionRequest.java:109)
^-- Holding lock: weblogic/common/CompletionRequest@0x09E5C2A8[thin lock]
at weblogic/store/gxa/internal/GXATransactionImpl.commitStoreIO(GXATransactionImpl.java:99)
at weblogic/store/gxa/internal/GXATransactionImpl.doOperationCallbacks(GXATransactionImpl.java:215)
at weblogic/store/gxa/internal/GXAResourceImpl.commit(GXAResourceImpl.java:1448)
at weblogic/transaction/internal/XAServerResourceInfo.commit(XAServerResourceInfo.java:1333)
at weblogic/transaction/internal/XAServerResourceInfo.commit(XAServerResourceInfo.java:577)
at weblogic/transaction/internal/ServerSCInfo.startCommit(ServerSCInfo.java:514)
at weblogic/transaction/internal/ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1993)
at weblogic/transaction/internal/ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2658)
at weblogic/transaction/internal/ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2580)
at weblogic/transaction/internal/ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:278)
at weblogic/transaction/internal/ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
at weblogic/deployment/jms/WrappedTransactionalSession.delistFromTransaction(WrappedTransactionalSession.java:258)
^-- Holding lock: weblogic/deployment/jms/PooledSession_weblogic_jms_client_JMSXASession@0x09D56368[thin lock]
at weblogic/deployment/jms/WrappedMessageProducer.send(WrappedMessageProducer.java:149)
at com/obopay/jms/helper/BaseQueueHelper.sendMessage(BaseQueueHelper.java:107)
The above is the jrockit crash dump file..
I am using the JMS Wrapper Connection Poooling provided by Weblogic. When i use Jmeter and do the load testing for around 10 users, the server gets crashed.
I doubt something is going wrong with the Weblogic JMS Connection Pooling, please help me..

The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
Regards,
tom
Edited by: TomB on Sep 17, 2010 2:33 PM

Monitoring the jms connection - normal behaviour

Similar Messages

Maybe you are looking for