StuckThreadMaxTime,"weblogic.rmi.internal.dgc.DGCClientImpl$HeartBeat@53ce6

Hi guys!
I am having a problem suddenly with weblogic application server on aix box. I am getting error after couple of users login.managed Server is getting shutdown. Here is the description of the error.
<weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '47' for queue: 'weblogic.kernel.Default' has been busy for "717" seconds working on the request "weblogic.rmi.internal.dgc.DGCClientImpl$HeartBeat@53ce690f", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
Please suggest something to fix this problem.can you explain how we can check thread dumps in weblogic on unix environment.
-Chandu

Paul Eddington wrote:
Thanks for the response.
We don't have any connection pools defined.
The application we have deployed gets information from the DB all the time. But it makes it's own connection. We connect to an Oracle 9i DB running on a different server. We are running on AIX 5.3 servers.
Thanks again
PaulHi. nevermind about the pool question. If/when you get that sort of message you want to get a thread
dump of the server or find the log where it shows the full stacktrace of that thread. The message
simply says a thread has been busy or hanging longer than the WLS limit (configurable). The thread
could be hung on a lock, waiting for the DBMS, in an infinite loop, os simply not done yet with
some job that is taking more than the stuck-thread-limit. WLS doesn't actually know what the
thread is doing...
Joe

Similar Messages

Weblogic.rmi.internal.LocalServerRefMissing

I am Attempting to serialize and deserialize a stateful session
bean. The deserialization seems to be the problem. I have
figured out that the line throwing the error is the "readObject"
line.
A similar problem was reported on Jan 31 2002, but the solution
suggested deals with the "getEJBObject" line. I have tryed to
implement this solution, as you can see below, but since the
error I am getting is thrown before getting to that line, it
makes no difference.
The Exception I am getting is an "InvalidClassException".
The message reads as follows = "weblogic.rmi.internal.
LocalServerRefMissing no-arg constructor for class".
As far as the "no-arg constructor" error goes, as I understand
it I should not be having that problem. My Session bean
implements the SessionBean interface and does not explicitly
extend anything, so by default it extends Object, right?!
Object has a no-args constructor, so there should be no problem.
My code is as follows:
---SERIALIZATION---
Handle msaHandle = contributions.getHandle();
ObjectOutputStream toFile = new ObjectOutputStream(
new FileOutputStream(handleFile));
toFile.writeObject(msaHandle);
toFile.close();
---DESERIALIZATION---
ObjectInputStream fromFile = new ObjectInputStream(
new FileInputStream(handleFile));
Handle msaHandle = (Handle) fromFile.readObject();
//MsaSession contributions =
(MsaSession) msaHandle.getEJBObject();
MsaSession contributions = (MsaSession) javax.rmi.PortableRemote
Object.narrow(msaHandle.getEJBObject(), MsaSession.class);
fromFile.close();
I have tried to print "classname" (available in the
InvalidClassException class), but only get null as the value.
Anyone have any ideas?
Matthew

I am Attempting to serialize and deserialize a stateful session
bean. The deserialization seems to be the problem. I have
figured out that the line throwing the error is the "readObject"
line.
A similar problem was reported on Jan 31 2002, but the solution
suggested deals with the "getEJBObject" line. I have tryed to
implement this solution, as you can see below, but since the
error I am getting is thrown before getting to that line, it
makes no difference.
The Exception I am getting is an "InvalidClassException".
The message reads as follows = "weblogic.rmi.internal.
LocalServerRefMissing no-arg constructor for class".
As far as the "no-arg constructor" error goes, as I understand
it I should not be having that problem. My Session bean
implements the SessionBean interface and does not explicitly
extend anything, so by default it extends Object, right?!
Object has a no-args constructor, so there should be no problem.
My code is as follows:
---SERIALIZATION---
Handle msaHandle = contributions.getHandle();
ObjectOutputStream toFile = new ObjectOutputStream(
new FileOutputStream(handleFile));
toFile.writeObject(msaHandle);
toFile.close();
---DESERIALIZATION---
ObjectInputStream fromFile = new ObjectInputStream(
new FileInputStream(handleFile));
Handle msaHandle = (Handle) fromFile.readObject();
//MsaSession contributions =
(MsaSession) msaHandle.getEJBObject();
MsaSession contributions = (MsaSession) javax.rmi.PortableRemote
Object.narrow(msaHandle.getEJBObject(), MsaSession.class);
fromFile.close();
I have tried to print "classname" (available in the
InvalidClassException class), but only get null as the value.
Anyone have any ideas?
Matthew

