[JBoss JIRA] (JBIDE-13246) When two servers with same version are found only one is added
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13246?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13246:
-------------------------------------
Max: Where is the appropriate place to put a UI test case for this? AS Tools has no bot tests itself. All the UI bot tests are in qe's repos.
This is a one line patch that snjezana posted a fix for and I have verified works. The logic is buried in the wizards and so it's not an obvious thing to test, and there is no obvious repo for which such a test should live.
I could conceivably come up with a bot test using test handlers to put in runtime (ie not using actual astools but simply testing the runtimes ability to handle multiple runtimes found at some path), but then runtimes/tests also has no ui bot tests.
Are you suggesting we make a new test plugin for the maintenance patch? Also it was my understanding that the bot tests were being moved out (or have already moved out) to a QE area, and that they don't belong in the primary test folders anymore.
So, please advise what you think is best here. In the past, one line fixes in a UI element do not require new tests.
> When two servers with same version are found only one is added
> ---------------------------------------------------------------
>
> Key: JBIDE-13246
> URL: https://issues.jboss.org/browse/JBIDE-13246
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.0.CR1
> Reporter: Petr Suchý
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Alpha1, 4.0.x
>
>
> Regression - JBIDE-12714
> When I add a path that contains two servers with the same type and version, both are correctly listed as found but just one is added.
--
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, 2 months
[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-13413 at 1/28/13 11:58 PM:
------------------------------------------------------------------
1. *Page* (http://jquerymobile.com/test/docs/pages/page-anatomy.html)
!NewPage.png|thumbnail!
Result:
{code}
<div data-role="page">
<div data-role="header">
<h1>Page Title</h1>
</div><!-- /header -->
<div data-role="content">
<p>Page content goes here.</p>
</div><!-- /content -->
<div data-role="footer">
<h4>Page Footer</h4>
</div><!-- /footer -->
</div><!-- /page -->
{code}
2. *Dialog* (http://jquerymobile.com/test/docs/pages/dialog/index.html)
!NewDialog.png|thumbnail!
Result:
{code}
<a href="foo.html" data-rel="dialog" data-transition="pop" data-close-btn="none">Open dialog</a>
{code}
3. *Popup* (http://jquerymobile.com/test/docs/pages/popup/index.html)
!NewPopup.png|thumbnail!
Result:
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
4. *Header Bar* (http://jquerymobile.com/test/docs/toolbars/docs-headers.html)
!NewHeaderBar.png|thumbnail!
Result:
{code}
<div data-role="header">
<a href="index.html" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="index.html" data-icon="check" data-theme="b">Save</a>
</div>
{code}
5. *Footer Bar* (http://jquerymobile.com/test/docs/toolbars/docs-footers.html)
No wizard.
Result:
{code}
<div data-role="footer" class="ui-bar">
</div>
{code}
6. *Navbar* (http://jquerymobile.com/test/docs/toolbars/docs-navbar.html)
!NewNavbar.png|thumbnail!
<div data-role="navbar">
<ul>
<li><a href="a.html">One</a></li>
<li><a href="b.html">Two</a></li>
</ul>
</div><!-- /navbar -->
7. *Button*
8. *Grouped Buttons*
9. *Grid*
10. *Collapsible Content Block*
11. *Collapsible Set*
12. *Field Container*
13. *Flip Toggle Switch*
14. *Radio Button*
15. *Check Box*
16. *Grouped Check Boxes*
17. *Select Menu*
18. *Listview*
19. *Panel*
20. *Table*
was (Author: akazakov):
1. *Page* (http://jquerymobile.com/test/docs/pages/page-anatomy.html)
!NewPage.png|thumbnail!
Result:
{code}
<div data-role="page">
<div data-role="header">
<h1>Page Title</h1>
</div><!-- /header -->
<div data-role="content">
<p>Page content goes here.</p>
</div><!-- /content -->
<div data-role="footer">
<h4>Page Footer</h4>
</div><!-- /footer -->
</div><!-- /page -->
{code}
2. *Dialog* (http://jquerymobile.com/test/docs/pages/dialog/index.html)
!NewDialog.png|thumbnail!
Result:
{code}
<a href="foo.html" data-rel="dialog" data-transition="pop" data-close-btn="none">Open dialog</a>
{code}
3. *Popup* (http://jquerymobile.com/test/docs/pages/popup/index.html)
!NewPopup.png|thumbnail!
Result:
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
4. *Header Bar* (http://jquerymobile.com/test/docs/toolbars/docs-headers.html)
!NewHeaderBar.png|thumbnail!
Result:
{code}
<div data-role="header">
<a href="index.html" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="index.html" data-icon="check" data-theme="b">Save</a>
</div>
{code}
5. *Footer Bar*
6. *Navbar*
7. *Button*
8. *Grouped Buttons*
9. *Grid*
10. *Collapsible Content Block*
11. *Collapsible Set*
12. *Field Container*
13. *Flip Toggle Switch*
14. *Radio Button*
15. *Check Box*
16. *Grouped Check Boxes*
17. *Select Menu*
18. *Listview*
19. *Panel*
20. *Table*
> jQuery Mobile Widget Palette
> ----------------------------
>
> Key: JBIDE-13413
> URL: https://issues.jboss.org/browse/JBIDE-13413
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.x
>
> Attachments: NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewHeaderBar.bmml, NewHeaderBar.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png
>
>
> http://jquerymobile.com/test/
--
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, 2 months
[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-13413 at 1/28/13 11:59 PM:
------------------------------------------------------------------
1. *Page* (http://jquerymobile.com/test/docs/pages/page-anatomy.html)
!NewPage.png|thumbnail!
Result:
{code}
<div data-role="page">
<div data-role="header">
<h1>Page Title</h1>
</div><!-- /header -->
<div data-role="content">
<p>Page content goes here.</p>
</div><!-- /content -->
<div data-role="footer">
<h4>Page Footer</h4>
</div><!-- /footer -->
</div><!-- /page -->
{code}
2. *Dialog* (http://jquerymobile.com/test/docs/pages/dialog/index.html)
!NewDialog.png|thumbnail!
Result:
{code}
<a href="foo.html" data-rel="dialog" data-transition="pop" data-close-btn="none">Open dialog</a>
{code}
3. *Popup* (http://jquerymobile.com/test/docs/pages/popup/index.html)
!NewPopup.png|thumbnail!
Result:
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
4. *Header Bar* (http://jquerymobile.com/test/docs/toolbars/docs-headers.html)
!NewHeaderBar.png|thumbnail!
Result:
{code}
<div data-role="header">
<a href="index.html" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="index.html" data-icon="check" data-theme="b">Save</a>
</div>
{code}
5. *Footer Bar* (http://jquerymobile.com/test/docs/toolbars/docs-footers.html)
No wizard.
Result:
{code}
<div data-role="footer" class="ui-bar">
</div>
{code}
6. *Navbar* (http://jquerymobile.com/test/docs/toolbars/docs-navbar.html)
!NewNavbar.png|thumbnail!
{code}
<div data-role="navbar">
<ul>
<li><a href="a.html">One</a></li>
<li><a href="b.html">Two</a></li>
</ul>
</div><!-- /navbar -->
{code}
7. *Button*
8. *Grouped Buttons*
9. *Grid*
10. *Collapsible Content Block*
11. *Collapsible Set*
12. *Field Container*
13. *Flip Toggle Switch*
14. *Radio Button*
15. *Check Box*
16. *Grouped Check Boxes*
17. *Select Menu*
18. *Listview*
19. *Panel*
20. *Table*
was (Author: akazakov):
1. *Page* (http://jquerymobile.com/test/docs/pages/page-anatomy.html)
!NewPage.png|thumbnail!
Result:
{code}
<div data-role="page">
<div data-role="header">
<h1>Page Title</h1>
</div><!-- /header -->
<div data-role="content">
<p>Page content goes here.</p>
</div><!-- /content -->
<div data-role="footer">
<h4>Page Footer</h4>
</div><!-- /footer -->
</div><!-- /page -->
{code}
2. *Dialog* (http://jquerymobile.com/test/docs/pages/dialog/index.html)
!NewDialog.png|thumbnail!
Result:
{code}
<a href="foo.html" data-rel="dialog" data-transition="pop" data-close-btn="none">Open dialog</a>
{code}
3. *Popup* (http://jquerymobile.com/test/docs/pages/popup/index.html)
!NewPopup.png|thumbnail!
Result:
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
4. *Header Bar* (http://jquerymobile.com/test/docs/toolbars/docs-headers.html)
!NewHeaderBar.png|thumbnail!
Result:
{code}
<div data-role="header">
<a href="index.html" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="index.html" data-icon="check" data-theme="b">Save</a>
</div>
{code}
5. *Footer Bar* (http://jquerymobile.com/test/docs/toolbars/docs-footers.html)
No wizard.
Result:
{code}
<div data-role="footer" class="ui-bar">
</div>
{code}
6. *Navbar* (http://jquerymobile.com/test/docs/toolbars/docs-navbar.html)
!NewNavbar.png|thumbnail!
<div data-role="navbar">
<ul>
<li><a href="a.html">One</a></li>
<li><a href="b.html">Two</a></li>
</ul>
</div><!-- /navbar -->
7. *Button*
8. *Grouped Buttons*
9. *Grid*
10. *Collapsible Content Block*
11. *Collapsible Set*
12. *Field Container*
13. *Flip Toggle Switch*
14. *Radio Button*
15. *Check Box*
16. *Grouped Check Boxes*
17. *Select Menu*
18. *Listview*
19. *Panel*
20. *Table*
> jQuery Mobile Widget Palette
> ----------------------------
>
> Key: JBIDE-13413
> URL: https://issues.jboss.org/browse/JBIDE-13413
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.x
>
> Attachments: NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewHeaderBar.bmml, NewHeaderBar.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png
>
>
> http://jquerymobile.com/test/
--
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, 2 months
[JBoss JIRA] (JBIDE-12403) Cannot start a server with JBT on eclipse Juno
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-12403:
------------------------------------
Release Notes Text: Servers were failing to start and error messages stated an invalid -server option was being used. This issue occurred because the -server option was mistakenly added to the program arguments when a server was starting. It is now correctly added to the JVM arguments and servers start successfully. (was: When launching a server, the -server flag was mistakenly added to program arguments rather than vm arguments. This has been fixed.
Servers were failing to start and error messages stated an invalid -server option was being used. The -server option is used to indicate that a JVM optimized for server applications should be used when a server is started. This option is automatically updated as users change their JVM and JRE choices. It was wrongly stored in the program arguments and should have been stored in the JVM arguments. )
> Cannot start a server with JBT on eclipse Juno
> ----------------------------------------------
>
> Key: JBIDE-12403
> URL: https://issues.jboss.org/browse/JBIDE-12403
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha1
> Environment: RHEL6
> java -version
> java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
> eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz
> http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
> http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
>
> To recreate:
> 1) Install eclipse Juno (eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz)
> 2) Help->Install New Software - install JBoss tools:
> http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
> http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> 3) Create a new SOA-P 5.3 server runtime
> 4) Create a new SOA-P server - accept defaults for run config:
> "-Dprogram.name=JBossTools: JBossTools: SOA-5.3" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/redhat_svn/jbds/jbosstools/esb/tests/org.jboss.tools.esb.ui.bot.test/target/requirements/jboss-soa-p-5/jboss-as/lib/endorsed"
> 5) Attempt to start the server - this error is returned:
> JBossTools: JBossTools: SOA-5.3: invalid option -- s
--
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, 2 months
[JBoss JIRA] (JBIDE-12403) Cannot start a server with JBT on eclipse Juno
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-12403:
------------------------------------
Release Notes Text:
When launching a server, the -server flag was mistakenly added to program arguments rather than vm arguments. This has been fixed.
Servers were failing to start and error messages stated an invalid -server option was being used. The -server option is used to indicate that a JVM optimized for server applications should be used when a server is started. This option is automatically updated as users change their JVM and JRE choices. It was wrongly stored in the program arguments and should have been stored in the JVM arguments.
was:When launching a server, the -server flag was mistakenly added to program arguments rather than vm arguments. This has been fixed.
> Cannot start a server with JBT on eclipse Juno
> ----------------------------------------------
>
> Key: JBIDE-12403
> URL: https://issues.jboss.org/browse/JBIDE-12403
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha1
> Environment: RHEL6
> java -version
> java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
> eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz
> http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
> http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
>
> To recreate:
> 1) Install eclipse Juno (eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz)
> 2) Help->Install New Software - install JBoss tools:
> http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
> http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> 3) Create a new SOA-P 5.3 server runtime
> 4) Create a new SOA-P server - accept defaults for run config:
> "-Dprogram.name=JBossTools: JBossTools: SOA-5.3" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/redhat_svn/jbds/jbosstools/esb/tests/org.jboss.tools.esb.ui.bot.test/target/requirements/jboss-soa-p-5/jboss-as/lib/endorsed"
> 5) Attempt to start the server - this error is returned:
> JBossTools: JBossTools: SOA-5.3: invalid option -- s
--
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, 2 months
[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2437:
----------------------------------
Release Notes Text: An issue occurred when deploying a BPEL project to a server. The project failed to deploy as a result of modifications to the getDeployableServer method, which other plug-ins were dependent on. This issue has been resolved by including both the modified and unmodified versions of the getDeployableServer method. As a result, BPEL projects will now deploy on servers. (was: A method was modified in such a way that it was source compatible, but not binary compatible, with consuming plugins who depended on said method. This has been fixed.
An issue occurred when deploying a BPEL project to a server. The project failed to deploy as a result of an error introduced when a method was modified. This issue has been resolved by reinstating the modified method. BPEL projects will now deploy on servers.)
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBDS-2437
> URL: https://issues.jboss.org/browse/JBDS-2437
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.2.GA
> Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 5.0.2.GA
>
> Attachments: deploy_error.png, jbosstools-diagnostics-20130109091445.zip
>
>
> Cannot deploy a bpel project.
--
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, 2 months
[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2437:
----------------------------------
Release Notes Text:
A method was modified in such a way that it was source compatible, but not binary compatible, with consuming plugins who depended on said method. This has been fixed.
An issue occurred when deploying a BPEL project to a server. The project failed to deploy as a result of an error introduced when a method was modified. This issue has been resolved by reinstating the modified method. BPEL projects will now deploy on servers.
was:
A method was modified in such a way that it was source compatible, but not binary compatible, with consuming plugins who depended on said method. This has been fixed.
An issue occurred when deploying a BPEL project to a server. The project
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBDS-2437
> URL: https://issues.jboss.org/browse/JBDS-2437
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.2.GA
> Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 5.0.2.GA
>
> Attachments: deploy_error.png, jbosstools-diagnostics-20130109091445.zip
>
>
> Cannot deploy a bpel project.
--
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, 2 months
[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2437:
----------------------------------
Release Notes Text:
A method was modified in such a way that it was source compatible, but not binary compatible, with consuming plugins who depended on said method. This has been fixed.
An issue occurred when deploying a BPEL project to a server. The project
was:A method was modified in such a way that it was source compatible, but not binary compatible, with consuming plugins who depended on said method. This has been fixed.
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBDS-2437
> URL: https://issues.jboss.org/browse/JBDS-2437
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.2.GA
> Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 5.0.2.GA
>
> Attachments: deploy_error.png, jbosstools-diagnostics-20130109091445.zip
>
>
> Cannot deploy a bpel project.
--
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, 2 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 Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13368:
------------------------------------
Release Notes Text: When a server is launched a JVM is selected. The first JVM matching the execution environment was selected despite a better match being available. This led to sub-optimal choices and, in some cases, the server failed to start. This has been corrected and now if a JVM is available that exactly matches the execution environment is it preferentially selected. (was: When servers are launched a JVM is selected. The first JVM matching the execution environment was selected despite a better match being available. This led to sub-optimal choices and, in some cases, the server failed to start. This has been corrected and now if a JVM is available that exactly matches the execution environment is it preferentially selected.)
> 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, 2 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 Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13368:
------------------------------------
Release Notes Text: When servers are launched a JVM is selected. The first JVM matching the execution environment was selected despite a better match being available. This led to sub-optimal choices and, in some cases, the server failed to start. This has been corrected and now if a JVM is available that exactly matches the execution environment is it preferentially selected. (was: Choosing the best matching VM to launch a server with did not give preference to exact matches of the execution environment, as it should have, and instead chose the first VM matching the execution environment. This led to sub-optimal choices. )
> 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, 2 months