[JBoss JIRA] (JBIDE-13368) When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13368:
---------------------------------------------
Okey +1 for the patch with one change:
move the comment that says "// Check if the workspace default vm is in the list" down to the second loop and add comment to first loop saying "// Check if there is a strictly compatible vm in the list" or similar.
> When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13368
> URL: https://issues.jboss.org/browse/JBIDE-13368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-13368.3.3.x.patch, Screenshot-1.png
>
>
> When a SOA-P 5.2 server is started in JBDS 5.0.2 and 5.0.1 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
> The root problem from EAP side is that this stacktrace occurs because it is launched with Java 7, same actually happens from command line.
> Now, the question is why does Java 7 get selected when the server is setup to run with Java Execution Environment 1.6 - that is the tooling bug here and which Rob made a patch for.
> To describe in cases:
> 1) Thus if the user have only Java 6 configured in Eclipse this issue should not occur.
> 2) If the user has only Java 7 configured in Eclipse this error is expected
> 3) If the user has both Java 6 and Java 7 configured and server adapter is configured to use Java 1.6 Execution Environment (which it is by default) then one would expect it to pick Java 6.
> Case 1 and 2 works - its case 3 that is failing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13329 at 1/11/13 10:03 AM:
--------------------------------------------------------------
We need multiple versions of the publish.sh script for 4.0 and 4.1 streams. Or the script has to know about 4.2.0.d, 4.2.1.b and 4.3.0.M4 for JBT and JBDS.
So either we need to commit your changes for 4.2.x into the 4.x branch of jbosstools-build/target-platforms (which IMHO makes sense because master branch won't care about 4.2.x TPs), or we need that the master branch have 3+ TP definitions for 4.2, 4.2.x, and 4.3.0.latestMilestone (currently M4 but will need to add M5 the week of Feb 8).
I would recommend we keep the 4.0/4.2/Juno stuff in the 4.x branch (and adjust the TP jobs accordingly) and keep the 4.1/4.3/Kepler in master, and not cross the streams. Because as you know, crossing the streams is bad.
http://www.imdb.com/title/tt0087332/quotes?qt=qt0475898
was (Author: nickboldt):
We need multiple versions of the publish.sh script for 4.0 and 4.1 streams. Or the script has to know about 4.2.0.*, 4.2.1.* and 4.3.0.M4 for JBT and JBDS.
So either we need to commit your changes for 4.2.x into the 4.x branch of jbosstools-build/target-platforms (which IMHO makes sense because master branch won't care about 4.2.x TPs), or we need that the master branch have 3+ TP definitions for 4.2, 4.2.x, and 4.3.0.latestMilestone (currently M4 but will need to add M5 the week of Feb 8).
I would recommend we keep the 4.0/4.2/Juno stuff in the 4.x branch (and adjust the TP jobs accordingly) and keep the 4.1/4.3/Kepler in master, and not cross the streams. Because as you know, crossing the streams is bad.
http://www.imdb.com/title/tt0087332/quotes?qt=qt0475898
> should unified.target includes sources?
> ---------------------------------------
>
> Key: JBIDE-13329
> URL: https://issues.jboss.org/browse/JBIDE-13329
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not.
> However:
> {code}
> unified-4.2.1.a-20121220.173723-14-unified.target:
> <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit">
> multiple-4.2.1.a-20121220.173233-14-multiple.target:
> <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true">
> {code}
> And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles:
> http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/
> Is this intentional? Or is there a bug in your flatten mojo?
> https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13329:
------------------------------------
We need multiple versions of the publish.sh script for 4.0 and 4.1 streams. Or the script has to know about 4.2.0.*, 4.2.1.* and 4.3.0.M4 for JBT and JBDS.
So either we need to commit your changes for 4.2.x into the 4.x branch of jbosstools-build/target-platforms (which IMHO makes sense because master branch won't care about 4.2.x TPs), or we need that the master branch have 3+ TP definitions for 4.2, 4.2.x, and 4.3.0.latestMilestone (currently M4 but will need to add M5 the week of Feb 8).
I would recommend we keep the 4.0/4.2/Juno stuff in the 4.x branch (and adjust the TP jobs accordingly) and keep the 4.1/4.3/Kepler in master, and not cross the streams. Because as you know, crossing the streams is bad.
http://www.imdb.com/title/tt0087332/quotes?qt=qt0475898
> should unified.target includes sources?
> ---------------------------------------
>
> Key: JBIDE-13329
> URL: https://issues.jboss.org/browse/JBIDE-13329
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not.
> However:
> {code}
> unified-4.2.1.a-20121220.173723-14-unified.target:
> <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit">
> multiple-4.2.1.a-20121220.173233-14-multiple.target:
> <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true">
> {code}
> And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles:
> http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/
> Is this intentional? Or is there a bug in your flatten mojo?
> https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-13368) When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13368:
----------------------------------------
Description:
When a SOA-P 5.2 server is started in JBDS 5.0.2 and 5.0.1 - this exception is raised:
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
at org.jboss.Main.boot(Main.java:218)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 6 more
The root problem from EAP side is that this stacktrace occurs because it is launched with Java 7, same actually happens from command line.
Now, the question is why does Java 7 get selected when the server is setup to run with Java Execution Environment 1.6 - that is the tooling bug here and which Rob made a patch for.
To describe in cases:
1) Thus if the user have only Java 6 configured in Eclipse this issue should not occur.
2) If the user has only Java 7 configured in Eclipse this error is expected
3) If the user has both Java 6 and Java 7 configured and server adapter is configured to use Java 1.6 Execution Environment (which it is by default) then one would expect it to pick Java 6.
Case 1 and 2 works - its case 3 that is failing.
was:
This is a regression relative to JBDS 5.0.1
When a SOA-P 5.2 server is started in JBDS 5.0.2 - this exception is raised:
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
at org.jboss.Main.boot(Main.java:218)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 6 more
> When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13368
> URL: https://issues.jboss.org/browse/JBIDE-13368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-13368.3.3.x.patch, Screenshot-1.png
>
>
> When a SOA-P 5.2 server is started in JBDS 5.0.2 and 5.0.1 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
> The root problem from EAP side is that this stacktrace occurs because it is launched with Java 7, same actually happens from command line.
> Now, the question is why does Java 7 get selected when the server is setup to run with Java Execution Environment 1.6 - that is the tooling bug here and which Rob made a patch for.
> To describe in cases:
> 1) Thus if the user have only Java 6 configured in Eclipse this issue should not occur.
> 2) If the user has only Java 7 configured in Eclipse this error is expected
> 3) If the user has both Java 6 and Java 7 configured and server adapter is configured to use Java 1.6 Execution Environment (which it is by default) then one would expect it to pick Java 6.
> Case 1 and 2 works - its case 3 that is failing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-13368) When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-13368:
--------------------------------------
Thanks Max - I missed that as I had JAVA_HOME set to 1.6, but was using 1.7
After fixing the JAVA_HOME reference - the server is failing to start from the command line as expected:
echo $JAVA_HOME
/usr/lib/jvm/java-1.7.0-openjdk.x86_64
[ldimaggi@ldimaggi bin]$ java -version
java version "1.7.0_05-icedtea"
OpenJDK Runtime Environment (rhel-2.2.1.el6_3.3-x86_64)
OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
[ldimaggi@ldimaggi bin]$ sh ./run.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/local/EAP_512/jboss-eap-5.1/jboss-as
JAVA: /usr/lib/jvm/java-1.7.0-openjdk.x86_64/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true
CLASSPATH: /opt/local/EAP_512/jboss-eap-5.1/jboss-as/bin/run.jar:/usr/lib/jvm/java-1.7.0-openjdk.x86_64/lib/tools.jar
=========================================================================
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
at org.jboss.Main.boot(Main.java:218)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 6 more
> When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13368
> URL: https://issues.jboss.org/browse/JBIDE-13368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-13368.3.3.x.patch, Screenshot-1.png
>
>
> This is a regression relative to JBDS 5.0.1
> When a SOA-P 5.2 server is started in JBDS 5.0.2 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-13368) When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13368:
----------------------------------------
Summary: When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch (was: Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2)
> When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13368
> URL: https://issues.jboss.org/browse/JBIDE-13368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-13368.3.3.x.patch, Screenshot-1.png
>
>
> This is a regression relative to JBDS 5.0.1
> When a SOA-P 5.2 server is started in JBDS 5.0.2 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (JBIDE-13368) Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13368:
---------------------------------------------
Just to make this clear:
The root problem from EAP side is that this stacktrace occurs because it is launched with Java 7, same actually happens from command line.
Now, the question is *why* does Java 7 get selected when the server is setup to run with Java Execution Environment 1.6 - *that* is the tooling bug here and which Rob made a patch for.
To describe in cases:
1) Thus if the user have *only* Java 6 configured in Eclipse this issue should not occur.
2) If the user has *only* Java 7 configured in Eclipse this error is *expected*
3) If the user has *both* Java 6 *and* Java 7 configured *and* server adapter is configured to use Java 1.6 Execution Environment (which it is by default) then one would expect it to pick Java 6.
Case 1 and 2 works - its case 3 that is failing.
> Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2
> ------------------------------------------------------------
>
> Key: JBIDE-13368
> URL: https://issues.jboss.org/browse/JBIDE-13368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-13368.3.3.x.patch, Screenshot-1.png
>
>
> This is a regression relative to JBDS 5.0.1
> When a SOA-P 5.2 server is started in JBDS 5.0.2 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months