Weblogic 10.3.4 timeout on shut down

Hi,
I have installed Weblogic 10.3.4 in Eclipse Galileo SR2 and everything goes right except when I want
to shut down the server becasue I get timeout.
It is not a problem of the IDE. I think it is a problem of the server.
How can I confugure the server to shut it down in a reassonable time?
My system is Win XP.
Kind Regards,
Jose

Hi Jose,
Are you executing a forced shutdown?
If so, you can try increasing the forceshutdown timeout.
On the Java command line, set -Dweblogic.ServerLifeCycleTimeoutVal=240
Or in the WebLogic console, increase the ServerLifeCycle Timeout before executing the forced shutdown. Go to Environment->Servers->servername->Control tab->Start/Stop tab. Change the value of "Server LifeCycle Timeout" to 240 or higher.

Similar Messages

System won't shut down due to timeout of some sort

I was wondering if someone can help me figure out why since a couple of weeks, one or another app seems to crash and timeout the shut down process. Which of the logs in the console are relevant and how do I read it to make any sense out of it. Maybe someone can help me with this.
Thanks,
Andreas

This problem happened to me once. It happened because I improperly quit OpenOffice. Some things to include in your question: What program is stopping, how often does it happen, can you force quit it, and what happens if you do?

App server shut down

Hi
does anybody knows why when i start app server 9 from console by typing .
./adadmin start-domain domain1
it runs fine, but if i close console app server shut down??
i'm using solaris 10 on ultra20, but same problem on sunfire v100
is there any way to make sun app server permanent?
Regards

For exploaded war files use following context parameters in web.xml
// For servlet reload
weblogic.httpd.servlet.reloadCheckSecs
// For JSP reload
weblogic.jsp.pageCheckSeconds
Example:
<context-param>
<param-name>weblogic.httpd.servlet.reloadCheckSecs</param-name>
<param-value>10</param-value>
</context-param>
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
marshalli wrote:
I set 
weblogic.httpd.webApp.tc=e:/weblogic/myserver/testWapp 
in my weblogic.properties 
But I must shut down my server for each time I change jsp file 
Otherwise, it will read old jsp file from tmp 
where can I setup for weblogic 
to reread a new jsp file with shut down? 
Thank a lot

Tuxedo transaction branch in GMTREADY and cannot finishit without shutting down weblogic server

Trying to reproduce a problem in an application we are deployed a servlet in a
weblogic 8.1 sp2 server, doing the folowing:
1. Begin a transaction
2. Call a tuxedo service (tuxedo 6.5) via tuxedo gateway "A"
3. Call another tuxedo service (tuxedo 6.5) via tuxedo gateway "B"
4. Before commit the transaction in the servlet, we shutdown tuxedo gateway "B"
5. After commit transaction branch via gateway "A" remains indefinitely in GMTREADY
state, while transaction branch via gateway "B" gets GMTABRTONLY after timming
out.
After commit(that fail doing rollback), transaction is not reported like inflight
in weblogic server. We cannot finish transaction branch in GMTREADY state. Only
after shutdown weblogic server, and after an undetermined time(sometimes a lot)
transaction branch is rolled back.
While transaccion is not rolled back, all locks in DB remains active.
How we could finnish that branch without shutting down weblogic server, or, if
not, how we could control the time in witch transaction is rolled back?

We open a case with BEA eSupport and the servlet problem was a bug. Engineering
got a
temporary patch that seems to solve the problem. The case continues trying to
solve our original problem (the servlet was to reproduce the situation).
Thank you very much.
Jose Emilio Ortega.
"Todd Little" <[email protected]> wrote:
>
Hi Jose,
Can you provide a little more information. In particular, what are the
JTA timeout
values configured for your WLS application? Did you set the interoperate
setting
to Yes under the WTC local access point's connection settings? When
you begin
the transaction in the servlet, do you specify a timeout value and if
not, do
you know what your thread's default transaction timeout value is?
If possible, can you post or e-mail your WLS's config.xml and the domain
configuration
files for the two Tuxedo domains (not the UBB files, although those would
be helpful
as well.)
Thanks,
Todd
"Jose Emilio Ortega" <[email protected]> wrote:
Trying to reproduce a problem in an application we are deployed a servlet
in a
weblogic 8.1 sp2 server, doing the folowing:
1. Begin a transaction
2. Call a tuxedo service (tuxedo 6.5) via tuxedo gateway "A"
3. Call another tuxedo service (tuxedo 6.5) via tuxedo gateway "B"
4. Before commit the transaction in the servlet, we shutdown tuxedo
gateway "B"
5. After commit transaction branch via gateway "A" remains indefinitely
in GMTREADY
state, while transaction branch via gateway "B" gets GMTABRTONLY after
timming
out.
After commit(that fail doing rollback), transaction is not reportedlike
inflight
in weblogic server. We cannot finish transaction branch in GMTREADYstate.
Only
after shutdown weblogic server, and after an undetermined time(sometimes
a lot)
transaction branch is rolled back.
While transaccion is not rolled back, all locks in DB remains active.
How we could finnish that branch without shutting down weblogic server,
or, if
not, how we could control the time in witch transaction is rolled back?

