You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/05/12 18:06:55 UTC
[jira] Created: (DERBY-3672) derbyrunjartest failed on weme 6.1
with "Process exception: Unable to start program"
derbyrunjartest failed on weme 6.1 with "Process exception: Unable to start program"
------------------------------------------------------------------------------------
Key: DERBY-3672
URL: https://issues.apache.org/jira/browse/DERBY-3672
Project: Derby
Issue Type: Bug
Components: Regression Test Failure
Affects Versions: 10.5.0.0
Reporter: Kathey Marsden
Priority: Minor
Saw this on the IBM run for 5/9/2008 Looks similar to DERBY-1003 which failed on the same day.
*** Start: derbyrunjartest jdkJ2ME Foundation Specification v1.1 derbyall:derbytools 2008-05-10 01:55:20 ***
2 del
< Usage: java org.apache.derby.tools.ij [-p propertyfile] [-ca connectionAttributePropertyFile] [inputfile]
2a2
> Process exception: Unable to start program
4 del
< USAGE: java org.apache.derby.tools.sysinfo -cp [ [ embedded ][ server ][ client] [ db2driver ] [ tools ] [ anyClass.class ] ]
4a4
> Process exception: Unable to start program
6 del
< USAGE:
7 del
< java org.apache.derby.tools.dblook -d <sourceDBUrl> [OPTIONS]
8 del
< where the source URL is the full URL, including the connection protocol
9 del
< and any connection attributes that might apply. For example, use
10 del
< 'jdbc:derby:myDB', or 'jdbc:derby://xxxFILTERED_HOSTNAMExxx:1527/myDB;user=usr;'.
11 del
< options include:
12 del
< -z <schemaName> to specify a schema to which the DDL generation
13 del
< should be limited. Only database objects with that schema will have
14 del
< their DDL generated.
15 del
< -t <tableOne> <tableTwo> ... to specify a list of tables for which
16 del
< the DDL will be generated; any tables not in the list will be ignored.
17 del
< -td <value> to specify what should be appended to the end
18 del
< of each DDL statement.
19 del
< This defaults to ';'.
20 del
< -noview to prevent the generation of DDL for views.
21 del
< -append to keep from overwriting the output files.
22 del
< -verbose to have error messages printed to the console (in addition
23 del
< to the log file). If not specified, errors will only be printed to the
24 del
< log file.
25 del
< -o <filename> to specify the file name to which the generated DDL
26 del
< will be written.
27 del
< If not specified, default is the console.
27a6
> Process exception: Unable to start program
29 del
< No command given.
30 del
< Usage: NetworkServerControl <commands>
31 del
< Commands:
32 del
< start [-h <host>] [-p <portnumber>] [-noSecurityManager] [-ssl <sslmode>]
33 del
< shutdown [-h <host>][-p <portnumber>] [-ssl <sslmode>] [-user <username>] [-password <password>]
34 del
< ping [-h <host>][-p <portnumber>] [-ssl <sslmode>]
35 del
< sysinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
36 del
< runtimeinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
37 del
< logconnections {on|off}[-h <host>][-p <portnumber>] [-ssl <sslmode>]
38 del
< maxthreads <max>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
39 del
< timeslice <milliseconds>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
40 del
< trace {on|off} [-s <session id>][-h <host>][-p <portnumber>] [-ssl <sslmode>]
41 del
< tracedirectory <traceDirectory>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
41 add
> Process exception: Unable to start program
Test Failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3672) derbyrunjartest failed on weme 6.1
with "Process exception: Unable to start program"
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-3672.
---------------------------------------
Resolution: Invalid
This was a problem with a variation of the setup on this machine, using cygwin, in combination with the -xbootclasspath, which we need with this specific jvm to find the jdbc implementation.
cygwin style paths (like: /cygdrive/c/derbytst/.. instead of c:/derbytst/...) do not work well for jvms (weme6.1 but also others) for windows.
Using the cygwin utility cygpath -m in the correct incantation and in the correct spot got around this problem.
> derbyrunjartest failed on weme 6.1 with "Process exception: Unable to start program"
> ------------------------------------------------------------------------------------
>
> Key: DERBY-3672
> URL: https://issues.apache.org/jira/browse/DERBY-3672
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.4.1.4
> Reporter: Kathey Marsden
> Priority: Minor
>
> Saw this on the IBM run for 5/9/2008 Looks similar to DERBY-1003 which failed on the same day.
> *** Start: derbyrunjartest jdkJ2ME Foundation Specification v1.1 derbyall:derbytools 2008-05-10 01:55:20 ***
> 2 del
> < Usage: java org.apache.derby.tools.ij [-p propertyfile] [-ca connectionAttributePropertyFile] [inputfile]
> 2a2
> > Process exception: Unable to start program
> 4 del
> < USAGE: java org.apache.derby.tools.sysinfo -cp [ [ embedded ][ server ][ client] [ db2driver ] [ tools ] [ anyClass.class ] ]
> 4a4
> > Process exception: Unable to start program
> 6 del
> < USAGE:
> 7 del
> < java org.apache.derby.tools.dblook -d <sourceDBUrl> [OPTIONS]
> 8 del
> < where the source URL is the full URL, including the connection protocol
> 9 del
> < and any connection attributes that might apply. For example, use
> 10 del
> < 'jdbc:derby:myDB', or 'jdbc:derby://xxxFILTERED_HOSTNAMExxx:1527/myDB;user=usr;'.
> 11 del
> < options include:
> 12 del
> < -z <schemaName> to specify a schema to which the DDL generation
> 13 del
> < should be limited. Only database objects with that schema will have
> 14 del
> < their DDL generated.
> 15 del
> < -t <tableOne> <tableTwo> ... to specify a list of tables for which
> 16 del
> < the DDL will be generated; any tables not in the list will be ignored.
> 17 del
> < -td <value> to specify what should be appended to the end
> 18 del
> < of each DDL statement.
> 19 del
> < This defaults to ';'.
> 20 del
> < -noview to prevent the generation of DDL for views.
> 21 del
> < -append to keep from overwriting the output files.
> 22 del
> < -verbose to have error messages printed to the console (in addition
> 23 del
> < to the log file). If not specified, errors will only be printed to the
> 24 del
> < log file.
> 25 del
> < -o <filename> to specify the file name to which the generated DDL
> 26 del
> < will be written.
> 27 del
> < If not specified, default is the console.
> 27a6
> > Process exception: Unable to start program
> 29 del
> < No command given.
> 30 del
> < Usage: NetworkServerControl <commands>
> 31 del
> < Commands:
> 32 del
> < start [-h <host>] [-p <portnumber>] [-noSecurityManager] [-ssl <sslmode>]
> 33 del
> < shutdown [-h <host>][-p <portnumber>] [-ssl <sslmode>] [-user <username>] [-password <password>]
> 34 del
> < ping [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 35 del
> < sysinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 36 del
> < runtimeinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 37 del
> < logconnections {on|off}[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 38 del
> < maxthreads <max>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 39 del
> < timeslice <milliseconds>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 40 del
> < trace {on|off} [-s <session id>][-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 41 del
> < tracedirectory <traceDirectory>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 41 add
> > Process exception: Unable to start program
> Test Failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3672) derbyrunjartest failed on weme 6.1
with "Process exception: Unable to start program"
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3672:
----------------------------------
Affects Version/s: (was: 10.5.0.0)
10.4.1.4
This failure was on the new machine setup for derby 10.4 so might be an environmental issue.
> derbyrunjartest failed on weme 6.1 with "Process exception: Unable to start program"
> ------------------------------------------------------------------------------------
>
> Key: DERBY-3672
> URL: https://issues.apache.org/jira/browse/DERBY-3672
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.4.1.4
> Reporter: Kathey Marsden
> Priority: Minor
>
> Saw this on the IBM run for 5/9/2008 Looks similar to DERBY-1003 which failed on the same day.
> *** Start: derbyrunjartest jdkJ2ME Foundation Specification v1.1 derbyall:derbytools 2008-05-10 01:55:20 ***
> 2 del
> < Usage: java org.apache.derby.tools.ij [-p propertyfile] [-ca connectionAttributePropertyFile] [inputfile]
> 2a2
> > Process exception: Unable to start program
> 4 del
> < USAGE: java org.apache.derby.tools.sysinfo -cp [ [ embedded ][ server ][ client] [ db2driver ] [ tools ] [ anyClass.class ] ]
> 4a4
> > Process exception: Unable to start program
> 6 del
> < USAGE:
> 7 del
> < java org.apache.derby.tools.dblook -d <sourceDBUrl> [OPTIONS]
> 8 del
> < where the source URL is the full URL, including the connection protocol
> 9 del
> < and any connection attributes that might apply. For example, use
> 10 del
> < 'jdbc:derby:myDB', or 'jdbc:derby://xxxFILTERED_HOSTNAMExxx:1527/myDB;user=usr;'.
> 11 del
> < options include:
> 12 del
> < -z <schemaName> to specify a schema to which the DDL generation
> 13 del
> < should be limited. Only database objects with that schema will have
> 14 del
> < their DDL generated.
> 15 del
> < -t <tableOne> <tableTwo> ... to specify a list of tables for which
> 16 del
> < the DDL will be generated; any tables not in the list will be ignored.
> 17 del
> < -td <value> to specify what should be appended to the end
> 18 del
> < of each DDL statement.
> 19 del
> < This defaults to ';'.
> 20 del
> < -noview to prevent the generation of DDL for views.
> 21 del
> < -append to keep from overwriting the output files.
> 22 del
> < -verbose to have error messages printed to the console (in addition
> 23 del
> < to the log file). If not specified, errors will only be printed to the
> 24 del
> < log file.
> 25 del
> < -o <filename> to specify the file name to which the generated DDL
> 26 del
> < will be written.
> 27 del
> < If not specified, default is the console.
> 27a6
> > Process exception: Unable to start program
> 29 del
> < No command given.
> 30 del
> < Usage: NetworkServerControl <commands>
> 31 del
> < Commands:
> 32 del
> < start [-h <host>] [-p <portnumber>] [-noSecurityManager] [-ssl <sslmode>]
> 33 del
> < shutdown [-h <host>][-p <portnumber>] [-ssl <sslmode>] [-user <username>] [-password <password>]
> 34 del
> < ping [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 35 del
> < sysinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 36 del
> < runtimeinfo [-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 37 del
> < logconnections {on|off}[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 38 del
> < maxthreads <max>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 39 del
> < timeslice <milliseconds>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 40 del
> < trace {on|off} [-s <session id>][-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 41 del
> < tracedirectory <traceDirectory>[-h <host>][-p <portnumber>] [-ssl <sslmode>]
> 41 add
> > Process exception: Unable to start program
> Test Failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.