Getting :java.lang.ClassCastException: weblogic.rmi.internal.MethodDescript

Hi I am getting the following exception:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
     at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:186)
     at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:300)
     at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:901)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:361)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1181)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:110)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
can any body explain the Cause for this exception and what will be the impact on the server.
but if i restart the server the error is not coming

Hi I am getting the following exception:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
     at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:186)
     at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:300)
     at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:901)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:361)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1181)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:110)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
can any body explain the Cause for this exception and what will be the impact on the server.
but if i restart the server the error is not coming

Weblogic.rmi.internal.BasicRemoteRef and ClusterableRemoteRef

Hi,
I have a ejb3 stateless session bean deployed on a wls 10 mp1 cluster (1 Admin + 2 Managed Servers).
The client side reference is a:
weblogic.rmi.internal.BasicRemoteRef when invocations go to Managed Server1
and
ClusterableRemoteRef when invocations go to Managed Server2
Is this indicative of a problem in cluster setup etc. ?
Thanx,

Hi ! I have a similar problem.
I have an EJB3 stateless bean on a WLS clustered server, in the same machine, server1 and sever2.This EJB3 is deployed in a application called appli.ear
My client is messageDrivenBean mdb deployed in another ear application client.ear , in the same machine, in the same clustered server.
Sometimes, my client call is succesfull, but most often, my lookup fails with java.lang.class.cast Exception.This exception is thrown because i get weblogic.rmi.internal.BasicRemoteRef class from my lookup.When my call is succeful ,i get weblogic.rmi.internal.CollocatedRemoteRef class.
Is it the same problem ? Must i get patch you are talking about?

Nullpointer in 'weblogic.transaction.internal.CoordinatorImpl

          I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
          My server has a transacted EJB which accesses Oracle and DB2 databases. I have
          been running my application for several months.
          Suddenly, yesterday it starting spitting out these exceptions a few times a minute.
          I cannot find the configuration change I made that would have caused this to
          suddenly start appearing. My code has not changed in 2 weeks.
          Has anyone seen this error before? Does anyone know what causes this, so that
          I can narrow my search?
          Thanks for your help,
          Tania
          ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025> <cuAS01> <ExecuteThread:
          '5' for queue: 'default'> <system> <> <000000> <RuntimeException thrown by rmi
          server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid: '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:qdomain4:cuAS01',
          oid: '261', implementation: 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
          java.lang.NullPointerException
          at weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignableTo(ServerResourceInfo.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
          Code))
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compiled
          Code))
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(Compiled
          Code))
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


          Thanks,
          The problem did clear up when the Unix server had to get bounced. I believe it
          was bounced for an unrelated issue.
          The one thing I noticed was that there were a couple of copies of my EJBs in the
          wlnotdelete directory that the server had been previously compliaining about.
          They went away after the Unix server was restarted and the NullPointer problem
          went away.
          We plan to upgrade to 7.1 soon, but will try to move to SP5 if we need to sooner.
          Thanks for your help.
          Tania Rhinehart
          Rajesh Mirchandani <[email protected]> wrote:
          >This is fixed in SP5. Open a case with [email protected] and reference
          >CR092301.
          >
          >Slava Imeshev wrote:
          >
          >> Hi Tania,
          >>
          >> I think you need to contact BEA support at [email protected]
          >>
          >> Regards,
          >>
          >> Slava Imeshev
          >>
          >> "Tania Rhinehart" <[email protected]> wrote in message
          >> news:[email protected]...
          >> >
          >> > I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
          >> > My server has a transacted EJB which accesses Oracle and DB2 databases.
          > I
          >> have
          >> > been running my application for several months.
          >> > Suddenly, yesterday it starting spitting out these exceptions a few
          >times
          >> a minute.
          >> > I cannot find the configuration change I made that would have caused
          >this
          >> to
          >> > suddenly start appearing. My code has not changed in 2 weeks.
          >> >
          >> > Has anyone seen this error before? Does anyone know what causes
          >this, so
          >> that
          >> > I can narrow my search?
          >> >
          >> > Thanks for your help,
          >> > Tania
          >> >
          >> > ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025>
          >> <cuAS01> <ExecuteThread:
          >> > '5' for queue: 'default'> <system> <> <000000> <RuntimeException
          >thrown by
          >> rmi
          >> > server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid:
          >> '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:q
          >> domain4:cuAS01',
          >> > oid: '261', implementation:
          >> 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
          >> >
          >> > java.lang.NullPointerException
          >> > at
          >> weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignable
          >> To(ServerResourceInfo.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
          >> rverTransactionImpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
          >> rverTransactionImpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
          >> ctionImpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorI
          >> mpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
          >> > Source)
          >> > at
          >> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compi
          >> led
          >> > Code))
          >> > at
          >> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(C
          >> ompiled
          >> > Code))
          >> > at
          >> weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
          >> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >> >
          >
          >--
          >Rajesh Mirchandani
          >Developer Relations Engineer
          >BEA Support
          >
          >