Weblogic shutting down keep-alive socket improperly?

We were sometimes experiencing strange IE behaviour when surfing on webapps on our Weblogic application servers. After investigation we found that IE has a bug in its resend behaviour, so when resending a POST request it sends the headers (including Content-Length) but forgets the form-data. This causes the server to time out waiting for the data. (Note: We are using Win2K and IE6 SP1 on the clients.)
The IE resend is triggered on a default installation when 31-59 seconds have passed since the last request.
This is because IE will try to reuse a socket that has been told to keep-alive until it has been idle for 60 seconds but WLS will by default close kept-alive sockets when they have been idle for 30 seconds. So in the range 31-59 seconds IE will consider the socket alive but WLS has closed it.
The resend bug is really an IE bug and doesn't concern WLS, but then I saw that IE would function correctly with an Apache server with a default keep-alive timeout of 15 seconds.
Using Ethereal I could get the information depicted in the tables below:
Weblogic with keep-alive timeout 30 secs
old socket
Time 00 : User navigates : IE POST request -> WLS, WLS HTML -> IE
Time 30 : Socket times out : (no network traffic)
Time 45 : User navigates : IE POST request -> WLS, WLS TCP_FIN -> IE
new socket
Time 45 : : IE resends POST request without form-data
Apache with keep-alive timeout 15 secs
old socket
Time 00 : User navigates : IE POST request -> Apache, Apache HTML -> IE
Time 15 : Socket times out : Apache TCP_FIN -> WLS
new socket
Time 45 : User navigates : IE POST request -> Apache, Apache HTML -> IE
To summarize, IE handles Apache well as Apache sends a TCP FIN telegram (to close the connection) as soon as the kept-alive socket times out.
Therefore IE never tries to reuse the socket but instead starts on a fresh one on the next navigation and a resend is never necessary.
Weblogic, on the other hand, doesn't send the TCP FIN (connection close) telegram until IE actually tries to use the connection even though it timed out 15 seconds earlier. In this case IE needs to resend the POST request and this is when the form-data is forgotten.
So, my question now is if WLS behaviour could be caused by not shutting down kept-alive sockets properly at keep-alive timeout? Or why are there no TCP FIN telegrams sent at timeout?
Mike Wilson

After doing some more investigation I have found that the "silent" shutdown of keep-alive sockets is only seen on the Linux version. The Windows version of Weblogic 8 behaves correctly, like Apache on Linux, but Weblogic on Linux does not...
Anyone can confirm if this is to be considered a bug?

Weblogic portal server is shutting down...

Hi ,
I have problem whenever iam trying to run the portal as going to RunAS-->Server-->Oracle Weblogic server..It showing as starting after that it shutting down..Iam bit confused why its happend..Iam coping the error also .Please check it.. I will be helpful if you solve this problem.And also can you tell me the cause of the problem
JAVA Memory arguments: -Xms256m -Xmx768m
WLS Start Mode=Development
CLASSPATH=;F:\BEAWEB~1\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;F:\BEAWEB~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;F:\BEAWEB~1\patch_wlp1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;F:\BEAWEB~1\patch_cie670\profiles\default\sys_manifest_classpath\weblogic_patch.jar;F:\BEAWEB~1\JROCKI~1\lib\tools.jar;F:\BEAWEB~1\WLSERV~1.3\server\lib\weblogic_sp.jar;F:\BEAWEB~1\WLSERV~1.3\server\lib\weblogic.jar;F:\BEAWEB~1\modules\features\weblogic.server.modules_10.3.0.0.jar;F:\BEAWEB~1\WLSERV~1.3\server\lib\webservices.jar;F:\BEAWEB~1\modules\ORGAPA~1.5/lib/ant-all.jar;F:\BEAWEB~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;F:\BEAWEB~1\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar;F:\BEAWEB~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;F:\BEAWEB~1\WLSERV~1.3\server\lib\xqrl.jar;F:\BEAWEB~1\WLSERV~1.3\server\lib\xquery.jar;F:\BEAWEB~1\WLSERV~1.3\server\lib\binxml.jar;
PATH=F:\BEAWEB~1\patch_wlw1030\profiles\default\native;F:\BEAWEB~1\patch_wls1030\profiles\default\native;F:\BEAWEB~1\patch_wlp1030\profiles\default\native;F:\BEAWEB~1\patch_cie670\profiles\default\native;F:\BEAWEB~1\WLSERV~1.3\server\native\win\32;F:\BEAWEB~1\WLSERV~1.3\server\bin;F:\BEAWEB~1\modules\ORGAPA~1.5\bin;F:\BEAWEB~1\JROCKI~1\jre\bin;F:\BEAWEB~1\JROCKI~1\bin;F:\Bea Weblogic 10\jrockit_160_05\jre\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Program Files\IBM\CICS Transaction Gateway\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\BEAWEB~1\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
Cleaning up license and uid files
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
BEA JRockit(R) (build R27.6.0-50_o-100423-1.6.0_05-20080626-2105-windows-ia32, compiled mode)
Starting WLS with line:
F:\BEAWEB~1\JROCKI~1\bin\java -jrockit -Xms256m -Xmx768m -Xverify:none -da -Dplatform.home=F:\BEAWEB~1\WLSERV~1.3 -Dwls.home=F:\BEAWEB~1\WLSERV~1.3\server -Dweblogic.home=F:\BEAWEB~1\WLSERV~1.3\server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=F:\BEAWEB~1\patch_wlw1030\profiles\default\sysext_manifest_classpath;F:\BEAWEB~1\patch_wls1030\profiles\default\sysext_manifest_classpath;F:\BEAWEB~1\patch_wlp1030\profiles\default\sysext_manifest_classpath;F:\BEAWEB~1\patch_cie670\profiles\default\sysext_manifest_classpath;F:\Bea Weblogic 10\wlportal_10.3\p13n\lib\system;F:\Bea Weblogic 10\wlportal_10.3\light-portal\lib\system;F:\Bea Weblogic 10\wlportal_10.3\portal\lib\system;F:\Bea Weblogic 10\wlportal_10.3\info-mgmt\lib\system;F:\Bea Weblogic 10\wlportal_10.3\analytics\lib\system;F:\Bea Weblogic 10\wlportal_10.3\apps\lib\system;F:\Bea Weblogic 10\wlportal_10.3\info-mgmt\deprecated\lib\system;F:\Bea Weblogic 10\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=F:\Bea Weblogic 10\wlportal_10.3\portal\lib\security -Dweblogic.Name=AdminServer -Djava.security.policy=F:\BEAWEB~1\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
Starting Autonomy with CONTENT_SEARCH_OPTION = full
Autonomy Distributed Search Handler engine started.
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: Weblogic
Stopping PointBase server...
PointBase server stopped.
Autonomy server stopped

