Running Weblogic 7.0
I have installed weblogic 7.0 in my system. Its main folder is bea under which i have got four folders namely jdk131_03, logs, utils, weblogic 700. Under Weblogic 700, we have got common, ebcc, integration, portal, samples, server, uninstall, workshop folder. I want to know where should i place my jsp and servlet file. please let me know asap.How to set the classpath and how to start my weblogic server from DOS.
Copy the servlet class file to the
mydomain\applications\
DefaultWebApp\WEB-INF\classes directory.
In the web.xml file located in the mydomain\applications\DefaultWebApp\
WEB-INF\ directory add <servlet/> tag for the servlet.
<web-app> and </web-app> tags:
<servlet>
<servlet-name>
ServletB
</servlet-name>
<servlet-class>
com.servlet.ServletB
</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>
ServletB
</servlet-name>
<url-pattern>
servletB
</url-pattern>
</servlet-mapping>
In the browser request the servlet
with
http://localhost:7001/servletB
Similar Messages
-
Rogue cpu hog while running WebLogic
Hello,
My application is a servlet/EJB/Oracle application running on
WebLogic.
During stress test, I am seeing a java thread that is taking up 50% of
available cpu on a dual cpu machine. The thread remains at 100% even
after the load is over.
Here are some data and observations:
0. I am running WebLogic 7.0.1 on RedHat 7.2 (kernel 2.4.9-31), dual
cpu. My application consists of a few servlets talking to some 20
stateless session beans which uses CMP 2.0 entity beans to talk to
Oracle 9.0.1. We are using the oci jdbc driver.
1. After the load was over, I used ps and saw that the thread was
still running. I tracked its parent to the weblogic root process.
2. I ran top and saw the thread taking up 50% of available cpu
(sometimes it is 100% of a cpu, but it may also be 60% of cpu1 and 40%
of cpu2, etc).
3. I did a full thread dump, all but one thread are weblogic's or the
jvm's internal threads. My application did have one thread remaining,
but it is a periodic cleanup thread that wakes up every 30 secs and I
believe it is benign. I am not able to quickly point out which thread
is the rogue thread.
4. Using vmstat, I believe the rogue thread kicked in about 10 minutes
into the load (but this number varies from load to load, there was one
that kicked in after an hour). After that point, I saw the number of
runnable process remained at least one, and the idle cpu never goes
above 50 (remember it is a dual cpu machine). After I stopped the
load, the number of runnable process stayed at 1 and the idle cpu
stayed at 50.
5. This thread does not always kicked in, sometimes I would be able to
complete a 24-hour load and did not see the evidence of the thread.
6. The presence of the thread caused a 30% performance degradation.
So here is the question, what is this thread and how can I stop it
from kicking in?
I have attached a full thread dump and the outputs of top and vmstat.
I have also searched previous posts and apparently this has been seen
before by other users of weblogic, but in those threads of discussions
I never saw a resolution.
Thanks in advance,
Chishun Kwong
=================
Full thread dump:
"Thread-11" daemon prio=1 tid=0x9b793138 nid=0xc59 waiting on monitor
[0xa7153000..0xa7153870]
at java.lang.Thread.sleep(Native Method)
at com.mycompany.myapp.SomeCleanupThread.run(SomeCleanupThread.java:234)
"ListenThread.Default" prio=1 tid=0x9fad0578 nid=0xb58 runnable
[0xa694f000..0xa694f870]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:256)
"ExecuteThread: '1' for queue: 'JMSStore<null>.ioThreadPool'" daemon
prio=1 tid=0x9fa0b438 nid=0xb27 waiting on monitor
[0xa674f000..0xa674f870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMSStore<null>.ioThreadPool'" daemon
prio=1 tid=0x9fa0b2d0 nid=0xb26 waiting on monitor
[0xa5dec000..0xa5dec870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
tid=0x8527000 nid=0xb21 waiting on monitor [0xa5bec000..0xa5bec870]
at java.lang.Object.wait(Native Method)
at weblogic.jms.backend.BETimerTree.execute(BETimerTree.java:140)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x83bec38 nid=0xb20 waiting on monitor [0xa37eb000..0xa37eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x83beae8 nid=0xb1f waiting on monitor [0xa35eb000..0xa35eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x85198f8 nid=0xb1e waiting on monitor [0xa33eb000..0xa33eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x85d8368 nid=0xb1d waiting on monitor [0xa31eb000..0xa31eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"CoreHealthMonitor" daemon prio=1 tid=0x8138938 nid=0xa97 waiting on
monitor [0xa2cff000..0xa2cff870]
at java.lang.Thread.sleep(Native Method)
at weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:114)
"ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x83be530 nid=0xa96 waiting on monitor [0xa29ff000..0xa29ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8246120 nid=0xa95 waiting on monitor [0xa27ff000..0xa27ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x834e868 nid=0xa94 waiting on monitor [0xa25ff000..0xa25ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x85813f8 nid=0xa93 waiting on monitor [0xa23ff000..0xa23ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x83be860 nid=0xa92 waiting on monitor [0xa21ff000..0xa21ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8504748 nid=0xa91 waiting on monitor [0xa1fff000..0xa1fff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x82f2908 nid=0xa90 waiting on monitor [0xa1dff000..0xa1dff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8396dd0 nid=0xa8f waiting on monitor [0xa1bff000..0xa1bff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8588b78 nid=0xa8e waiting on monitor [0xa19ff000..0xa19ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x858e000 nid=0xa8d waiting on monitor [0xa17ff000..0xa17ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x844c6b0 nid=0xa8c waiting on monitor [0xa15ff000..0xa15ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x837b8b0 nid=0xa8b waiting on monitor [0xa13ff000..0xa13ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x82158f0 nid=0xa8a waiting on monitor [0xa11ff000..0xa11ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x840a6f8 nid=0xa89 waiting on monitor [0xa0fff000..0xa0fff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8398578 nid=0xa88 waiting on monitor [0xa0dff000..0xa0dff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x8222408 nid=0xa87 waiting on monitor
[0xa0bff000..0xa0bff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x847df98 nid=0xa86 waiting on monitor
[0xa09ff000..0xa09ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x856cd28 nid=0xa85 waiting on monitor
[0xa07ff000..0xa07ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"Thread-4" prio=1 tid=0x8523528 nid=0xa84 waiting on monitor
[0xa05ff000..0xa05ff870]
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:427)
at java.util.TimerThread.run(Timer.java:380)
"ExecuteThread: '1' for queue: 'DRS'" daemon prio=1 tid=0x8582bc0
nid=0xa83 waiting on monitor [0x9feff000..0x9feff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'DRS'" daemon prio=1 tid=0x85640d8
nid=0xa82 waiting on monitor [0x9fcff000..0x9fcff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"VDE Transaction Processor Thread" prio=1 tid=0xa021c060 nid=0xa53
waiting on monitor [0x9f9ff000..0x9f9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:306)
at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:192)
"ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030f218 nid=0xa52 waiting on monitor
[0x9f7ff000..0x9f7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030e7d0 nid=0xa51 waiting on monitor
[0x9f5ff000..0x9f5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030dd88 nid=0xa50 waiting on monitor
[0x9f3ff000..0x9f3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030d340 nid=0xa4f waiting on monitor
[0x9f1ff000..0x9f1ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030c8f8 nid=0xa4e waiting on monitor
[0x9edff000..0x9edff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030beb0 nid=0xa4d waiting on monitor
[0x9ebff000..0x9ebff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030b468 nid=0xa4c waiting on monitor
[0x9e9ff000..0x9e9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030aa20 nid=0xa4b waiting on monitor
[0x9e7ff000..0x9e7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa0309fd8 nid=0xa4a waiting on monitor
[0x9e5ff000..0x9e5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa0309990 nid=0xa49 waiting on monitor
[0x9e3ff000..0x9e3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
prio=1 tid=0xa0309748 nid=0xa48 waiting on monitor
[0x9e1ff000..0x9e1ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
prio=1 tid=0xa0309530 nid=0xa47 waiting on monitor
[0x9dfff000..0x9dfff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"TimeEventGenerator" daemon prio=1 tid=0x9ef68d50 nid=0xa46 waiting on
monitor [0x9ddff000..0x9ddff870]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=1
tid=0x9b77b5e0 nid=0xa45 waiting on monitor [0x9dbff000..0x9dbff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=1
tid=0x9b77b3c8 nid=0xa44 waiting on monitor [0x9d9ff000..0x9d9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"HighPriority TimeEventGenerator" daemon prio=1 tid=0x9b77b1d8
nid=0xa43 waiting on monitor [0x9d7ff000..0x9d7ff870]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=1 tid=0x9bfc1e48 nid=0xa41 waiting
on monitor [0x9d5ff000..0x9d5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:60)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x9ef45218
nid=0xa40 waiting for monitor entry [0x9d3ff000..0x9d3ff870]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x9ef460f8
nid=0xa3f runnable [0x9d1ff000..0x9d1ff870]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:612)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x9ef64588
nid=0xa3e waiting for monitor entry [0x9cfff000..0x9cfff870]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x9ef69070
nid=0xa3d waiting on monitor [0x9cdff000..0x9cdff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x9ef6abb8
nid=0xa3c waiting on monitor [0x9cbff000..0x9cbff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x9ef6a5d8
nid=0xa3b waiting on monitor [0x9c9ff000..0x9c9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x9ef69be8
nid=0xa3a waiting on monitor [0x9c7ff000..0x9c7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'lookup_servlet'" daemon prio=1
tid=0x9ef699f8 nid=0xa39 waiting on monitor [0x9c5ff000..0x9c5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'lookup_servlet'" daemon prio=1
tid=0x9b705c18 nid=0xa38 waiting on monitor [0x9c3ff000..0x9c3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"Thread-0" daemon prio=1 tid=0x9effaea8 nid=0xa34 waiting on monitor
[0x9c1ff000..0x9c1ff870]
at java.lang.Thread.sleep(Native Method)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1660)
at java.lang.Thread.run(Thread.java:479)
"Signal Dispatcher" daemon prio=1 tid=0x80be850 nid=0x9fe waiting on
monitor [0..0]
"Finalizer" daemon prio=1 tid=0x80b69e8 nid=0x9fb waiting on monitor
[0x983ae000..0x983ae870]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
"Reference Handler" daemon prio=1 tid=0x80b6618 nid=0x9fa waiting on
monitor [0x981ae000..0x981ae870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
"main" prio=1 tid=0x804f3d0 nid=0x9e0 waiting on monitor
[0xbfffb000..0xbfffb8b4]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1042)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:313)
at weblogic.Server.main(Server.java:32)
"VM Thread" prio=1 tid=0x80b3d68 nid=0x9f9 runnable
"VM Periodic Task Thread" prio=1 tid=0x80bd4a0 nid=0x9fc waiting on
monitor
"Suspend Checker Thread" prio=1 tid=0x80bde78 nid=0x9fd runnable
==============
Output of top:
11:17am up 20:14, 2 users, load average: 1.16, 1.28, 1.50
185 processes: 183 sleeping, 2 running, 0 zombie, 0 stopped
CPU0 states: 0.1% user, 65.1% system, 0.0% nice, 34.0% idle
CPU1 states: 100.0% user, 0.0% system, 0.0% nice, 0.0% idle
Mem: 2316784K av, 2306924K used, 9860K free, 72K shrd,
90844K buff
Swap: 2097112K av, 0K used, 2097112K free
1178236K cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
COMMAND
2560 root 14 0 943M 943M 42492 R 99.9 41.7 1155m java
30119 wf 11 0 1288 1284 832 R 66.0 0.0 0:03 top
1 root 8 0 520 520 452 S 0.0 0.0 0:04 init
2 root 9 0 0 0 0 SW 0.0 0.0 0:00
keventd
===========================================================
Output of vmstat (when I believe the rogue thread started):
procs memory swap io system
cpu
r b w swpd free buff cache si so bi bo in cs
us sy id
0 0 0 0 1556812 15476 274440 0 0 0 212 445 845
17 1 82
0 0 0 0 1556780 15476 274476 0 0 0 0 400 667
6 0 93
0 0 0 0 1556736 15476 274484 0 0 0 0 175 361
1 1 98
4 0 1 0 1554032 15480 274564 0 0 0 94 651 2769
25 3 72
1 0 0 0 1553936 15480 274672 0 0 0 0 826 3072
33 4 63
0 0 0 0 1553804 15484 274772 0 0 0 208 836 1898
25 4 72
0 0 0 0 1553764 15484 274816 0 0 0 0 424 1510
8 1 91
4 0 0 0 1553564 15484 275144 0 0 0 0 1479 7049
64 10 26
4 0 2 0 1553484 15496 275464 0 0 0 342 1471 8538
57 7 36
1 0 0 0 1553368 15496 275632 0 0 0 0 940 3199
55 5 40
1 0 0 0 1553308 15496 275720 0 0 0 316 580 1437
63 3 34
1 0 0 0 1553304 15496 275776 0 0 0 0 606 1108
71 1 28
1 0 0 0 1553288 15496 275912 0 0 0 0 683 1740
68 3 29
2 0 1 0 1543236 15500 275980 0 0 0 180 383 3191
66 2 33"laxman" <[email protected]> wrote in message
news:[email protected]...
|
| I have had the exact same problem! It took us a long time to find the
resolution.
| I had a BEA engineer and a SUN engineer on site and finally we discovered
it
| to be a problem with the SUN JVM JDK1.3.1
|
| The BEA contact who resolved this for us is Richard Wallace.
|
| -- Laxman
|
|
| Rob Woollen <[email protected]> wrote:
| >Interesting. I think we'll need even more information to know for sure
| >
| >what's going on here. WLS (almost) never creates threads after it
| >starts. However, it does fork a process to compile JSPs. I'm
| >suspicious this could be a spinning javac process. If you cat
| >/proc/<pid>/cmdline then we should be able to tell whether it's a server
| >
| >thread or a javac process.
| >
| >Does your app start any threads or processes? The thread dump you
| >showed appeared to be idle.
| >
| >-- Rob
| >
| >Chishun Kwong wrote:
| >> Hello,
| >>
| >> My application is a servlet/EJB/Oracle application running on
| >> WebLogic.
| >> During stress test, I am seeing a java thread that is taking up 50%
| >of
| >> available cpu on a dual cpu machine. The thread remains at 100% even
| >> after the load is over.
| >> Here are some data and observations:
| >>
| >> 0. I am running WebLogic 7.0.1 on RedHat 7.2 (kernel 2.4.9-31), dual
| >> cpu. My application consists of a few servlets talking to some 20
| >> stateless session beans which uses CMP 2.0 entity beans to talk to
| >> Oracle 9.0.1. We are using the oci jdbc driver.
| >>
| >> 1. After the load was over, I used ps and saw that the thread was
| >> still running. I tracked its parent to the weblogic root process.
| >>
| >> 2. I ran top and saw the thread taking up 50% of available cpu
| >> (sometimes it is 100% of a cpu, but it may also be 60% of cpu1 and
| >40%
| >> of cpu2, etc).
| >>
| >> 3. I did a full thread dump, all but one thread are weblogic's or the
| >> jvm's internal threads. My application did have one thread remaining,
| >> but it is a periodic cleanup thread that wakes up every 30 secs and
| >I
| >> believe it is benign. I am not able to quickly point out which thread
| >> is the rogue thread.
| >>
| >> 4. Using vmstat, I believe the rogue thread kicked in about 10 minutes
| >> into the load (but this number varies from load to load, there was
| >one
| >> that kicked in after an hour). After that point, I saw the number of
| >> runnable process remained at least one, and the idle cpu never goes
| >> above 50 (remember it is a dual cpu machine). After I stopped the
| >> load, the number of runnable process stayed at 1 and the idle cpu
| >> stayed at 50.
| >>
| >> 5. This thread does not always kicked in, sometimes I would be able
| >to
| >> complete a 24-hour load and did not see the evidence of the thread.
| >>
| >> 6. The presence of the thread caused a 30% performance degradation.
| >>
| >> So here is the question, what is this thread and how can I stop it
| >> from kicking in?
| >>
| >> I have attached a full thread dump and the outputs of top and vmstat.
| >> I have also searched previous posts and apparently this has been seen
| >> before by other users of weblogic, but in those threads of discussions
| >> I never saw a resolution.
| >>
| >> Thanks in advance,
| >> Chishun Kwong
| >>
| >> =================
| >>
| >> Full thread dump:
| >>
| >> "Thread-11" daemon prio=1 tid=0x9b793138 nid=0xc59 waiting on monitor
| >> [0xa7153000..0xa7153870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
com.mycompany.myapp.SomeCleanupThread.run(SomeCleanupThread.java:234)
| >>
| >> "ListenThread.Default" prio=1 tid=0x9fad0578 nid=0xb58 runnable
| >> [0xa694f000..0xa694f870]
| >> at java.net.PlainSocketImpl.socketAccept(Native Method)
| >> at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
| >> at java.net.ServerSocket.implAccept(ServerSocket.java:238)
| >> at java.net.ServerSocket.accept(ServerSocket.java:217)
| >> at
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
| >> at weblogic.t3.srvr.ListenThread.run(ListenThread.java:256)
| >>
| >> "ExecuteThread: '1' for queue: 'JMSStore<null>.ioThreadPool'" daemon
| >> prio=1 tid=0x9fa0b438 nid=0xb27 waiting on monitor
| >> [0xa674f000..0xa674f870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMSStore<null>.ioThreadPool'" daemon
| >> prio=1 tid=0x9fa0b2d0 nid=0xb26 waiting on monitor
| >> [0xa5dec000..0xa5dec870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
| >> tid=0x8527000 nid=0xb21 waiting on monitor [0xa5bec000..0xa5bec870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.jms.backend.BETimerTree.execute(BETimerTree.java:140)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x83bec38 nid=0xb20 waiting on monitor [0xa37eb000..0xa37eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x83beae8 nid=0xb1f waiting on monitor [0xa35eb000..0xa35eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x85198f8 nid=0xb1e waiting on monitor [0xa33eb000..0xa33eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x85d8368 nid=0xb1d waiting on monitor [0xa31eb000..0xa31eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "CoreHealthMonitor" daemon prio=1 tid=0x8138938 nid=0xa97 waiting on
| >> monitor [0xa2cff000..0xa2cff870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:11
4)
| >>
| >> "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x83be530 nid=0xa96 waiting on monitor [0xa29ff000..0xa29ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8246120 nid=0xa95 waiting on monitor [0xa27ff000..0xa27ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x834e868 nid=0xa94 waiting on monitor [0xa25ff000..0xa25ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x85813f8 nid=0xa93 waiting on monitor [0xa23ff000..0xa23ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x83be860 nid=0xa92 waiting on monitor [0xa21ff000..0xa21ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8504748 nid=0xa91 waiting on monitor [0xa1fff000..0xa1fff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x82f2908 nid=0xa90 waiting on monitor [0xa1dff000..0xa1dff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8396dd0 nid=0xa8f waiting on monitor [0xa1bff000..0xa1bff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8588b78 nid=0xa8e waiting on monitor [0xa19ff000..0xa19ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x858e000 nid=0xa8d waiting on monitor [0xa17ff000..0xa17ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x844c6b0 nid=0xa8c waiting on monitor [0xa15ff000..0xa15ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x837b8b0 nid=0xa8b waiting on monitor [0xa13ff000..0xa13ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x82158f0 nid=0xa8a waiting on monitor [0xa11ff000..0xa11ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x840a6f8 nid=0xa89 waiting on monitor [0xa0fff000..0xa0fff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8398578 nid=0xa88 waiting on monitor [0xa0dff000..0xa0dff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x8222408 nid=0xa87 waiting on monitor
| >> [0xa0bff000..0xa0bff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x847df98 nid=0xa86 waiting on monitor
| >> [0xa09ff000..0xa09ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x856cd28 nid=0xa85 waiting on monitor
| >> [0xa07ff000..0xa07ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "Thread-4" prio=1 tid=0x8523528 nid=0xa84 waiting on monitor
| >> [0xa05ff000..0xa05ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.util.TimerThread.mainLoop(Timer.java:427)
| >> at java.util.TimerThread.run(Timer.java:380)
| >>
| >> "ExecuteThread: '1' for queue: 'DRS'" daemon prio=1 tid=0x8582bc0
| >> nid=0xa83 waiting on monitor [0x9feff000..0x9feff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'DRS'" daemon prio=1 tid=0x85640d8
| >> nid=0xa82 waiting on monitor [0x9fcff000..0x9fcff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "VDE Transaction Processor Thread" prio=1 tid=0xa021c060 nid=0xa53
| >> waiting on monitor [0x9f9ff000..0x9f9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at
com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(Transac
tionProcessor.java:306)
| >> at
com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionPro
cessor.java:192)
| >>
| >> "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030f218 nid=0xa52 waiting on monitor
| >> [0x9f7ff000..0x9f7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030e7d0 nid=0xa51 waiting on monitor
| >> [0x9f5ff000..0x9f5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030dd88 nid=0xa50 waiting on monitor
| >> [0x9f3ff000..0x9f3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030d340 nid=0xa4f waiting on monitor
| >> [0x9f1ff000..0x9f1ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030c8f8 nid=0xa4e waiting on monitor
| >> [0x9edff000..0x9edff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030beb0 nid=0xa4d waiting on monitor
| >> [0x9ebff000..0x9ebff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030b468 nid=0xa4c waiting on monitor
| >> [0x9e9ff000..0x9e9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030aa20 nid=0xa4b waiting on monitor
| >> [0x9e7ff000..0x9e7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa0309fd8 nid=0xa4a waiting on monitor
| >> [0x9e5ff000..0x9e5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa0309990 nid=0xa49 waiting on monitor
| >> [0x9e3ff000..0x9e3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
| >> prio=1 tid=0xa0309748 nid=0xa48 waiting on monitor
| >> [0x9e1ff000..0x9e1ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
| >> prio=1 tid=0xa0309530 nid=0xa47 waiting on monitor
| >> [0x9dfff000..0x9dfff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "TimeEventGenerator" daemon prio=1 tid=0x9ef68d50 nid=0xa46 waiting
| >on
| >> monitor [0x9ddff000..0x9ddff870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
| >> at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:139)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=1
| >> tid=0x9b77b5e0 nid=0xa45 waiting on monitor [0x9dbff000..0x9dbff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=1
| >> tid=0x9b77b3c8 nid=0xa44 waiting on monitor [0x9d9ff000..0x9d9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "HighPriority TimeEventGenerator" daemon prio=1 tid=0x9b77b1d8
| >> nid=0xa43 waiting on monitor [0x9d7ff000..0x9d7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
| >> at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:139)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "SpinnerRandomSource" daemon prio=1 tid=0x9bfc1e48 nid=0xa41 waiting
| >> on monitor [0x9d5ff000..0x9d5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at
weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:6
0)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x9ef45218
| >> nid=0xa40 waiting for monitor entry [0x9d3ff000..0x9d3ff870]
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x9ef460f8
| >> nid=0xa3f runnable [0x9d1ff000..0x9d1ff870]
| >> at weblogic.socket.PosixSocketMuxer.poll(Native Method)
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:612)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x9ef64588
| >> nid=0xa3e waiting for monitor entry [0x9cfff000..0x9cfff870]
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x9ef69070
| >> nid=0xa3d waiting on monitor [0x9cdff000..0x9cdff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x9ef6abb8
| >> nid=0xa3c waiting on monitor [0x9cbff000..0x9cbff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x9ef6a5d8
| >> nid=0xa3b waiting on monitor [0x9c9ff000..0x9c9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x9ef69be8
| >> nid=0xa3a waiting on monitor [0x9c7ff000..0x9c7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'lookup_servlet'" daemon prio=1
| >> tid=0x9ef699f8 nid=0xa39 waiting on monitor [0x9c5ff000..0x9c5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'lookup_servlet'" daemon prio=1
| >> tid=0x9b705c18 nid=0xa38 waiting on monitor [0x9c3ff000..0x9c3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "Thread-0" daemon prio=1 tid=0x9effaea8 nid=0xa34 waiting on monitor
| >> [0x9c1ff000..0x9c1ff870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1660)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "Signal Dispatcher" daemon prio=1 tid=0x80be850 nid=0x9fe waiting on
| >> monitor [0..0]
| >>
| >> "Finalizer" daemon prio=1 tid=0x80b69e8 nid=0x9fb waiting on monitor
| >> [0x983ae000..0x983ae870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
| >> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
| >> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
| >>
| >> "Reference Handler" daemon prio=1 tid=0x80b6618 nid=0x9fa waiting on
| >> monitor [0x981ae000..0x981ae870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
| >>
| >> "main" prio=1 tid=0x804f3d0 nid=0x9e0 waiting on monitor
| >> [0xbfffb000..0xbfffb8b4]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1042)
| >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:313)
| >> at weblogic.Server.main(Server.java:32)
| >>
| >> "VM Thread" prio=1 tid=0x80b3d68 nid=0x9f9 runnable
| >>
| >> "VM Periodic Task Thread" prio=1 tid=0x80bd4a0 nid=0x9fc waiting on
| >> monitor
| >> "Suspend Checker Thread" prio=1 tid=0x80bde78 nid=0x9fd runnable
| >>
| >> ==============
| >>
| >> Output of top:
| >>
| >> 11:17am up 20:14, 2 users, load average: 1.16, 1.28, 1.50
| >> 185 processes: 183 sleeping, 2 running, 0 zombie, 0 stopped
| >> CPU0 states: 0.1% user, 65.1% system, 0.0% nice, 34.0% idle
| >> CPU1 states: 100.0% user, 0.0% system, 0.0% nice, 0.0% idle
| >> Mem: 2316784K av, 2306924K used, 9860K free, 72K shrd,
| >
| >> 90844K buff
| >> Swap: 2097112K av, 0K used, 2097112K free
| >> 1178236K cached
| >>
| >> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
| >> COMMAND
| >> 2560 root 14 0 943M 943M 42492 R 99.9 41.7 1155m java
| >> 30119 wf 11 0 1288 1284 832 R 66.0 0.0 0:03 top
| >> 1 root 8 0 520 520 452 S 0.0 0.0 0:04 init
| >> 2 root 9 0 0 0 0 SW 0.0 0.0 0:00
| >> keventd
| >>
| >> ===========================================================
| >>
| >> Output of vmstat (when I believe the rogue thread started):
| >>
| >> procs memory swap io system
| >
| >> cpu
| >> r b w swpd free buff cache si so bi bo in cs
| >
| >> us sy id
| >> 0 0 0 0 1556812 15476 274440 0 0 0 212 445 845
| >
| >> 17 1 82
| >> 0 0 0 0 1556780 15476 274476 0 0 0 0 400 667
| >
| >> 6 0 93
| >> 0 0 0 0 1556736 15476 274484 0 0 0 0 175 361
| >
| >> 1 1 98
| >> 4 0 1 0 1554032 15480 274564 0 0 0 94 651 2769
| >
| >> 25 3 72
| >> 1 0 0 0 1553936 15480 274672 0 0 0 0 826 3072
| >
| >> 33 4 63
| >> 0 0 0 0 1553804 15484 274772 0 0 0 208 836 1898
| >
| >> 25 4 72
| >> 0 0 0 0 1553764 15484 274816 0 0 0 0 424 1510
| >
| >> 8 1 91
| >> 4 0 0 0 1553564 15484 275144 0 0 0 0 1479 7049
| >
| >> 64 10 26
| >> 4 0 2 0 1553484 15496 275464 0 0 0 342 1471 8538
| >
| >> 57 7 36
| >> 1 0 0 0 1553368 15496 275632 0 0 0 0 940 3199
| >
| >> 55 5 40
| >> 1 0 0 0 1553308 15496 275720 0 0 0 316 580 1437
| >
| >> 63 3 34
| >> 1 0 0 0 1553304 15496 275776 0 0 0 0 606 1108
| >
| >> 71 1 28
| >> 1 0 0 0 1553288 15496 275912 0 0 0 0 683 1740
| >
| >> 68 3 29
| >> 2 0 1 0 1543236 15500 275980 0 0 0 180 383 3191
| >
| >> 66 2 33
| >
|
|
Is this specific to a version of the 1.3.1 JVM? (1.3.1_x)?
k -
Memory maxed out when running weblogic 4.5
I am the tech support guy for my office, but I am WebLogic illiterate. I have a user who is running WebLogic, but when he runs it, his RAM and virtual memory max out. Are there any settings in WebLogic for memory allocation? Or is there a known problem with memory?
Please see my reply in misc.
Michael Girdley
Product Manager, WebLogic Server
BEA Systems Inc.
Jay A. Fulks <[email protected]> wrote in message
news:89gt0e$91a$[email protected]..
Hi.
I am running WebLogic 4.5.1.5 under Solaris 2.6. I am using JDK 1.2.2
with HotSpot. When we shutdown our server, it essentially crashes with
the following error:
# HotSpot Virtual Machine Error, Unexpected Signal 11
# Error happened during: mark sweep
# Error ID: 4F533F534F4C415249530E4350500BC2 01
After looking into the problem, we found that it is easily recreatable,
simply
by (1) starting the server, (2) hitting any web page (which causes
FileServlet
to be loaded), and (3) shutting down the server.
I have attached a tail of my log file as evidence.
Anybody else seen this problem? Is it a Weblogic/HotSpot compatibility
problem?
Thanks. -
How to run weblogic server in backgroud?
I just installed weblogic60sp1 on Aix.
how can i start weblogic server in backgroud?
RonHi Kartheek,
If you're new to running WebLogic as a Windows service, you'll probably find it a bit tricky at first. I found troubleshooting problems, especially start-up and process-crashes, awkward at first. If you have time, you may want to check these out:
[ http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html|http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html]
[http://e-docs.bea.com/wls/docs81/adminguide/winservice.html|http://e-docs.bea.com/wls/docs81/adminguide/winservice.html]
-Jones -
Error when running weblogic.appc
We have been running weblogic.appc for quite some time for precompiling our war-files. A few days ago we have been getting errors when precompiling one of our applications (it worked fine just a week ago). We build the war files using the same build setup.
We run the precompilation using the following command:
MW_HOME=/opt/lf/weblogic/wls1035_dev
java -classpath $MW_HOME/wlserver/server/lib/weblogic.jar:$MW_HOME/wlserver/server/lib/wlclient.jar weblogic.appc -verbose -verboseJavac -nowarn -k -maxfiles $2 -output $OUTPUT_HOME/$WAR_FILE-$WAR_END $WAR_HOME/$WAR_FILE*
The error we are getting is:
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:127)
at java.util.zip.ZipFile.<init>(ZipFile.java:144)
at weblogic.jsp.internal.Jar.<init>(Jar.java:24)
at weblogic.jsp.internal.Application.createJavelinFile(Application.java:185)
at weblogic.jsp.internal.CPL.initializeBinaryPaths(CPL.java:234)
at weblogic.servlet.jsp.JspCLLManager.initPaths(JspCLLManager.java:437)
at weblogic.servlet.jsp.JspCLLManager.initialize(JspCLLManager.java:237)
at weblogic.servlet.jsp.JspCLLManager.<init>(JspCLLManager.java:228)
at weblogic.servlet.jsp.JspCLLManager.<init>(JspCLLManager.java:221)
at weblogic.servlet.jsp.JspCLLManager.compileJsps(JspCLLManager.java:126)
at weblogic.servlet.jsp.jspc20.runBodyInternal(jspc20.java:454)
at weblogic.servlet.jsp.jspc20.runJspc(jspc20.java:227)
at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:236)
at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:376)
at weblogic.application.compiler.WARModule.compile(WARModule.java:245)
at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:29)
at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.Appc.runBody(Appc.java:203)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:262)
at weblogic.appc.main(appc.java:14)
And then for every jsp in the war file we are getting this error:
Exception encountered while compiling /tmp/appcgen_1316596871973_application.war/jspview/view.jsp
java.lang.NullPointerException
at weblogic.jsp.internal.jsp.JspParser.jspParse(JspParser.java:1092)
at weblogic.jsp.internal.jsp.JspParser._parse(JspParser.java:604)
at weblogic.jsp.internal.jsp.JspParser.parse(JspParser.java:597)
at weblogic.jsp.internal.jsp.JspAnalyzer.parseFile(JspAnalyzer.java:104)
at weblogic.jsp.internal.jsp.JspAnalyzer.parse(JspAnalyzer.java:92)
at weblogic.jsp.internal.ProxySourceFile.parse(ProxySourceFile.java:106)
at weblogic.jsp.internal.SourceFile.getAst(SourceFile.java:559)
at weblogic.jsp.internal.SourceFile.getAst(SourceFile.java:533)
at weblogic.jsp.internal.SourceFile.check(SourceFile.java:335)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:224)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
At the end we are also getting the following output (I have checked the ownership and permissions and they are the same as for the applications that we get successful compilations).
There are 1 nested errors:
java.lang.RuntimeException: Error enumerating directory "/tmp/.jspcgen_1316596885663/war"; please check its ownership and permissions.
at weblogic.utils.FileUtils.remove(FileUtils.java:299)
at weblogic.utils.FileUtils.remove(FileUtils.java:316)
at weblogic.application.io.ExplodedJar.remove(ExplodedJar.java:262)
at weblogic.servlet.internal.War.remove(War.java:278)
at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:249)
at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:376)
at weblogic.application.compiler.WARModule.compile(WARModule.java:245)
at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:29)
at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.Appc.runBody(Appc.java:203)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:262)
at weblogic.appc.main(appc.java:14)We solved this by increasing the number of open files, by adding the following in the /etc/security/limits.conf
* soft nofile 50000
* hard nofile 50000 -
Running Weblogic Server 7.0 SP4 using JDK 1.4
Is it possible to run Weblogic Server 7.0 SP4 with a different JRE than the one
that ships with 7.0 SP4. I am having issues with a bug in JDK 1.3.1 which when
I run under JBuilder X using 1.4 is not there. ANy help as to how I go about
doing this would be welcomed.
Thanks
JustinYes,
The JDK is just the Sun JDK...nothing special. You may upgrade minor versions quite safely by dowloading later one at Sun website and pointting your "JAVA_HOME" at it.
I would not jump to 1.4, as changes in java language may impact. -
Running Weblogic Server 10.3.3 in Debug mode
Hi to all,
Here i got a problem after installing Oracle Identity Manager 11g R3,to solve the issue i need to run WebLogic Server 10.3.3 in Debug mode.
Can any suggest how to run WebLogic Server 10.3.3 in Debug mode.
Here i find a solution to run in debug mode,but no difference in log files before and after changing debug mode.
Enable Debugging on the WebLogic Server
To start WebLogic Server in debug mode, you will need to modify the startWebLogic.cmd script in the <WLS-root>\wlserver_10.0\samples\domains\wl_server directory. <WLS-root> is the directory in which WebLogic 10.0.1 was installed into.
In the startWebLogic.cmd script, specify the JAVA OPTIONS with:
set JAVA_OPTIONS=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=n
Let me know if u have any questions,
Thanks and Ragards,
SatishGreg,
I cam across this issue too. It looks like there is a bug in sample script provided by weblogic documentation. We should not use ADMIN_URL as they mentioned in the script.
Remove it and try. For more info. please see this link helps:
http://ananthkannan.blogspot.com/2009/10/weblogic-server-instance-as-window.html
Thanks.
Ananth -
Running Weblogic 8.1 SP3 and IPlanet 6.0 on same machine
I have requirement to run Weblogic Platform SP3 and IPlanet 6.0 servers on same Solaris machine
for a client of ours.
Please let me if we can do this. What kind of issues we may run into.
Thanks,
SanjayHi
Of course, you can install both at the same machine.
Only remember the memory required ... and the real memory available ... this for don't have swap problems.
Remember too if you are planning to create WLS clusters ... BEA recommends 1 cluster per CPU ... and reserve 1 CPU for the iPlanet web Server. Even, you can install all clusters and web server as your machine support ( under load, try to mantain the CPU usage under 70-80%).
Jin -
Running weblogic as a service on NT
We are currently trying to run weblogic as a service on Windows NT. Yet the service
has hung once and run out of memory once. The hardware and software specification
is listed below.
Hardware
System Intel
CPU: Dual 866 MHz or faster
Memory: 500 MB
Hard Drives: 2 x 10 GB RAID-1 System Drive
Network: Static IP allocation and TCP/IP network protocolTwo Fast Ethernet 10/100
Software
Windows NT 4.0 Option Pack Typical InstallBEA WebLogic Version 5.1 with Service Pack
8 and JDBC drivers for MSSQL ServerJava 2 SDK Version 1.3.1 RC 2
The WebLogic server has been using the srvany.exe and instsrv.ex utilities (part
of the NT Resource Kit) . Note that it is necessary to use the srvany utility rather
than the custom BEA service utilities in order to allow the passing of command line
parameters to the JVM. An important JVM parameter is –Xrs which prevents JDK1.3
applications which run as a service on NT from shutting-down when the user who started
the service logs out. This problem does not occur on Win2K systems.
1. Set-up a ‘weblogic’ user account that is a member of the Users group
and has explicitly assigned 'log on as a service' right.
2. At a command prompt install srvany with the command
INSTSRV WGO_server c:\winnt\system32\srvany.exe
3. Use the services applet (in the Control Panel) to ensure that the service will
run using the weblogic account and that the service is set for automatic startup
4. Use the Registry Editor REGEDT32.exe to configure srvany as follows:
a. Highlight HKEY_LOCAL_MACHINE\SYSTEM\CurrentContrelSet\Services\WGO_server and
select Add Key from the edit menu.
b. The key to be added should have the name “Parameters” – the
class field may be left empty.
c. Highlight the newly created Parameters key and select the Add Value option from
the edit menu. The name of the value to be added is “Application” and
the type of value is REG_SZ. When you o.k. these options, you will be asked to provide
the string value representing the application to be triggered by servany –
type in the path to the startweblogic.cmd file:
c:\weblogic\WGO_server\startweblogic.cmd
d. With the Parameters key still highlighted, select the Add Value option from the
edit Menu. The name of the value is “AppDirectory” and the type is REG_SZ.
Set the directory in which the application runs by typing in the path
c:\weblogic\WGO_server
5. To start the weblogic server, return to the Service applet in the control panel
and start the service named WGO_server. To shutdown the service, first run the script
c:\weblogic\WGO_server\shutdown to shutdown weblogic cleanly, wait a few moments
and then stop the WGO_server service via the Service applet.
If anyone has experienced a similar problem please let me know
Thanks
JoI would look at all the other startup script you have on your machine already.
They are usually placed in /etc/init.d and these files are often linking into /etc/rc3.d
I suggest you google on how to setup a service for your flavour of linux as they are not all the same. -
What privileges user should have to install and run weblogic on linux box
What privileges user should have to install and run weblogic on linux box ?
Hello.
Normal user if you don't want to listen to ip port < 1024 or write in protected directories (like /var).
Regards. -
How to run weblogic server in background process on Windows XP 2002 ?
Hi,
I have installed weblogic server 9.2 in Windows XP 2002, I want to start my weblogic server and instances in background and keep running .
Can anybody please provide information on the same ?
Thanks in Advance,
Kartheek.Hi Kartheek,
If you're new to running WebLogic as a Windows service, you'll probably find it a bit tricky at first. I found troubleshooting problems, especially start-up and process-crashes, awkward at first. If you have time, you may want to check these out:
[ http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html|http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html]
[http://e-docs.bea.com/wls/docs81/adminguide/winservice.html|http://e-docs.bea.com/wls/docs81/adminguide/winservice.html]
-Jones -
Re: Running weblogic multiple instances on different ports
Hi,
I am planning to run multiple weblogic instances on different ports on the
same machine.
Is it possible ? If so, how ?
Details:
I am using IIS on the same machine. I am currently running weblogic on
7001 and 7002(ssl).
I dont how to run multiple instances. Please help me or guide me where I
can get documentation.
These two instances have to refer two different set of code bases ...
Please point me where I can more details.
Thanks in advance.
Sreedhar VIs it possible for the two instances on the same machine to participate in
the same cluster? I believe servers in a cluster must share the same port
(which is also used for multicasting). Does a virtual IP address need to be
configured?
"Per Jessen" <[email protected]> wrote in message
news:[email protected]..
>
>
Sreedhar Vankayala wrote:
Hi,
I am planning to run multiple weblogic instances on different ports on
the
same machine. Is it possible ? If so, how ?Assuming you are using WLS6.x, simply define as many servers as needed andgive
them different ports to listen to. This is easily accomplished using theWLS
Admin Console.
Then start individual weblogic processes using this config file.
regards,
Per Jessen, Zurich. -
Hello,
Using visual cafe 3 (enterprise), I've got a class which run Weblogic in
order to debug EJB, so I had to insert weblogic classes in VC classpath
(sc.ini) to debug EJB (which uses weblogic classes like weblogic.rmi,...)
and run WL.
It works fine with weblogic 3.1 (no java and wl distinct classpaths) but
not with newer versions (4.5.2, 5.1) because WL refuse to run coz of
weblogicaux.jar in java classpath !!!!
So how can I do ?
Thx,
MattYou should upgrade to VCafe Enterprise 3.1a. I believe there's no charge. Check out the WebGain
website.
WebLogic 4.5.x and 5.1.x use dynamic class loading to enable runtime replacement of servlets, jsps,
and ejbs.
The server should be started with the standard class libraries and directories given by -classpath
and the weblogic\classes and weblogicaux.jar on the -Dweblogic.class.path.
The Server can be started with everthing on the classpath in what's called static mode. In this
case, the important thing is to make sure that weblogic\classes\boot appears BEFORE
weblogic\classes.
For 5.1.x, also make sure that the parameter -Dweblogic.system.disableWeblogicClassPath=true is
added.
But the automated EJB features in VCafe 3.1a won't work with 5.1.x. For that you'll need to update
to VCafe 4.0 Enterprise (and I believe there is an upgrade cost there.)
-dana
Matt wrote:
>
Hello,
Using visual cafe 3 (enterprise), I've got a class which run Weblogic in
order to debug EJB, so I had to insert weblogic classes in VC classpath
(sc.ini) to debug EJB (which uses weblogic classes like weblogic.rmi,...)
and run WL.
It works fine with weblogic 3.1 (no java and wl distinct classpaths) but
not with newer versions (4.5.2, 5.1) because WL refuse to run coz of
weblogicaux.jar in java classpath !!!!
So how can I do ?
Thx,
Matt -
What Solaris packages are needed to run WebLogic 5.1?
Solaris by default comes with 4 installation methods, namely core, end-user,
developer, full. In comparison, full consists of 300+ solaris packages and
core about 30+. I was wondering if there are any docs lying around on
specifcally what packages are required of Solaris 2.6 by Weblogic 5.1. Would
greatly appreciate any help here. Thx
Rgrds,
Wong.Acckk a full installation is bad... real bad for security in a production
env. You guys should investigate thoroughly exactly what packages are needed
to run JVM. There are a lot of useless binaries/libs in a full Solaris
installation. For the record, I installed a core installation + two packages
(required by JDK). The thing works anyhow... but I thought BEA would have
some guidelines on a Solaris installation for host security. I mean, even
M$ have guidelines on running IIS securely, and apache have theirs long ago.
Any of you guys ever tried stripping Solaris to run weblogic??
Rgrds,
Wong.
"Michael Girdley" <[email protected]> wrote in message
news:3988bbd3$[email protected]..
We certify with full installations, but others may work as well. The
ability to run the JVM is the biggest factor.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"C.M. Wong" <[email protected]> wrote in message
news:[email protected]..
Solaris by default comes with 4 installation methods, namely core,end-user,
developer, full. In comparison, full consists of 300+ solaris packages
and
core about 30+. I was wondering if there are any docs lying around on
specifcally what packages are required of Solaris 2.6 by Weblogic 5.1.Would
greatly appreciate any help here. Thx
Rgrds,
Wong. -
ExceptionInInitializer when running weblogic.jspc
I am getting the following error when running weblogic.jspc:
I am using 4.5.1 and am trying to pre-compile a jsp file.
Any ideas?
I am using the following command line:
java -classpath $CLASSPATH:$WEBLOGICCLASSPATH
-Dweblogic.class.path=$WEBLOGICCLASSPATH weblogic.jspc 100-Welcome.jsp
I have also tried the above command w/ -classpath $CLASSPATH
Thanks,
Richard
java.lang.ExceptionInInitializerError
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Error.<init>(Compiled Code)
at java.lang.LinkageError.<init>(Compiled Code)
at java.lang.ExceptionInInitializerError.<init>(Compiled Code)
at java.beans.Beans.instantiate(Compiled Code)
at weblogic.servlet.jsp.JspLexer.processBeanTag(Compiled Code)
at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(Compiled
Code)
at weblogic.servlet.jsp.JspLexer.mXML_THING(Compiled Code)
at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled Code)
at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code)
at weblogic.servlet.jsp.JspLexer.parse(Compiled Code)
at weblogic.servlet.jsp.JspParser.doit(Compiled Code)
at weblogic.servlet.jsp.JspParser.parse(Compiled Code)
at
weblogic.servlet.jhtmlc.Jhtml2Java$Output.setSourceFile(Compiled Code)
at weblogic.servlet.jhtmlc.Jhtml2Java.outputs(Compiled Code)
at weblogic.utils.compiler.CodeGenerator.generate(Compiled Code)
at weblogic.jhtmlc.runBody(Compiled Code)
at weblogic.jspc.runBody(Compiled Code)
at weblogic.utils.compiler.Tool.run(Compiled Code)
at weblogic.jspc.main(Compiled Code)
Hi again,
it turns out that the application outputs the above error if I run it from anywhere except EditPlus (what I use to code my applications - not an IDE), i.e. if I run the main class file from the command line, the same thing happens.
AAAAAHHHHH!!!!! -
Apache overrides running Weblogic on same port
Hi,
today I found something strange. I installed an Apache Server on our
Application Server. This Apache is meant to display an information page
in case we have to take the WebLogic down for maintenance. As a test
case I started Apache on the WebLogic port while WebLogic was still
running. My expectation was that Apache would not be able to start as
the port was not available. What actually happened was that WebLogic was
not reachable anymore and the Apache Pages were shown instead. After I
stopped the Apache instance, WebLogic was reachable as usual. Does
anyone have an idea of what might lead to this behaviour?
Cheers,
DanielHi Adam,
it's a Winnt4 box with two network adapters, one connecting to the
'outer world', the other one directly connecting to the Oracle box with
an internal ip address. The WL5.1 is running on the external address,
Apache is running on the domain name to which the external ip address is
mapped. I don't know of any DNS magic, there are just several domains
mapped onto the ip (.com, .de, .it etc); I'll try to figure out if there
is something unusual in DNS config anyway. Even more strange is that if
WL is started after Apache, it shows the expected behaviour...
Regards,
Daniel
-----Ursprüngliche Nachricht-----
Von: Adam Messinger [mailto:[email protected]]
Bereitgestellt: Mittwoch, 7. März 2001 05:57
Bereitgestellt in: misc
Unterhaltung: Apache overrides running Weblogic on same port
Betreff: Re: Apache overrides running Weblogic on same port
This is very strange indeed. I would have expected the same thing you
did -
that Apache would fail to start up because it could not bind to the
port.
My guess is that there is something funny going on with the address that
is
being used.
Is the machine multihomed and Apache is binding to one address while WLS
is
binding to another? Perhaps something strange is happening with the
loopback interface.
The part about Apache getting all the requests while it is running and
then
not when it is shut down is interesting. What sorts of URLs are you
using
to connect? Perhaps there is some type of DNS magic happening which
enables
this behavior.
Finally what OS are you using?
Regards,
Adam
"Daniel Hoppe" <[email protected]> wrote in message
news:[email protected]...
Hi,
today I found something strange. I installed an Apache Server on our
Application Server. This Apache is meant to display an informationpage
in case we have to take the WebLogic down for maintenance. As a test
case I started Apache on the WebLogic port while WebLogic was still
running. My expectation was that Apache would not be able to start as
the port was not available. What actually happened was that WebLogicwas
not reachable anymore and the Apache Pages were shown instead. After I
stopped the Apache instance, WebLogic was reachable as usual. Does
anyone have an idea of what might lead to this behaviour?
Cheers,
Daniel
Maybe you are looking for
-
Brain pick on an old problem of mine (squealing and poping sound when system is under heavy loa
Firstly, my apologies if this post gets double posted as I am on a barely functional dsl connection?<SPAN> It get?s flaky when it rains which is only periodically for about 2 months of the year? I was wondering if someone in the know might be able to
-
Final Cut Pro X Crashes when sending to device
Hey, so I'm trying to get the movies I'm creating to be .mp4 so I can put it on my phone. However, everytime I go to Share>Apple Devices, Final Cut glitches. It begins to render the movie but then freezes at the "Processing" stage of rendering. The m
-
Ever since the apple 8.1 update, my phone has been on extended LTE service. My data seems to be going really fast with not much usage. I've done some reading up on this and I'm not the only person having this problem. Any kind of help would be apprec
-
N9 web browser doesn't render most pages correctl...
I got my N9 a few days back and while using it, I found that the web browser isn't exactly good. It renders the web pages in weird ways. For eg: when I open the billmonk web page, it displays the page in half the screen which makes it extremely unrea
-
How to create button region such that the buttons appear both on top and bottom of the page. similar to page button bar in OAF, do we have any inbuilt way of doing this? I read somewhere that panelButtonBar should be used. But I could not find any pa