JMSClientExceptions:055053 -WebLogic10 Cluster - Remote WebLogic JMS - Help
All,
We are using a foreign JMS provider from WeLogic 10 cluster to connect to the Remote WebLogic JMS Server. We are getting below error while posting the data to the queue. Any help , ideas as to why this is occuring please?
/ Error
Error during connection/session creation:weblogic.jms.common.JMSException: [*JMSClientExceptions:055053*]Error creating connection to the server: java.rmi.UnmarshalException: failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is: java.io.StreamCorruptedException|portal
Thanks a lot for your help.
All
The issue popped up gain. Below is the full stack trace. I confirmed that we are using the t3 URL to connect to remote JMS server (which is Weblogic 10 /JMS). Appreciate any insights help to resolve this issue.
// Stack Trace
weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.UnmarshalException:
failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is:
java.io.StreamCorruptedException
at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:253)
at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
at com.juniper.core.mdb.MessageSender.initSession(MessageSender.java:79)
at com.juniper.core.mdb.MessageSender.<init>(MessageSender.java:64)
at com.juniper.core.mdb.MDBHelper.processMessage(MDBHelper.java:98)
at com.juniper.core.mdb.BaseMDB.onMessage(BaseMDB.java:35)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3964)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is:
java.io.StreamCorruptedException
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:229)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreate(Unknown Source)
at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:244)
... 15 more
Caused by: java.io.StreamCorruptedException
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:227)
... 19 more
Thanks
Edited by: user3285437 on May 4, 2009 9:26 AM
Similar Messages
-
Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server
Hi,
I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
<Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
nect to the JMS destination: FMAContractOutboundQueue. The Error was:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
:weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
-SreekanthI recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
* The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
* The connection factory doesn't exist.
* The object in JNDI with the specified connection factory name isn't actually a connection factory.
* The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
Tom -
Hi,
I have a 6.1 cluster that has a JMS server A and a JMS Server B
deployed and running on each of the managed nodes. As destination I
created a topic with the same name for each JMS Server. The connection
factories I deployed to the cluster only.
My problem is, when I start the second managed server, I get the
following error:
<Error> <Cluster> <Conflict start: You tried to bind an object under
the name
com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
have bound
from 169.59.5.26 is non clusterable and you have tried to bind more
than once
from two or more servers. Such objects can only deployed from one
server.>
When I understand correctly, this happens because the JNDI tree gets
distributed to all nodes of the cluster, so there would be two object
with the same name. How do I solve this situation? Do I have the
specify different names for topics in different JMSServer running in a
cluster? How would the load balancing work?
Please help. Thanks in advance
Juerg
Tom,
Thanks for your help so far, I installed the patch and got things
working. However I still have some open points where you might be able
to help.
Let's assume I don't have these smart forwarders and I have four
topics per JMSServer deployed to two managed nodes. Connection
factories deployed to the cluster. When I connect N publishers
through the cluster, messages from one publisher end up in the
appropriate topic on nodeA, messages from another publisher end up in
the appropriate topic on nodeB. Now when I connect a durable
subscriber via the cluster I only get messages from topics from one of
the managed nodes, right? (This is exactly what I am seeing in my
tests) Connecting durable subscribers to each managed node is not
possible because of JNDI (throws exception like
InstanceAlreadyExists). How would I connect a subscriber so that it
subscribes to the right topics on the right node ( one the works with
the previously described publisher)?
All this leads me to the conclusion, that without the forwarders, a
JMS cluster with Weblogic 6.1 is not so powerful, it basically does
just load balacing.
Is this correct or am I missing something important here?
Thanks a lot and have a nice weekend
Juerg
Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
> Juerg Staub wrote:
> > Tom,
> >
> > Thanks a lot. Bascially I did everything right, just need the patch.
> >
> > In the other hand I'd like to know what the benefits of the smart
> > forwarders would be. When I understand correctly, every message would
> > be forwarded to the appropriate topic in the different JMS servers.
> > What would that bring in the case of a failure(one node of a cluster
> > goes down)? As far as I can see, I still would need to 're-establish'
> > the connection factory, topic session, topic and publisher in order to
> > publish messages again?
> >
>
> Yep. I think we are on the same page:
>
> The "smart-forwarders" would do what the 7.0 distributed topic
> forwarders do for you. They would forward messages bound to
> a particular physical topic to all instances of the topic.
> This can be implemented via a durable subscription on a
> member topic by each remote member topic's host.
> MDBs could be used to service the durable subscription,
> as they already have the reconnect logic built in.
> (Durable subscriptions are used if you wish to guard against
> lost messages). The forwarders
> need to change a property on the message to indicate
> that the message is already forwarded, and forward
> only messages that have'nt been forwarded (to prevent
> endless loops!).
>
>
> > Thanks
> >
> > Juerg
> >
> > Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
> >
> >>I suggest you read the "emulating 7.0 distributed destinations"
> >>section of the JMS performance white-paper available on dev2dev.bea.com.
> >>You will need to apply the referenced enhancement patch on top of SP3 to
> >>disable JNDI replication (or update to 6.1SP4).
> >>
> >>If you need to create a true distributed topic, you will also need to
> >>write your own "smart-forwarders" to forward messages
> >>between the different physical instances of the topic. Or simply
> >>use WL JMS 7.0 (the upgrade from 6.1 is straight-forward).
> >>
> >>Tom
> >>
> >>Juerg Staub wrote:
> >>
> >>>Hi,
> >>>
> >>>I have a 6.1 cluster that has a JMS server A and a JMS Server B
> >>>deployed and running on each of the managed nodes. As destination I
> >>>created a topic with the same name for each JMS Server. The connection
> >>>factories I deployed to the cluster only.
> >>>
> >>>My problem is, when I start the second managed server, I get the
> >>>following error:
> >>>
> >>><Error> <Cluster> <Conflict start: You tried to bind an object under
> >>>the name
> >>>com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
> >>>have bound
> >>>from 169.59.5.26 is non clusterable and you have tried to bind more
> >>>than once
> >>>from two or more servers. Such objects can only deployed from one
> >>>server.>
> >>>
> >>>
> >>>When I understand correctly, this happens because the JNDI tree gets
> >>>distributed to all nodes of the cluster, so there would be two object
> >>>with the same name. How do I solve this situation? Do I have the
> >>>specify different names for topics in different JMSServer running in a
> >>>cluster? How would the load balancing work?
> >>>
> >>>
> >>>Please help. Thanks in advance
> >>>
> >>>Juerg
> >>
-
Starting Weblogic Server Cluster remotely via VPN
We have a site-to-site VPN setup from our office to our ISP so we can
control our system remotely. We can stop our Weblogic servers (in a
cluster) remotely via the VPN no problem via the "stopweblogic.cmd" command
where we just change the IP address of our remote server. We're having
trouble starting them through the WebLogic console applet. We can bring the
applet up & running, but no luck starting them.
Is there another way to start your weblogic servers (besides using something
like PC Anywhere).
Or is there any documentation that could point to an answer here?
Any suggestions?
Mike Kendzierski
B2BGalaxy.com
1. "myserver" is the name of the server. It doesn't want the name of the
machine the server is on.
2. It is possible that something is wrong in the license file. I've made a
typo when changing the license on my server that prevented weblogic from
starting.
Hope this helps.
"Hilmar" <[email protected]> wrote in message
news:[email protected]..
>
When I start WebLogic server using startweblogic.cmd everything seems tobe okay.
Using the 'Start a new WebLogic server or cluster' command from WebLogicConsole
5.1.0, I get the following error message:
Attempting to start server on the machine running the console using
C:\weblogic\jre1_2\jre\bin\java.exe -mx32m -ms32m -classpath"C:\weblogic\jre1_2\jre\lib\rt.jar;C:\weblogic\jre1_2\jre\lib\i18n.jar;C:\we
blogic\lib\i18n.jar;C:\weblogic\classes\boot;C:\weblogic\eval\cloudscape\lib
\cloudscape.jar"
-Dweblogic.class.path=C:\weblogic\license;C:\weblogic\classes;C:\weblogic\myserver\serverclasses;C:\weblogic\lib\weblogicaux.jar
-Dweblogic.system.discardOutAndErr=true -Djava.security.manager -Djava.security.policy==C:\weblogic\weblogic.policy
-Dweblogic.system.name=kenapp00111 -Dweblogic.system.home=C:\weblogic -Dweblogic.cluster.enable=false
-Dweblogic.cluster.name=mycluster -Dweblogic.system.listenPort=7001 -Dweblogic.system.SSLListenPort=7002
-Dweblogic.cluster.multicastAddress=237.0.0.1 weblogic.Server
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Loaded License : C:/weblogic/license/WebLogicLicense.xml
However Unable to start because :
No License found for WebLogic
As well as the fact that: No License found for Tengah
As well as the fact that: No License found for WebLogic/JDBC
As well as the fact that: No License found for Tengah/JDBC
As well as the fact that: No License found for jdbcKona/T3
Is the 'server name' the name of the machine or 'myserver' ? Could therereally
be something wrong with the licence file ?
Thanks for helping !
Hilmar -
Using JMS Event Generator w/ remote WebLogic 8.1 queue
Hello,
I'm trying to create a workflow that is started by a JMS message queue event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
file for the tool:
<message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
and Destination using the Weblogic Admin Console. Below are the parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
I found the existing BEA documentation to be a bit too generic, containing no
specific examples of the proper syntax to use for this task. Can anyone offer
any advice or better, a working example? Any BEA reps out there?Hello,
I'm trying to create a workflow that is started by a JMS message queue event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
file for the tool:
<message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
and Destination using the Weblogic Admin Console. Below are the parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
I found the existing BEA documentation to be a bit too generic, containing no
specific examples of the proper syntax to use for this task. Can anyone offer
any advice or better, a working example? Any BEA reps out there? -
Weblogic JMS Client App fails creating queue connection
Using the example provided from installation: ...\bea\wlserver_10.0\samples\server\examples\src\examples\jms\queue\QueueBrowse.java
I can successfully connect and display the queue when this test app runs on the local Weblogic Server. When I run the test app on a remote server (not the Weblogic server), I get the following error:
Exception in thread "main" weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
java.lang.NullPointerException
at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:258)
at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
at com.lodestarcorp.custom.QueueBrowse.init(QueueBrowse.java:53)
at com.lodestarcorp.custom.QueueBrowse.main(QueueBrowse.java:129)
Caused by: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
java.lang.NullPointerException
at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:91)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:332)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreateRequest(Unknown Source)
at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224)
... 4 more
Caused by: java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
java.lang.NullPointerException
at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:118)
at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:89)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:55)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:41)
at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:194)
at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceSmartStubInfo(RemoteObjectReplacer.java:116)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:102)
at weblogic.rmi.utils.io.InteropObjectReplacer.replaceObject(InteropObjectReplacer.java:62)
at weblogic.utils.io.ChunkedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:40)
at weblogic.utils.io.ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:141)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.writeObject(Unknown Source)
at weblogic.messaging.dispatcher.DispatcherWrapper.writeExternal(DispatcherWrapper.java:152)
at weblogic.jms.frontend.FEConnectionCreateRequest.writeExternal(FEConnectionCreateRequest.java:98)
at java.io.ObjectOutputStream.writeExternalData(Unknown Source)
at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.writeObject(Unknown Source)
at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:614)
at weblogic.rjvm.MsgAbbrevOutputStream.writeObjectWL(MsgAbbrevOutputStream.java:605)
at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:38)
at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:87)
... 8 more
Caused by: java.lang.NullPointerException
at weblogic.rmi.internal.BasicRuntimeDescriptor.createSkeletonClass(BasicRuntimeDescriptor.java:272)
at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:158)
at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:140)
at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:110)
... 30 more
FYI: I did create the wlfullclient.jar from the installation.
Could the problem be related to a proxy issue? It's not a DNS problem (I've tested with the IP address).
Thanks,
BrianI had this very same issue, in a project I was importing directly individual jars:
<classpathentry kind="lib" path="lib/javax.jms_1.1.1.jar"/>
<classpathentry kind="lib" path="lib/weblogic.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.identity_1.1.2.1.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager_1.9.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager.ja_1.9.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.transaction_2.7.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client.ja_1.8.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client_1.8.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.wls_1.0.0.0_6-1-0-0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.utils.full_1.9.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.security_1.0.0.0_6-1-0-0.jar"/>
<classpathentry kind="lib" path="lib/wlclient.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.utils.classloaders_1.8.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.management.core_2.8.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.descriptor_1.9.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.logging_1.8.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.timers_1.7.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.socket.api_1.2.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.digest_1.0.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.weblogic.lifecycle_1.4.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.store_1.7.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.common.security.api_1.0.0.0_6-1-0-0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.utils.wrapper_1.4.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.messaging.kernel_1.8.0.0.jar"/>
<classpathentry kind="lib" path="lib/com.bea.core.utils.expressions_1.4.0.0.jar"/>
and everything was working;
in another project I was importing the "Weblogic System Libraries" libraries, and I was getting the NullPointerException...
I have the sensation that there is room for improvement in the way libraries are managed. -
Session Beans and TIBCO E4JMS and Weblogic JMS 8.1
Setup:-
Weblogic Server 8.1 SP2 on Linux
TIBCO E4JMS 3.1.2
I have a two Staeless Session Beans which are deployed in both sides of the cluster
- Cluster is made up of two servers(ManagedServer1 and ManagedServer2) on the
same machine. The beans have container managed transaction and trans-type set
to required. The JMS Server is on ManagedServer1. The session bean publishes 100
messages to TIBCO JMS and Weblogic JMS and calls the second bean which again publishes
100 messages to TIBCO JMS and Weblogic JMS .
The connection factories used are XAQueueConnectionFactories.
This seems to work under the following conditions:-
a) The session beans are deployed just in ManagedServer1
b) The WL load balancing scheme manages to run both the beans on ManagedServer1
c) If I don't publish onto Weblogic JMS( It runs successfully on ManagedServer1
and ManagedServer2)
It does not seems to work :-
When the The WL load balancing scheme manages to run both the beans on ManagedServer2.I
put debug statements on the beans and it seems to publish everything but fails
during the commit
murali@dbuslinux1:~/SessionBeanExample> ant run
Buildfile: build.xml
run:
[java] Run : 0
[java] InitialContextFactory weblogic.jndi.WLInitialContextFactory
[java] Provider Url t3://myhost.mycompany.com:18003,myhost.mycompany.com:18005
[java] javax.transaction.TransactionRolledbackException: Exception while
commiting Tx : Name=[EJB Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer,java.lang.String,boolean,boolean)],Xid=BEA1-000649EC8876A0032A5E(160401684),Status=Rolled
back. [Reason=javax.transaction.xa.XAException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=3,seconds left=30,XAServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN1TCF]=(ServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN1TCF]=(state=rolledback,assigned=ManagedServer2),xar=weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource@a0181b0),XAServerResourceInfo[JMS_MyJMS
File Store]=(ServerResourceInfo[JMS_MyJMS File Store]=(state=rolledback,assigned=ManagedServer1),xar=null),XAServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(ServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(state=rolledback,assigned=ManagedServer2),xar=weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource@98f6821),SCInfo[E4JMSDOMAIN+ManagedServer1]=(state=rolledback),SCInfo[E4JMSDOMAIN+ManagedServer2]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer,java.lang.String,boolean,boolean)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ManagedServer2+myhost.mycompany.com:18005+E4JMSDOMAIN+t3+,
XAResources={},NonXAResources={})],CoordinatorURL=ManagedServer2+myhost.mycompany.com:18005+E4JMSDOMAIN+t3+):
javax.transaction.xa.XAException
[java] at com.tibco.tibjms.TibjmsXAResource.end(Ljavax.transaction.xa.Xid;I)V(TibjmsXAResource.java:157)
[java] at weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.end(Ljavax.transaction.xa.Xid;I)V(Unknown
Source)
[java] at weblogic.transaction.internal.XAServerResourceInfo.end(Lweblogic.transaction.internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid;I)V(XAServerResourceInfo.java:1124)
[java] at weblogic.transaction.internal.XAServerResourceInfo.internalDelist(Lweblogic.transaction.internal.ServerTransactionImpl;I)V(XAServerResourceInfo.java:325)
[java] at weblogic.transaction.internal.XAServerResourceInfo.delist(Lweblogic.transaction.internal.ServerTransactionImpl;IZ)V(XAServerResourceInfo.java:255)
[java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(IZ)V(ServerTransactionImpl.java:1408)
[java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(I)V(ServerTransactionImpl.java:1396)
[java] at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare()V(ServerTransactionImpl.java:1932)
[java] at weblogic.transaction.internal.ServerTransactionImpl.internalCommit()V(ServerTransactionImpl.java:252)
[java] at weblogic.transaction.internal.ServerTransactionImpl.commit()V(ServerTransactionImpl.java:221)
[java] at weblogic.ejb20.internal.BaseEJBObject.postInvoke(Lweblogic.ejb20.interfaces.InvocationWrapper;Ljava.lang.Throwable;)V(BaseEJBObject.java:289)
[java] at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(Lweblogic.ejb20.interfaces.InvocationWrapper;Ljava.lang.Throwable;)V(StatelessEJBObject.java:141)
[java] at Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Ljava.lang.Integer;Ljava.lang.Integer;Ljava.lang.String;ZZ)V(Stateless_soycq8_EOImpl.java:112)
[java] at Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(ILweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Object;)Lweblogic.rmi.spi.OutboundResponse;(Unknown
Source)
[java] at weblogic.rmi.internal.BasicServerRef.invoke(Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;)V(BasicServerRef.java:477)
[java] at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;)V(ReplicaAwareServerRef.java:108)
[java] at weblogic.rmi.internal.BasicServerRef$1.run()Ljava.lang.Object;(BasicServerRef.java:420)
[java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedExceptionAction;)Ljava.lang.Object;(AuthenticatedSubject.java:353)
[java] at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedExceptionAction;)Ljava.lang.Object;(SecurityManager.java:144)
[java] at weblogic.rmi.internal.BasicServerRef.handleRequest(Lweblogic.rmi.spi.InboundRequest;)V(BasicServerRef.java:415)
[java] at weblogic.rmi.internal.BasicExecuteRequest.execute(Lweblogic.kernel.ExecuteThread;)V(BasicExecuteRequest.java:30)
[java] at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
[java] at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
[java] at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown
Source)
[java] ; nested exception is:
[java] javax.transaction.xa.XAException
[java] at weblogic.rjvm.BasicOutboundRequest.sendReceive()Lweblogic.rmi.spi.InboundResponse;(BasicOutboundRequest.java:108)
[java] at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Lweblogic.rmi.extensions.server.RemoteReference;Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(ReplicaAwareRemoteRef.java:284)
[java] at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Ljava.rmi.Remote;Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(ReplicaAwareRemoteRef.java:244)
[java] at Case463495.Stateless_soycq8_EOImpl_812_WLStub.sendMessageWrap(Ljava.lang.Integer;Ljava.lang.Integer;Ljava.lang.String;ZZ)V(Unknown
Source)
[java] at Case463495.Client.run()V(Client.java:103)
[java] at Case463495.Client.sendMessage()V(Client.java:132)
[java] at Case463495.Client.main([Ljava.lang.String;)V(Client.java:195)
[java] Caused by: javax.transaction.xa.XAException
[java] at com.tibco.tibjms.TibjmsXAResource.end(TibjmsXAResource.java:157)
[java] at weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.end(Unknown
Source)
[java] at weblogic.transaction.internal.XAServerResourceInfo.end(XAServerResourceInfo.java:1124)
[java] at weblogic.transaction.internal.XAServerResourceInfo.internalDelist(XAServerResourceInfo.java:325)
[java] at weblogic.transaction.internal.XAServerResourceInfo.delist(XAServerResourceInfo.java:255)
[java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransactionImpl.java:1408)
[java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransactionImpl.java:1396)
[java] at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1932)
[java] at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:252)
[java] at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
[java] at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:289)
[java] at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:141)
[java] at Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Stateless_soycq8_EOImpl.java:112)
[java] at Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(Unknown Source)
[java] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
[java] at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
[java] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
[java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
[java] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
[java] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
[java] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
[java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
[java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
[java] at java.lang.Thread.startThreadFromVM(Unknown Source)
Apologies in advance if this need to be posted in the JTA news group..
Any ideas?
Murali
Posting to the transaction newsgroup would probably also be helpful.
Can you post the code for the session bean so we can see how you're
enlisting Tibco in the transaction? It looks like you're using the JMS
provider wrappers from 8.1, which do the transaction enlistment for you, so
you shouldn't need to mess with JTA at all in your code. Still, something
weird is going on and it'd be nice to see exactly what your code looks like.
greg
"L Muralidharan" <[email protected]> wrote in message
news:[email protected]...
>
> Setup:-
>
> Weblogic Server 8.1 SP2 on Linux
>
> TIBCO E4JMS 3.1.2
>
> I have a two Staeless Session Beans which are deployed in both sides of
the cluster
> - Cluster is made up of two servers(ManagedServer1 and ManagedServer2) on
the
> same machine. The beans have container managed transaction and trans-type
set
> to required. The JMS Server is on ManagedServer1. The session bean
publishes 100
> messages to TIBCO JMS and Weblogic JMS and calls the second bean which
again publishes
> 100 messages to TIBCO JMS and Weblogic JMS .
>
> The connection factories used are XAQueueConnectionFactories.
>
> This seems to work under the following conditions:-
>
> a) The session beans are deployed just in ManagedServer1
> b) The WL load balancing scheme manages to run both the beans on
ManagedServer1
> c) If I don't publish onto Weblogic JMS( It runs successfully on
ManagedServer1
> and ManagedServer2)
>
> It does not seems to work :-
>
> When the The WL load balancing scheme manages to run both the beans on
ManagedServer2.I
> put debug statements on the beans and it seems to publish everything but
fails
> during the commit
>
> murali@dbuslinux1:~/SessionBeanExample> ant run
> Buildfile: build.xml
>
> run:
> [java] Run : 0
> [java] InitialContextFactory weblogic.jndi.WLInitialContextFactory
> [java] Provider Url
t3://myhost.mycompany.com:18003,myhost.mycompany.com:18005
> [java] javax.transaction.TransactionRolledbackException: Exception
while
> commiting Tx : Name=[EJB
Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer
,java.lang.String,boolean,boolean)],Xid=BEA1-000649EC8876A0032A5E(160401684)
,Status=Rolled
> back.
[Reason=javax.transaction.xa.XAException],numRepliesOwedMe=0,numRepliesOwedO
thers=0,seconds
> since begin=3,seconds
left=30,XAServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEA
N1TCF]=(ServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN1
TCF]=(state=rolledback,assigned=ManagedServer2),xar=weblogic.deployment.jms.
WrappedXAResource_com_tibco_tibjms_TibjmsXAResource@a0181b0),XAServerResourc
eInfo[JMS_MyJMS
> File Store]=(ServerResourceInfo[JMS_MyJMS File
Store]=(state=rolledback,assigned=ManagedServer1),xar=null),XAServerResource
Info[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(ServerResourceIn
fo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(state=rolledback,a
ssigned=ManagedServer2),xar=weblogic.deployment.jms.WrappedXAResource_com_ti
bco_tibjms_TibjmsXAResource@98f6821),SCInfo[E4JMSDOMAIN+ManagedServer1]=(sta
te=rolledback),SCInfo[E4JMSDOMAIN+ManagedServer2]=(state=rolledback),propert
ies=({weblogic.transaction.name=[EJB
>
Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer
,java.lang.String,boolean,boolean)]}),OwnerTransactionManager=ServerTM[Serve
rCoordinatorDescriptor=(CoordinatorURL=ManagedServer2+myhost.mycompany.com:1
8005+E4JMSDOMAIN+t3+,
>
XAResources={},NonXAResources={})],CoordinatorURL=ManagedServer2+myhost.myco
mpany.com:18005+E4JMSDOMAIN+t3+):
> javax.transaction.xa.XAException
> [java] at
com.tibco.tibjms.TibjmsXAResource.end(Ljavax.transaction.xa.Xid;I)V(TibjmsXA
Resource.java:157)
> [java] at
weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.
end(Ljavax.transaction.xa.Xid;I)V(Unknown
> Source)
> [java] at
weblogic.transaction.internal.XAServerResourceInfo.end(Lweblogic.transaction
.internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid;I)V(XAServerResour
ceInfo.java:1124)
> [java] at
weblogic.transaction.internal.XAServerResourceInfo.internalDelist(Lweblogic.
transaction.internal.ServerTransactionImpl;I)V(XAServerResourceInfo.java:325
> [java] at
weblogic.transaction.internal.XAServerResourceInfo.delist(Lweblogic.transact
ion.internal.ServerTransactionImpl;IZ)V(XAServerResourceInfo.java:255)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.delistAll(IZ)V(ServerTra
nsactionImpl.java:1408)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.delistAll(I)V(ServerTran
sactionImpl.java:1396)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare()V(ServerT
ransactionImpl.java:1932)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit()V(Server
TransactionImpl.java:252)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.commit()V(ServerTransact
ionImpl.java:221)
> [java] at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(Lweblogic.ejb20.interfaces.
InvocationWrapper;Ljava.lang.Throwable;)V(BaseEJBObject.java:289)
> [java] at
weblogic.ejb20.internal.StatelessEJBObject.postInvoke(Lweblogic.ejb20.interf
aces.InvocationWrapper;Ljava.lang.Throwable;)V(StatelessEJBObject.java:141)
> [java] at
Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Ljava.lang.Integer;Ljava.
lang.Integer;Ljava.lang.String;ZZ)V(Stateless_soycq8_EOImpl.java:112)
> [java] at
Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(ILweblogic.rmi.spi.InboundR
equest;Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Object;)Lweblogic.rmi.s
pi.OutboundResponse;(Unknown
> Source)
> [java] at
weblogic.rmi.internal.BasicServerRef.invoke(Lweblogic.rmi.extensions.server.
RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.O
utboundResponse;)V(BasicServerRef.java:477)
> [java] at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(Lweblogic.rmi.extensions.s
erver.RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi
.spi.OutboundResponse;)V(ReplicaAwareServerRef.java:108)
> [java] at
weblogic.rmi.internal.BasicServerRef$1.run()Ljava.lang.Object;(BasicServerRe
f.java:420)
> [java] at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.
subject.AbstractSubject;Ljava.security.PrivilegedExceptionAction;)Ljava.lang
.Object;(AuthenticatedSubject.java:353)
> [java] at
weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.inter
nal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubjec
t;Ljava.security.PrivilegedExceptionAction;)Ljava.lang.Object;(SecurityManag
er.java:144)
> [java] at
weblogic.rmi.internal.BasicServerRef.handleRequest(Lweblogic.rmi.spi.Inbound
Request;)V(BasicServerRef.java:415)
> [java] at
weblogic.rmi.internal.BasicExecuteRequest.execute(Lweblogic.kernel.ExecuteTh
read;)V(BasicExecuteRequest.java:30)
> [java] at
weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(Exe
cuteThread.java:197)
> [java] at
weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
> [java] at
java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown
> Source)
> [java] ; nested exception is:
> [java] javax.transaction.xa.XAException
> [java] at
weblogic.rjvm.BasicOutboundRequest.sendReceive()Lweblogic.rmi.spi.InboundRes
ponse;(BasicOutboundRequest.java:108)
> [java] at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Lweblogic.rmi.extensions.s
erver.RemoteReference;Lweblogic.rmi.extensions.server.RuntimeMethodDescripto
r;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(ReplicaAw
areRemoteRef.java:284)
> [java] at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Ljava.rmi.Remote;Lweblogic
.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang
.reflect.Method;)Ljava.lang.Object;(ReplicaAwareRemoteRef.java:244)
> [java] at
Case463495.Stateless_soycq8_EOImpl_812_WLStub.sendMessageWrap(Ljava.lang.Int
eger;Ljava.lang.Integer;Ljava.lang.String;ZZ)V(Unknown
> Source)
> [java] at Case463495.Client.run()V(Client.java:103)
> [java] at Case463495.Client.sendMessage()V(Client.java:132)
> [java] at
Case463495.Client.main([Ljava.lang.String;)V(Client.java:195)
> [java] Caused by: javax.transaction.xa.XAException
> [java] at
com.tibco.tibjms.TibjmsXAResource.end(TibjmsXAResource.java:157)
> [java] at
weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.
end(Unknown
> Source)
> [java] at
weblogic.transaction.internal.XAServerResourceInfo.end(XAServerResourceInfo.
java:1124)
> [java] at
weblogic.transaction.internal.XAServerResourceInfo.internalDelist(XAServerRe
sourceInfo.java:325)
> [java] at
weblogic.transaction.internal.XAServerResourceInfo.delist(XAServerResourceIn
fo.java:255)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransact
ionImpl.java:1408)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransact
ionImpl.java:1396)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
sactionImpl.java:1932)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:252)
> [java] at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:221)
> [java] at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:289)
> [java] at
weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.jav
a:141)
> [java] at
Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Stateless_soycq8_EOImpl.j
ava:112)
> [java] at
Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(Unknown Source)
> [java] at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
> [java] at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:108)
> [java] at
weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
> [java] at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:353)
> [java] at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
> [java] at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
> [java] at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:3
0)
> [java] at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> [java] at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
> [java] at java.lang.Thread.startThreadFromVM(Unknown Source)
>
>
> Apologies in advance if this need to be posted in the JTA news group..
>
> Any ideas?
>
> Murali
>
-
hi weblogic users,
i have a problem in sending jms messages
across two different weblogic host/domain.
the configuration is:
jms client:
-JAX-WS webservice web app
-deployed in WebLogic Server Version: 10.3.1.0
-host: 192.168.30.133:7011
-domain: ChSoaAdminServer1
-can access server's console: http://192.168.1.22:6001/console
server:
-jms server, jms module, cf, queue configured
with subdeployment targeted to the jmsserver
-deployed in WebLogic Server Version: 10.3.2.0
-host: 192.168.1.22:6001
-domain: soa_domain
-cannot access client's console: http://192.168.30.133:7011/console
i use standard lookup method in my java client code:
String settingJmsServer="t3://192.168.1.22:6001";
String settingCF="jms/adminduk/cf";
String settingQueue="jms/adminduk/queue/central";
env=new Hashtable();
env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
env.put(Context.PROVIDER_URL, settingJmsServer);
ctx = new InitialContext( env );
System.out.println("-- Destination");
ds = (Destination) ctx.lookup(settingQueue);
System.out.println("-- ConnectionFactory");
cf = (ConnectionFactory) ctx.lookup(settingCF);
but it's getting exception
when looking up the connection factory (look at the bottom of my post):
ok now, how to solve this problem?
-i tried to change the server to another host with WL 10.3.1.0 installed (so
it's the same version with the client) and its ok (receiving messages)
-i tried to deploy the WS client to the same host as the jms (WL 10.3.2.0), so no
remote lookup needed (java lookup code adjusted), it's ok
-based on the stack trace:
"Could not find dynamically generated class:
'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub
(class not found) ..."
-does it mean do i've to use the same version of WL installed in the client side ??
-is WL 10.3.2.0 compatible with WL 10.3.1.0 ?
-is it possible to use a different version of weblogic (in the client/server)
in using the jms feature ?
-do the jms server must have access to client's port (7011) for it to work ?
thanks,
any info/hints/helps will be appreciated :)
---------- start error ---------
####<Mar 23, 2010 4:24:51 PM ICT> <Error> <com.sun.xml.ws.server.sei.EndpointMethodHandler>
<coolpie> <ChSoaAdminServer1> <[ACTIVE] ExecuteThread: '1' for queue:
'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1269336291921> <BEA-000000>
<***** ASSERTION FAILED *****[ Could not find dynamically generated class:
'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub' ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not find dynamically
generated class: 'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub' ]
at weblogic.utils.classfile.utils.CodeGenerator.generateClass(CodeGenerator.java:78)
at weblogic.rmi.internal.StubGenerator.hotCodeGenClass(StubGenerator.java:775)
at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:759)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:779)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:213)
at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:207)
at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
weblogic.jms.client.JMSConnectionFactory.readExternal(JMSConnectionFactory.java:382)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
at
weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1031_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:400)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:194)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at siak.model.MessageManager.init(MessageManager.java:101)
at siak.ws.SiakWS.sendEvent(SiakWS.java:37)
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:597)
at
weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:101)
at
weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:83)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:152)
at
com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:264)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:249)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:453)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:250)
at
com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
at
weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:298)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:211)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:297)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java
:227)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletConte
xt.java:3588)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.ClassNotFoundException: weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub
at
weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at
weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:55)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at
weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:36)
at
weblogic.utils.classloaders.FilteringClassLoader.findClass(FilteringClassLoader.java:100)
at
weblogic.wsee.util.JAXWSClassLoaderFactory$1.findClass(JAXWSClassLoaderFactory.java:45)
at
weblogic.utils.classloaders.FilteringClassLoader.loadClass(FilteringClassLoader.java:85)
at
weblogic.utils.classloaders.FilteringClassLoader.loadClass(FilteringClassLoader.java:80)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
weblogic.utils.classloaders.GenericClassLoader.defineCodeGenClass(GenericClassLoader.java:516
at weblogic.utils.classfile.utils.CodeGenerator.generateClass(CodeGenerator.java:73)
at weblogic.rmi.internal.StubGenerator.hotCodeGenClass(StubGenerator.java:775)
at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:759)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:779)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:213)
at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:207)
at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
weblogic.jms.client.JMSConnectionFactory.readExternal(JMSConnectionFactory.java:382)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
at
weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1031_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:400)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:194)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at siak.model.MessageManager.init(MessageManager.java:101)
at siak.ws.SiakWS.sendEvent(SiakWS.java:37)
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:597)
at
weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:101)
at
weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:83)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:152)
at
com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:264)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:249)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:453)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:250)
at
com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
at
weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:298)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:211)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:297)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java
:227)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletConte
xt.java:3588)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
---------- end error ---------1 - A class-not-found is an odd exception to get on a server. Did you perhaps try to add client-only jars to the server classpath? The server classpath is already setup properly to act as a client.
2 - Its usually not a good practice to create contexts in client code (instead of simply using the Servlet context in your case), or to hard code URLs, dests, and CF references into the code. It works, but can be hard to maintain and inefficient.
3 - See:
[ Enhanced Support for Using WebLogic JMS with EJBs and Servlets | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/j2ee.htm#g1329180 ]
and
[ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/interop.htm#JMSPG553 ]
and the cross-domain advice in
[ Integration and Multi-Domain Best Practices |
http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACFBCHB ]
Hope this helps,
Tom -
Hi All,
I need help understanding weblogic JMS clustering. I read few documents regarding this but not very clear about it.
Hope to get help/suggestion here.
I have following setup
box1 - adminserver, osbserver1
box2- osbserver2
osbserver1 and osbserver2 are clustered together
I have a JMS server created each one for each managed server (OSB server) in the cluster. These JMS servers are non-persistent. persistent store is "None".
I have one JMS module created with connection factory, distributed Qs and are associated with a subdeployment that is targeting to the cluster
I have all the servers(admin server and both OSB servers) are in running state
To monitor JMS server I go to services->JMS Servers
I see jmsserver1 which is targeted to osbserver1 has "Health" is marked as "OK"
jmserver2 which is targeted to osbserver2 has no "health" check
If I go to environment->servers , I see all the 3 servers are marked as "RUNNING" with "Health" OK
As a note I created managed server in the second box before creating the JMS server and resources.
And I do not have any nodemanager setup at this point.
How would I know the JMSserver in both servers are active and have no issues ?
Do I need to do anything to start JMSServer in OSBServer2 ?
Edited by: 818591 on Feb 11, 2011 8:27 AM
Edited by: 818591 on Feb 11, 2011 9:31 AMShould the JMS Server/JMS modules already be created so that the remote managed server will get configuration of these setup?No. This is not how resorces are created. Pack/unpack is used for creating the domains, ONCE. Later on you may very well use Weblogic admin console to create the resources and target/untarget those.
As a note I do not have node managed setup yet. It is recommended that you use node manager in environments where servers may be installed on different machines -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13740/toc.htm
To me, it seems a network/cluster communication issue. If you have Oracle Support, better raise a SR with them to find out the exact issue as they would be in better position to understand your architecture and analyzing logs. You may also raise a thread in Oracle Weblogic forum to get a suggestion from a Weblogic expert -
WebLogic Server - Clustering
Regards,
Anuj -
Problem in Interacting with Weblogic JMS through Informatica ETL server
Hi All,
We are trying to configure Informatica PowerCenter server to interact with JMS queues created on Weblogic 11gR1 server. We have copied the necessary
jar file - wlfullclient.jar to the classpath of the Informatica server.
Now when i try to read contents of a JMS queue created on Weblogic server through Informatica, i get this error:-
Failed to get the Queue Connection Factory [weblogic.jms.common.DestinationImpl]. Reason: Failed to look up object [While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms'Exception Stack: javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'. Resolved 'weblogic.jms']; remaining name 'common/DestinationImpl'
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:464)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:272)
at weblogic.jndi.internal.ServerNamingNode_1211_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:418)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.informatica.powerconnect.jms.server.common.JNDIConnection.getJNDIObject(JNDIConnection.java:84)
at com.informatica.powerconnect.jms.server.common.PlginJMSConnection$PlginJMSQueueConnection.createConnection(PlginJMSConnection.java:363)
at com.informatica.powerconnect.jms.server.common.PlginJMSConnection.<init>(PlginJMSConnection.java:90)
at com.informatica.powerconnect.jms.server.common.PlginJMSConnection$PlginJMSQueueConnection.<init>(PlginJMSConnection.java:352)
at com.informatica.powerconnect.jms.server.common.PlginJMSConnection.create(PlginJMSConnection.java:115)
at com.informatica.powerconnect.jms.server.reader.JMSReaderSQDriver.createPartitionDriver(JMSReaderSQDriver.java:557)
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jms.common.DestinationImpl' didn't find subcontext 'common'
I have checked that this class file exists in the above said location :- "weblogic/jms/common/DestinationImpl.class" within the wlfullclient.jar but still the
code is not able to access the class. Similar error came initially while doing JNDI connection using "weblogic.jndi.WLInitialContextFactory" class but it vanished,
when i explicitly named the jar file on classpth, instead of just the folder containing the jar file.
To all the users/experts/moderators of Weblogic - Could you please help me understand why Weblogic is not able to look up subcontext 'common'
for the class - "weblogic.jms.common.DestinationImpl" ??
Thanks & Regards
Raj
Edited by: user8931188 on May 17, 2012 7:39 AMYou are experiencing a NameNotFoundException, not ClassNotFoundException so it seems there is something wrong about the client connection code or WebLogic config.
Can you share your client connection connection config/code? -
TIBCO consumer, WebLogic JMS, reconnecting
We're currently running TIBCO 7.2 processes with WebLogic 7 as the JMS and DB connection factory.
When using weblogic.jar to access JMS, we have discovered that TIBCO seems to loose connection entirely if a JMS server node dies, even when using distributed queues.
We have implemented the 'forward-delay' option to process messages from queues without an active consumer, in the event of a physical node failure. When this occurs however, TIBCO will not automatically reconnect.
Does anyone know of a work-around or whether or not this is resolved with the WL 9 releast of weblogic.jar?
The issue is that the entry point to TIBCO processes is to listen on a queue. Once the connection is broken, the component stops listening for messages.Hi Uday,
The best option depends on your use case.
A messaging bridge is usually only appropriate when you want to store-and-forward from a local destination to a remote destination, instead of directly sending to the remote destination. Store-and-forward is helpful when you still want to be able to produce a message even when the remote destination is unavailable.
SAF Agents are a store and forward solution, just like bridges, but are only designed to only work with WebLogic JMS destinations.
For links to WebLogic Messaging white-papers, blog posts, samples, and documentation, click Enterprise Grid Messaging on the [url http://www.oracle.com/technetwork/middleware/weblogic/overview/index.html]Oracle WebLogic Product Page.
Specifically, see the [url http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/interop.htm#JMSPG553]Integrating Remote JMS Providers FAQ, which should help you choose between WebLogic's various JMS integration options.
Hope this helps,
Tom -
JMS cluster and happen JMS Queue Exception javax.naming.NameAlreadyBoundExc
Hi,
Sorry I not sure how to setup JMS cluster in WLS 10.3.2. We have two manager server in two machine. And will join into one cluster. After configure the JMS module & JMS server. We found it only can work in one server. And will faill in another server. And reply the error message as below :
Any one can help to tell me why one server success. And other is fail !
javax.naming.NameAlreadyBoundException: JMS_Queue_misdel_a is already bound; rem
aining name ''
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:140)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.jav
==> config for JMS
<jms-server>
<name>JMS_Server_cim_a</name>
<target>ebowls05</target>
<persistent-store xsi:nil="true"></persistent-store>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
<expiration-scan-interval>30</expiration-scan-interval>
</jms-server>
<jms-server>
<name>JMS_Server_cim_b</name>
<target>ebowls06</target>
<persistent-store xsi:nil="true"></persistent-store>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
<expiration-scan-interval>30</expiration-scan-interval>
</jms-server>
<migratable-target>
<name>ebowls06 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do
not delete manually.</notes>
<user-preferred-server>ebowls06</user-preferred-server>
<cluster>ebouatCluster</cluster>
</migratable-target>
<migratable-target>
<name>ebowls05 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do
not delete manually.</notes>
<user-preferred-server>ebowls05</user-preferred-server>
<cluster>ebouatCluster</cluster>
</migratable-target>
<jms-system-resource>
<name>JMS_ConnFactory_cim</name>
<target>ebouatCluster</target>
<descriptor-file-name>jms/JMS_ConnFactory_cim/JMS_ConnFactory_cim-jms.xml</d
escriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_promis</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_promis@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_promis@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_promis/JMS_Queue_promis-jms.xml</descrip
tor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Template_cim</name>
<target>ebouatCluster</target>
<descriptor-file-name>jms/JMS_Template_cim/JMS_Template_cim-jms.xml</descrip
tor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_misdel_a</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_misdel_a@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_misdel_a@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_misdel_a/JMS_Queue_misdel_a-jms.xml</des
criptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>JMS_Queue_misdel_b</name>
<target>ebouatCluster</target>
<sub-deployment>
<name>JMS_Queue_misdel_b@JMS_Server_cim_a</name>
<target>JMS_Server_cim_a</target>
</sub-deployment>
<sub-deployment>
<name>JMS_Queue_misdel_b@JMS_Server_cim_b</name>
<target>JMS_Server_cim_b</target>
</sub-deployment>
<descriptor-file-name>jms/JMS_Queue_misdel_b/JMS_Queue_misdel_b-jms.xml</des
criptor-file-name>
</jms-system-resource>1 - JMS clustering is an advanced concept, and, in most cases, uses "distributed queues". In case you haven't already, I highly recommend reading the JMS chapter of the new book "Professional Oracle WebLogic" as well as the related chapters in the JMS Programmer's Guide in the edocs.
2 - The basic problem below is that you have two different queues that have matching JNDI names, but are in the same cluster.
3 - The config snippet supplied below does not include the queue configuration. Queue configuration is embedded within the referenced module files.
4 - Please ensure that you follow configuration best practices, as per: http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACJCGHG -
Weblogic.jms.frontend.FEConnectionFactory on Stuck Thread
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I need help on this issue quite
urgently.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Server Environment</FONT></DIV>
<DIV><FONT face=Arial size=2>----------------------</FONT></DIV>
<DIV>
<DIV><FONT face=Arial size=2>Server: Weblogic 8.1 SP4</FONT></DIV>
<DIV><FONT face=Arial size=2>Java version: 1.4.2_05</FONT></DIV></DIV>
<DIV><FONT face=Arial size=2>I have 2 Sun Solaris Servers each having 4
NICs with the following addresses:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>SERVER A
SERVER B</FONT></DIV>
<DIV><FONT face=Arial size=2>-------------
-------------</FONT></DIV>
<DIV><FONT face=Arial size=2>10.32.10.11
10.32.10.13</FONT></DIV>
<DIV><FONT face=Arial size=2>10.32.10.12
10.32.10.14</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial
size=2>10.31.10.131 10.31.10.133</FONT></DIV>
<DIV><FONT face=Arial size=2>10.31.10.132
10.31.10.134</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>
<DIV>
<DIV><FONT face=Arial size=2>10.32.10.11 / 10.32.10.12 / 10.32.10.13 /
10.32.10.14 are all mapped onto a Virtual IP Address
10.32.10.1</FONT></DIV><FONT face=Arial size=2>10.31.10.131 / 10.31.10.132 /
10.31.10.133 / 10.31.10.134 are all mapped onto a Virtual IP Address
10.31.10.1</FONT></DIV></DIV>
<DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>And the subnet for the above NICs is all
255.255.255.0.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The 2 Sun Servers are being clustered by Vertias
Cluster Server and At any one time, only one server is in active
state.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV><FONT face=Arial size=2>Scenario:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>When a client (IP Address:
10.32.10.101/255.255.255.0) tries to subscribe to the server's JMS Topic, the
entire server hanged and no other client requests can be further
processed.</FONT></DIV>
<DIV><FONT face=Arial size=2>Health status checks on the server also did not get
any response and the client also hanged.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>A check on the Weblogic's Kernal threads shows that
one of the thread is currently handling
"weblogic.jms.frontend.FEConnectionFactory".</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>This hanged state will eventually timeout after
600s and everything goes back to normal. </FONT></DIV>
<DIV><FONT face=Arial size=2>The client will have exceptions saying No route to
destination due to "Empty Reply".</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I've also tried upgradng the Client's JDK to
1.4.2_07 and the reslt is still the same.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For weblogic.jms.frontend.FEConnectionFactory, it
seems that the Client is trying to establish a JMS connection with the server
but somehow it got stuck in the process.</FONT></DIV>
<DIV><FONT face=Arial size=2>Why is this so? Is this a SP4 bug?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Regards</FONT></DIV>
<DIV><FONT face=Arial size=2>Mike</FONT></DIV></BODY></HTML>check whether the QCF is targetted and deployed on the Managed Server. I am assuming your war is deployed on the managed server.
cheers
dips -
Cannot deploy BPM process from JDev into remote weblogic server
Hi all,
I have in a trouble!
I've built a simple BPM process but when i deploy it from JDeveloper to a remote weblogic server it have following error, pls give me solution
[02:16:27 PM] ---- Deployment started. ----
[02:16:27 PM] Target platform is (Weblogic 10.3).
[02:16:27 PM] Running dependency analysis...
[02:16:27 PM] Building...
[02:16:31 PM] Deploying profile...
[02:16:31 PM] Updating revision id for the SOA Project 'Project1.jpr' to '1.0'..
[02:16:31 PM] Wrote Archive Module to C:\JDeveloper\mywork\TestDeploy\Project1\deploy\sca_Project1_rev1.0.jar
[02:16:31 PM] Running dependency analysis...
[02:16:31 PM] Building...
[02:16:33 PM] Deploying 2 profiles...
[02:16:33 PM] Wrote Web Application Module to C:\JDeveloper\mywork\TestDeploy\Project2_UI\deploy\Project2_UI.war
[02:16:33 PM] Wrote Enterprise Application Module to C:\JDeveloper\mywork\TestDeploy\deploy\TestDeploy.ear
[02:16:33 PM] Deploying sca_Project1_rev1.0.jar to partition "default" on server AdminServer [http://HP:7001]
[02:16:33 PM] Processing sar=/C:/JDeveloper/mywork/TestDeploy/Project1/deploy/sca_Project1_rev1.0.jar
[02:16:33 PM] Adding sar file - C:\JDeveloper\mywork\TestDeploy\Project1\deploy\sca_Project1_rev1.0.jar
[02:16:33 PM] Preparing to send HTTP request for deployment
[02:16:33 PM] Creating HTTP connection to host:HP, port:7001
[02:16:33 PM] Sending internal deployment descriptor
[02:16:33 PM] Sending archive - sca_Project1_rev1.0.jar
[02:16:33 PM] Received HTTP response from the server, response code=503
[02:16:33 PM] Invalid logging line: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
[02:16:33 PM] Invalid logging line: <html><head>
[02:16:33 PM] Invalid logging level on line: <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
[02:16:33 PM] Invalid logging line: <title>ERROR: The requested URL could not be retrieved</title>
[02:16:33 PM] Invalid logging line: <style type="text/css"><!--
[02:16:33 PM] Invalid logging line: /*
[02:16:33 PM] Invalid logging line: Stylesheet for Squid Error pages
[02:16:33 PM] Invalid logging line: Adapted from design by Free CSS Templates
[02:16:33 PM] Invalid logging line: http://www.freecsstemplates.org
[02:16:33 PM] Invalid logging line: Released for free under a Creative Commons Attribution 2.5 License
[02:16:33 PM] Invalid logging line: */
[02:16:33 PM] Invalid logging line: /* Page basics */
[02:16:33 PM] Invalid logging line: * {
[02:16:33 PM] Invalid logging level on line: font-family: verdana, sans-serif;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: html body {
[02:16:33 PM] Invalid logging level on line: margin: 0;
[02:16:33 PM] Invalid logging level on line: padding: 0;
[02:16:33 PM] Invalid logging level on line: background: #efefef;
[02:16:33 PM] Invalid logging level on line: font-size: 12px;
[02:16:33 PM] Invalid logging level on line: color: #1e1e1e;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* Page displayed title area */
[02:16:33 PM] Invalid logging line: #titles {
[02:16:33 PM] Invalid logging level on line: margin-left: 15px;
[02:16:33 PM] Invalid logging level on line: padding: 10px;
[02:16:33 PM] Invalid logging level on line: padding-left: 100px;
[02:16:33 PM] Invalid logging level on line: background: url('http://www.squid-cache.org/Artwork/SN.png') no-repeat left;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* initial title */
[02:16:33 PM] Invalid logging line: #titles h1 {
[02:16:33 PM] Invalid logging level on line: color: #000000;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: #titles h2 {
[02:16:33 PM] Invalid logging level on line: color: #000000;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* special event: FTP success page titles */
[02:16:33 PM] Invalid logging line: #titles ftpsuccess {
[02:16:33 PM] Invalid logging level on line: background-color:#00ff00;
[02:16:33 PM] Invalid logging level on line: width:100%;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* Page displayed body content area */
[02:16:33 PM] Invalid logging line: #content {
[02:16:33 PM] Invalid logging level on line: padding: 10px;
[02:16:33 PM] Invalid logging level on line: background: #ffffff;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* General text */
[02:16:33 PM] Invalid logging line: p {
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* error brief description */
[02:16:33 PM] Invalid logging line: #error p {
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* some data which may have caused the problem */
[02:16:33 PM] Invalid logging line: #data {
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* the error message received from the system or other software */
[02:16:33 PM] Invalid logging line: #sysmsg {
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: pre {
[02:16:33 PM] Invalid logging level on line: font-family:sans-serif;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* special event: FTP / Gopher directory listing */
[02:16:33 PM] Invalid logging line: #dirlisting tr.entry td.icon,td.filename,td.size,td.date {
[02:16:33 PM] Invalid logging level on line: border-bottom: groove;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: #dirlisting td.size {
[02:16:33 PM] Invalid logging level on line: width: 50px;
[02:16:33 PM] Invalid logging level on line: text-align: right;
[02:16:33 PM] Invalid logging level on line: padding-right: 5px;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* horizontal lines */
[02:16:33 PM] Invalid logging line: hr {
[02:16:33 PM] Invalid logging level on line: margin: 0;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: /* page displayed footer area */
[02:16:33 PM] Invalid logging line: #footer {
[02:16:33 PM] Invalid logging level on line: font-size: 9px;
[02:16:33 PM] Invalid logging level on line: padding-left: 10px;
[02:16:33 PM] Invalid logging line: }
[02:16:33 PM] Invalid logging line: body
[02:16:33 PM] Invalid logging level on line: :lang(fa) { direction: rtl; font-size: 100%; font-family: Tahoma, Roya, sans-serif; float: right; }
[02:16:33 PM] Invalid logging level on line: :lang(he) { direction: rtl; float: right; }
[02:16:33 PM] Invalid logging line: --></style>
[02:16:33 PM] Invalid logging line: </head><body>
[02:16:33 PM] Invalid logging line: <div id="titles">
[02:16:33 PM] Invalid logging line: <h1>ERROR</h1>
[02:16:33 PM] Invalid logging line: <h2>The requested URL could not be retrieved</h2>
[02:16:33 PM] Invalid logging line: </div>
[02:16:33 PM] Invalid logging line: <hr>
[02:16:33 PM] Invalid logging line: <div id="content">
[02:16:33 PM] Invalid logging line: <p>The following error was encountered while trying to retrieve the URL: http://hp:7001/soa-infra/deployer</p>
[02:16:33 PM] Invalid logging line: <blockquote id="error">
[02:16:33 PM] Invalid logging line: <p><b>Unable to determine IP address from host name <q>hp</q></b></p>
[02:16:33 PM] Invalid logging line: </blockquote>
[02:16:33 PM] Invalid logging line: <p>The DNS server returned:</p>
[02:16:33 PM] Invalid logging line: <blockquote id="data">
[02:16:33 PM] Invalid logging line: <pre>Name Error: The domain name does not exist.</pre>
[02:16:33 PM] Invalid logging line: </blockquote>
[02:16:33 PM] Invalid logging line: <p>This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.</p>
[02:16:33 PM] Invalid logging level on line: <p>Your cache administrator is [email protected].</p>
[02:16:33 PM] Invalid logging line: <br>
[02:16:33 PM] Invalid logging line: </div>
[02:16:33 PM] Invalid logging line: <hr>
[02:16:33 PM] Invalid logging line: <div id="footer">
[02:16:33 PM] Invalid logging line: <p>Generated Tue, 20 Dec 2011 07:18:27 GMT by proxy.hipt.com.vn (squid/3.1.4)</p>
[02:16:33 PM] Invalid logging line: <!-- ERR_DNS_FAIL -->
[02:16:33 PM] Invalid logging line: </div>
[02:16:33 PM] Invalid logging line: </body></html>
[02:16:33 PM] Error deploying archive sca_Project1_rev1.0.jar to partition "default" on server AdminServer [http://HP:7001]
[02:16:33 PM] HTTP error code returned [503]
[02:16:33 PM] No error message is returned from the server.
[02:16:33 PM] Error deploying archive sca_Project1_rev1.0.jar to partition "default" on server AdminServer [http://HP:7001]
[02:16:33 PM] #### Deployment incomplete. ####
[02:16:33 PM] Error deploying archive file:/C:/JDeveloper/mywork/TestDeploy/Project1/deploy/sca_Project1_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Thanks a lot!Hi, thanks for your reply,
I just check but soa-infra is up
Result:
Welcome to the Oracle SOA Platform on WebLogic
SOA Version: v11.1.1.5.0 - 11.1.1.5.0_110418.1550.0174 built on Mon Apr 18 18:05:14 PDT 2011
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 (10.3.5.0)
I've deployed my process in local computer that good! but from remote JDev i've wrong
Help me pls! -
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,
Maybe you are looking for
-
So I just migrated (using the Assistant) my Admin account from my old Powerbook G4 to my MacBook Air (used) , but now it's disregarding its new Trackpad settings (such as scrolling and double finger tapping, etc.) It also won't let me find my Applica
-
ORA-01722: invalid number error with Bulk collect
Hi , I have been using the script to delete old seasonal data from my application DB tables. The stored procedure has been created successfully but when i try to run the proc it has been throwing 'ORA-01722: invalid number' exception at line 'FETCH C
-
I have 1500 pictures on my I phone and I started importing them to I photo, but it takes a lot of time and not completed yet? Is that normal? I am not plugging the phone all the time, so does it resume automatically when I connect it or should I do s
-
ITunes LP buttons don't work?
I just purchased Pink Floyd 'The Wall' iTunes LP version and the 'play album' button and 'song selection' button do not work when i click on them. Any ideas? the other buttons in the iTunes LP work fine. Thanks Steve
-
SUBMIT and RETUTN with ALV output
Hello Friends, I have one standard program (RSVTPROT) which returns ALV output. I want this output as internal table into my Zreport. I used SUBMIT statement with RETURN but not working. can anybody tell me what I missed? Regards, RH