You have spaces in the folder to which you have installed BEA and they arent being correctly escaped , see the starting java with line
F:\Bea Weblogic 10\
Your simplest best is to probably reinstall into a location which doesnt have spaces like f:\bea (you could also fix all the command files to quote all values with spaces , but since you are probably beginning portal, reinstall is easier)
regards
deepak

Shutting down Server from command line in WebLogic 5.1

Cannot shut down the WebLogic Server using the command line:
java weblogic.Admin URL SHUTDOWN system password
Errors out saying:
java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser; Local class not
compatible: stream classdesc serialVersionUID=6699361079932480379 local
class serialVersionUID=2825328378974757378
at
java.io.ObjectStreamClass.validateLocalClass(ObjectStreamClass.java:523)
at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:567)
at
java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:936)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:518)
at
weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:610)
at
weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
a:34)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
at
weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:342)
at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Currently using Service Pack 8.
Has anyone faced this problem before? Any solutions?
Thanks.
MN

Hi Murali,
Are you using 128bit version of the server for wls5.1 ? if so have you
correctly installed the Service pack 8 ?
Can you show me the result of
java weblogic.Admin url VERSION
Murali Nanchala wrote:
Cannot shut down the WebLogic Server using the command line:
java weblogic.Admin URL SHUTDOWN system password
Errors out saying:
java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser; Local class not
compatible: stream classdesc serialVersionUID=6699361079932480379 local
class serialVersionUID=2825328378974757378
at
java.io.ObjectStreamClass.validateLocalClass(ObjectStreamClass.java:523)
at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:567)
at
java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:936)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:518)
at
weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:610)
at
weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
a:34)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
at
weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:342)
at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Currently using Service Pack 8.
Has anyone faced this problem before? Any solutions?
Thanks.
MN

Weblogic client not shutting down properly in web app

Hi,
We have an application running on Tomcat which uses wlfullclient.jar to connect to EJB's hosted on a Weblogic server. We're seeing errors like the following in the logs when the web application is shutdown, which appear to indicate that the Weblogic client is not cleaning up threads upon application shutdown.
Jul 31, 2013 10:44:10 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/myapp] created a ThreadLocal with key of type [weblogic.kernel.ResettableThreadLocal$1] (value [weblogic.kernel.ResettableThreadLocal$1@39c79485]) and a value of type [weblogic.kernel.ResettableThreadLocal.ThreadStorage] (value [weblogic.kernel.ResettableThreadLocal$ThreadStorage@5de7c565]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Jul 31, 2013 10:44:10 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/myapp] appears to have started a thread named [ExecuteThread: '0' for queue: 'default'] but has failed to stop it. This is very likely to create a memory leak.
Is there a recommended way (configuration, API, etc.) of getting the client to clean up after itself?
Thanks.

Hi Tim,
where did you deploy your Coherence jars? In the application (APP-INF/lib or WEB-INF/lib) or into the server classpath?
If you deployed it within the application APP-INF/lib, then you should register an application-specific ApplicationLifecycleListener in weblogic-application.xml which invokes CacheFactory.shutdown() in the postStop() method.
If you deployed it within a WEB-INF/lib directory, then you should do similarly from a JSDK ContextListener.
If you deployed it to the server classpath, then it has nothing to do with the application lifecycle, nor should it have, so it is normal if it does not shut down upon application undeployment.
Best regards,
Robert