I have a question about weblogic RMI , how can I resolve it.Thank you

I have a question about the weblogic RMI .
I have a program.web services+weblogic RMI +Data Sources When I run the program in the console application.it is ok.But When i run it with the web services(it 'is mean Get some parameter and run the different program).it's fail.The Exception is
cannot assign instance of yype weblogic.rmi.RMIServices_1033_WLStub to field demo.RMIServer_1033_WLStub.stubinfo of type weblogic.rmi.internal.StubInfo in instance of demo.RMIEsrver_1033_WLStub
how to resolve .Thank you.

Hi Charles,
Parental Controls has always had problems with https sites, no idea if it's fixed in 10.9.x or not.
When you setup your Mac it shouldv'e made an admin account, are you not running from that account, or did you somehow change it to a Managed account???

Java.io.NotSerializableException: weblogic.ejb20.internal.EntityEJBContextImpl

Hi,
We are currently in the process of moving from Weblogic 6.1 SP5 and
Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
I have seen a "scaring" stack trace. It seems that, for some reason, a
thing that "uses to work" failed with a very strange error. I tried to
reproduce it but without any success. Besides asking if anybody knows
what could have caused this error I would like to know what the "not
serializable" object is. Is it the EntityEJBContext?
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
In case it could share some light in the case I will explain a bit what
does the process intended to do:
The general idea is that, given some data (managed with Toplink's 9.0.4
CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
has been working for ages without any problem) and "publish" it via JMS
in order to perform asyncronous actions with it. I'm sure this is a,
more than usual, scenario for a lot of folks.
As it seems looking at the stack at some point during some internal
object serialization it fails and rollbacks all the process. The object
being serialized by our side only contains four attributes: a
java.math.BigDecimal for it's primary key, a java.util.Date for
timestamp locking and two simple java.lang.String's
Although I'm pretty sure the problem should not be with the entity bean
itself but with an internal Weblogic op (is it trying to serialize the
EntityBeanContext as stated after the java.io.NotSerializableException
message?
Any help with this would be greatly appreciated as I have no clue how
this happened and I'm also unable to reproduce it (I'm also sure if I
managed to trigger it testing the application alone it will rise many
more times that could be admited if we move to production).
I would like to point also that currently until we have some more time
to fix it we are using "remote" entity bean, I mean even if we are alway
s calling them within the container they are not deployed with "local"
interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
being co-located with the session beans).
Regards.
Ignacio.
P.S. here is the full stack dump
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at
app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
at
app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
at app.biz.common.Publisher.performPublication(Publisher.java:1644)
at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
at app.biz.module.ModuleDAO.update(ModuleDAO.java)
at
app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at app.core.util.Proxy.execute(Proxy.java:583)
at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
at
app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
at
app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Ignacio,
6.1 used pass-by-reference by default, so parameters to beans were
passed by reference.
It's very likely that you are getting this error because in 8.1 this default
was turned off. This causes serialization of parameters by default and
that's why your code that worked started failing - you just did not know
that you were passing non-serializable objects around.
To fix this you could either turn on the pass-by-reference explicitly and/or
find out where your code is passing non-serializable objects. This is a useful
exercise anyways.
Hope this helps.
Regards,
Slava Imeshev
"Ignacio G. Dupont" <[email protected]> wrote in message news:41b8c93f@mail...
Hi,
We are currently in the process of moving from Weblogic 6.1 SP5 and
Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
I have seen a "scaring" stack trace. It seems that, for some reason, a
thing that "uses to work" failed with a very strange error. I tried to
reproduce it but without any success. Besides asking if anybody knows
what could have caused this error I would like to know what the "not
serializable" object is. Is it the EntityEJBContext?
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
In case it could share some light in the case I will explain a bit what
does the process intended to do:
The general idea is that, given some data (managed with Toplink's 9.0.4
CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
has been working for ages without any problem) and "publish" it via JMS
in order to perform asyncronous actions with it. I'm sure this is a,
more than usual, scenario for a lot of folks.
As it seems looking at the stack at some point during some internal
object serialization it fails and rollbacks all the process. The object
being serialized by our side only contains four attributes: a
java.math.BigDecimal for it's primary key, a java.util.Date for
timestamp locking and two simple java.lang.String's
Although I'm pretty sure the problem should not be with the entity bean
itself but with an internal Weblogic op (is it trying to serialize the
EntityBeanContext as stated after the java.io.NotSerializableException
message?
Any help with this would be greatly appreciated as I have no clue how
this happened and I'm also unable to reproduce it (I'm also sure if I
managed to trigger it testing the application alone it will rise many
more times that could be admited if we move to production).
I would like to point also that currently until we have some more time
to fix it we are using "remote" entity bean, I mean even if we are alway
s calling them within the container they are not deployed with "local"
interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
being co-located with the session beans).
Regards.
Ignacio.
P.S. here is the full stack dump
<12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
weblogic.kernel.Default]:Exception:
javax.transaction.TransactionRolledbackException at getXML
javax.transaction.TransactionRolledbackException: EJB Exception: :
java.io.NotSerializableException:
weblogic.ejb20.internal.EntityEJBContextImpl
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at
app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
Source)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at
app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
at
app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
at app.biz.common.Publisher.performPublication(Publisher.java:1644)
at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
at app.biz.module.ModuleDAO.update(ModuleDAO.java)
at
app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at app.core.util.Proxy.execute(Proxy.java:583)
at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
at
app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
at
app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Weblogic.management.internal.RemoteMBeanServerImpl.invoke

