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

java.rmi.NoSuchObjectException: RemoteInvokable - id: '280'

4 views
Skip to first unread message

Judy

unread,
Dec 27, 2001, 3:52:37 PM12/27/01
to
A response on the newsgroup indicated that more information regarding this problem would be provided: This is a known problem. I believe it has something to do with
the timeouts on the distributed garbage collection and the
timeouts on the cluster heartbeat. Will have someone else post
with the real story.

_sjz.

This entry was dated Nov 28. May we expect a response anytime soon?

Zach

unread,
Jan 1, 2002, 2:08:46 PM1/1/02
to
Sorry. I delegated. My mistake. As always, this is an informal support
channel patrolled by engineers in their free time. Entering a support case
is the best way to drive a problem to resolution. While you are doing
that, try adding the following attribute to your server definition in your
configuration file and let us know how that works for you.

<Server
DGCIdlePeriodsUntilTimeout=10
/>

"Judy" <judy...@pcshs.com> wrote in message
news:3c2b8a15$1...@newsgroups.bea.com...

Dave Gray

unread,
Jan 15, 2002, 10:16:15 AM1/15/02
to
Suddenly yesterday I started getting lots of these exceptions. I am test
running a 2 appsever cluster with WebLogic 6.1 sp 2.

Should the solution you offered below still apply? I'm not sure exactly what
has to be done. For each server I have a config entry like:

<Server Cluster="OpusCluster" ListenAddress="opus-dev03" Machine="dev03"
Name="OpusServer03">
<KernelDebug Name="OpusServer03" />
<WebServer Name="OpusServer03" />
<ExecuteQueue Name="default" ThreadCount="15" />
<SSL Name="OpusServer03" />
<ServerDebug Name="OpusServer03" />
<ServerStart Name="OpusServer03" />
<Log FileName="OpusServer03.log" Name="OpusServer03" />
</Server>

Do I add the DGCIdlePeriodsUntilTimeout entry somewhere in this section? Is
order important?

Is there any other information on this exception? It appears to be happening
when our network or one of the servers slows down.

Thanks,

Dave

"Zach" <za...@nospam.com> wrote in message
news:3c32...@newsgroups.bea.com...

Zach

unread,
Jan 15, 2002, 11:45:11 AM1/15/02
to
If you are getting the same exception, then yes, it should work. Just
add the line to your server configuration like I have done after the
Name="OpusServer03" below.

> <Server Cluster="OpusCluster" ListenAddress="opus-dev03" Machine="dev03"

> Name="OpusServer03" DGCIdlePeriodsUntilTimeout=10>


> <KernelDebug Name="OpusServer03" />
> <WebServer Name="OpusServer03" />
> <ExecuteQueue Name="default" ThreadCount="15" />
> <SSL Name="OpusServer03" />
> <ServerDebug Name="OpusServer03" />
> <ServerStart Name="OpusServer03" />
> <Log FileName="OpusServer03.log" Name="OpusServer03" />
> </Server>

_sjz.


Dave Gray

unread,
Jan 16, 2002, 1:30:33 PM1/16/02
to
When I make this change I get the following exception when I try to start
the admin server:

***************************************************************************
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: Error parsing
configur
ation on line 17, column 72
at
weblogic.management.internal.xml.ConfigurationParser.parse(Configurat
ionParser.java:122)
at
weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
Repository.java:261)
at
weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
Repository.java:223)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy1.loadDomain(Unknown Source)
at
weblogic.management.AdminServer.configureFromRepository(AdminServer.j
ava:188)
at weblogic.management.AdminServer.configure(AdminServer.java:173)
at weblogic.management.Admin.initialize(Admin.java:239)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
***************************************************************************

Line 17, column 72 is the "=" in the expression
"DGCIdlePeriodsUntilTimeout=10".

Dave

"Zach" <za...@nospam.com> wrote in message

news:3c44...@newsgroups.bea.com...

Tom Barnes

unread,
Jan 16, 2002, 1:44:39 PM1/16/02
to Dave Gray
Zach had a syntax error.
There needs to be a set of quotes around the 10. It should read
DGCIdlePeriodsUntilTimeout="10"

Dave Gray

unread,
Jan 16, 2002, 2:13:50 PM1/16/02
to
Thanks Tom, that worked much better.

"Tom Barnes" <dev....@not.my.address.com> wrote in message
news:3C45CA17...@not.my.address.com...

0 new messages