Unable to start weblogic - force shutting down

Weblogic admin server force shutting down, with the below dump... it is on windows 7...
===== FULL THREAD DUMP ===============
Thu Mar 21 12:41:47 2013
BEA JRockit(R) R27.6.5-32_o-121899-1.6.0_14-20091001-2107-windows-ia32
"Main Thread" id=1 idx=0x4 tid=4728 prio=5 alive, in native, blocked
-- Blocked trying to get lock: java/lang/Class@0x15AB9AE0[thin lock]
at jrockit/vm/Threads.sleep(I)V(Native Method)
at jrockit/vm/Locks.waitForThinRelease(Locks.java:1209)
at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1342)
at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1259)
at jrockit/vm/Locks.monitorEnter(Locks.java:2466)
at java/lang/Shutdown.exit(Shutdown.java:164)
at java/lang/Runtime.exit(Runtime.java:90)
at java/lang/System.exit(System.java:904)
at weblogic/Server.main(Server.java:87)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"(Signal Handler)" id=2 idx=0x8 tid=2200 prio=5 alive, in native, daemon
"(GC Main Thread)" id=3 idx=0xc tid=4500 prio=5 alive, in native, native_waiting, daemon
"(GC Worker Thread 1)" id=? idx=0x10 tid=400 prio=5 alive, in native, daemon
"(GC Worker Thread 2)" id=? idx=0x14 tid=5004 prio=5 alive, in native, daemon
"(Code Generation Thread 1)" id=4 idx=0x18 tid=5568 prio=5 alive, in native, native_waiting, daemon
"(Code Optimization Thread 1)" id=5 idx=0x1c tid=4048 prio=5 alive, in native, native_waiting, daemon
"(VM Periodic Task)" id=6 idx=0x20 tid=4224 prio=10 alive, in native, daemon
"(Attach Listener)" id=7 idx=0x24 tid=1628 prio=5 alive, in native, daemon
"Finalizer" id=8 idx=0x28 tid=4416 prio=8 alive, in native, native_waiting, daemon
at jrockit/memory/Finalizer.waitForFinalizees([Ljava/lang/Object;)I(Native Method)
    at jrockit/memory/Finalizer.access$500(Finalizer.java:12)
    at jrockit/memory/Finalizer$4.run(Finalizer.java:159)
    at java/lang/Thread.run(Thread.java:619)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
"Reference Handler" id=9 idx=0x2c tid=5864 prio=10 alive, in native, native_waiting, daemon
    at java/lang/ref/Reference.waitForActivatedQueue()Ljava/lang/ref/Reference;(Native Method)
    at java/lang/ref/Reference.access$100(Reference.java:11)
    at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:79)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
