Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unexplained Exception

2 views
Skip to first unread message

keddara

unread,
Jun 17, 2002, 1:52:07 PM6/17/02
to

Greetings,

Occasinally, we get the exception described below from within a stateless EJB.
Any ideas as to what may cause that to happen?
Thank you.

----------------------------------------------------------------
<Jun 6, 2002 1:08:24 PM MDT> <Warning> <Dispatcher> <RuntimeException thrown by rmi
server: 'weblogic.rmi.cluster.Clusterable ServerRef@186 - jvmid: '3953353846957644037S:172.16.16.246:[7001,7001,7002,7002,7001,7002,-1]:creekpathAIM:AIMServer',
oid: ' 390', implementation: '[BaseEJBObject] home: com.creekpath.server.advisor.policy.PolicyManagerBean_72xlol_HomeImpl@6c7b2''
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.next(HashMap.java:736)
at weblogic.rjvm.ConnectionRuntime.<init>(ConnectionRuntime.java:47)
at weblogic.rjvm.ConnectionRuntime.getConnections(ConnectionRuntime.java:19)
at weblogic.t3.srvr.ServerRuntime.getConnections(ServerRuntime.java:101)
at weblogic.ejb20.internal.BaseEJBHome.getOriginalProtocol(BaseEJBHome.java:534)
at weblogic.ejb20.internal.BaseEJBHome.getURL(BaseEJBHome.java:439)
at weblogic.ejb20.internal.HomeHandleImpl.<init>(HomeHandleImpl.java:49)
at weblogic.ejb20.internal.BaseEJBHome.getHomeHandle(BaseEJBHome.java:162)
at weblogic.ejb20.internal.HandleImpl.<init>(HandleImpl.java:110)
at weblogic.ejb20.internal.StatelessEJBObject.getHandle(StatelessEJBObject.java:37)
at com.creekpath.server.advisor.policy.PolicyManagerBean_72xlol_EOImpl_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)
>

Bob Lee

unread,
Jun 17, 2002, 2:07:34 PM6/17/02
to
You are using a HashMap in your stateless session bean. You have a local
client accessing the stateless session bean. The stateless session bean
returns a reference to the HashMap that the client iterates over. Another
client access that stateless session bean instance and modifies the HashMap
while the first client is still iterating over it.

The solution is to either use a local HashMap instance (i.e. inside of the
method), or to disable pass by reference in the WebLogic EJB deployment
descriptor.

Bob

"keddara" <kked...@creekpath.com> wrote in message
news:3d0e...@newsgroups2.bea.com...

Deyan D. Bektchiev

unread,
Jun 17, 2002, 5:28:05 PM6/17/02
to
Actually it looks more like a bug in Weblogic itself having to do with
its RMI connection management -- send this to support, they might have
seen it already and provide you with a workaround and fix.

One thing you can do to avoid some of the issues is to have your servers
in the cluster named differently but I don't think that this is the case.

HT.,

--dejan

Bob Lee

unread,
Jun 17, 2002, 6:10:28 PM6/17/02
to
I'm sorry. Should have looked closer.

Bob

"Deyan D. Bektchiev" <dejan_b...@appl.net> wrote in message
news:3D0E5465...@appl.net...

keddara

unread,
Jun 17, 2002, 6:30:23 PM6/17/02
to

Thank you for the help. Just submitted the question to BEA support and am waiting
for their explanation.
Cheers...
Karim

Rajesh Mirchandani

unread,
Jun 17, 2002, 7:59:12 PM6/17/02
to
This is a bug. Contact support and reference CR057313.

keddara wrote:

--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support


0 new messages