DGCserver
I am working with Weblogic 6.1 and testing a data access class. The data access
class calls another class, and passes it a connection. The second class is being
called many times before the first class finishes and returns a result. While
the test is running, I am getting several messages in the console as follows:
<Feb 26, 2003 9:42:38 AM MST> <Info> <DGCserver> <Tried to renew lease on lost
reference: '30869'>
I have checked to make sure that the PreparedStatements and ResultSets are closed
when no longer needed. The test eventually finishes, and returns the results.
The problem started when I added the code that calls the second class. I use the
second class in other places, and have not seen this problem before, but it isn't
called as many times as in the current test.
Any suggestions?
Thanks, Tom K
Hi Tom,
"Tom Koenning" <[email protected]> wrote in message
news:3e5e6a9d$[email protected]..
>
I am working with Weblogic 6.1 and testing a data access class. The dataaccess
class calls another class, and passes it a connection. The second class isbeing
called many times before the first class finishes and returns a result.While
the test is running, I am getting several messages in the console asfollows:
<Feb 26, 2003 9:42:38 AM MST> <Info> <DGCserver> <Tried to renew lease onlost
reference: '30869'>
I have checked to make sure that the PreparedStatements and ResultSets areclosed
when no longer needed. The test eventually finishes, and returns theresults.
The problem started when I added the code that calls the second class. Iuse the
second class in other places, and have not seen this problem before, butit isn't
called as many times as in the current test.
Any suggestions?DGCCerver stands for Distributed Garbage Collection Server. Normally
it happens when a client dies leaving RMI objects, like Connections, open.
Server tries to renew lease on such a disappeared object and gives up.
This message is harmless. AFAIR it was suppressed in 6.1 SP3.
Regards,
Slava Imeshev
Similar Messages
-
DGCserver messages in log... "Tried to renew lease on lost reference"
Hi,
I am running weblogic server 6.1 and get the following messages
####<Jan 30, 2002 2:36:55 PM CST> <Info> <DGCserver> <MBarton> <myserver> <ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Tried to renew lease on lost reference: '706'>
I have seen in the newsgroup that this was a problem previously in version 4.5.1
any help would be appreciated.
best regards,
Mickey
This shouldn't cause any problems. Does it? We will turn off these info messages.
Cheers,
-- Prasad
Mickey Barton <[email protected]> wrote:
>Hi,
>I am running weblogic server 6.1 and get the following messages
>
>####<Jan 30, 2002 2:36:55 PM CST> <Info> <DGCserver> <MBarton> <myserver>
><ExecuteThread: '12' for queue: 'default'> <> <> <000000> <Tried to
>renew lease on lost reference: '706'>
>
>I have seen in the newsgroup that this was a problem previously in version
>4.5.1
>
>any help would be appreciated.
>
>best regards,
>Mickey
-
DGCServer messages in log... "tried to renew lease"
Hi,
I'm running three WL 4.5.2 servers clustered, JDK1.1.7b on Solaris 2.6.
Normally the cluster runs just fine, but now I'm beginning to see the
following message in all three servers:
<DGCserver> tried to renew lease for lost ref: nnn
Usually they come in small bursts of about 5 or 10 messages that are the
same, except the "ref"s keep increasing. I'm guessing it has to do something
with the in-memory replication of sessions (which I'm using).
Any ideas? I tried restarting the servers but after a little while the
messages started again.
Thanks,
Matias
One common symptom for this (Bad Status Exception) has been long gc. If gc
takes more 30 seconds then you will start seeing these errors. To assertain
this, you could turn on weblogic.debug.cluster=1 and if you see a message "Timed
out server" in the log then you should tune your server.
Please use latest service packs.
thanks
- Prasad
Matias Pelenur wrote:
> Well, after a few restarts the DGC messages aren't appearing anymore... But
> something different is happening now which seems to be worse... And it's
> affecting performance too. For some pages, one of the servers will throw a
> bunch of exceptions (see below), and it seems it's cutting off the output so
> pages get only half-created. Any ideas? I don't think I changed any settings
> or anything like that.
>
> Thanks,
> Matias
>
> Fri Sep 15 11:19:15 EDT 2000:<E> <HTTP> Servlet request terminiated with
> Error:
> Fri Sep 15 11:19:15 EDT 2000:<E> <HTTP>
> weblogic.cluster.replication.BadStatusException: update found
> 1802540915606489052 but it is not the secondary
> at weblogic.rmi.extensions.BasicRequest.sendReceive(Compiled Code)
> at
> weblogic.cluster.replication.ReplicationManager_WLStub.update(Compiled Code)
> at
> weblogic.cluster.replication.ReplicationManager.updateSecondary(Compiled
> Code)
> at weblogic.servlet.internal.session.ReplicatedSession.sync(Compiled
> Code)
> at
> weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Compiled
> Code)
> at weblogic.servlet.internal.ServletRequestImpl.syncSession(Compiled
> Code)
> at
> weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
> at
> weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
> at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
> at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
> at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
> --------------- nested within: ------------------
> weblogic.utils.NestedError: Tried to update secondary, but it thought it was
> the primary
> - with nested exception:
> [weblogic.cluster.replication.BadStatusException: update found
> 18025409156064890
> 52 but it is not the secondary]
> at java.lang.Throwable.<init>(Compiled Code)
> at java.lang.Error.<init>(Compiled Code)
> at weblogic.utils.NestedError.<init>(Compiled Code)
> at weblogic.servlet.internal.session.ReplicatedSession.sync(Compiled
> Code)
> at
> weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Compiled
> Code)
> at weblogic.servlet.internal.ServletRequestImpl.syncSession(Compiled
> Code)
> at
> weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
> at
> weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
> at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
> at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
> at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
>
> "Prasad Peddada" <[email protected]> wrote in message
> news:[email protected]...
> > Is this causing any problems on the server. Like unable to create sessions
> for
> > servlets/jsp's
> >
> > If so, this is related to DGC bug, if not then it is something else,
> unless we
> > know the object it is trying to find, I can't be of much help.
> >
> > - Prasad
> >
> > Matias Pelenur wrote:
> >
> > > Hi,
> > > I'm running three WL 4.5.2 servers clustered, JDK1.1.7b on Solaris 2.6.
> > >
> > > Normally the cluster runs just fine, but now I'm beginning to see the
> > > following message in all three servers:
> > >
> > > <DGCserver> tried to renew lease for lost ref: nnn
> > >
> > > Usually they come in small bursts of about 5 or 10 messages that are the
> > > same, except the "ref"s keep increasing. I'm guessing it has to do
> something
> > > with the in-memory replication of sessions (which I'm using).
> > >
> > > Any ideas? I tried restarting the servers but after a little while the
> > > messages started again.
> > > Thanks,
> > >
> > > Matias
> >
Cheers
- Prasad
-
DGCserver problem.......
I am using the RDBMSRealm security provided in the
examples for my custom security in my application.It works fine for
sometime and once i encounter the following lines in the weblogic.log
file, it gives me SecurityException there after....
And if i restart the Sever it works fine for sometime and again when
the above line appear it again gives the exception.What is this
"DGCserver".I couldn't find anything about it in the
documentation.Please give me a workaround ASAP.
I am using
JDK : JDK1.2.2
Server : WebLogicServer5.1
Database : OracleServer 8.1.6
JDBC Driver: Oracle thin Driver
WebServer : Apache 8.3.12
ServletEngine : ServletExec3.0.
The error I get get in the WebLogic.log file:
Thu Nov 02 13:56:33 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:56:33 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:56:33 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:56:33 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:56:33 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:56:33 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:57:34 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:57:34 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:57:34 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 ! lost reference(s).
Thu Nov 02 13:57:34 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:57:34 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:57:34 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:58:32 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:58:32 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:58:32 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:58:32 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).
Thu Nov 02 13:58:32 GMT+05:30 2000:<I> <DGCserver> tried to renew
lease for 1 lost reference(s).Hi, Beverley.
Thank you for visiting Apple Support Communities.
I understand that you are unable to trim clips using iMovie. I would need a little more information on how you were attempting to trim a clip to provide a better answer. However, make sure you have the movie project open and are selecting the clip that you wish to trim as this will activate the clip trimmer.
Trim clips
-Jason H. -
In testing the cluster failover capability, I disconnected the network cable from one of the servers I was running in a cluster. The system failed over properly. When I reattached the network cable, the system added the server back into the cluster. However, I continue to get the following message:Tue Dec 12 17:34:51 GMT 2000:<I> <DGCserver> tried to renew lease for 1 lost reference(s). What is the cause of this message? What needs to be done to clean up the cluster?
"Rich Kolkmeier" <[email protected]> wrote in message
news:3a366798$[email protected]..
In testing the cluster failover capability, I disconnected the
network cable from one of the servers I was running in a cluster.
The system failed over properly. When I reattached the network
cable, the system added the server back into the cluster. However,
I continue to get the following message:
Tue Dec 12 17:34:51 GMT 2000:<I> <DGCserver> tried to renew lease
for 1 lost references
(s).
What is the cause of this message? What needs to be done to clean
up the cluster?Rich,
This message is printed when one WebLogic kernel tries to renew a lease for
an remote object from another WebLogic which has already been collected. It
makes sense that this might happen in the failure scenario you describe.
When the network is disconnected DGC lease renewals can't be sent and the
kernel exporting the object may therefore believe that the object is no
longer in use and collect it. When the network is re-established the remote
objects may be gone.
However the fact that you are seeing this message printed repeatedly is
troubling. You may want to contact [email protected] with the
description you provided here along with the following additional
information.
Are you seeing this message on the client or server? If on the server is it
on the server that was disconnected or on one of the other servers? What
version (including service packs) of WebLogic are you running?
Regards,
Adam Messinger -
My weblogic Server keep on giving this message:
<Jun 24, 2002 6:06:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renew lease
on
lost reference: '286'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renew lease
on
lost reference: '289'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renew lease
on
lost reference: '290'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renew lease
on
lost reference: '291'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renew lease
on
lost reference: '286'>
Any idea what does this message means?
I am using Weblogic Server 6.1 SP2 running on HP-UX.Lim Boon Siong <[email protected]> wrote:
Thanks for your answer. I need more details.
Do you know why is this happen?ed Any impact to the server? Is it caused by
my application or weblogic server? How to prevent it from happening?I think these are harmless - you can simply change severity from 'Info' to
'Error'.
Many thanks for your answer.
Boon Siong
"Dimitri I. Rakitine" <[email protected]> wrote in message
news:[email protected]..
I think it means that server was not able to process RMI lease renewal
message in time, and by the time when message is finally processed, object
is already gone.
Lim Boon Siong <[email protected]> wrote:
My weblogic Server keep on giving this message:
<Jun 24, 2002 6:06:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renew
lease
on
lost reference: '286'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renewlease
on
lost reference: '289'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renewlease
on
lost reference: '290'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renewlease
on
lost reference: '291'>
<Jun 24, 2002 6:07:19 PM GMT+08:00> <Info> <DGCserver> <Tried to renewlease
on
lost reference: '286'>
Any idea what does this message means?
I am using Weblogic Server 6.1 SP2 running on HP-UX.--
Dimitri
Dimitri -
Hey all,
We're running WLS 4.5.1sp5 on solaris 2.7.
After some time, we start to see our execute queue length start to
increase dramatically. At the same time we start to see the following
messages:
Fri Jul 06 12:03:54 EDT 2001:<I> <DGCserver> tried to renew lease for
lost ref: 677
Fri Jul 06 12:03:54 EDT 2001:<I> <DGCserver> tried to renew lease for
lost ref: 678
Fri Jul 06 12:03:54 EDT 2001:<I> <DGCserver> tried to renew lease for
lost ref: 692
This happens a lot and soon after start up on the new hosting
environment but hardly ever on the old hosting environment and never on
the development machines. The boxes are all the same... why would this
happen?
Any insights would be appreciated.
C.Chad,
These messages indicate that a server got a message to renew a DGC lease for
a reference it had already collected. This means that the lease renewal
messages aren't being received and/or processed in a timely manner. Since
you mention that the execute queue length is quite long that is likely the
cause of the problem.
To diagnose that problem I would recommend taking a thread dump from the
server VM. Look at what the threads are doing. Are they blocked trying to
obtain some resource or doing some other operation that is preventing them
from proceeding?
Cheers!
Adam
"Chad Bryant" <[email protected]> wrote in message
news:[email protected]..
Hey all,
We're running WLS 4.5.1sp5 on solaris 2.7.
After some time, we start to see our execute queue length start to
increase dramatically. At the same time we start to see the following
messages:
Fri Jul 06 12:03:54 EDT 2001:<I> <DGCserver> tried to renew lease for
lost ref: 677
Fri Jul 06 12:03:54 EDT 2001:<I> <DGCserver> tried to renew lease for
lost ref: 678
Fri Jul 06 12:03:54 EDT 2001:<I> <DGCserver> tried to renew lease for
lost ref: 692
This happens a lot and soon after start up on the new hosting
environment but hardly ever on the old hosting environment and never on
the development machines. The boxes are all the same... why would this
happen?
Any insights would be appreciated.
C. -
DGCServer - tried to renew lease for lost ref: 509
Recently we have been getting ALOTof messages in our server log file of the
form:
Fri Jul 14 10:08:19 PDT 2000:<I> <DGCserver> tried to renew lease for lost
ref: 509
We use RMI for java client to server communcation and are using Weblogic
4.5.1 SP 8
with nativeIO enabled.
What could be causing these messages?
Thanks!
RickThanks! I still have one problem, the lease renewal messages for lost
references never seem
to end for the specific reference. I have a weblogic.log file with hundreds
of those messages for
each lost reference (and still going). It seems that it is not giving
up... any ideas?
Rick
"Michael Girdley" <[email protected]> wrote in message
news:396fa6c8$[email protected]..
Normally, I would ask a customer in the situation to provide more about
their application. But, since I know a lot about how your application is
architected, I would guess the people are shutting down their browserswhile
your applet still running. The applet is not closing the socket cleanly
with Weblogic. The distributed garbage collector, which keeps track ofall
of the distributed objects, is trying to renew a lease for that object.It
cannot locate it and will eventually give up on it.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
Rick Spickelmier <[email protected]> wrote in message
news:396f960d$[email protected]..
Recently we have been getting ALOTof messages in our server log file ofthe
form:
Fri Jul 14 10:08:19 PDT 2000:<I> <DGCserver> tried to renew lease forlost
ref: 509
We use RMI for java client to server communcation and are using Weblogic
4.5.1 SP 8
with nativeIO enabled.
What could be causing these messages?
Thanks!
Rick -
I am using WLS6.0SP2. When the server runs for a while, the server console
print out a lot of messages like the following:
<Sep 19, 2001 3:46:34 PM PDT> <Info> <DGCserver> <tried to renew lease for 1
los
t reference(s).>
<Sep 19, 2001 3:46:34 PM PDT> <Info> <DGCserver> <tried to renew lease for 1
los
t reference(s).>
Howerver, the server is still behaving well.
Anybody know what is the DGCServer?
In what circumstance, the above message may appear? What is the effect of
the above messages?
Thanks alot!
--ChunboDGC is distributed garbage collection algorithm. I think that
you see this message when server tries to renew lease for an
object instance which no longer exists (client want's able to
send lease renewal message in time, or server wasn't able to
process it in time - something like that).
Of course, I can be wrong ;-)
Chunbo Huang <[email protected]> wrote:
I am using WLS6.0SP2. When the server runs for a while, the server console
print out a lot of messages like the following:
<Sep 19, 2001 3:46:34 PM PDT> <Info> <DGCserver> <tried to renew lease for 1
los
t reference(s).>
<Sep 19, 2001 3:46:34 PM PDT> <Info> <DGCserver> <tried to renew lease for 1
los
t reference(s).>
Howerver, the server is still behaving well.
Anybody know what is the DGCServer?
In what circumstance, the above message may appear? What is the effect of
the above messages?
Thanks alot!
--Chunbo--
Dimitri -
EAR *RE*-deployment failing
I have a simple WL 6.1 setup. One admin server on one box, and a
cluster of two WL servers on two other boxes. My EAR (wp-dyn.ear)
contains one JAR (WPNIBeans.jar) and one WAR (WPNI.war) file. When I
deploy my EAR to the admin server, and then deploy my components to the
managed server cluster, everything works fine, exactly as it's supposed
to.
The problem comes when, without stopping any of the servers, I try to
re-deploy that EAR file. One of my managed servers consistently works
fine, and one of my managed servers consistently throws a bunch of
errors.
Here's what happens in the managed server that works fine:
<Aug 27, 2001 3:44:08 PM EDT> <Info> <HTTP> <[HTTP wl6test2] Unloading
web app: WPNI>
<Aug 27, 2001 3:44:08 PM EDT> <Info> <HTTP>
<[WebAppServletContext(2034542,WPNI,/WPNI)] *.jsp: destroy>
<Aug 27, 2001 3:44:08 PM EDT> <Info> <HTTP>
<[WebAppServletContext(2034542,WPNI,/WPNI)] *.html: destroy>
<Aug 27, 2001 3:44:19 PM EDT> <Info> <J2EE> <Undeployed : wp-dyn>
<Aug 27, 2001 3:44:37 PM EDT> <Info> <EJB> <EJB Deploying file:
WPNIBeans.jar>
<Aug 27, 2001 3:44:27 PM EDT> <Info> <EJB> <EJB Deployed EJB with JNDI
name ...>
(although I am getting LOTS of <Info> <DGCserver> <Tried to renew lease
on lost reference: '###'> errors on this server)
Here's what happens in the managed server that fails to redeploy:
<Aug 27, 2001 3:44:08 PM EDT> <Info> <HTTP> <[HTTP wl6test2] Unloading
web app: WPNI>
<Aug 27, 2001 3:44:08 PM EDT> <Info> <HTTP>
<[WebAppServletContext(2034542,WPNI,/WPNI)] *.jsp: destroy>
<Aug 27, 2001 3:44:08 PM EDT> <Info> <HTTP>
<[WebAppServletContext(2034542,WPNI,/WPNI)] *.html: destroy>
<Aug 27, 2001 3:44:19 PM EDT> <Info> <J2EE> <Undeployed : wp-dyn>
<Aug 27, 2001 3:44:37 PM EDT> <Info> <EJB> <EJB Deploying file:
WPNIBeans.jar>
<Aug 27, 2001 3:44:38 PM EDT> <Error> <J2EE> <Error deploying
application wp-dyn:
Unable to deploy EJB: Interview from WPNIBeans.jar:
Unable to bind EJB Home Interface to the JNDI name:
[EJB JNDI name]. The error was:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a
replica-aware stub to a name that is currently bound to a replica-aware
stub; remaining name ''
<<no stack trace available>>
>
<Aug 27, 2001 3:44:38 PM EDT> <Error> <Management>
<InvocationTargetException setting attribute Deployed on MBean
common:Location=wl6test2,Name=wp-dyn,Type=ApplicationConfig to value
true. Method: public void
weblogic.management.mbeans.custom.Application.setDeployed(boolean)
throws
weblogic.management.DeploymentException,weblogic.management.UndeploymentException
Unable to deploy EJB: Interview from WPNIBeans.jar:
Unable to bind EJB Home Interface to the JNDI name:
[EJB JNDI name]. The error was:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a
replica-aware stub to a name that is currently bound to a replica-aware
stub; remaining name ''
<<no stack trace available>>
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1011)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.deploy(Application.java:244)
at
weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:183)
at
weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:360)
at
weblogic.management.mbeans.custom.Application.setDeployed(Application.java:294)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1313)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:825)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:791)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:286)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at
weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Aug 27, 2001 3:44:45 PM EDT> <Error> <Cluster> <Conflict start: You
tried to bind an object under the name
[EJB JNDI name] in the JNDI tree. The object you have
bound from [IP Address] 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.>
Here's what happens in the Admin server:
<Aug 27, 2001 3:44:08 PM EDT> <Info> <HTTP> <[HTTP testserver] Unloading
web app: WPNI>
<Aug 27, 2001 3:44:08 PM EDT> <Info> <J2EE> <Undeployed : wp-dyn>
<Aug 27, 2001 3:44:25 PM EDT> <Info> <EJB> <EJB Deploying file:
WPNIBeans.jar>
<Aug 27, 2001 3:44:27 PM EDT> <Info> <EJB> <EJB Deployed EJB with JNDI
name ...>
(and so on, but then about the same time the deployment on the bad
managed server fails, I get this:)
<Aug 27, 2001 3:44:51 PM EDT> <Error> <HTTP>
<[WebAppServletContext(2728006,console,/console)] Servlet failed with
Exception
weblogic.management.DistributedManagementException: Distributed
Management [1 exceptions]
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:434)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:289)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at
weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:298)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy73.setDeployed(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:842)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:807)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:701)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:198)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy5.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:150)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:190)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:172)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationError - with nested
exception:
[weblogic.management.DistributedManagementException: Distributed
Management [1 exceptions]]
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:846)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:807)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:701)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:198)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy5.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:150)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:190)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:172)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
I can't for the life of me figure out why this would work on deployment,
but not on redeployment, and then only on one of the two managed
serevrs. Any ideas?
Thanks,
- E
* "A few years ago, when I happened to be out
* of the country, the top editors at Newsweek
* called me to tell me that some of the women
* on the staff had presented them with a
* petition protesting the unfair treatment of
* women there. My first reaction was, 'Do you
* want me to consider the petition, or sign it?'"
* Katharine Graham, Washington Post (who else?)
* www.washingtonpost.com/wp-dyn/articles/A29237-2001Jul20.html
* Erik (Erin) Reid Jones, Chief Architect
* WashingtonPost.Newsweek Interactive
* Work: (703) 469-3154
* Cell: (703) 725-3050
[att1.html]
Hi,
SharePoint designer may have limited capability on this, you may need to create your workflow using a code.
If you are using a visual studio workflows, you may try to:
Set the IgnoreIfAlreadyExists="False" and ReplaceContent="True" for the WF XAML and Assocaition file in the Elements.xml
Then update the solution with update-spsolution command.
If the workflow changes are not effective, then re-activate the feature on the site.
If should you need help to creating the source codes, you may try to open an advisory ticket regarding this issue.
Best Regards,
Lisa Chen
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Lisa Chen
TechNet Community Support -
Errors encountered during perfromance testing
While doing some stress testing on our WLS server we kept seeing the
following errors:
1) NullPointerException on NTSocketMuxer, error log follows:
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux> failure in processSockets()
loop: GetData: fd=16764 numBytes=23
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux>
java.lang.NullPointerException: null native pointer - socket was closed
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
This error doesn't seem to have any immediate impact, although it can't
be a good thing and it seems to happen even at times when we are not
doing stress testing. Also, it is very frequent that we see the above
messages. We are running WLS 4.51 w/ Service Pack 5. I am wondering if
this is a problem w/ Service Pack 5 since I don't see this on another
machine running WLS 4.51 with Service Pack 4. Both are using JDK 1.2.2.
2) Connection Rejected, error log follows:
Tue Feb 22 07:08:16 EST 2000:<W> <ListenThread> Connection rejected:
Login timed out after 15000 msec. The socket came from
[host=207.17.47.141,port=11929,localport=443] See property
weblogic.login.readTimeoutMillis.
I know how to adjust this for this one. My questions on this are:
If I set my readTimeoutMillisSSL (SSL in this case) from 15000 to 30000
what does this exactly mean. Does this mean that instead of allowing a
max 15 seconds for a connection to be established, now I am allowing 30
seconds? Also, is this only for the initial connection establishment (ie
user login), or does this parameter effect other aspects of the
connection later on? What negative side effects would I encounter if I
set this to 60000 (1 minute)?
Finally, what can I do so that a connection does not take over 15
seconds to establish? Note this is not the norm, just happens more often
during stress testing.
3) Creating & Closing connection & DGCserver, log follows:
Tue Feb 22 07:08:44 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
144.14.157.204/144.14.157.204 2864292845294268830
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:51 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 902
Tue Feb 22 07:08:52 EST 2000:<I> <RJVM> Heartbeat/PublicKey resend
detected
Tue Feb 22 07:08:54 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 904
Tue Feb 22 07:08:58 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Why the constant trying to create connection, close connection?
What is DGCserver?
4) Ignoring message from a previous JVM, log follows:
Tue Feb 22 08:29:50 EST 2000:<E> <RJVM> Ignoring message from a previous
generation: JVMMessage from 8729925219143181234C138.8.222.21 to
-3465797227003769874C192.168.100.61 with CMD_ONE_WAY, prtNum=6, ack=103,
seqNum=1384
Tue Feb 22 08:30:15 EST 2000:<I> <HTTPTunneling> Sending DEAD response
What does this mean?
5) PeerGoneExceptions
What causes these?
Our environment is set up as follows:
WLS Server
WLS 4.51 w/ Service Pack 5
NativeIO = true
ExecuteThreadCount = 40
readTimeoutMillis=5000
readTimeoutMillisSSL=10000
Dell Pentium III 600 w/ 512 MB memory
NT 4.0
JavaSoft 1.2.2
-ms128 -mx350
WLS Client
Java Application
t3s and https (using WLS RMI)
JavaSoft 1.1.7b
typically Pentium 200 MHz or better w/ 64MB or more
Basically our clients connect to our WLS server using RMI. Each client
also has a callback object where the server sends event notification
back to the clients. Most of the communication is back through these
client callback objects. Its similar to a stock trading application in
that 1 client incoming requests will generate 200 outgoing events (if
for example there are 200 users on the system). The above observations
where made while 25 very active users where on the system.
Thanks very much for any and all help,
Edwin Marcial
Continental Power ExchangeHi Kim,
Thanks for the response, but which problem in particular did you solve, I've
listed a couple here.
Edwin
kim hyun chan wrote:
hi,
I met the problem like you before.
so I reduce executeThreadCount from 50 to 20 , and then I solved my proplem.
"Edwin Marcial" <[email protected]> wrote in message
news:[email protected]...
While doing some stress testing on our WLS server we kept seeing the
following errors:
1) NullPointerException on NTSocketMuxer, error log follows:
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux> failure in processSockets()
loop: GetData: fd=16764 numBytes=23
Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux>
java.lang.NullPointerException: null native pointer - socket was closed
at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
This error doesn't seem to have any immediate impact, although it can't
be a good thing and it seems to happen even at times when we are not
doing stress testing. Also, it is very frequent that we see the above
messages. We are running WLS 4.51 w/ Service Pack 5. I am wondering if
this is a problem w/ Service Pack 5 since I don't see this on another
machine running WLS 4.51 with Service Pack 4. Both are using JDK 1.2.2.
2) Connection Rejected, error log follows:
Tue Feb 22 07:08:16 EST 2000:<W> <ListenThread> Connection rejected:
Login timed out after 15000 msec. The socket came from
[host=207.17.47.141,port=11929,localport=443] See property
weblogic.login.readTimeoutMillis.
I know how to adjust this for this one. My questions on this are:
If I set my readTimeoutMillisSSL (SSL in this case) from 15000 to 30000
what does this exactly mean. Does this mean that instead of allowing a
max 15 seconds for a connection to be established, now I am allowing 30
seconds? Also, is this only for the initial connection establishment (ie
user login), or does this parameter effect other aspects of the
connection later on? What negative side effects would I encounter if I
set this to 60000 (1 minute)?
Finally, what can I do so that a connection does not take over 15
seconds to establish? Note this is not the norm, just happens more often
during stress testing.
3) Creating & Closing connection & DGCserver, log follows:
Tue Feb 22 07:08:44 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
144.14.157.204/144.14.157.204 2864292845294268830
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
138.8.81.19/138.8.81.19 5634583086356155101
Tue Feb 22 07:08:51 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 902
Tue Feb 22 07:08:52 EST 2000:<I> <RJVM> Heartbeat/PublicKey resend
detected
Tue Feb 22 07:08:54 EST 2000:<I> <DGCserver> tried to renew lease for
lost ref: 904
Tue Feb 22 07:08:58 EST 2000:<I> <RJVM> Creating connection to
138.8.81.19/138.8.81.19 5634583086356155101
Why the constant trying to create connection, close connection?
What is DGCserver?
4) Ignoring message from a previous JVM, log follows:
Tue Feb 22 08:29:50 EST 2000:<E> <RJVM> Ignoring message from a previous
generation: JVMMessage from 8729925219143181234C138.8.222.21 to
-3465797227003769874C192.168.100.61 with CMD_ONE_WAY, prtNum=6, ack=103,
seqNum=1384
Tue Feb 22 08:30:15 EST 2000:<I> <HTTPTunneling> Sending DEAD response
What does this mean?
5) PeerGoneExceptions
What causes these?
Our environment is set up as follows:
WLS Server
WLS 4.51 w/ Service Pack 5
NativeIO = true
ExecuteThreadCount = 40
readTimeoutMillis=5000
readTimeoutMillisSSL=10000
Dell Pentium III 600 w/ 512 MB memory
NT 4.0
JavaSoft 1.2.2
-ms128 -mx350
WLS Client
Java Application
t3s and https (using WLS RMI)
JavaSoft 1.1.7b
typically Pentium 200 MHz or better w/ 64MB or more
Basically our clients connect to our WLS server using RMI. Each client
also has a callback object where the server sends event notification
back to the clients. Most of the communication is back through these
client callback objects. Its similar to a stock trading application in
that 1 client incoming requests will generate 200 outgoing events (if
for example there are 200 users on the system). The above observations
where made while 25 very active users where on the system.
Thanks very much for any and all help,
Edwin Marcial
Continental Power Exchange -
Distributed Garbage Collector (DGC) messages in cluster when using Message Driven Beans
Version: Weblogic 6.1 SP2
I'm seeing a lot of messages output on the node ** hosting my JMS
server/destination ** in the cluster
<Jun 4, 2002 5:35:03 PM EDT> <Info> <DGCserver> <Tried to renew lease on
lost reference: '448'>
Unfortunately, this message coincides with my MDB's ** on other nodes ** not
being able to lookup the JMS destination that they are configured for.
MDB's on the same node as the JMS server/destination are able to do lookups
fine.
Checking the JNDI tree on all nodes, I see the destinations replicated to
all nodes. The MDB's use the default (i.e WebLogic's) connection factory
(weblogic.jms.MessageDrivenBeanConnectionFactory) and I've bumped up the
polling interval to 5 minutes from the default of 10 seconds.
Any guidance on this would be greatly appreciated.
I see that there is a patch available to fix the DCC info messages (April
,2002) on dev2dev. Anyone know if this addresses the MDB problem?
Thanks in advance
FYI - in case anyone else sees this problem - it has been fixed in WLS 6.1
SP3.
If you are seeing this problem then you will see a log of
NoSuchObjectException's in your console.
Regards
"Prashant Nayak" <[email protected]> wrote in message
news:[email protected]...
> Version: Weblogic 6.1 SP2
>
> I'm seeing a lot of messages output on the node ** hosting my JMS
> server/destination ** in the cluster
>
> <Jun 4, 2002 5:35:03 PM EDT> <Info> <DGCserver> <Tried to renew lease on
> lost reference: '448'>
>
> Unfortunately, this message coincides with my MDB's ** on other nodes **
not
> being able to lookup the JMS destination that they are configured for.
> MDB's on the same node as the JMS server/destination are able to do
lookups
> fine.
>
> Checking the JNDI tree on all nodes, I see the destinations replicated to
> all nodes. The MDB's use the default (i.e WebLogic's) connection factory
> (weblogic.jms.MessageDrivenBeanConnectionFactory) and I've bumped up the
> polling interval to 5 minutes from the default of 10 seconds.
>
> Any guidance on this would be greatly appreciated.
>
> I see that there is a patch available to fix the DCC info messages (April
> ,2002) on dev2dev. Anyone know if this addresses the MDB problem?
>
> Thanks in advance
>
>
>
>
>
-
WLS 6.1 SP2 Cluster fails
Hi All.
we have migrated to WLS 6.1 SP2, now we have a serious problem with the cluster
wihch die after several minutes. Our architecture is several front-ends servers
(concretely servelts, without cluster) make request to back-end (starteles EJB,
DB access). This back-end is compuond by four WLS instances running into 2 Sun
Solaris Machines. The system reports the nexts messages in the weblogic.log.
* backendPlatformA instance
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformA|129.1027407260379', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
<platformA> <ExecuteThread: '117' for queue: 'default'> <system> <>
<000000> <Tried to renew lease on lost reference: '257'>
* backendPlatformB instance
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformB|118.1027407423933', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
<platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
<Removing "ClientContext - id: '#|platformB|119.1027407423933', bound:
'false', dead: 'false'" because of soft disconnect timeout.>
* ioboxPlatfromC instance
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformC|139.1027407286958', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
<platformC> <ExecuteThread: '119' for queue: 'default'> <system> <>
<000000> <Tried to renew lease on lost reference: '257'>
* Instancia ioboxPlatfromD
for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
'#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
of soft disconnect timeout.>
####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
<platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
<Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
'false', dead: 'false'" because of soft disconnect timeout.>
####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
<ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
platformA
jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
from cluster view due to PeerGone>
####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
<ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
to the cluster>
####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
<platformD> <ExecuteThread: '102' fo
r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
anaydidos>
####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
<platformD> <ExecuteThread: '119' for queue: 'default'> <system> <>
<000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because of:
'Server received a message over an uninitialized connection: 'JVMMessage
from: 'null' to:
'1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
Any idea?
Thanks for all
Hi,
We are using Weblogic 6.1 SP2, NT 4.0 and java 1.3.1. We have also encountered
the same error message. We have 1 admin and 2 managed servers. We have tried connecting
in using weblogic.admin to check the idle thread and we are able to connect. However,
when we connect from IIS to Weblogic, the application failed to response. We have
tried connect direct to weblogic but it does not response as well. We have seen
that the idle thread left has been reduced but there is no activites from the
weblogic console. The thread is used but not releasing and the console is not
moving. When we shutdown one of the managed server, the application is able to
process as seen from the console.
We have turned off native io and this behavior is not seen. When we turn on native
io, it appear. So we can conclude that it is related to native io.
Is there any solution or intermediate patch without upgrading to the later SP
Thanks
Rajesh Mirchandani <[email protected]> wrote:
>We are shipping the Jdriver for oracle 816 with SP3. Use the driver
>from .\bin\oci816_8
>
>Manuel wrote:
>
>> Thanks Rajesh,
>>
>> we have another problem since our database is Oracle 8.1.6 and SP3
>jDriver doesn´t
>> support this version.
>>
>> Best Regards
>>
>> Rajesh Mirchandani <[email protected]> wrote:
>> >Upgrade to SP3, if possible.
>> >
>> >Manuel wrote:
>> >
>> >> Hi All.
>> >>
>> >> we have migrated to WLS 6.1 SP2, now we have a serious problem with
>> >the cluster
>> >> wihch die after several minutes. Our architecture is several front-ends
>> >servers
>> >> (concretely servelts, without cluster) make request to back-end
>(starteles
>> >EJB,
>> >> DB access). This back-end is compuond by four WLS instances running
>> >into 2 Sun
>> >> Solaris Machines. The system reports the nexts messages in the weblogic.log.
>> >>
>> >> * backendPlatformA instance
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformA|129.1027407260379', bound: 'false', dead: 'false'"
>because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
>> >> <platformA> <ExecuteThread: '117' for queue: 'default'> <system>
><>
>> >> <000000> <Tried to renew lease on lost reference: '257'>
>> >>
>> >> * backendPlatformB instance
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformB|118.1027407423933', bound: 'false', dead: 'false'"
>because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
>> >> <platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
>> >> <Removing "ClientContext - id: '#|platformB|119.1027407423933',
>bound:
>> >> 'false', dead: 'false'" because of soft disconnect timeout.>
>> >>
>> >> * ioboxPlatfromC instance
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformC|139.1027407286958', bound: 'false', dead: 'false'"
>because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
>> >> <platformC> <ExecuteThread: '119' for queue: 'default'> <system>
><>
>> >> <000000> <Tried to renew lease on lost reference: '257'>
>> >>
>> >> * Instancia ioboxPlatfromD
>> >>
>> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
>id:
>> >> '#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
>> >> of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
>> >> <platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
>> >> <Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
>> >> 'false', dead: 'false'" because of soft disconnect timeout.>
>> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
>> >> <ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
>> >> platformA
>> >> jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
>> >> from cluster view due to PeerGone>
>> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
>> >> <ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
>> >> 7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
>> >> to the cluster>
>> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
>> >> <platformD> <ExecuteThread: '102' fo
>> >> r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
>> >> anaydidos>
>> >> ####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
>> >> <platformD> <ExecuteThread: '119' for queue: 'default'> <system>
><>
>> >> <000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because
>> >of:
>> >> 'Server received a message over an uninitialized connection: 'JVMMessage
>> >> Wrom: HJEXXIMQZU
>> >> '1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
>> >> cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
>> >> flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
>> >>
>> >> Any idea?
>> >>
>> >> Thanks for all
>> >
>> >--
>> >Rajesh Mirchandani
>> >Developer Relations Engineer
>> >BEA Support
>> >
>> >
>
>--
>Rajesh Mirchandani
>Developer Relations Engineer
>BEA Support
>
>
-
WL6.1 and Red Hat 7.1 Issue
After porting an application from WL5.1 to WL 6.1 we are seeing the error message
shown below,
The Garbage Collection slows the complete system down to a grinding halt. One
cannot even login.
The machine has over 700M of memory.
Any suggestions ?
<Nov 1, 2001 12:13:40 PM MST> <Info> <DGCserver> <Tried to renew lease on lost
reference: '266'>
[GC 16071K->14110K(392960K), 0.0985651 secs]
<Nov 1, 2001 12:13:41 PM MST> <Error> <Cluster> <Multicast socket receive error:
java.io.InterruptedIOException: Receive timed out
java.io.InterruptedIOException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:392)
at weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:145)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:293)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)Hi,
Can you help me please. I get 2 error messages when starting up names. The first I understand because my SQLNET.ORA needs work, but the second is, it can not find the names executable file. I did a find and it is not on installed. I am trying to use 8.1.7 . I must have missed something on install. Any ideas?
Thank you for your help,
Jay Bennett
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Abhishek Srivastava ([email protected]):
Running netca creates a proper tnsnames.ora file.
My installation is fully working now.
Thanks for all your help.
regards,
Abhishek.<HR></BLOCKQUOTE>
null -
Our app is deployed as cluster (two instances), recently we saw some errors as
below. What's the cause of it, is it critical? Since it's labeled as 'info", should
we just ignore it?
Thanks in advance.
####<Apr 7, 2003 4:39:33 PM GMT+00:00> <Info> <DGCserver> <our url address> <m0034-instance1>
<ExecuteThread: '34' for queue: 'default'> <> <> <000000> <tried to renew lease
for 1 lost reference(s).>
####<Apr 7, 2003 4:40:32 PM GMT+00:00> <Info> <DGCserver> <our url address> <m0034-instance1>
<ExecuteThread: '34' for queue: 'default'> <> <> <000000> <tried to renew lease
for 1 lost reference(s).>
Our app is deployed as cluster (two instances), recently we saw some errors as
below. What's the cause of it, is it critical? Since it's labeled as 'info", should
we just ignore it?
Thanks in advance.
####<Apr 7, 2003 4:39:33 PM GMT+00:00> <Info> <DGCserver> <our url address> <m0034-instance1>
<ExecuteThread: '34' for queue: 'default'> <> <> <000000> <tried to renew lease
for 1 lost reference(s).>
####<Apr 7, 2003 4:40:32 PM GMT+00:00> <Info> <DGCserver> <our url address> <m0034-instance1>
<ExecuteThread: '34' for queue: 'default'> <> <> <000000> <tried to renew lease
for 1 lost reference(s).>
Maybe you are looking for
-
Hi Experts! I have successfully activated the PR and PO standard workflow scenario. The only problem is that <b>any user can RELEASE the PR or PO document even if he/she is not the intended approver</b>. The PR and PO (IMG) release strategies were a
-
Hi, In testing server when i created a vendor it skipped number series sequence. Lastly vendor was created with xxxx50 but upon creation it created vendor with xxxx67, i have heard there is some problem with buffering settings in SNRO but when i lo
-
Record set size in Gantt Chart
Hi all, I am developing an application that has a Gantt Chart. The tree drawn is a 2 level tree. I have two VOs. The second VO (Child) has more than 20 rows. I want to show only 10 child at once. Record set size attribute is the one that is used to r
-
Hi All, When purchasing creates the info record we populate a price linked to that supplier/part # combination. Later, if we get a price change, we would like to update that field so that it autopopulates the requisition with the correct value - but
-
Spotlight, Fonts in French, account set to English.
After installing Snow Leopard, I noticed (without me changing anything) that now when I search for an app in Spotlight it searches in French (not that I can't understand it.. but its annoying) so if I quickly search for "Calc" it will return "Calcule