"(Sensor Event Thread)" id=10 idx=0x30 tid=3640 prio=5 alive, in native, daemon
"JDWP Transport Listener: dt_socket" id=11 idx=0x34 tid=4120 prio=10 alive, in native, daemon
"JDWP Event Helper Thread" id=12 idx=0x38 tid=3428 prio=10 alive, in native, native_waiting, daemon
"Timer-0" id=15 idx=0x3c tid=3808 prio=5 alive, in native, waiting, daemon
    -- Waiting for notification on: java/util/TaskQueue@0x120011C0[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at java/util/TimerThread.mainLoop(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0x120011C0[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Timer-1" id=16 idx=0x40 tid=4724 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: java/util/TaskQueue@0x12001578[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/util/TimerThread.mainLoop(Timer.java:509)
^-- Lock released while waiting: java/util/TaskQueue@0x12001578[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x44 tid=5008 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/t3/srvr/T3Srvr$2@0x15AC6550[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Thread.join(Thread.java:1143)
^-- Lock released while waiting: weblogic/t3/srvr/T3Srvr$2@0x15AC6550[fat lock]
at java/lang/Thread.join(Thread.java:1196)
at java/lang/ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:79)
at java/lang/ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:24)
at java/lang/Shutdown.runHooks(Shutdown.java:79)
at java/lang/Shutdown.sequence(Shutdown.java:123)
at java/lang/Shutdown.exit(Shutdown.java:168)
^-- Holding lock: java/lang/Class@0x15AB9AE0[thin lock]
at java/lang/Runtime.exit(Runtime.java:90)
at java/lang/System.exit(System.java:904)
at com/fedex/k2/webapp/servlet/IK2StartupServletContextListener.contextInitialized(IK2StartupServletContextListener.java:61)
at weblogic/servlet/internal/EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:121)
at weblogic/servlet/internal/EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic/servlet/internal/WebAppServletContext.preloadResources(WebAppServletContext.java:1801)
^-- Holding lock: weblogic/servlet/internal/WebAppServletContext@0x1449CBA8[thin lock]
at weblogic/servlet/internal/WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic/servlet/internal/WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic/servlet/internal/WebAppModule.start(WebAppModule.java:460)
at weblogic/application/internal/flow/ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic/application/utils/StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic/application/internal/flow/ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic/application/internal/flow/ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic/application/internal/flow/ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic/application/internal/flow/ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic/application/utils/StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic/application/internal/flow/ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic/application/internal/flow/StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic/application/internal/BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic/application/utils/StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic/application/internal/BaseDeployment.activate(BaseDeployment.java:409)
at weblogic/application/internal/SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
at weblogic/application/internal/DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic/deploy/internal/targetserver/AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic/deploy/internal/targetserver/BasicDeployment.activate(BasicDeployment.java:184)
at weblogic/deploy/internal/targetserver/BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic/management/deploy/internal/DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic/management/deploy/internal/DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic/management/deploy/internal/AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic/management/deploy/internal/ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic/management/deploy/internal/ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic/management/deploy/internal/ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic/management/deploy/internal/DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic/management/deploy/internal/DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic/t3/srvr/SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:201)
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"weblogic.time.TimeEventGenerator" id=18 idx=0x48 tid=1180 prio=9 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/time/common/internal/TimeTable@0x12001E70[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
^-- Lock released while waiting: weblogic/time/common/internal/TimeTable@0x12001E70[fat lock]
at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
at java/lang/Thread.run(Thread.java:619)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"JMAPI event thread" id=19 idx=0x4c tid=4752 prio=5 alive, in native, native_waiting, daemon
"weblogic.timers.TimerThread" id=20 idx=0x50 tid=3764 prio=9 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/timers/internal/TimerThread@0x144839C0[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:267)
^-- Lock released while waiting: weblogic/timers/internal/TimerThread@0x144839C0[fat lock]
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" id=21 idx=0x54 tid=1840 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/work/ExecuteThread@0x1447C848[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
^-- Lock released while waiting: weblogic/work/ExecuteThread@0x1447C848[fat lock]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Thread-7" id=24 idx=0x58 tid=5156 prio=5 alive, in native, parked, daemon
-- Parking to wait for: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x12F80AC0
at jrockit/vm/Locks.park0(J)V(Native Method)
at jrockit/vm/Locks.park(Locks.java:2517)
at sun/misc/Unsafe.park(ZJ)V(Native Method)
at java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
at java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
at weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
at weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
at weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:615)
at weblogic/store/internal/PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" id=25 idx=0x5c tid=1880 prio=5 alive, in native, daemon
at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSocketMuxer$IoCompletionData;)Z(Native Method)
at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" id=26 idx=0x60 tid=4688 prio=5 alive, in native, daemon
at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSocketMuxer$IoCompletionData;)Z(Native Method)
at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=27 idx=0x64 tid=5300 prio=5 alive, in native, daemon
at weblogic/socket/NTSocketMuxer.getIoCompletionResult(Lweblogic/socket/NTSocketMuxer$IoCompletionData;)Z(Native Method)
at weblogic/socket/NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"VDE Transaction Processor Thread" id=30 idx=0x68 tid=4260 prio=2 alive, in native, waiting, daemon
-- Waiting for notification on: com/octetstring/vde/backend/standard/TransactionProcessor@0x12F80720[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at com/octetstring/vde/backend/standard/TransactionProcessor.waitChange(TransactionProcessor.java:367)
^-- Lock released while waiting: com/octetstring/vde/backend/standard/TransactionProcessor@0x12F80720[fat lock]
at com/octetstring/vde/backend/standard/TransactionProcessor.run(TransactionProcessor.java:212)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"DoSManager" id=32 idx=0x70 tid=3492 prio=6 alive, in native, sleeping, native_waiting, daemon
at java/lang/Thread.sleep(J)V(Native Method)
at com/octetstring/vde/DoSManager.run(DoSManager.java:433)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Thread-11" id=33 idx=0x74 tid=5936 prio=5 alive, in native, parked, daemon
-- Parking to wait for: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x12F80FA0
at jrockit/vm/Locks.park0(J)V(Native Method)
at jrockit/vm/Locks.park(Locks.java:2517)
at sun/misc/Unsafe.park(ZJ)V(Native Method)
at java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
at java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
at weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
at weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
at weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:615)
at weblogic/store/internal/PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" id=34 idx=0x78 tid=3976 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/work/ExecuteThread@0x1447C920[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
^-- Lock released while waiting: weblogic/work/ExecuteThread@0x1447C920[fat lock]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Timer-2" id=35 idx=0x7c tid=4992 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: java/util/TaskQueue@0x12F81018[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/util/TimerThread.mainLoop(Timer.java:509)
^-- Lock released while waiting: java/util/TaskQueue@0x12F81018[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=36 idx=0x80 tid=4668 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/work/ExecuteThread@0x1447C9F8[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
^-- Lock released while waiting: weblogic/work/ExecuteThread@0x1447C9F8[fat lock]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Session Monitor" id=37 idx=0x84 tid=4308 prio=5 alive, in native, sleeping, native_waiting, daemon
at java/lang/Thread.sleep(J)V(Native Method)
at com/icesoft/faces/webapp/http/servlet/SessionDispatcher$Listener$1.run(SessionDispatcher.java:315)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Thread-1" id=14 idx=0xb0 tid=1404 prio=5 alive, in native, blocked
-- Blocked trying to get lock: weblogic/servlet/internal/WebAppServletContext@0x1449CBA8[thin lock]
at jrockit/vm/Threads.sleep(I)V(Native Method)
at jrockit/vm/Locks.waitForThinRelease(Locks.java:1209)
at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1342)
at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1259)
at jrockit/vm/Locks.monitorEnter(Locks.java:2466)
at weblogic/servlet/internal/WebAppServletContext.destroy(WebAppServletContext.java:3094)
at weblogic/servlet/internal/ServletContextManager.destroyContext(ServletContextManager.java:240)
at weblogic/servlet/internal/HttpServer.unloadWebApp(HttpServer.java:457)
^-- Holding lock: weblogic/servlet/internal/HttpServer@0x14508638[thin lock]
at weblogic/servlet/internal/WebAppModule.destroyContexts(WebAppModule.java:1424)
at weblogic/servlet/internal/WebAppModule.unprepare(WebAppModule.java:501)
at weblogic/application/internal/flow/ModuleStateDriver$1.previous(ModuleStateDriver.java:339)
at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:329)
at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:309)
at weblogic/application/internal/flow/ModuleStateDriver.unprepare(ModuleStateDriver.java:167)
at weblogic/application/internal/flow/ScopedModuleDriver.unprepare(ScopedModuleDriver.java:212)
at weblogic/application/internal/flow/ModuleListenerInvoker.unprepare(ModuleListenerInvoker.java:285)
at weblogic/application/internal/flow/DeploymentCallbackFlow$1.previous(DeploymentCallbackFlow.java:397)
at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:329)
at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:309)
at weblogic/application/internal/flow/DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:111)
at weblogic/application/internal/flow/DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:102)
at weblogic/application/internal/BaseDeployment$1.previous(BaseDeployment.java:1233)
at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:329)
at weblogic/application/utils/StateMachineDriver.previousState(StateMachineDriver.java:309)
at weblogic/application/internal/BaseDeployment.unprepare(BaseDeployment.java:495)
at weblogic/application/internal/SingleModuleDeployment.unprepare(SingleModuleDeployment.java:39)
at weblogic/application/internal/DeploymentStateChecker.unprepare(DeploymentStateChecker.java:205)
at weblogic/deploy/internal/targetserver/AppContainerInvoker.unprepare(AppContainerInvoker.java:117)
at weblogic/deploy/internal/targetserver/BasicDeployment.unprepare(BasicDeployment.java:287)
at weblogic/management/deploy/internal/DeploymentAdapter$1.doUnprepare(DeploymentAdapter.java:81)
at weblogic/management/deploy/internal/DeploymentAdapter.unprepare(DeploymentAdapter.java:220)
at weblogic/management/deploy/internal/AppTransition$7.transitionApp(AppTransition.java:75)
at weblogic/management/deploy/internal/ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic/management/deploy/internal/ConfiguredDeployments.unprepare(ConfiguredDeployments.java:204)
at weblogic/management/deploy/internal/ConfiguredDeployments.undeploy(ConfiguredDeployments.java:192)
at weblogic/management/deploy/internal/DeploymentServerService.shutdownApps(DeploymentServerService.java:188)
at weblogic/management/deploy/internal/DeploymentServerService.shutdownHelper(DeploymentServerService.java:120)
at weblogic/application/ApplicationShutdownService.halt(ApplicationShutdownService.java:142)
at weblogic/t3/srvr/ServerServicesManager.haltInternal(ServerServicesManager.java:504)
at weblogic/t3/srvr/ServerServicesManager.halt(ServerServicesManager.java:336)
at weblogic/t3/srvr/T3Srvr.shutdown(T3Srvr.java:986)
at weblogic/t3/srvr/T3Srvr.forceShutdown(T3Srvr.java:892)
at weblogic/t3/srvr/T3Srvr$2.run(T3Srvr.java:905)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Thread-14" id=49 idx=0xc4 tid=5752 prio=5 alive, in native, daemon
at bea/jmapi/DiagnosticCommandImpl.execute(Ljava/lang/String;Ljava/io/FileDescriptor;)V(Native Method)
at bea/jmapi/DiagnosticCommandImpl.execute(DiagnosticCommandImpl.java:50)
at com/bea/jvm/DiagnosticCommand.execute(DiagnosticCommand.java:242)
at com/bea/jvm/DiagnosticCommand$Command.execute(DiagnosticCommand.java:394)
at bea/jmapi/ThreadSystemImpl.getThreadStackDump(ThreadSystemImpl.java:98)
at weblogic/platform/JRockitVM.threadDump(JRockitVM.java:61)
at weblogic/t3/srvr/T3Srvr.logThreadDump(T3Srvr.java:280)
at weblogic/t3/srvr/ServerLifeCycleTimerThread.run(ServerLifeCycleTimerThread.java:77)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" id=50 idx=0xc8 tid=5500 prio=5 alive, in native, waiting, daemon
-- Waiting for notification on: weblogic/work/ExecuteThread@0x01C1A998[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)
^-- Lock released while waiting: weblogic/work/ExecuteThread@0x01C1A998[fat lock]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
Blocked lock chains
===================
Chain 2:
"Thread-1" id=14 idx=0xb0 tid=1404 waiting for weblogic/servlet/internal/WebAppServletContext@0x1449CBA8 held by:
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x44 tid=5008 in chain 1
Open lock chains
================
Chain 1:
"Main Thread" id=1 idx=0x4 tid=4728 waiting for java/lang/Class@0x15AB9AE0 held by:
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x44 tid=5008 (waiting on notification)
===== END OF THREAD DUMP ===============