Hello,
I' d like to use Spotlight for Weblogic on our production system, which containes 4 wls node with 1 admin srv (WLS 7.0 sp2). When I start monitor the system with Spotlight, I get the following messages continously in my servers' logs for every jar which are deployed as an application:
<Exception thrown by rmi server: weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)
javax.management.InstanceNotFoundException: PA:Application=amBeans,Name=Up.jar,Type=EJBComponent
javax.management.InstanceNotFoundException: PA:Application=amBeans,Name=Up.jar,Type=EJBComponent
     at com.sun.management.jmx.MBeanServerImpl.getMBean(MBeanServerImpl.java:1680)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1524)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:952)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>
I had a case with Quest, but they gave up. Spotlight seems to work fine, but my logs become unreadable and huge in size...
Any suggestion?

yes, the problem is that users and groups must be administered from the external authentication provider, NOT the bea console

ClassCastException:class weblogic.servlet.internal.ROIDLookupImp

          I am seeing this error in the application server logs. It does not indicate to
          any application. I will greatly appreciate any help with this.
          <RuntimeException thrown by rmi server(class weblogic.servlet.internal.ROIDLookupImpl)
          weblogic.servlet.internal.ROIDLookupImpl@b9585e>
          java.lang.ClassCastException
          at weblogic.servlet.internal.ROIDLookupImpl.lookupROID(ROIDLookupImpl.java,
          Compiled Code)
          at weblogic.servlet.internal.ROIDLookup_WLSkel.invoke(ROIDLookup_WLSkel.java,
          Compiled Code)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java,
          Compiled Code)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java,
          Compiled Code)
          at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java,
          Compiled Code)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
          Compiled Code)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java, Compiled
          Code)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
          Udit


