#1 2012-03-14 00:00:53

**_cnj125_**

Connect Pro service terminated after startup

Hello,

I have a Connect Pro server (connect_750_r134) running on Win 2003 platform.
The server will connect to a LDAP server to update user accounts and it is running smooth before. After I have setup a daily synchronization job in Connect Pro admin interface, the Connect Pro service may be terminated abnormally when I start the Connect Pro server randomly. So I have disable the scheduled job, however the error still occurs randomly during service startup. Anyone can help? Thanks

Connect Pro service log:
2012/03/14 09:34:45 | ERROR  | wrapper  | Shutdown failed: Timed out waiting for signal from JVM.
2012/03/14 09:34:45 | ERROR  | wrapper  | JVM did not exit on request, terminated
2012/03/14 09:34:45 | STATUS | wrapper  | on_exit trigger matched.  Restarting the JVM.  (Exit code: 1)
2012/03/14 09:34:50 | STATUS | wrapper  | Launching a JVM...
2012/03/14 09:37:41 | ERROR  | wrapper  | Shutdown failed: Timed out waiting for signal from JVM.
2012/03/14 09:37:41 | ERROR  | wrapper  | JVM did not exit on request, terminated
2012/03/14 09:37:42 | STATUS | wrapper  | on_exit trigger matched.  Restarting the JVM.  (Exit code: 1)
2012/03/14 09:37:42 | FATAL  | wrapper  | There were 2 failed launches in a row, each lasting less than 300 seconds.  Giving up.
2012/03/14 09:37:42 | FATAL  | wrapper  |   There may be a configuration problem: please check the logs.
2012/03/14 09:37:42 | STATUS | wrapper  | <-- Wrapper Stopped

Error log:
2012-03-14    09:37:06    "Master thread has not reported progress in 125047 milliseconds."    PLATFORM_FRAMEWORK    MASTER_THREAD_TIMED_OUT    C    S    -    "-"    -    -    -

Regards,
Ben