Thread Operation - daemon thread

What will be the output of the following program (with explaination)?
public class A extends Thread {
A() {
setDaemon(true);
public void run() {
(new B()).start();
try{
Thread.sleep(60000);
} catch (InterruptedException x) {}
System.out.println("A done");
class B extends Thread{
public void run() {
try{
Thread.sleep(60000);
} catch (InterruptedException x) {}
System.out.println("B done");
public static void main(String[] args) {
(new A()).start();
}

If you consult the documentation for Thread.setDaemon to see what a daemon thread means; and the docs for the constructors of Thread to see what the default daemon status is, then you will understand why this program prints nothing.
Now if you moved those prints ahead of the sleeps it might print something but it need not - all depends on scheduling.

Similar Messages

  • TT14000: TimesTen daemon internal error: subd: flusher thread failed

    Hi,
    I encountered this on a production environment, the datastore was then became invalid, no connection to TimesTen available causing failures in our Java application. TimesTen version is 7.0.5 64-bit on RedHat Linux.
    Wondering what the root cause and how to prevent it. Thanks in advance.
    15:44:09.44 Err : : 23922: 17268/0x2aad67ef1820: Assertion failed: len > 0 [ttree.c:4.391:tnLookup():6884] PID 17268 (java) CONN 82 (java) 2012-03-08 15:44:09.433
    15:44:09.47 Err : : 23922: 17268/0x2aad67ef1820: Data store marked invalid [ttree.c:4.391:tnLookup():6884] PID 17268 (java) CONN 82 (java) Context 0x2aad67ef1820
    15:44:09.47 Warn: : 23922: 23925/0x194e2990: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.47 Err : : 23925: TT14000: TimesTen daemon internal error: subd: flusher thread failed in sb_dbLogFlusherSvc, tt error 994 (TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 9535, procedure "sb_dbLogFlusherSvc")
    15:44:09.48 Err : REP: 29066: tt_data_1:receiver.c(2273): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:09.49 Err : REP: 29066: tt_data_1:receiver.c(1095): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:09.49 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:09.49 Err : : 23925: TT14000: TimesTen daemon internal error: subd: flusher thread failed to disconnect, tt error 0 (TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()").
    15:44:09.49 Warn: : 23922: 17268/0x2aad78b0aa30: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.49 Warn: : 23922: 17268 ----------: Disconnecting from an old instance
    15:44:09.49 Warn: : 23925: Stopping subdaemon worker for /opt/datastore/tt705/datastore/tt_data_1 because db is invalid.
    15:44:09.49 Err : : 23925: subd: manager exiting due to invalidation
    15:44:09.50 Warn: : 23922: 29066/0x490cdf0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.50 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
    15:44:09.50 Warn: : 23922: 29066/0x493fb10: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.50 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
    15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'LOGFORCE' thread
    15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
    15:44:09.50 Warn: : 23922: 29066/0x4a44b20: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.50 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
    15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'RECEIVER' thread
    15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
    15:44:09.51 Err : REP: 29066: tt_data_1:transmitter.c(8190): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:09.51 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:09.51 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'TRANSMITTER' thread
    15:44:09.51 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
    15:44:09.52 Warn: : 23922: 8527/0xb35b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.52 Warn: : 23922: 8527 ----------: Disconnecting from an old instance
    15:44:09.55 Warn: SRV: 8527: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.66 Warn: : 23922: 4729/0xdfe50a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.66 Warn: : 23922: 4729 ----------: Disconnecting from an old instance
    15:44:09.67 Warn: : 23922: 8511/0xe6f50a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.67 Warn: : 23922: 8511 ----------: Disconnecting from an old instance
    15:44:09.70 Warn: : 23922: 10288/0x5ff0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.70 Warn: : 23922: 10288 ----------: Disconnecting from an old instance
    15:44:09.70 Warn: : 23922: 23985/0x31f20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.70 Warn: : 23922: 23985 ----------: Disconnecting from an old instance
    15:44:09.71 Warn: SRV: 4729: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.71 Warn: SRV: 8511: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.73 Warn: : 23922: 29556/0x964b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.73 Warn: : 23922: 29556 ----------: Disconnecting from an old instance
    15:44:09.74 Warn: : 23922: 4716/0x193050a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.74 Warn: : 23922: 4716 ----------: Disconnecting from an old instance
    15:44:09.74 Warn: : 23922: 3887/0xbb780a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.74 Warn: : 23922: 3887 ----------: Disconnecting from an old instance
    15:44:09.77 Warn: SRV: 10288: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.81 Warn: SRV: 3887: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.81 Warn: : 23922: 16522/0x1cc900a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.81 Warn: : 23922: 16522 ----------: Disconnecting from an old instance
    15:44:09.81 Warn: SRV: 23985: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.82 Warn: SRV: 29556: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.83 Warn: SRV: 4716: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.87 Warn: : 23922: 23973/0x46c30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.87 Warn: : 23922: 23973 ----------: Disconnecting from an old instance
    15:44:09.88 Warn: : 23922: 3902/0xb1670a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.88 Warn: : 23922: 3902 ----------: Disconnecting from an old instance
    15:44:09.88 Warn: SRV: 3902: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.89 Warn: SRV: 16522: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.92 Warn: SRV: 23973: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.93 Warn: : 23922: 29575/0x14fc20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.93 Warn: : 23922: 29575 ----------: Disconnecting from an old instance
    15:44:09.95 Warn: : 23922: 23925 ------------------: subdaemon process exited
    15:44:09.95 Warn: : 23922: 23925 exited while connected to data store '/opt/datastore/tt705/datastore/tt_data_1' shm 134809540 count=5
    15:44:09.95 Warn: : 23922: daRecovery: subdaemon 23925, managing data store, failed: invalidate (failcode=202)
    15:44:09.96 Warn: SRV: 29575: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:09.96 Warn: : 23922: 3894/0x41d20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.96 Warn: : 23922: 3894 ----------: Disconnecting from an old instance
    15:44:09.97 Warn: : 23922: 23977/0x1505d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.97 Warn: : 23922: 23977 ----------: Disconnecting from an old instance
    15:44:09.97 Warn: : 23922: 10276/0xb81d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.97 Warn: : 23922: 10276 ----------: Disconnecting from an old instance
    15:44:09.99 Warn: : 23922: 4712/0x19ca50a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:09.99 Warn: : 23922: 4712 ----------: Disconnecting from an old instance
    15:44:09.99 Warn: SRV: 4712: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.00 Warn: : 23922: 16531/0x175920a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.00 Warn: : 23922: 16531 ----------: Disconnecting from an old instance
    15:44:10.05 Warn: SRV: 10276: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.06 Warn: SRV: 3894: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.07 Warn: : 23922: 29567/0x190a80a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.07 Warn: : 23922: 29567 ----------: Disconnecting from an old instance
    15:44:10.07 Warn: SRV: 23977: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.08 Warn: : 23922: 10280/0x36420a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.08 Warn: : 23922: 10280 ----------: Disconnecting from an old instance
    15:44:10.10 Warn: SRV: 16531: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.11 Warn: SRV: 29567: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.12 Warn: SRV: 10280: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.16 Err : REP: 29066: tt_data_1:rephold.c(141): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:10.16 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:10.16 Warn: : 23922: 29066/0x4969bf0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.16 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
    15:44:10.16 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'REPHOLD' thread
    15:44:10.16 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
    15:44:10.18 Err : REP: 29066: tt_data_1:receiver.c(1637): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:10.18 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:10.18 Warn: : 23922: 29066/0x2aad480008c0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.18 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
    15:44:10.24 Warn: : 23922: 22348/0x1fa20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.24 Warn: : 23922: 22348 ----------: Disconnecting from an old instance
    15:44:10.29 Warn: SRV: 22348: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.35 Warn: : 23922: 17268 exited while connected to data store '/opt/datastore/tt705/datastore/tt_data_1' shm 134809540 count=92
    15:44:10.35 Warn: : 23922: 29562/0x858b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.35 Warn: : 23922: 29562 ----------: Disconnecting from an old instance
    15:44:10.37 Warn: : 23922: 14964/0x42250a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.37 Warn: : 23922: 14964 ----------: Disconnecting from an old instance
    15:44:10.37 Warn: : 23922: 16535/0x138840a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.37 Warn: : 23922: 16535 ----------: Disconnecting from an old instance
    15:44:10.37 Warn: : 23922: 29653/0x1555b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.37 Warn: : 23922: 29653 ----------: Disconnecting from an old instance
    15:44:10.38 Warn: SRV: 16535: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.39 Warn: : 23922: 10284/0x17b7f0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.39 Warn: : 23922: 10284 ----------: Disconnecting from an old instance
    15:44:10.39 Warn: SRV: 10284: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.40 Warn: SRV: 14964: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.41 Warn: : 23922: 4725/0x1b9380a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.41 Warn: : 23922: 4725 ----------: Disconnecting from an old instance
    15:44:10.43 Warn: SRV: 29562: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.44 Warn: : 23922: 16519/0x14de30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.44 Warn: : 23922: 16519 ----------: Disconnecting from an old instance
    15:44:10.46 Warn: SRV: 29653: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.47 Warn: SRV: 4725: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.47 Warn: : 23922: 29650/0x1658d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.47 Warn: : 23922: 29650 ----------: Disconnecting from an old instance
    15:44:10.49 Warn: SRV: 16519: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.50 Warn: : 23922: 3898/0x1e7c70a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.50 Warn: : 23922: 3898 ----------: Disconnecting from an old instance
    15:44:10.51 Warn: SRV: 3898: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.51 Warn: : 23922: 16526/0x18bc60a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.51 Warn: : 23922: 16526 ----------: Disconnecting from an old instance
    15:44:10.51 Warn: SRV: 29650: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.53 Warn: : 23922: 29662/0x3fcd0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.53 Warn: : 23922: 29662 ----------: Disconnecting from an old instance
    15:44:10.54 Warn: SRV: 16526: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.54 Warn: : 23922: 3890/0x1720a0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.54 Warn: : 23922: 3890 ----------: Disconnecting from an old instance
    15:44:10.57 Warn: : 23922: 29657/0x1a1860a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.57 Warn: : 23922: 29657 ----------: Disconnecting from an old instance
    15:44:10.57 Warn: : 23922: 22356/0x1110f0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.57 Warn: : 23922: 22356 ----------: Disconnecting from an old instance
    15:44:10.58 Warn: : 23922: 22345/0x70a30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.58 Warn: : 23922: 22345 ----------: Disconnecting from an old instance
    15:44:10.58 Warn: : 23922: 8500/0x78290a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.58 Warn: : 23922: 8500 ----------: Disconnecting from an old instance
    15:44:10.58 Warn: : 23922: 29666/0x26920a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.58 Warn: : 23922: 29666 ----------: Disconnecting from an old instance
    15:44:10.58 Warn: : 23922: 14947/0x39020a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.58 Warn: : 23922: 14947 ----------: Disconnecting from an old instance
    15:44:10.60 Warn: SRV: 29662: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.61 Warn: SRV: 14947: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.62 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'REPLISTENER' thread
    15:44:10.62 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
    15:44:10.62 Warn: : 23922: 14952/0x49970a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.62 Warn: : 23922: 14952 ----------: Disconnecting from an old instance
    15:44:10.62 Warn: : 23922: 14960/0x76770a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.62 Warn: : 23922: 14960 ----------: Disconnecting from an old instance
    15:44:10.63 Warn: SRV: 3890: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.63 Warn: SRV: 29666: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.64 Warn: SRV: 29657: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.65 Warn: SRV: 22356: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.65 Warn: SRV: 22345: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.65 Warn: SRV: 14952: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.66 Warn: SRV: 8500: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.67 Warn: SRV: 14960: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.81 Err : : 23922: repagent says it has failed to start: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
    15:44:10.89 Warn: : 23922: 10273/0x1b1460a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.89 Warn: : 23922: 10273 ----------: Disconnecting from an old instance
    15:44:10.91 Warn: SRV: 10273: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.96 Warn: : 23922: 4720/0x56290a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.96 Warn: : 23922: 4720 ----------: Disconnecting from an old instance
    15:44:10.96 Warn: SRV: 4720: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:10.98 Warn: : 23922: 23970/0x1d4530a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:10.98 Warn: : 23922: 23970 ----------: Disconnecting from an old instance
    15:44:11.01 Warn: SRV: 23970: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:11.10 Warn: : 23922: 29571/0x1fd0d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:11.10 Warn: : 23922: 29571 ----------: Disconnecting from an old instance
    15:44:11.17 Warn: SRV: 29571: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:11.24 Warn: : 23922: 14956/0x159720a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:11.24 Warn: : 23922: 14956 ----------: Disconnecting from an old instance
    15:44:11.25 Warn: : 23922: 22360/0xb5de0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:11.25 Warn: : 23922: 22360 ----------: Disconnecting from an old instance
    15:44:11.29 Warn: SRV: 14956: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:11.32 Warn: SRV: 22360: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:11.32 Warn: : 23922: 23981/0xf5b30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:11.32 Warn: : 23922: 23981 ----------: Disconnecting from an old instance
    15:44:11.38 Warn: SRV: 23981: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:11.38 Warn: : 23922: 8515/0x69940a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:11.38 Warn: : 23922: 8515 ----------: Disconnecting from an old instance
    15:44:11.40 Warn: : 23922: 8495/0x1c0a30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:11.40 Warn: : 23922: 8495 ----------: Disconnecting from an old instance
    15:44:11.41 Warn: SRV: 8515: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:11.44 Warn: : 23922: 22352/0x176130a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
    15:44:11.44 Warn: : 23922: 22352 ----------: Disconnecting from an old instance
    15:44:11.47 Warn: SRV: 22352: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:44:12.50 Warn: SRV: 8495: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
    15:45:54.96 Warn: : 23922: 29081/0x611f0f0: Recovery started
    15:55:32.03 Warn: : 29081: subd: Warning identified in [sub.c: line 3188]
    15:55:32.03 Warn: : 29081: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
    15:55:32.03 Warn: : 29081: file "db.c", lineno 11566, procedure "sbDbConnect"
    15:55:32.03 Warn: : 29081: subd: connect trouble, rc 2, reason 20100
    15:55:32.03 Warn: : 29081: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
    15:57:35.55 Err : REP: 3041: tt_data_1:receiver.c(10091): TT16084: Table: tt_data_1.SESSION. Failed to insert row for 'insert'
    15:57:35.55 Err : REP: 3041: tt_data_1:receiver.c(10091): TT907: TT0907: Unique constraint (SESSION) violated at Rowid <0x000000012f62d8b0> -- file "hindex.c", lineno 2529, procedure "sbHixInsert"
    15:57:35.55 Err : REP: 3041: tt_data_1:receiver.c(5439): TT16187: Transaction 1317905232/3501279703; Error: transient 0, permanent 1

    Hi,
    I can see an assertion error from the log which has caused the datastore to invalidate
    15:44:09.44 Err : : 23922: 17268/0x2aad67ef1820: Assertion failed: len > 0 [ttree.c:4.391:tnLookup():6884] PID 17268 (java) CONN 82 (java) 2012-03-08 15:44:09.433
    1) Any stack trace being dumped in the .inval file created at the datastore directory ?
    2) Any sql operation you were doing when this issue happened?
    This issue might be due to the BUG 6671095 - KILL TEST: ASSERTION FAILED: LEN > 0 [TTREE.C:4.391:TNLOOKUP():6884] , but there is no fix for this bug yet.
    I would prefer you raise a Service request at support.oracle.com so that we can work further on this issue. Please note that 7.0.5 is very old TT version so you should consider to upgrade to latest versions soon.
    Regards
    Rajesh

  • What is a daemon thread?

    hi all,
    can somebody plz tell me what is daemon thread and what is the difference between daemon thread a user thread. thanx in advance..

    Daemons are background programs that run all the time
    during up-time, ready to do something that may be
    required at any point. These are NOT limited to the
    JVM, but the concept is mirrored in teh ability to
    set a java thread as daemon, as the JVM is just that:
    a Virtual Machine that mimics an environment.
    Correspondingly OSs have daemon processes (called
    d services on windows) e.g. for printing. Calling
    Thread.setDaemon() will I believe mark the thread as
    to not be destroyed until VM shutdown, and will not
    itself stop shutdown of the VM if it is still running.Maybe I got confused by all those nots but if the only threads running are daemon
    threads, the VM is allowed to stop; I made that mistake myself several times.
    This is what I ripped from the API docs:
    The Java Virtual Machine continues to execute threads until either of the following occurs:
    - The exit method of class Runtime has been called and the security manager has permitted the exit operation to take place.
    - All threads that are not daemon threads have died, either by returning from the call to the run method or by throwing an exception that propagates beyond the run method.
    It's the "continues to execute until' ... 'all threads that are *not* daemon threads
    have died" part. They should have worded that a bit less cryptic ;-)
    kind regards,
    Jos
    ps. First I thought daemon threads run under your bed while drooling sometimes ;-)

  • Weblogic 8.14: Stuck Threads during JMS - IO native write operations

    G'day!
    Hope somebody can advise a solution on the following...
    Recently message loads have started to increase on our weblogic 8.14 cluster (3 servers) and we started to see an almost daily occurrence of Stuck Thread issues. From thread dumps we could see these were caused by jrockit/net/SocketNativeIO.write processes. We concluded we had reached the max performance limit for the file based JMS stores and so we moved these to database based JMS stores. This certainly seemed to improve matters - but we have recently seen the issue return. Which is puzzling, as technically we thought all messages would be persisted to the database, and any file IO on the application server would be eliminated. Our database resides on a separate dedicated oracle server. We tracked a recent cause to a large message (200K) which caused the Struck Thread - resulting in a build up of pending messages. After bouncing the server the message processed ok. Any thoughts on how to overcome these issues - greatly appreciated. Here's some detail on the stuck thread from the thread dump: (+Why does weblogic use IO when the JMS store is on a database?+). All messages are persistant.
    "ExecuteThread: '6' for queue: 'weblogic.kernel.Default'" prio=5 id=0xc00 pid=27544 active, daemon
    at jrockit/net/SocketNativeIO.write(Native Method)@0xf3aeae10
    at jrockit/net/SocketNativeIO.write(Unknown Source)@0xf3aeae9c
    at jrockit/io/NativeIO.write(Unknown Source)@0xf3ae62c6
    at java/net/AbstractSocketImpl$2.write(Unknown Source)@0xf3aeada4
    at jrockit/io/NativeIOOutputStream.write(Unknown Source)@0xf3ae61ec
    at jrockit/io/NativeIOOutputStream.write(Unknown Source)@0xf3ae618d
    at java/io/DataOutputStream.write(Unknown Source)@0xf4e3ec25
    ^-- Holding lock: java/io/DataOutputStream@0x4309fc80[thin lock]
    at com/ibm/mq/MQInternalCommunications.send(MQInternalCommunications.java:1022)@0xed34364a
    ^-- Holding lock: com/ibm/mq/MQInternalCommunications@0x4309f7e0[thin lock]
    at com/ibm/mq/MQSESSIONClient.lowLevelComms(MQSESSIONClient.java:2832)@0xed342fbd
    ^-- Holding lock: java/lang/Integer@0x4309f8a0[thin lock]
    at com/ibm/mq/MQSESSIONClient.MQPUT(MQSESSIONClient.java:3844)@0xed34271b
    at com/ibm/mq/MQQueue.putMsg2(MQQueue.java:1486)@0xed342262
    ^-- Holding lock: com/ibm/mq/MQSPIQueue@0x4312ce80[thin lock]
    at com/ibm/mq/jms/MQMessageProducer.sendInternal(MQMessageProducer.java:1569)@0xed33d1ab
    at com/ibm/mq/jms/MQMessageProducer.send(MQMessageProducer.java:1012)@0xed860a49
    at com/ibm/mq/jms/MQMessageProducer.send(MQMessageProducer.java:1046)@0xed8605f4
    at weblogic/jms/adapter/JMSBaseConnection.sendInternal(JMSBaseConnection.java:667)@0xef7df0bf
    ^-- Holding lock: weblogic/jms/adapter/JMSBaseConnection@0x43093748[thin lock]
    at weblogic/jms/adapter/JMSBaseConnection.access$200(JMSBaseConnection.java:80)@0xef7dee28
    at weblogic/jms/adapter/JMSBaseConnection$6.run(JMSBaseConnection.java:647)@0xef7dee1d
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)@0xf2fcbb88
    at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:147)@0xf2fcbb0a
    at weblogic/jms/adapter/JMSBaseConnection.send(JMSBaseConnection.java:644)@0xef7decf3
    at weblogic/jms/adapter/JMSConnectionHandle.send(JMSConnectionHandle.java:144)@0xef7dec7c
    at jrockit/reflect/NativeMethodInvoker.invoke0(Native Method)@0xf4f10d10
    at jrockit/reflect/NativeMethodInvoker.invoke(Unknown Source)@0xf4f10e98
    at jrockit/reflect/VirtualNativeMethodInvoker.invoke(Unknown Source)@0xf4e86d70
    at java/lang/reflect/Method.invoke(Unknown Source)@0xf4f104c3
    at weblogic/connector/common/internal/ConnectionWrapper.invoke(ConnectionWrapper.java:149)@0xed96a498
    at $Proxy14.send(Unknown Source)@0xef7dec04
    at weblogic/jms/bridge/internal/MessagingBridge.onMessageInternal(MessagingBridge.java:1258)@0xed857b25
    at weblogic/jms/bridge/internal/MessagingBridge.onMessage(MessagingBridge.java:1181)@0xed857864
    at weblogic/jms/adapter/JMSBaseConnection$27.run(JMSBaseConnection.java:1943)@0xef7de623
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)@0xf2fcbb88
    at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:147)@0xf2fcbb0a
    at weblogic/jms/adapter/JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)@0xef7de586
    at weblogic/jms/client/JMSSession.onMessage(JMSSession.java:2678)@0xeee7e30c
    at weblogic/jms/client/JMSSession.execute(JMSSession.java:2598)@0xeee7d25d
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:219)@0xf4e14070
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:178)@0xf4e1fddb
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0xf4f3c9f3
    Thanks
    C.

    I'm not sure what operating system you're running, but I only have experience of WLS8.1 on Windows.
    We did extensive load testing of JMS before we went live, and found JDBC file stores to be rubbish in comparison to file store. When a message is persisted, it has to be written to the database, then when it is consumed, it must be deleted from the table. This simply killed our system when we load tested it.
    One thing we did do though, was use a second JMS server and second file store for one particularly heavy queue, where we did have IO issues. This was with a JMS distributed destination. We also use a synchronous write policy of cache-flush on the file store and we also have configured a paging store to page messages so the app server does not run out of memory.
    200K isn't by any means a huge message though, and shouldn't be any problem at all, we have 1mb messages quite regularly.
    I notice from the stack trace, that you have MQ series aswell. I'm not experienced with MQ, so can't give any information, but what I would try is the following.
    Using a JMS server with JMS File storage, develop a small java client to write as many messages to the queue and effectively stress the JMS subsystem just to establish if the filestore is the problem. This should be done without a connection to MQ and also use large messages. if you don't get any issues and WebLogic JMS with file store looks ok, then attach a consumer to the queue, which should also be a simple java client. Then you have production and consumption going on, which will result in writes and read's/deletes from the jms file store.
    Once you've stress tested JMS and you are satisfied that its ok or not, then add the MQseries connection and see how that affects things.
    You may well have already done all this, so please feel free to ignore me! I did a load of this kind of stuff before we went live to try and bash JMS to bits, but I didn't manage it! The only thing we did was add a second file store and second JMS server.
    I just looked back in my support cases, and found we'd had a similar issue - disk fragmentation seemed to be one of the factors here too. The JMS file store was heavily fragmented. That's windows for you though!!!
    Hope that helps.
    Pete

  • BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'CA_BAB_MSSQL_e85860_10001_2085d987_ERP_DATABASE_ST_1'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application reque

    hello,
    i getting the following error message in event id while backing up my SQL db by third party backing tool
    BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'CA_BAB_MSSQL_e85860_10001_2085d987_ERP_DATABASE_ST_1'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
      <Data>995(The I/O operation has been aborted because of either a thread exit or an application request.)
    please suggest the solution.

    Hi pulkit,
    According to your description, the actual error could be caused by but not limited to the following issues: Memory issues, Third Party issues, or SQL Server issues and so on. However, as shanky post, if you use an external or third party backup tool like
    NetBackup, BackupExec, or one of the many other tools available for backing up SQL Server databases without having to write your own backup scripts, and the error occurs. You need to check if there are some issues about your VDI or SQLVDI.DLL. Meanwhile,
    you also need to troubleshooting Memory Issue or the third tool issue. For more information about troubleshooting the error 995 when backing up database via the third party tool. You can review the following blog.
    https://support.software.dell.com/kb/SOL14674
    In addition, the error may include additional text from the operating system indicating that the disk is full. When performing a backup or restore operation with third-party backup software an additional message may occur indicating that the backup failed.
    Perform the following tasks as appropriate:
     1. Review the underlying system error messages and SQL Server error messages preceding this one to identify the cause of the failure.
     2. Ensure that the backup and restore medium has sufficient space.
     3. Correct any errors raised by third-party backup and restore software.
    There is also detail about backing up database via T-SQL statement /GUI, you can review the following article.
    http://technet.microsoft.com/en-us/library/ms187510.aspx
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • WLS threads - how to retrieve individual operations?

    Hello everybody,
    can anyone tell me if is there a way to find out which WLS thread is
    performing each individual operation - for instance, compiling or executing
    a specific JSP?
    TIA
    Paola R.

    You can get a "photo" of what each execution thread is doing in two ways:
    - weblogic console - select a server in the left pane, then, on the right
    pane, select 'Monitoring' tab and 'General' subtab; click on 'Monitor all
    Active Queues...' then click on the 'default' queue
    - you can have a thread dump on the standard output using the command line
    Admin (http://e-docs.bea.com/wls/docs81/admin_ref/cli.html#THREAD_DUMP) or
    doing a kill -3 on the server provess
    Ciao
    Marco
    "Paola R." <[email protected]> wrote in message news:41505ea2@mail...
    Hello everybody,
    can anyone tell me if is there a way to find out which WLS thread is
    performing each individual operation - for instance, compiling orexecuting
    a specific JSP?
    TIA
    Paola R.

  • Thread safe operations on table in pl/sql procedure?

    I am developing java application which will be running in N localizations simultaneously, each application will have M threads. Every thread takes an unique ID with status NOT_TAKEN from table Queue and changes its status to TAKEN.
    Problem:
    How to prevent thread from situation like this:
    1. Thread A select first ID with status NOT_TAKEN
    2. In the same time thread B select first (so it will be the same ID which selected thread A) ID with status NOT_TAKEN.
    3. Thread A changes status of ID to TAKEN
    4. Thread B changes status of ID to TAKEN
    After this operation thread A and B are using the same ID.
    What I did:
    I have written pl/sql procedure which lock table Queue in exclusive mode, selects first ID, changes its status to TAKEN and unlocks the table. Because it is lock in exclusive mode so only one thread can run this procedure simultaneously.
    Question:
    How optimally should it be solved, because mine solution prevents from doing all other Updates on Queue table while it is locked, like changing status from TAKEN to OPERATION_DONE so it has performance issue.

    As Centinul has said, you need to lock just one row.
    I would just add NOWAIT to the select statement to let the Java thread go and try again, instead of waiting for the other threads.
    Example: (not tested)
    -- Assuming structure of your QueueTable: ( IDCol is PK , StatusCol is VARCHAR2, ... )
    -- or make it part of the package....
    CREATE OF REPLACE
    FUNCTION updateQueue( nQID QueueTable.IDCol%TYPE) RETURN VARCHAR2 AS
       eLocked EXCEPTION;
       PRAGMA EXCEPTION_INIT(eLocked,-54);
       CURSOR curQueueTable IS SELECT 1 CNTR FROM QueueTable WHERE IDCol=nQID AND StatusCol='NOT_TAKEN' FOR UPDATE OF StatusCol NOWAIT;
       recQueueTable curQueueTable%ROWTYPE;
       cRtn VARCHAR2(1);
    BEGIN
       cRtn := 'Y';
       BEGIN
          OPEN curQueueTable;
          FETCH curBuffSummary INTO recQueueTable;
          CLOSE curQueueTable;
          IF recQueueTable.CNTR IS NOT NULL AND recQueueTable.CNTR = 1 THEN
              UPDATE QueueTable SET StatusCol = 'TAKEN' WHERE IDCol=nQID;
          ELSE
              -- Already updated
              cRtn := 'N';
          END IF;
             -- You can control your transaction here as well
             -- COMMIT;
             -- But if realy should be done in the Java thread.
        EXCEPTION
           WHEN eLocked OR STANDARD.TIMEOUT_ON_RESOURCE THEN
           -- Thread could not get exclusice row lock. Ignore error.
             cRtn := 'N';
             NULL;
          WHEN OTHERS THEN
             -- Handle other errors...
             -- NULL; just kidding...
             RAISE;
       END;
       RETURN cRtn;
    END; Edited by: thomaso on Sep 18, 2009 10:30 AM

  • B1 8.8 EventLogger:  Cross-thread operation not valid

    Greetings,
    I'm  trying to run EventLogger on Windows Server 2008 for use with B1 8.8.  I converted EL to VS 2005, updated it to use the new UI for 8.8 and when EL runs it crashes as soon as it receives an event.
    The message is "Cross-thread operation not valid: Control 'ToolBar1' accessed from a thread other than the thread it was created on.
    Does anyone have any ideas?  I wouldn't be surprised if it's a security issue, but I wouldn't know how to fix it even if it were.
    Thanks!

    Sheer Genius, Eddy - thanks!
    I tried recompiling the program and used the advanced compile option to tell it X86 but that didn't solve it (by itself, anyway) but when I used the compability mode everything was smooth.

  • Using Operations on TextFields as part of a thread

    Hello,
    How can I do the Operations on the TextFields as part of a thread like :
    accepting the values from the user through TextField
    doing operations on the values
    displaying the result
    The Application must have a main function. and the class inherited from Applet and is implementing Runnable Interface.
    I have this class in which a clock is also already running as a part of a Thread.
    Thank you

    Hi,
    What have you done so far? What is your actual problem?
    /Kaj

  • How do I cancel an operation in Pro*C (with threads)

    I would like to be able to cancel a potentially long running Oracle operation initiated in Pro*C. It seems that, in an application having only a single database connection (i.e. does not use EXEC SQL ENABLE THREADS), I can do this by sending the SIGINT signal from another thread -- since obviously the DB thread is blocked waiting for the operation to complete. By having the "cancel thread" execute a pthread_kill(tid, SIGINT) against the blocked thread the operation is cancelled and the requisite Oracle error (ORA-01013) is caught.
    However, it seems that once I enable threads, this method stops working. Unfortunately, the application I am writing needs multiple database threads. More dismal, I need to direct the cancellation to a single thread. I can, of course, direct the SIGINT to a thread via pthread_kill, but it does not work. Even a single thread with a single DB connection ignores the attempt to cancel -- in fact the program I wrote to test my initial theory stopped working (well, stopped canceling the operation) immediately just by adding an EXEC SQL ENABLE THREADS call.
    So...does anyone know a call that I can make, from within another thread, that would cause an operation (executing on a given database context (sql_context) to become cancelled? Or does anyone have any other suggestions that I may experiment with?
    Thanks all! Looking forward to any ideas.
    OS: AIX 5.3
    DB: Oracle 10g

    Well, while I am still unsure why enabling threads renders my original solution incapable, I have found a suitable working solution.
    After some research, I came across the OCIBreak call in the Oracle Call Interface. Mating this with the Pro*C functions to get the environment and service contexts (SQLEnvGet and SQLSvcCtxGet) allows me to call it. So, currently I set a SIGALRM signal handler and use pthread_kill in the monitoring thread to fire it off. The signal handler eventually calls OCIBreak.
    I am hoping I can get rid of the signal handler and directly call OCIBreak from within the the monitoring thread itself -- but I'm not sure if this will break Oracle's thread consistency model and cause any heart ache. Oracle says that only a single thread should execute commands on a context, so I am not sure if OCIBreak is an exception to that rule. I may just try it and see what happens, but just because it works does not mean it is right or even stable. I'd like definitive proof (or disproof), so if anyone has some insight that'd be welcome.
    Thanks again.
    Edited by: DreamWarrior1337 on Jan 22, 2009 2:53 PM

  • What is a daemon thread in java ?

    What is a daemon thread in java ? Explain with a small example.

    Any thread marked as a daemon. There is nothing special about it. The only intersting thing is that the Java VM terminates if no non-daemon thread is running. So you usually use a daemon thread for bookkeeping tasks, so that this thread doesn't prevent the VM from successfully terminating.

  • "there were not enough threads in the threadpool object to complete the operation" exception

    Post Author: crystalmatrix
    CA Forum: .NET
    I have a WinForm application using a Crystal Report Viewer control that in turn connects to a CR web service to display report. The client side application runs on WinXP SP1 with .Net framework 1.1, and the server is Win2k with ASP.Net 1.1. I am using CR XI out of the box.
    Users would periodically get "there were not enough threads in the threadpool object to complete the operation." exception when trying to launch the report viewer connected to the web service. The web service is a standard example implementation derived from CrystalDecisions.Web.Services.ReportServiceBase class. The problem usually happens when the user tries to open multiple report viewer forms, but once they get the error, it would continue to happen even after the user shuts down all viewer forms and then tries to launch a new one.
    There are some posts on the web regarding multiple asynchronous HttpWebRequest draining threadpool when running simultaneously and each one taking a long time to complete. However, our reports all run pretty quickly and results are usually returned before the next report starts to run. So my question is: does Crystal Report Viewer control has a problem with web service in that it may hold the HttpWebRequest thread even after the report is returned, or any other problem that may prevents the asynchronous thread being released back to the Threadpool? Anyone has experienced similar problems and has a workaround?
    Any advice is appreciated.

    Find your serial number quickly

  • Thread pool of daemon threads?

    If I create a Thread, it can be made a daemon thread by invoking setDaemon(true). But what if I create a thread pool via java.util.concurrent.Executors.newFixedThreadPool(NTHREADS)? How can those threads be made daemon threads?
    CBy

    Thanks Joachim! I didn't know that the newFixedThreadPool method was overloaded.

  • Thread pool configuration for write-behind cache store operation?

    Hi,
    Does Coherence have a thread pool configuration for the Coherence CacheStore operation?
    Or the CacheStore implementation needs to do that?
    We're using write-behind and want to use multiple threads to speed up the store operation (storeAll()...)
    Thanks in advance for your help.

    user621063 wrote:
    Hi,
    Does Coherence have a thread pool configuration for the Coherence CacheStore operation?
    Or the CacheStore implementation needs to do that?
    We're using write-behind and want to use multiple threads to speed up the store operation (storeAll()...)
    Thanks in advance for your help.Hi,
    read/write-through operations are carried out on the worker thread (so if you configured a thread-pool for the service the same thread-pool will be used for the cache-store operation).
    for write-behind/read-ahead operations, there is a single dedicated thread per cache above whatever thread-pool is configured, except for remove operations which are synchronous and still carried out on the worker thread (see above).
    All above is of course per storage node.
    Best regards,
    Robert

  • How to use a thread as daemon thread

    In multithreading i have undergone through daemon thread concepts and its mentioned as low priority thread which runs in the background of garbage collection.
    My query is how to make the thread daemon thread r we going to use thread priorities here.
    Can anyone demonstrate with an example reg this. I will be very much thankful to them.

    In general, threads that run application code are not daemon threads, and threads that run system code are daemon threads,so the daemon attribute is queried using the isDaemon() method; it is set using the setDaemon() method.....

Maybe you are looking for

  • Post Processing Failed in XML Publiser

    Hi all, We are dealing with XML Publisher reports and when trying to run one XML PUblisher report it is completing with warning. Log file is showing the following message. Malaysia Payroll: Version : UNKNOWN Copyright (c) 1979, 1999, Oracle Corporati

  • Organization and Reliability of these Forums

    Last night, I posted this message to the AppleScript forum and elaborated slightly here: Just a general observation: as a participant in a number of forums, several about AppleScript issues, I must congratulate Apple for running the least friendly an

  • PO Create - Workflow - Mail Problem

    Hi experts, I have an workflow that trigers after PO creation.(BUS2012). Then it sends a mail. But, mail does not work correctly. In SBWP , if i run the workflow, mail comes to inbox. I want it works directly. Waiting for helps. Regards, Orhan

  • TS3899 When I transferred my home email to my iphone, some mail comes through and some dont, any explanations??

    When I set up to transfer home emails to my iphone,, some come through and others dont, Any one know why?  and how to correct this??

  • IPhone keyboard shift key not working

    Today out of nowhere the shift key stopped working on my iPhone. When I press it it clicks like normal but does not capitalize the next letter that I type. I haven't changed any settings or anything. Does anyone know what's up? iPhone 3GS, iOS 4.0