Hi,
This is a one off issue which occurred when there are thread dumps originating from WLS trying to determine if there are stuck threads in the system.
The upgrade to R28 is pertinent because these code level changes will not be feasible to be backported and that the code level fixes are included in R28.1.1.
Please upgrade the Jrockit version to R28.1.1.
Mark If this helps you.
Regards,
Kishore

WebLogic server is shut down automatically

 After i install weblogic6.1 and run default server, I got the fowllowing message
 and then server is shut down automatically, I tried it days before, and it works,
 why not work now?
 Thanks in advance!
 moonriver
 <Nov 6, 2001 11:40:53 PM EST> <Notice> <Management> <Starting discovery of Managed
 Server... This feature is on by default, you may turn this off by passing -Dweblogic.management.discover=false>
 <Nov 6, 2001 11:40:58 PM EST> <Notice> <Management> <Application Poller not started
 for production server.>
 <Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <Unable to create a
 server socket for port: 7002. java.net.BindException: Address in use: JVM_Bind
 Perhaps another process is using port 7002.>
 <Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <The WebLogic Server
 is no longer listening for connections. You should probably restart it.>
 <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <Server shutdown has been
 requested by system>
 <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <The shutdown sequence
 has been initiated.>
 <Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <Unable to create a
 server socket for port: 7001. java.net.BindException: Address in use: JVM_Bind
 Perhaps another process is using port 7001.>
 <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <Server shutdown has been
 requested by system>
 <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <The shutdown sequence
 has been initiated.>
 <Nov 6, 2001 11:41:58 PM EST> <Notice> <WebLogicServer> <Started WebLogic AdminServer
 "myserver" for domain "mydomain" running in Production Mode>