If you are having a cluster, make sure all the servers are on the same set
          of service packs.
          -Sabha
          "Udit Singh" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I am seeing this error in the application server logs. It does not
          indicate to
          > any application. I will greatly appreciate any help with this.
          >
          >
          > <RuntimeException thrown by rmi server(class
          weblogic.servlet.internal.ROIDLookupImpl)
          > weblogic.servlet.internal.ROIDLookupImpl@b9585e>
          >
          > java.lang.ClassCastException
          > at
          weblogic.servlet.internal.ROIDLookupImpl.lookupROID(ROIDLookupImpl.java,
          > Compiled Code)
          > at
          weblogic.servlet.internal.ROIDLookup_WLSkel.invoke(ROIDLookup_WLSkel.java,
          > Compiled Code)
          > at
          weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java,
          > Compiled Code)
          > at
          weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java,
          > Compiled Code)
          > at
          weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
          java,
          > Compiled Code)
          > at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
          > Compiled Code)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java,
          Compiled
          > Code)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
          Code)
          >
          > Udit

Java.lang.ClassCastException: Cannot narrow remote object weblogic.rmi.inte

Hi,
I am trying to deploy ejb3.0 on weblogic 10 server. I am able to find the JNDI name of the stateless session bean correctly, but getting an exception while narrowing it down. My ejb3.0 client is a standalone java client. I am trying to access the stateless session ejb3.0 bean.Please help me. i have been trying it for many days.
thanks in advance,
Sanjeev
[sanpraka@localhost certEjb]$ java -cp ./:/usr/weblogic/bea/wlserver_10.0/server/lib/weblogic.jar:/usr/weblogic/bea/wlserver_10.0/server/lib/wlclient.jar com.titan.clients.Client
Object is weblogic.rmi.internal.BasicRemoteRef - hostID: '5337880647112897730S:127.0.0.1:[7001,7001,-1,-1,-1,-1,-1]:wl_server:examplesServer', oid: '302', channel: 'null'
java.lang.ClassCastException: Cannot narrow remote object weblogic.rmi.internal.BasicRemoteRef - hostID: '5337880647112897730S:127.0.0.1:[7001,7001,-1,-1,-1,-1,-1]:wl_server:examplesServer', oid: '302', channel: 'null' to com.titan.travelagent.TravelAgentRemote
at weblogic.corba.server.naming.ReferenceHelperImpl.narrow(ReferenceHelperImpl.java:206)
at weblogic.rmi.extensions.PortableRemoteObject.narrow(PortableRemoteObject.java:88)
at weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteObjectDelegateImpl.java:32)
at javax.rmi.PortableRemoteObject.narrow(Unknown Source)
at com.titan.clients.Client.main(Client.java:24)
[sanpraka@localhost certEjb]$

