Sleeping thread that was started by startup class: wakes up on jsp compiler run

Question

Hello,
I've ecountered the following unexpected behaviour:
A class defined as a WL startup class creates a thread in the startup() method. This
thread then calls the Thread.sleep method.
So far so good.
Now each time an updated JSP is accessed by a browser, this JSP gets recompiled by
the JSP compiler (so far so good, nothing to do with the startup thread), and each
time this happens, the above mentioned thread wakes up as if his time were up. (Output
is "TestStartupThread: Woken up: timer timed out", see code below)
Anybody know anything??
Code of startup class ( = thread class) listed below.
Dirk
import java.util.Hashtable;
import weblogic.common.*;
public class TestStartupThread extends Thread implements T3StartupDef, T3ShutdownDef
private static TestStartupThread testThread = null;
/** controls running of thread, will be set to false when server shuts down
private static volatile boolean runThread = true;
public void setServices(T3ServicesDef t3def) {  }
public String startup(String s, Hashtable ht) {
testThread = new TestStartupThread();
testThread.start();
return "ok";
public String shutdown(String s, Hashtable ht) {
runThread = false;
testThread.interrupt();
return "ok";
public void run() {
while (runThread) {
try {
System.err.println("TestStartupThread: now going to sleep");
Thread.sleep(1000*60*60);
System.err.println("TestStartupThread: Woken up: timer timed out");
} catch (InterruptedException ie) {
System.err.println("TestStartupThread: Woken up by InterruptedException");

Answer 1

Looks like a good use for WL time services.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Brian Dowd" <[email protected]> wrote in message
news:[email protected]...
>
I am getting exactly the same problem, but I did something
similar (to this & mine) in WL 4.5.1 and it worked OK.
About the best solution we can come up with is to test the time
before and after wake up, if the time is less then go back
to sleep for the new amount of time ...
Does anyone know how to properly do this in WL 5.1 ?
I notice this thread is a bit old ....
"Dirk Rehberger" <[email protected]> wrote:
Hello,
I've ecountered the following unexpected behaviour:
A class defined as a WL startup class creates a thread in the startup()
method. This
thread then calls the Thread.sleep method.
So far so good.
Now each time an updated JSP is accessed by a browser, this JSP gets
recompiled by
the JSP compiler (so far so good, nothing to do with the startup thread),
and each
time this happens, the above mentioned thread wakes up as if his time
were up. (Output
is "TestStartupThread: Woken up: timer timed out", see code below)
Anybody know anything??
Code of startup class ( = thread class) listed below.
Dirk
import java.util.Hashtable;
import weblogic.common.*;
public class TestStartupThread extends Thread implements T3StartupDef,
T3ShutdownDef
private static TestStartupThread testThread = null;
/** controls running of thread, will be set to false when server shuts
down
private static volatile boolean runThread = true;
public void setServices(T3ServicesDef t3def) {  }
public String startup(String s, Hashtable ht) {
testThread = new TestStartupThread();
testThread.start();
return "ok";
public String shutdown(String s, Hashtable ht) {
runThread = false;
testThread.interrupt();
return "ok";
public void run() {
while (runThread) {
try {
System.err.println("TestStartupThread: now going to sleep");
Thread.sleep(1000*60*60);
System.err.println("TestStartupThread: Woken up: timer timed
out");
} catch (InterruptedException ie) {
System.err.println("TestStartupThread: Woken up by
InterruptedException");