Most likely you have another WebLogic instance already listening on 7001.
 Moonriver Sun <[email protected]> wrote:
 > After i install weblogic6.1 and run default server, I got the fowllowing message
 > and then server is shut down automatically, I tried it days before, and it works,
 > why not work now?
 > Thanks in advance!
 > moonriver
 > -----------------
 > <Nov 6, 2001 11:40:53 PM EST> <Notice> <Management> <Starting discovery of Managed
 > Server... This feature is on by default, you may turn this off by passing -Dweblogic.management.discover=false>
 > <Nov 6, 2001 11:40:58 PM EST> <Notice> <Management> <Application Poller not started
 > for production server.>
 > <Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <Unable to create a
 > server socket for port: 7002. java.net.BindException: Address in use: JVM_Bind
 > Perhaps another process is using port 7002.>
 > <Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <The WebLogic Server
 > is no longer listening for connections. You should probably restart it.>
 > <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <Server shutdown has been
 > requested by system>
 > <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <The shutdown sequence
 > has been initiated.>
 > <Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <Unable to create a
 > server socket for port: 7001. java.net.BindException: Address in use: JVM_Bind
 > Perhaps another process is using port 7001.>
 > <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <Server shutdown has been
 > requested by system>
 > <Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <The shutdown sequence
 > has been initiated.>
 > <Nov 6, 2001 11:41:58 PM EST> <Notice> <WebLogicServer> <Started WebLogic AdminServer
 > "myserver" for domain "mydomain" running in Production Mode>
 Dimitri

WebLogic server is shut down automatically(in win2k pro)

After i install weblogic6.1 and run default server, I got the fowllowing message
and then server is shut down automatically, I tried it days before, and it works,
why not work now?
Thanks in advance!
moonriver
<Nov 6, 2001 11:40:53 PM EST> <Notice> <Management> <Starting discovery of Managed
Server... This feature is on by default, you may turn this off by passing -Dweblogic.management.discover=false>
<Nov 6, 2001 11:40:58 PM EST> <Notice> <Management> <Application Poller not started
for production server.>
<Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <Unable to create a
server socket for port: 7002. java.net.BindException: Address in use: JVM_Bind
Perhaps another process is using port 7002.>
<Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <The WebLogic Server
is no longer listening for connections. You should probably restart it.>
<Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <Server shutdown has been
requested by system>
<Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Nov 6, 2001 11:40:58 PM EST> <Emergency> <WebLogicServer> <Unable to create a
server socket for port: 7001. java.net.BindException: Address in use: JVM_Bind
Perhaps another process is using port 7001.>
<Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <Server shutdown has been
requested by system>
<Nov 6, 2001 11:40:58 PM EST> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Nov 6, 2001 11:41:58 PM EST> <Notice> <WebLogicServer> <Started WebLogic AdminServer
"myserver" for domain "mydomain" running in Production Mode>