We have a similar problem. We have a web application (on server A) that invokes an EJB on a remote server (server B). This works fine, until we deploy another web application to server A at which point the existing web application starts to throw java.lang.ClassCastException when narrowing the remote EJB interface. The exception starts to be thrown at the moment the latter web application is deployed - start is not required.
The latter web application contains (actually in APP-INF/lib) the old version of the EJB remote interface, that somehow gets to be loaded into the classpath of the existing web application. The solution is to delete the old version of the EJB remote interface from APP-INF/lib of the latter web application (we didn't need it anyway), but it would be interesting to know in which circumstances classes can get mixed between enterprise applications.
I failed to reproduce the error in simple scenario, so this does not happen always.

WLS 10.3 - BEA-000337 with request weblogic.servlet.internal.ServletRequest

Hi,
we have an 7x24 hour application which causes sometimes (error happend e.g. 4 times in 2 weeks) following error:
=====================
<30.06.2009 14:41 Uhr CEST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "615" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@1885c28[
GET /tls-lmrg-ViewController-context-root/faces/lmrg0001.jspx?_adf.ctrl-state=373697585_3&Adf-Rich-Message=true&unique=1246365071463&oracle.adf.view.rich.STREAM=j_id_id4:tableWa&javax.faces.ViewState=!5ea5ac22&oracle.adf.view.rich.forceHTML=true HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, */*
Referer: http://trnas029:7001/tls-lmrg-ViewController-context-root/faces/lmrg0001.jspx?_adf.ctrl-state=373697585_3
Accept-Language: de
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)
Connection: Keep-Alive
Cookie: JSESSIONID=nGrHKG6SWG2Tg2Z515GzlxhJFRw1pdX7Gm3F1YYcL23ppXHy3kgj!-2050079672
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.io.FileOutputStream.writeBytes(Native Method)
java.io.FileOutputStream.write(FileOutputStream.java:260)
java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
java.io.PrintStream.write(PrintStream.java:430)
sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
java.util.logging.StreamHandler.flush(StreamHandler.java:225)
java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:89)
java.util.logging.Logger.log(Logger.java:472)
oracle.adf.share.logging.ADFLogger.doLog(ADFLogger.java:1747)
oracle.adf.share.logging.ADFLogger.log(ADFLogger.java:430)
oracle.adf.share.logging.ADFLogger.severe(ADFLogger.java:986)
oracle.adfinternal.view.faces.model.binding.CurrencyRowKeySet._computeCurrentRowKey(CurrencyRowKeySet.java:146)
oracle.adfinternal.view.faces.model.binding.CurrencyRowKeySet.iterator(CurrencyRowKeySet.java:37)
oracle.adfinternal.view.faces.renderkit.rich.TableRendererUtils.writePojoSelectionState(TableRendererUtils.java:308)
oracle.adfinternal.view.faces.renderkit.rich.TableRenderer.renderDataBlockRows(TableRenderer.java:1608)
oracle.adfinternal.view.faces.renderkit.rich.TableRenderer._renderSingleDataBlock(TableRenderer.java:1488)
oracle.adfinternal.view.faces.renderkit.rich.TableRenderer._handleDataFetch(TableRenderer.java:918)
oracle.adfinternal.view.faces.renderkit.rich.TableRenderer.encodeAll(TableRenderer.java:394)
oracle.adf.view.rich.render.RichRenderer.encodeAll(RichRenderer.java:1050)
org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224)
org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:763)
org.apache.myfaces.trinidad.component.UIXCollection.encodeEnd(UIXCollection.java:533)
org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:70)
oracle.adfinternal.view.faces.util.rich.InvokeOnComponentUtils$RenderCallback.invokeContextCallback(InvokeOnComponentUtils.java:97)
org.apache.myfaces.trinidad.component.UIXCollection.invokeOnComponent(UIXCollection.java:1030)
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.invokeOnComponent(ContextSwitchingComponent.java:153)
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.invokeOnComponent(ContextSwitchingComponent.java:153)
oracle.adf.view.rich.component.fragment.UIXPageTemplate.invokeOnComponent(UIXPageTemplate.java:208)
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:664)
oracle.adfinternal.view.faces.util.rich.InvokeOnComponentUtils.renderChild(InvokeOnComponentUtils.java:29)
oracle.adfinternal.view.faces.streaming.StreamingDataManager._pprComponent(StreamingDataManager.java:577)
oracle.adfinternal.view.faces.streaming.StreamingDataManager.execute(StreamingDataManager.java:442)
oracle.adfinternal.view.faces.renderkit.rich.DocumentRenderer._encodeStreamingResponse(DocumentRenderer.java:2124)
oracle.adfinternal.view.faces.renderkit.rich.DocumentRenderer.encodeAll(DocumentRenderer.java:787)
oracle.adf.view.rich.render.RichRenderer.encodeAll(RichRenderer.java:1050)
org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:224)
org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:763)
org.apache.myfaces.trinidad.component.UIXComponentBase.__encodeRecursive(UIXComponentBase.java:1351)
org.apache.myfaces.trinidad.component.UIXComponentBase.encodeAll(UIXComponentBase.java:783)
javax.faces.component.UIComponent.encodeAll(UIComponent.java:942)
com.sun.faces.application.ViewHandlerImpl.doRenderView(ViewHandlerImpl.java:273)
com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:204)
javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:188)
oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:652)
oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:243)
oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:203)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:181)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:278)
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:238)
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:195)
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138)
org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
weblogic.security.service.SecurityManager.runAs(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
========================
Application is developed with ADF 11g (11.1.1.0.2) and only refreshes a graph periodically via af:poll.
Any ideas what I can do to analyze and resolve the problem?
regards
Peter

repost

Java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl

Hi All,
I have recently encountered very very unusual problem which am not able to understand. If you could kindly shade some light on that it would be of great help. I have three environment where the application is being deployed. In the first two environment it works fine without any problem. But when I deployed in the third environment it behave very funny. The full stack trace of the error is bellow:
Exception in EJBTestClient: java.rmi.RemoteException: ; nested exception is:
weblogic.rmi.ServerError: A RemoteException occurred in the server metho
d
- with nested exception:
[java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method findMeth
The problem occurs when I try to call EJB from client. When I re-build the EJBS on the same environment it works fine. Am not able to understand this unusual behavior. If you could kindly help me understand the problem it would of great help. The environments are as follows.
ENV-1
OS - SunOS 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-Enterprise
JDK - Solaris VM (build Solaris_JDK_1.2.2_07, native threads, sunwjit)
Weblogic - 5.1.0 Service Pack 8 12/20/2000 16:34:54 #95137
Oracle � 8.1.6
ENV-2
OS - SunOS 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-Enterprise
JDK - Solaris VM (build Solaris_JDK_1.2.2_07, native threads, sunwjit)
Weblogic - 5.1.0 Service Pack 9 04/06/2001 12:10:43 #105983
Oracle � 8.1.6
ENV-3
OS - SunOS cfesit 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-Enterprise
JDK - Solaris VM (build Solaris_JDK_1.2.2_07, native threads, sunwjit)
Weblogic - 5.1.0 Service Pack 9 04/05/2001 14:59:53 #105983
Oracle � 8.1.6
The problem occurs in the 3rd environment.
Cheers,
Tapas

Hi..
I guess itzz more of the service pack problems.
Jars built on the later version won't work in the previous version (service packs) of weblogic.
Try building a jar on the oldest version (service pack) u have and then try deploying it to the later version , i think it won't give u any problems.
Try it out and let me know if u face any problems

CMP Bean - weblogic.transaction.internal.TimedOutException

Hi,
I have two CMP beans. Bean1 is stateless bean and Bean2 is stateful. I am
using a method of Bean2 from Bean1 and later on call Bean1.remove(). Now, I
am getting the following error in my application. I would appreciate any
help.
Thanks,
SamK
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
weblogic.transaction.internal.TimedOutException: Transaction timed out after
62 seconds
2240:505a02f68bbeb855
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1214)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:888)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1695)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:813)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1661)
at java.lang.Thread.run(Thread.java:479)

Do you really mean to say 'CMP beans'? Usually the terms stateless and
stateful are applied to
session beans.
Seth
"Sameer Karmarkar" <[email protected]> wrote in message
news:[email protected]..
Hi,
I have two CMP beans. Bean1 is stateless bean and Bean2 is stateful. I am
using a method of Bean2 from Bean1 and later on call Bean1.remove(). Now,I
am getting the following error in my application. I would appreciate any
help.
Thanks,
SamK
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
weblogic.transaction.internal.TimedOutException: Transaction timed outafter
>
62 seconds
2240:505a02f68bbeb855
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
>
Impl.java:1214)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
>
ansactions(ServerTransactionManagerImpl.java:888)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
>
erImpl.java:1695)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
>
sactionManagerImpl.java:813)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
>
rImpl.java:1661)
at java.lang.Thread.run(Thread.java:479)

Weblogic.jndi.internal.RootNamingNode by Startup

Hi,
I have definied a ConnectionPool, but in Startup exception raised:
Anyone knows why?
Interesting, I can see my connectionpool in "View JNDI tree" at the Consol. But
trying to use it from an EJB exception raised:
java.sql.SQLException: Connection Pool SEOInterBaseConnectionPool does not exist.
####<01.03.2001 10:35:39 GMT+01:00> <Info> <JDBC Connection Pool> <pc0194> <rpcserver>
<main> <system> <> <000000> <Connection for pool "SEOInterBaseConnectionPool"
created.>
####<01.03.2001 10:35:39 GMT+01:00> <Info> <Adapter> <pc0194> <rpcserver> <main>
<system> <> <000000> <Exception thrown by rmi server(class weblogic.jndi.internal.RootNamingNode)
[-7684374466692944493S:10.2.3.119:[7001,7001,7002,7002,7001,7002,-1]/9]: weblogic.jndi.internal.RootNamingNode@951a0>
javax.naming.NameNotFoundException: Unable to resolve weblogic.jdbc.connectionPool
Resolved: 'weblogic' Unresolved:'jdbc' ; remaining name 'connectionPool'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
     at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)

Hi,
I have definied a ConnectionPool, but in Startup exception raised:
Anyone knows why?
Interesting, I can see my connectionpool in "View JNDI tree" at the Consol. But
trying to use it from an EJB exception raised:
java.sql.SQLException: Connection Pool SEOInterBaseConnectionPool does not exist.
####<01.03.2001 10:35:39 GMT+01:00> <Info> <JDBC Connection Pool> <pc0194> <rpcserver>
<main> <system> <> <000000> <Connection for pool "SEOInterBaseConnectionPool"
created.>
####<01.03.2001 10:35:39 GMT+01:00> <Info> <Adapter> <pc0194> <rpcserver> <main>
<system> <> <000000> <Exception thrown by rmi server(class weblogic.jndi.internal.RootNamingNode)
[-7684374466692944493S:10.2.3.119:[7001,7001,7002,7002,7001,7002,-1]/9]: weblogic.jndi.internal.RootNamingNode@951a0>
javax.naming.NameNotFoundException: Unable to resolve weblogic.jdbc.connectionPool
Resolved: 'weblogic' Unresolved:'jdbc' ; remaining name 'connectionPool'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
     at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)

Undocumented weblogic.ejb20.internal.MethodPermissionException?

Environment: Weblogic 6.0 sp2 w/ ejb20.jar.
We are experimenting with security and noticed that if a client to an ejb
(session bean in our case) attempts to make a method call that they do not
have permission for (due to the descriptor .xml file roles), the exception
that is thrown on the client is this very proprietary sounding and
undocumented exception:
weblogic.ejb20.internal.MethodPermissionException
Using reflection we can see that this exception class has this lineage:
weblogic.ejb20.internal.MethodPermissionException
java.rmi.RemoteException
java.io.IOException
java.lang.Exception
java.lang.Throwable
java.lang.Object
Can you provide any more info on this? Ideally I'd like to be able to
distinguish between the very generic RemoteException, but not code such
undocumented exception names into my files (i.e. it sounds like the name of
this "internal" exception could easily change with a service pack or
something and then we'd be hosed).
Thanks,
- John Freeborg

Lourdes,
We are encountering the exact same issue and thread dump. Did you ever determine a resolution?
An example thread dump from our server.
"ExecuteThread: '38' for queue: 'rplarge1'" daemon prio=10 tid=009e7460 nid=111 lwp_id=1102694 in Object.wait() [0x0e611000..0x0e6104f0]
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.jms.store.StoreRequest.waitForIOComplete(StoreRequest.java:465)
     - locked <5593dbe0> (a weblogic.jms.store.StoreRequest)
     at weblogic.jms.backend.BEXATranEntrySend.finishPrepare(BEXATranEntrySend.java:61)
     at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:943)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1195)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:411)
     at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.Kernel.executeIfIdle(Kernel.java:378)
     at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:244)
     at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:2301)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2015)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:244)
     at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:299)
     at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:140)
We are running wls8.1sp3 on HPUX.
Thanks

StuckThreadMaxTime,"weblogic.rmi.internal.dgc.DGCClientImpl$HeartBeat@53ce6

Similar Messages

Maybe you are looking for