Versions Compared

Version Old Version 1 New Version Current
Changes made by

Shaun Morris

Shaun Morris

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • Multiple java.exe processes running indicating more than one
    Include Page
    ApplicationName
    ApplicationName
    instance is running. This can be caused by not shutting down another
    Include Page
    ApplicationName
    ApplicationName
    .

Include Page
ApplicationName
ApplicationName
becomes Unresponsive to Incoming Requests

 

Excerpt

Problem:
Include Page
ApplicationName
ApplicationName
Becomes Unresponsive to Incoming Requests. An example of what the log file will look like is located below:

 

Code Block
Feb 7, 2013 10:51:33 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Feb 7, 2013 10:51:33 AM org.apache.karaf.main.Main doLock
INFO: Waiting for the lock ...
Feb 7, 2013 10:51:33 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Feb 7, 2013 10:51:33 AM org.apache.karaf.main.Main doLock
INFO: Waiting for the lock ...
Feb 7, 2013 10:51:34 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Feb 7, 2013 10:51:34 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Feb 7, 2013 10:51:35 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Feb 7, 2013 10:51:35 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking

 

Possible Solutions:

  • Wait for proper shutdown of
    Include Page
    ApplicationName
    ApplicationName
    prior to starting a new instance
  • Verify running java.exe are not
    Include Page
    ApplicationName
    ApplicationName
    (e.g. kill/close if necessary)
  • Utilize automated start/stop scripts to run
    Include Page
    ApplicationName
    ApplicationName
    as a service.

...