|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (CARGO-729) Cargo doesn't work with JBoss EAP 5 on IBM JDK 6Cargo doesn't work with JBoss EAP 5 on IBM JDK 6
------------------------------------------------ Key: CARGO-729 URL: http://jira.codehaus.org/browse/CARGO-729 Project: Cargo Issue Type: Bug Environment: IBM JDK 6 - x64 EAP 5 CR3 RHEL 5 Reporter: Ondrej Zizka Cargo can't start EAP server when running in IBM JDK 6. Fails with the exception listed below. No other log info available. Tested with Embedded Jopr testsuite. [INFO] [cargo:start {execution: start-container}] Exception in thread "Thread-9" key and value must be specified for environment variables. at org.apache.tools.ant.types.Environment$Variable.validate(Environment.java:128) at org.apache.tools.ant.types.Environment$Variable.getContent(Environment.java:116) at org.apache.tools.ant.types.Environment.getVariables(Environment.java:162) at org.apache.tools.ant.types.CommandlineJava$SysProperties.addDefinitionsToList(CommandlineJava.java:107) at org.apache.tools.ant.types.CommandlineJava.addCommandsToList(CommandlineJava.java:416) at org.apache.tools.ant.types.CommandlineJava.getCommandline(CommandlineJava.java:402) at org.apache.tools.ant.types.CommandlineJava.describeCommand(CommandlineJava.java:479) at org.apache.tools.ant.taskdefs.Java.checkConfiguration(Java.java:173) at org.apache.tools.ant.taskdefs.Java.execute(Java.java:104) at org.codehaus.cargo.container.internal.AntContainerExecutorThread.run(AntContainerExecutorThread.java:50) [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to start the JBoss 5.0.0 container. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-729) Cargo doesn't work with JBoss EAP 5 on IBM JDK 6[ http://jira.codehaus.org/browse/CARGO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189407#action_189407 ] Ondrej Zizka commented on CARGO-729: ------------------------------------ <jboss.platform.mbeanserver/> doesn't work. <jboss.platform.mbeanserver></jboss.platform.mbeanserver> doesn't work. <jboss.platform.mbeanserver></jboss.platform.mbeanserver> works. works. So I guess it really is a minor bug in cargo. (20:24:06) ozizka: See the stack trace... I think that cargo creates Ant task programatically, (20:24:14) ozizka: but ommits the env var value (20:24:29) ozizka: But that's only my 2c > Cargo doesn't work with JBoss EAP 5 on IBM JDK 6 > ------------------------------------------------ > > Key: CARGO-729 > URL: http://jira.codehaus.org/browse/CARGO-729 > Project: Cargo > Issue Type: Bug > Environment: IBM JDK 6 - x64 > EAP 5 CR3 > RHEL 5 > Reporter: Ondrej Zizka > > Cargo can't start EAP server when running in IBM JDK 6. Fails with the exception listed below. > No other log info available. > Tested with Embedded Jopr testsuite. > [INFO] [cargo:start {execution: start-container}] > Exception in thread "Thread-9" key and value must be specified for environment variables. > at org.apache.tools.ant.types.Environment$Variable.validate(Environment.java:128) > at org.apache.tools.ant.types.Environment$Variable.getContent(Environment.java:116) > at org.apache.tools.ant.types.Environment.getVariables(Environment.java:162) > at org.apache.tools.ant.types.CommandlineJava$SysProperties.addDefinitionsToList(CommandlineJava.java:107) > at org.apache.tools.ant.types.CommandlineJava.addCommandsToList(CommandlineJava.java:416) > at org.apache.tools.ant.types.CommandlineJava.getCommandline(CommandlineJava.java:402) > at org.apache.tools.ant.types.CommandlineJava.describeCommand(CommandlineJava.java:479) > at org.apache.tools.ant.taskdefs.Java.checkConfiguration(Java.java:173) > at org.apache.tools.ant.taskdefs.Java.execute(Java.java:104) > at org.codehaus.cargo.container.internal.AntContainerExecutorThread.run(AntContainerExecutorThread.java:50) > [INFO] ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] ------------------------------------------------------------------------ > [INFO] Failed to start the JBoss 5.0.0 container. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-729) Cargo doesn't work with JBoss EAP 5 on IBM JDK 6[ http://jira.codehaus.org/browse/CARGO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189456#action_189456 ] Ondrej Zizka commented on CARGO-729: ------------------------------------ If I could edit this the issue, I would change the title to "Empty system variables cause Ant exception." Seems to have nothing to do with IBM JDK. > Cargo doesn't work with JBoss EAP 5 on IBM JDK 6 > ------------------------------------------------ > > Key: CARGO-729 > URL: http://jira.codehaus.org/browse/CARGO-729 > Project: Cargo > Issue Type: Bug > Environment: IBM JDK 6 - x64 > EAP 5 CR3 > RHEL 5 > Reporter: Ondrej Zizka > > Cargo can't start EAP server when running in IBM JDK 6. Fails with the exception listed below. > No other log info available. > Tested with Embedded Jopr testsuite. > [INFO] [cargo:start {execution: start-container}] > Exception in thread "Thread-9" key and value must be specified for environment variables. > at org.apache.tools.ant.types.Environment$Variable.validate(Environment.java:128) > at org.apache.tools.ant.types.Environment$Variable.getContent(Environment.java:116) > at org.apache.tools.ant.types.Environment.getVariables(Environment.java:162) > at org.apache.tools.ant.types.CommandlineJava$SysProperties.addDefinitionsToList(CommandlineJava.java:107) > at org.apache.tools.ant.types.CommandlineJava.addCommandsToList(CommandlineJava.java:416) > at org.apache.tools.ant.types.CommandlineJava.getCommandline(CommandlineJava.java:402) > at org.apache.tools.ant.types.CommandlineJava.describeCommand(CommandlineJava.java:479) > at org.apache.tools.ant.taskdefs.Java.checkConfiguration(Java.java:173) > at org.apache.tools.ant.taskdefs.Java.execute(Java.java:104) > at org.codehaus.cargo.container.internal.AntContainerExecutorThread.run(AntContainerExecutorThread.java:50) > [INFO] ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] ------------------------------------------------------------------------ > [INFO] Failed to start the JBoss 5.0.0 container. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |