[JBoss JIRA] (JBIDE-18253) Error when starting a remote EAP 6.3 server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18253?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18253:
------------------------------------------
I see this in a slightly different way:
I get an error dialog while the console shows the error started:
!server-failed-started.png!
> Error when starting a remote EAP 6.3 server
> -------------------------------------------
>
> Key: JBIDE-18253
> URL: https://issues.jboss.org/browse/JBIDE-18253
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
> Attachments: remote-server.png, server-failed-started.png
>
>
> When I start a remote EAP 6.3 server, I get an error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-09-04 09:30:35.102
> !MESSAGE Server JBoss EAP 6.3 marvin failed to start.
> {code}
> A window pops up as well:
> !remote-server.png!
> The funny thing is that the server actually starts and is working, but is shown as stopped in the Server view.
> I have a suspicion that this has something to do with JBIDE-16898
> The worst thing is that you have no way of stopping the server process from the IDE - you have to manually kill it on the machine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18253) Error when starting a remote EAP 6.3 server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18253?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18253:
-------------------------------------
Attachment: server-failed-started.png
> Error when starting a remote EAP 6.3 server
> -------------------------------------------
>
> Key: JBIDE-18253
> URL: https://issues.jboss.org/browse/JBIDE-18253
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
> Attachments: remote-server.png, server-failed-started.png
>
>
> When I start a remote EAP 6.3 server, I get an error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-09-04 09:30:35.102
> !MESSAGE Server JBoss EAP 6.3 marvin failed to start.
> {code}
> A window pops up as well:
> !remote-server.png!
> The funny thing is that the server actually starts and is working, but is shown as stopped in the Server view.
> I have a suspicion that this has something to do with JBIDE-16898
> The worst thing is that you have no way of stopping the server process from the IDE - you have to manually kill it on the machine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18083:
----------------------------------
Fix Version/s: 4.2.0.CR2
> Issues in the new "Edit server runtime environment" window
> ----------------------------------------------------------
>
> Key: JBIDE-18083
> URL: https://issues.jboss.org/browse/JBIDE-18083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7x6, Eclipse 64 bit version, java 1.7
> Reporter: Wolfgang Knauf
> Assignee: Daniel Azarov
> Priority: Minor
> Fix For: 4.2.0.CR2
>
> Attachments: server_runtime.png
>
>
> See attached screenshot: there are three problems in the "Edit Server runtime environment" window.
> a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused
> b) same for the button "Installed JREs"
> c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18083:
---------------------------------------
[~dazarov] could you check it under windows?
> Issues in the new "Edit server runtime environment" window
> ----------------------------------------------------------
>
> Key: JBIDE-18083
> URL: https://issues.jboss.org/browse/JBIDE-18083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7x6, Eclipse 64 bit version, java 1.7
> Reporter: Wolfgang Knauf
> Assignee: Daniel Azarov
> Priority: Minor
> Fix For: 4.2.0.CR2
>
> Attachments: server_runtime.png
>
>
> See attached screenshot: there are three problems in the "Edit Server runtime environment" window.
> a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused
> b) same for the button "Installed JREs"
> c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18083:
----------------------------------
Assignee: Daniel Azarov
> Issues in the new "Edit server runtime environment" window
> ----------------------------------------------------------
>
> Key: JBIDE-18083
> URL: https://issues.jboss.org/browse/JBIDE-18083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7x6, Eclipse 64 bit version, java 1.7
> Reporter: Wolfgang Knauf
> Assignee: Daniel Azarov
> Priority: Minor
> Attachments: server_runtime.png
>
>
> See attached screenshot: there are three problems in the "Edit Server runtime environment" window.
> a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused
> b) same for the button "Installed JREs"
> c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18267) Errors when starting EAP 5.2 - problem with jmx agent
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18267?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-18267:
----------------------------------
Labels: respin-b (was: respin-a)
> Errors when starting EAP 5.2 - problem with jmx agent
> -----------------------------------------------------
>
> Key: JBIDE-18267
> URL: https://issues.jboss.org/browse/JBIDE-18267
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
>
> When I add EAP 5.2 using runtime detection and then start the server, I get errors in the console:
> {code}
> 15:07:25,729 INFO [JMXKernel] Legacy JMX core initialized
> javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:481)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:512)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:299)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:214)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:175)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:458)
> at sun.management.Agent.startAgent(Agent.java:135)
> at sun.management.Agent.agentmain(Agent.java:95)
> 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 sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:325)
> at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348)
> Caused by: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:424)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:466)
> ... 15 more
> Exception thrown by the agent : javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> Exception in thread "Attach Listener" java.lang.reflect.InvocationTargetException
> 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 sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:325)
> at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348)
> Caused by: java.lang.RuntimeException: javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at sun.management.Agent.error(Agent.java:309)
> at sun.management.Agent.startAgent(Agent.java:153)
> at sun.management.Agent.agentmain(Agent.java:95)
> ... 6 more
> Caused by: javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:481)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:512)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:299)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:214)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:175)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:458)
> at sun.management.Agent.startAgent(Agent.java:135)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:424)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:466)
> ... 15 more
> Agent failed to start!
> {code}
> It's kind of strange, but it didn't happen at first. When I changed the server to compressed deployment, it started happening. So I wanted to check again in a new workspace. In the new workspace, I just added the server and start (with default - exploded wars) and it happened again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months