[att1.html]

Weblogic shutting down abnormally

hi my weblogic server is shutting down abnormally.when i checked the weblogic.log
file i could trace the following error i dont know whether this error is related to the abnormal shutdown of weblogic i am
copying the error message for your reference
ERROR: Mon Apr 08 13:20:00 CEST 2002:<W> <SSLListenThread> Connection rejected: 'Login
timed out after: '25000' ms on socket: 'Socket[addr=eurcic1.emea.citicorp.com/16
9.194.168.43,port=63988,localport=7003}''
please help me out with a solution at the earliest
Regards
Surender

Is it actually shutting down (ie is it clean)? or is it dying or hanging?

Weblogic shuts down unexpectedly

Hi all,
My weblogic server 4.5.1 with SP 8 shuts down every 15 mins. Does
anyone has any idea why is that happening? I am new to weblogic... so if
you guys need any additional information from me before you can help me out.
Please let me know. Many thanks!
--Tony

We have a very similar sounding problem. We can start the server and recon users fine for a period of time. Then the recon seems to hang until the Weblogic server is restarted. I can still get into the Design Console or the web app but I can't successfully seem to get any more tcRecon instances. After the error no additional users will show up in the design console.
We have the PeopleSoft connector on OIM 9.1.0.2 and Weblogic 10.3.
Do you have any insight of things to look at?
Thanks.

Weblogic 11g abruptly shutting down while deployment

Hi Guys,
I have configured a weblogic server in a UNIX box & the server works fine when i deploy a working ear.
But if the ear has any initialization codes (init) that throws error, the deployment of the application fails as expected but the server shuts down abruptly.
Is there any way I can stop the server from shutting down abruptly?
Thanks & Regards,
Varun V. Iyer
Edited by: Varun V. Iyer on 11 Apr, 2013 11:07 PM

Hi,
Can you show what's happening in server logs.
Thanks,
Ranjan

Suddenly WebLogic Server shutting down while doing testing

Hi All,
While we doing testing weblogic server shutting down.Here is the log generated by weblogic.
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> Listen failed. Failure count: 1
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> ListenThread:run failed:
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> **** The WebLogic Server is no longer listening for connections.
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> **** You should probably restart it.
Tue Aug 22 12:38:27 EDT 2000: <WebLogicServer> Server shutdown by system
Tue Aug 22 12:38:27 EDT 2000: <WebLogicServer> Server shutdown commencing NOW
Tue Aug 22 12:38:28 EDT 2000: <HTTP> Destroying servlets in default servlet context.
Tue Aug 22 12:38:28 EDT 2000:<E> <SSLListenThread> ListenThread:run failed:
Please let me know the reason for this.It's very very urgent.
Thanks
Venkat

See case #188305. There is not a whole lot of information there and we really don't like to reproduce this.
If it happens again we will add more info to the case. In the log file we have seen 'class not found' for
weblogic.utils.... classes before it shuts down. Boot it again under no load and it comes up fine.
Mike.
Kumar Allamraju <[email protected]> wrote:
Hmm.. that's interesting.
What version of WLS, SP-level? what 's the avg load that you are putting on WLS? Is it in a clustered environment? what
the min/max heap size, executeThreadCount etc...
Any other details that you can provide us would be helpful for us to debug further.
Kumar
Michael Reiche wrote:
Kumar -
We have seen this as well when load testing. It's hard to ignore the WL server shutting down by itself for no reason.
Mike Reiche
Kumar Allamraju <[email protected]> wrote:
You will only see this, if WLS shutdown is commenced and if you try to PING the server.
you can safely ignore it.
Kumar
Venkat wrote:
Hi All,
While we doing testing weblogic server shutting down.Here is the log generated by weblogic.
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> Listen failed. Failure count: 1
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> ListenThread:run failed:
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> **** The WebLogic Server is no longer listening for connections.
Tue Aug 22 12:38:27 EDT 2000:<E> <ListenThread> **** You should probably restart it.
Tue Aug 22 12:38:27 EDT 2000: <WebLogicServer> Server shutdown by system
Tue Aug 22 12:38:27 EDT 2000: <WebLogicServer> Server shutdown commencing NOW
Tue Aug 22 12:38:28 EDT 2000: <HTTP> Destroying servlets in default servlet context.
Tue Aug 22 12:38:28 EDT 2000:<E> <SSLListenThread> ListenThread:run failed:
Please let me know the reason for this.It's very very urgent.
Thanks
Venkat

Weblogic 10.3.4 timeout on shut down

Similar Messages

Maybe you are looking for