6:52 a.m.
Martin Malina created JBIDE-11626:
-------------------------------------
Summary: Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it starts
OK, but the state stays in Starting... until it times out and kills the process. So it
seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11626:
---------------------------------------
It seems it only applies to EAP 6 and not AS 7 it seems. But with AS 7 there is another
potential problem - when you stop the server, the server is stopped, but nothing is
displayed in the console - like the "server stopped" message.
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-11626:
--------------------------------
Priority: Critical (was: Major)
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11626.
---------------------------------
Resolution: Done
Committed to trunk. users are expected not to add [ ] but it will work even if they do.
Works for run as -> run on server, as well as for web port poller
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:18 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11626:
---------------------------------------
And "Run on server" doesn't work either - if you use internal eclipse
browser, it will just open blank page - I guess it just doesn't support IPv6 since not
even entering the address manually worked :( Not sure what we can do here.
But even if I set eclipse to use my default system browser (external), it didn't work
and displayed NPE in log:
{code}
!ENTRY org.jboss.ide.eclipse.as.ui 4 0 2012-05-28 11:15:36.294
!MESSAGE Unable to open web browser
!STACK 0
java.lang.NullPointerException
at
org.eclipse.ui.internal.browser.SystemBrowserInstance.openURL(SystemBrowserInstance.java:29)
at
org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.openBrowser(JBTWebLaunchableClient.java:165)
at
org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient$2.run(JBTWebLaunchableClient.java:65)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
{code}
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:58 p.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11626:
-------------------------------------
This is very strange. I had it work 100% fine inside eclipse browser, though it did not
work at all for my external firefox browser.
I would make a screencast for you but my main laptop is in the shop. This will naturally
make working very hard for me this week :|
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11626:
-------------------------------------
The given NPE indicates a null url... nothing at all to do with specific browser support
but rather the presence of a null URL. This seems *extremely* unlikely, as the URL is
based on what resource you select (servlet, index.html, etc) to run on the server. And in
the event the selection is the project, the url will be based on the context root if
possible. So a null url shows something is significantly wrong with your build.
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:52 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-11626:
--------------------------------
Attachment: JBIDE-11626.png
This screenshot shows I am seriously unable to replicate this. Run On Server on an
index.html seems to function fine, adn the internal eclipse browser seems to show it fine.
I am running on fedora 12, yes, a very old one, showing that the current code in trunk
seems to work fine even when running on super old OS's. (My real dev is in for repairs
so I had to set up a new one asap on this old box). I'm amazed that it works, but it
really does seem to work 100% on an old f12 system using trunk code.
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: JBIDE-11626.png
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11626:
---------------------------------------
So I had Radim Hopp try this for me on Fedora and really, "Show in browser" on
server module and "Run on server" on project works correctly. But no so on Mac
:( I guess we can't do anything here.
But what still remains a valid problem is that fact that "Show in browser" on
server (in server view) tries to open ::1:8080 - Radim could reproduce this also on Fedora
16. This generates this error:
{code}
Unable to open web browser
java.net.MalformedURLException: For input string: ":1:8080"
at java.net.URL.<init>(URL.java:601)
at java.net.URL.<init>(URL.java:464)
at java.net.URL.<init>(URL.java:413)
at
org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.openUrl(JBTWebLaunchableClient.java:150)
at
org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.checkedCreateInternalBrowser(JBTWebLaunchableClient.java:123)
at
org.jboss.ide.eclipse.as.ui.views.server.extensions.ShowInWelcomePageActionProvider$1.run(ShowInWelcomePageActionProvider.java:68)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
{code}
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Martin Malina
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: JBIDE-11626.png
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:41 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11626:
---------------------------------------
And when I change eclipse to use external browser, it opens Safari with address
http://%5b::1%5D:8080/jboss-as-helloworld/ which obviously doesn't work - it wrongly
translates the [] characters. But again, this works fine for Radim on Fedora 16 and
Firefox.
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Martin Malina
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: JBIDE-11626.png
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:52 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11626.
---------------------------------
Resolution: Done
show in web browser fixed. I was unable to replicate at first because i was right-clicking
a web project under the server. Did not realize you were right-clicking the server, not
the module.
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: JBIDE-11626.png
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-11626?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-11626.
---------------------------------
Verified on Ubuntu with jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar .
Not working entirely correctly on Mac though but the server start is recognized.
Start of AS7/EAP6 is not recognized when IPv6 local address ::1 is
used
-----------------------------------------------------------------------
Key: JBIDE-11626
URL: https://issues.jboss.org/browse/JBIDE-11626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT trunk nightly 2012-04-21
Mac OS X 10.7 Lion | Fedora 16
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: JBIDE-11626.png
When you set up JBoss AS 7.1.1 or EAP 6.0.0 ER5 to start in IPv6 mode using ::1, it
starts OK, but the state stays in Starting... until it times out and kills the process. So
it seems the mechanism used to check if the server is started doesn't work when using
IPv6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5055
days inactive
5099
days old
jbosstools-issues@lists.jboss.org
11 comments
2 participants
participants (2)
-
Martin Malina (JIRA) -
Rob Stryker (JIRA)