Bug #6794


Cannot run two instances at the same time with two different users

Added by Vincenzo Forchi over 8 years ago. Updated over 8 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


If I try to run Kepler at the same time with two different users the second instance fails with the following error:

[run] Kepler Initializing...
[run] Command failed
[run] Arguments: -kepler
[run] java.lang.Exception: Failed to parse "-kepler"
[run] at
[run] at<init>(
[run] at<init>(
[run] at ptolemy.vergil.VergilApplication.<init>(
[run] at ptolemy.vergil.VergilApplication$
[run] at java.awt.event.InvocationEvent.dispatch(
[run] at java.awt.EventQueue.dispatchEventImpl(
[run] at java.awt.EventQueue.access$200(
[run] at java.awt.EventQueue$
[run] at java.awt.EventQueue$
[run] at Method)
[run] at$1.doIntersectionPrivilege(
[run] at java.awt.EventQueue.dispatchEvent(
[run] at java.awt.EventDispatchThread.pumpOneEventForFilters(
[run] at java.awt.EventDispatchThread.pumpEventsForFilter(
[run] at java.awt.EventDispatchThread.pumpEventsForHierarchy(
[run] at java.awt.EventDispatchThread.pumpEvents(
[run] at java.awt.EventDispatchThread.pumpEvents(
[run] at
[run] Caused by: java.lang.Exception: Failed to read configuration 'file:/diskb/scratch/vforchi/sw/reflex/common-2.4/configs/ptolemy/configs/kepler/configuration.xml'
[run] at ptolemy.vergil.VergilApplication._createDefaultConfiguration(
[run] at ptolemy.vergil.VergilApplication._createEmptyConfiguration(
[run] at
[run] at ptolemy.vergil.VergilApplication._parseArgs(
[run] at<init>(
[run] ... 17 more
[run] Caused by: java.lang.Exception: Failed to call application initializer class "org.kepler.gui.KeplerInitializer". Perhaps the configuration file "file:/diskb/scratch/vforchi/sw/reflex/common-2.4/configs/ptolemy/configs/kepler/configuration.xml" has a problem?
[run] at
[run] at ptolemy.vergil.VergilApplication._createDefaultConfiguration(
[run] ... 21 more
[run] Caused by: java.sql.SQLException: Access is denied
[run] at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
[run] at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
[run] at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
[run] at org.hsqldb.jdbcDriver.connect(Unknown Source)
[run] at java.sql.DriverManager.getConnection(
[run] at java.sql.DriverManager.getConnection(
[run] at org.kepler.util.sql.HSQL._getConnection(
[run] at org.kepler.util.sql.DatabaseFactory.getDBConnection(
[run] at org.kepler.gui.KeplerInitializer.initializeSystem(
[run] at org.kepler.gui.KeplerInitializer.<init>(
[run] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[run] at sun.reflect.NativeConstructorAccessorImpl.newInstance(
[run] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
[run] at java.lang.reflect.Constructor.newInstance(
[run] at java.lang.Class.newInstance(
[run] at
[run] ... 22 more
[run] Checking for patches...

And the attached window pops up.
Are there any plans to fix this or is it there a workaround?


Kepler_error.PNG (11.5 KB) Kepler_error.PNG Vincenzo Forchi, 07/07/2015 09:08 AM
Actions #1

Updated by Matt Jones over 8 years ago

What version of Kepler do you have? I thought we had worked out these issues with launching multiple versions of Kepler with the 2.4 release. Details of the conflicts with HSQL ports for multiple instances are described here:

Dan Crawl, do you have a sense whether this SQL exception on launching the second error is related to HSQL port conflicts? Seems like this should work under Kepler 2.4.

Actions #2

Updated by Matt Jones over 8 years ago

  • Assignee set to Daniel Crawl
Actions #3

Updated by Daniel Crawl over 8 years ago

This problem is fixed in the Kepler svn trunk and in Kepler 2.4 as a patch. If you are using Kepler 2.4, make sure you have downloaded the patches. You can check by going to Tools -> Module Manager, and in the Current Suite tab list of modules, you should see core-2.4.1. If you have core-2.4.0, then you'll need to download the patches by going to the Available Suites and Modules tab and clicking on Check for Patches Now.

The error message in the stack trace looks like the second Kepler instance is trying to connect to the first instance using the same port.


Also available in: Atom PDF