RE: possible deadlock in the event service?

Sorry for the large stack trace.  Here's the important bit.  

 

I was able to reprocuce it consistently without removeing the timeout on
the PushServer example.  What I did was start a client, kill it, start
another, and mess with the time (going backward and forward by years).
After a few times the event service crashed and I think that the
deadlock was because of this thread.  The timeout calculated by
JTCC_COND_calc_timeout is HUGE.

 

 

 (gdb) thread 13

[Switching to thread 13 (Thread 11276 (LWP 17197))]#0  0x0fdb4a74 in
nanosleep () from /lib/libc.so.6

(gdb) bt

#0  0x0fdb4a74 in nanosleep () from /lib/libc.so.6

#1  0x0fe5ba24 in __pthread_timedsuspend_new () from
/lib/libpthread.so.0

#2  0x0fe576ec in pthread_cond_timedwait_relative () from
/lib/libpthread.so.0

#3  0x0fe578a4 in pthread_cond_timedwait () from /lib/libpthread.so.0

#4  0x0ffc5b64 in JTCC_Cond_wait_internal (this=0x1001f4fc,
mutex_if=0x1001f50c, timeout=1800000, env=0x7e3ffa58)

    at Cond.c:447

#5  0x0ffc5ea0 in JTCC_Cond_wait_timeout (this=0x1001f4fc,
mutex_if=0x1001f50c, timeout=1800000, env=0x7e3ffa58)

    at Cond.c:575

#6  0x0ffcb5f8 in JTCC_Monitor_wait_timeout (this=0x1001f4fc,
timeout=1800000, env=0x7e3ffa58) at Monitor.c:298

#7  0x0ff6ed08 in Reaper_run (self=0x1001f4f0) at Reaper.c:114

#8  0x0ffc9dac in JTCC_Thread_entrance_hook (this=0x1001f4f0,
env=0x7e3ffae8) at Thread.c:1678

#9  0x0ffc75b8 in lsf_thread_adapter (arg=0x1001f4f0) at Thread.c:170

#10 0x0fe58554 in pthread_start_thread () from /lib/libpthread.so.0

#11 0x0fe5859c in pthread_allocate_stack () from /lib/libpthread.so.0

#12 0x0fddfa18 in clone () from /lib/libc.so.6

(gdb) thread 12

_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html