[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13768:
--------------------------------
Workaround Description: If using a Java 6 for installer and IDE launch - also use Java 6 for launching the app server - then all is well.
Workaround: Workaround Exists
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: Error_Failed_to_start.png, failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13768:
--------------------------------
Attachment: Error_Failed_to_start.png
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: Error_Failed_to_start.png, failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-13768:
-------------------------------------
The following is the interesting bits from About - Installation Details - Configuration:
*** Date: Monday, March 11, 2013 at 4:05:01 PM Eastern Daylight Time
*** Platform Details:
*** System properties:
J2EEcache=
applicationXMI=org.eclipse.ui.workbench/LegacyIDE.e4xmi
awt.nativeDoubleBuffering=true
awt.toolkit=apple.awt.CToolkit
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.commands=-os
macosx
-ws
cocoa
-arch
x86_64
-showsplash
-launcher
/Users/burr/gettingstarted/jbds7alpha1c_with_EAP_Java6/studio/JBoss Developer Studio.app/Contents/MacOS/jbdevstudio
-name
Jbdevstudio
--launcher.library
/Users/burr/gettingstarted/jbds7alpha1c_with_EAP_Java6/studio/JBoss Developer Studio.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130117-173747/eclipse_1503.so
-startup
/Users/burr/gettingstarted/jbds7alpha1c_with_EAP_Java6/studio/JBoss Developer Studio.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130125-144918.jar
--launcher.overrideVmargs
-product
com.jboss.jbds.product.product
-keyring
/Users/burr/.eclipse_keyring
-consoleLog
-showlocation
-vm
/System/Library/Frameworks/JavaVM.framework
eclipse.consoleLog=true
eclipse.home.location=file:/Users/burr/gettingstarted/jbds7alpha1c_with_EAP_Java6/studio/
eclipse.launcher=/Users/burr/gettingstarted/jbds7alpha1c_with_EAP_Java6/studio/JBoss Developer Studio.app/Contents/MacOS/jbdevstudio
eclipse.launcher.name=Jbdevstudio
eclipse.p2.data.area=@config.dir/../p2/
eclipse.p2.profile=jbds
eclipse.product=com.jboss.jbds.product.product
eclipse.startTime=1363031806073
eclipse.vm=/System/Library/Frameworks/JavaVM.framework
eclipse.vmargs=-Djboss.discovery.directory.url=https://devstudio.jboss.co...
-Xms512m
-Xmx1024m
-Dosgi.instance.area.default=(a)user.home/workspace
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Xdock:icon=../Resources/JBDevStudio.icns
-XX:MaxPermSize=256m
-Djava.class.path=/Users/burr/gettingstarted/jbds7alpha1c_with_EAP_Java6/studio/JBoss Developer Studio.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130125-144918.jar
equinox.use.ds=true
file.encoding=MacRoman
file.encoding.pkg=sun.io
file.separator=/
ftp.nonProxyHosts=local|*.local|169.254/16|*.169.254/16
gopherProxySet=false
gosh.args=--nointeractive
java.awt.graphicsenv=apple.awt.CGraphicsEnvironment
java.awt.printerjob=apple.awt.CPrinterJob
java.class.path=/Users/burr/gettingstarted/jbds7alpha1c_with_EAP_Java6/studio/JBoss Developer Studio.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130125-144918.jar
java.class.version=50.0
java.endorsed.dirs=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/endorsed
java.ext.dirs=/Library/Java/Extensions:/System/Library/Java/Extensions:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/ext
java.home=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
java.io.tmpdir=/var/folders/st/1b3cldjx29l46j86zsf55p700000gp/T/
java.library.path=.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
java.rmi.server.randomIDs=true
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.6.0_43-b01-447-11M4203
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.6
java.vendor=Apple Inc.
java.vendor.url=http://www.apple.com/
java.vendor.url.bug=http://bugreport.apple.com/
java.version=1.6.0_43
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Apple Inc.
java.vm.version=20.14-b01-447
jboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-dev...
line.separator=
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13768:
--------------------------------
Description:
My Mac has both the Apple Java 6 and Oracle Java 7 installed.
If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
Installation1.png - a screenshot of the defaults selected by the installer.
This places the following in my jbdevstudio.ini
-vm
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
and in About - Installation Details - Configuration:
-vm
/System/Library/Frameworks/JavaVM.framework
Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
The result is a failed start (failed_start.png)
was:
My Mac has both the Apple Java 6 and Oracle Java 7 installed.
If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
Installation1.png - a screenshot of the defaults selected by the installer.
This places the following in my jbdevstudio.ini
-vm
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
and in About - Installation Details - Configuration:
-vm
/System/Library/Frameworks/JavaVM.framework
Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13768:
--------------------------------
Attachment: failed_start.png
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13768:
--------------------------------
Attachment: server_state_detectors.png
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13768:
--------------------------------
Description:
My Mac has both the Apple Java 6 and Oracle Java 7 installed.
If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
Installation1.png - a screenshot of the defaults selected by the installer.
This places the following in my jbdevstudio.ini
-vm
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
and in About - Installation Details - Configuration:
-vm
/System/Library/Frameworks/JavaVM.framework
Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
was:
My Mac has both the Apple Java 6 and Oracle Java 7 installed.
If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
Installation1.png - a screenshot of the defaults selected by the installer.
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: Installation1.png, runtime_JDK_7_selection.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13768:
--------------------------------
Attachment: runtime_JDK_7_selection.png
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Burr Sutter
> Attachments: Installation1.png, runtime_JDK_7_selection.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
--
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, 1 month
[JBoss JIRA] (JBIDE-13763) openshift-java-client: exception does not say to what server it was trying to connect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13763?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13763:
------------------------------------------
pushed to master and rebased.
verified on jenkins which now reports:
{code}
com.openshift.client.OpenShiftEndpointException: Could not request https://stg.openshift.redhat.com/broker/rest/api: java.net.ConnectException: Connection timed out
at com.openshift.internal.client.RestService.request(RestService.java:106)
at com.openshift.internal.client.RestService.request(RestService.java:91)
at com.openshift.internal.client.RestService.request(RestService.java:72)
at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:161)
{code}
> openshift-java-client: exception does not say to what server it was trying to connect
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-13763
> URL: https://issues.jboss.org/browse/JBIDE-13763
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> Most exceptions that occur while talking to OpenShift are not telling you to what server the client was talking to. They mostly simply repeat the path:
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.ConnectException: Connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:103)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:72)
> at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:161)
> at com.openshift.client.utils.TestConnectionFactory.getConnection(TestConnectionFactory.java:31)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.setUp(ApplicationResourceIntegrationTest.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiv
> {code}
--
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, 1 month