2:27 p.m.
Jesper Skov created JBIDE-11215:
-----------------------------------
Summary: JbossTools 3.3.0M5 fail deployment after some time
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown
Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:15 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
what kind of errors are you seeing on the server side ? (if any?)
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Fix For: 3.3.0.Beta2
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:15 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11215:
----------------------------------------
Fix Version/s: 3.3.0.Beta2
Priority: Critical (was: Major)
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta2
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:25 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
We do see something in the logs, but have none at hand. Will provide output tomorrow after
next failure.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta2
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:08 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov updated JBIDE-11215:
--------------------------------
Attachment: eclipseproblem.zip
Eclipse workspace log
EAP server + bootstrap logs
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta2
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:02 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
The problem also applies to Beta2 (as expected).
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta3
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
We're a tiny bit sharper on the problem now:
The problem does _not_ appear with Eclipse 3.7sr1 + JbossTools M4.
The problem does appear with Eclipse 3.7sr2 + JBossTools M4 (and M5+Beta2).
So it may be due to changes in Eclipse 3.7sr2 rather than JBossTools itself.
The symptom remains the same. Don't know if that tells you anything.
I hope to get the developers to try out JBossTools Beta2 on JunoM6 next week. It may
provide another datapoint (or a fix).
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta3
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:10 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11215:
----------------------------------------
Priority: Blocker (was: Critical)
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
Thanks for letting us know Jesper - we haven't been able to reproduce it yet so will
have to push this out after B3 but rasising to blocker since we must look at it to at
least find explanation. B2/B3 unfortunately requires sr2.
if you find out more due let us know.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.Beta3
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:51 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11215:
-------------------------------------
The AS client jars were changed on march 8th.
https://source.jboss.org/browse/JBossTools/trunk/as/plugins/org.jboss.ide...
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.Beta3
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:54 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
Rob, what does AS 7.1 client jar updates have to have with EAP 5.1 ?
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.Beta3
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:54 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
Rob, what does AS 7.1 client jar updates have to have with EAP 5.1 ?
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.Beta3
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
9:34 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11215:
-------------------------------------
Sorry... I must have posted that to the wrong jira. cough.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:17 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
Jesper - in your testing of SR1 and SR2 are you saying that with SR1 you do not get
authentication errors, but with SR2 you do ?
Or are you just seeing sudden stop of deployments ?
Does the files actually changes ?
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:19 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
btw. are you sure its eclipse that is the differentiator ? how about the actual runtime
(EAP5?) does it start working again if you stop/start EAP5 ?
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:19 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11215:
----------------------------------------
Fix Version/s: 3.3.x
(was: 3.3.0.CR1)
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
need to push of 3.3.0 for now - can't reproduce/not enough info yet.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:30 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
Yes, we're sure it's eclipse. Both runtime and workspace is unchanged.
Only happens with SR2.
Restarting the server has no effect when the problem occurs. Need to restart Eclipse.
I'll retest JunoM7 and your Beta3 after next week and let you know what I find.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
8:49 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
Jesper - sent you a direct email to try drill down some more on this.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:39 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
I've spent some more time on this - doing it myself, instead of just passing
information along from others :)
We can talk next week, if you would still like it. I'm running against the clock right
now.
What I've found to be a dead-certain way of reproducing the problem is this:
* Clean JBoss installation, Clean workspace, Eclipse 3.7sr2 + JBossTools
2.3.0.v20111104-1515-H45-M4
* Create our default template project.
* Create new Server instance.
* Deploy application. I can now make Full Publish ad nauseum - it'll probably hit the
problem eventually as my developers have experienced.
* Change the Server Deployment to use JBoss deploy folder. (remove app, change+restart,
add app)
* I start seeing the errors in the log, but Full Publish continues to work as far as I can
tell.
* Change the Server Deployment to use Workspace metadata again (remove app,
change+restart, add app)
* Now Full Publish does nothing.
Obviously, not the convoluted steps my developers use. They just wait for it to happen.
I just accidentally found these steps when trying to understand the problem - and how to
possibly work around it.
Can't guarantee it is the same problem, but the symptom (log output) appears to be the
same.
I can try with a newer JBoss Tools plugin next week if you would prefer it.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
9:33 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
I don't think you reproducing the error that is seen, if you are then this here is a
much simpler issue than a "nothing changes, eventually it stops publishing". At
least simpler to explain.
In your description you are going from workspace deployment, to in server deployment and
then back to workspace deployment.
That's a lot of change compared to not doing anything.
You now say "Full publish does nothing" - what does this mean exactly ?
Does the files actually get copied to the workspace location you enabled ?
If not, any chance that the deployments in the jboss deploy folder is being updated ?
And are they already there actually creating duplicate deployments of the same thing and
thus might
confuse the server (or tools, which would be a bug) ?
And could you check that if you actually *change* the username/password to something else
than admin that it still is happening ? i.e. change it to username "wonka"
password "bear". ?
hmm - actually I think that might be the bug .... somehow when username/password is not
changed (i.e. just kept at "admin") that is seen as the "default" and
thus not actually listened too AND between SR1 and SR2 they did actually change some
behavior that affects the saving/handling of these values in the server editor.
So yes, please let me know if it changes anything if you change the username/password on
the server in the jmx console properties file AND set it in the UI.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
I know this is more than "nothing". It is what I found would reproduce the
problem without spending half a day of EE development. Because that doesn't happen at
my dest - not with this setup anyway (the tooling infrastructure runs on JBoss7, and
I've never seen the problem there).
I'll look for what happens to the files in the target deploy folder after the switch
and let you know.
I'll also ask one of the developers to try switching passwords. May not be possible
this week. They've grown weary of this problem...
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
9:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
Make of this what you want.
When I reproduce the problem following the recipe above, things stay broken.
If I reinstall JBoss and make a clean workspace, the deployment is still hosed.
I found that if I reinstall eclipse, it gets fixed.
In particular, after the breakage, I find the folder server/jb/tmp/jbosstoolsTemp in my
eclipse installation folder.
That path matches the server configuration we use (jb). If I stop eclipse, delete the
folder, reinstall JBoss, and start eclipse again, deployment starts working again.
On my box, changed classes kept getting updated in the deploy folder even though Full
Publish had no effect.
I'm waiting for a developer to hit the problem again, to verify my findings against
the "naturally occuring" problem.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
12:10 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
The developer tried changing the JMX credentials in both server and in the Eclipse JMX
Login Credentials.
The result was immediately the error:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
{code}
He changed the JBoss login-config.xml setup like the below to work around it (adding the
unauthenticatedIdentity line):
{code}
<application-policy name="jmx-console">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
flag="required">
<module-option
name="unauthenticatedIdentity">fsadmin</module-option>
<module-option
name="usersProperties">props/jmx-console-users.properties</module-option>
<module-option
name="rolesProperties">props/jmx-console-roles.properties</module-option>
</login-module>
</authentication>
</application-policy>
{code}
Don't know if this will fix the problem of deployments failing after some time. Will
return with more data later.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:48 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
Until now, the workaround prevents the problem. So we can push some more developers onto
the new eclipse+jbosstools.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11215:
----------------------------------------
Fix Version/s: 3.3.0.CR1
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
I'm 99% convinced this is a problem of username or password being somehow set to null
;(
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11215:
----------------------------------------
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:10 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
Jesper, you use "fsadmin" on the login-config.xml I assume you then are setting
username on eclipse side to 'fsadmin' too ?
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
Yes, fsadmin in both places.
The other developers use the default admin/admin - no changes in the Eclipse Server Setup.
They just the unauthenticatedIdentity tweak on the server.
Still no reported problems.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
12:41 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
sorry for being terse here but just to verify, the devs using admin/admin in eclipse
server setup adds this to the login-config.xml:
<module-option
name="unauthenticatedIdentity">admin</module-option>
right ? i.e. enable admin to be always logged in independent of password?
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
12:43 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
Yep, that's it.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
12:51 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
Thanks Jesper - and you haven't found that its only triggered when editing or
non-editing the username/password in the server editor ?
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:01 p.m.
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
We've never changed the credentials in the server editor before you suggested it.
When the fail happens (for the developers), it is not related to editing in the server
editor. Just happens after some time of development and deployments.
JbossTools 3.3.0M5 fail deployment after some time
--------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:03 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-11215:
--------------------------------
Summary: JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time (was:
JbossTools 3.3.0M5 fail deployment after some time)
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
9:14 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11215:
-------------------------------------
Hey Jesper:
The concern right now is that somehow perhaps the credentials in teh editor are getting
wiped but you're not seeing it due to default values. So next time it happens, I
request you immediately go reset the values in the editor and try to do it again.
If re-setting the values in the editor doesn't fix it, then that means it is likely
some type of server error as opposed to us accidentally passing a null username.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
9:20 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
We'll give it a shot. It'll be on JunoM7 though...
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
9:38 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
Fails pretty much immediately on JunoM7 (with JBossTools Beta3).
Re-entering the credentials didn't make a change; same error in log when trying to
make a full publish.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
Jesper, I tried following your steps, but couldn't reproduce the problem. Even after
switching back to workspace metadata deployment, I can use Full publish again and again
and it redeploys the app every time. I used a simple dynamic web project. I tried this in
the latest JBoss Tools 3.3.0.CR1
(jbosstools-3.3_stable_branch.aggregate-Update-2012-06-04_21-27-23-H174.zip). I didn't
do anything about login details in Eclipse. The only thing I did was enable the admin user
in jboss-eap-5.1.1/jboss-as/server/default/conf/props/jmx-console-users.properties.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:19 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11215:
----------------------------------------
Fix Version/s: 3.3.1
3.4.x
(was: 3.3.x)
(was: 3.3.0.CR1)
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
moving off as blocking since we cannot reproduce/find cause yet.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
6:06 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Vlado Pakan commented on JBIDE-11215:
-------------------------------------
I cannot replicate this issue on Linux 32bit with JBDS CR1a
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
6:54 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-11215:
-------------------------------------
Well, annoying as it is, it is also somewhat comforting that you cannot reproduce :)
We've talked about XP being the root cause, since we appear to be the only ones with
the problem. And we cannot think of others than banks that would run such an obsoleted OS
;)
But I guess there could be a thousand other reasons...
If nothing else, we'll know more when we move off XP in 2-3 months.
And we have a workaround, so we're happy for now.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:25 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
Thanks for update Jesper and happy you got a workaround.
I will though like to find the root cause, even if it is XP since even though that is
obsolete its user base is still significant (more than Linux+OSX combined :)
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:04 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
I just tried to reproduce it on Windows XP and still no "luck".
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:14 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
Huh! After trying to reproduce it (XP running in VirtualBox) I left it running. And now I
tried to remove the app (dynamic web project) and nothing happens! From this point no
change deployment is registered - I tried adding it again and doing Full Publish and still
nothing happens.
To be honest now I remember that something like that happened to me in the past but I
never figured out why or how to reproduce.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:22 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
At that time I even reported it but nobody could reproduce it: JBIDE-9994
Note that when this happens in my opinion the tooling is doing everything right - it makes
the changes to the deploy directory - what else should it do? But the server somehow
doesn't pick it up.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:08 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11215:
---------------------------------------------
okey so here is how the tools work (in simplified form):
1) User changes files.
2) Server adapter tells server to stop scanning for changes in the directory we are
copying to.
3) Server adapter copies files.
4) Server adapter tells server to start scanning for changes in the directory we are
copying to
5) Server eventually sees the changes and redeploys/picksup the changes (depends on the
kind of content, but thats unrelated to this I believe)
If #2 or #4 errors the server adapter does not stop since servers can be deploying just
fine without admin access if user already configured it to be picking up changes.
My theory is that either:
A) the server eventually gets confused and just fails (no idea why/how :)
OR
B) #2 completes, but #4 fails....
or both A+B since A causes B.
To figure out where the fail is:
Check server log - any errors/warnings that relate to scanning or jmx or login errors ?
Check eclipse log - anything ?
Go to JMX console and look for HDScanner I believe to see if it is enabled and what
directories it is scanning.
Then that should give a clue.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:40 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
Thanks, Max. I didn't know it was so sophisticated. AFAIR there wasn't anything in
the server log nor workspace log. But checking the scanner in jmx console might give us
the answer. I will try it now.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:24 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
Unfortunately I can't hit the problem now - I tried doing things similarly and leaving
the server intact for some time, but it still works. I will try again later.
And when I succeed I will try to check if the deploy scanner is working or not. But my
guess is that it will be stopped.
To check if the problem is really the deployment scanner being disabled one can do one of
these (once you hit the problem):
a) In JMX console or MBean Explorer, go to jboss.deployment->URL->DeploymentScanner
and use the start() operation to start the scanner again - if it was really disabled, this
will enable it and you should see the deployment in the server log
b) Check the HDScanner thread - jboss.system->ServerInfo, operation listThreadDump() -
search for HDScanner. If it's enabled, it will be in state TIMED_WAITING. If it is
disabled, it will be in state WAITING.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:14 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
So... I was finally able to hit the issue again. After many attempts. And I have now the
server running on Win XP in virtual box. The server stopped responding to any
deployments.
But the HDScanner seems to be running - it is in state TIMED_WAITING.
Rob, what now? :) I will save the state of the VM, so hopefully I will preserve this
behavior and can investigate more later.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.1, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
9:01 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
8:43 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
10:48 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-11215:
--------------------------------
Fix Version/s: 3.3.2
(was: 3.3.1)
Forum Reference: https://community.jboss.org/message/722437#722437 (was:
https://community.jboss.org/message/722437#722437)
push
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.2, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
11:17 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11215:
-------------------------------------
I would argue this sounds like a server issue, but I have no idea what exactly can be
causing it. I feel I hit this once or twice in the past but never figured it out. Your
results are exactly as I expected and as I remember my experience. Even re-starting the
deployment scanner, even stopping it and starting it again, did not work.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.2, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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
12:09 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen reassigned JBIDE-11215:
-------------------------------------------
Assignee: Len DiMaggio (was: Rob Stryker)
Len - we can't find a way to reliably reproduce this but the issue is annoying enough
to not just drop as non-reproducable when both user and QE (mmalina) have been able to
reproduce.
Any chance we could get JBDS-QE reproduce this and have EAP-QE guys help on tracking down
if/where the bug is in the app server ?
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Len DiMaggio
Priority: Blocker
Fix For: 3.3.2, 3.4.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{code}
--
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:24 a.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11215:
---------------------------------------
Len, I saw these tests, but apparently they cannot reproduce this issue unfortunately :(
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Len DiMaggio
Priority: Blocker
Fix For: 3.3.2, 4.0.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{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
3:07 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11215:
-------------------------------------
We suspect this is directly related to the following:
https://issues.jboss.org/browse/JBIDE-12643
https://issues.jboss.org/browse/JBPAPP-9973
These issues have no error such as security authentication failing, but they do very
clearly reproduce the issue of deployment no longer working.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Len DiMaggio
Priority: Blocker
Fix For: 3.3.2, 4.0.x
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{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
2:39 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina resolved JBIDE-11215.
-----------------------------------
Release Notes Text:
JBPAPP-9973 is fixed and I verified it with JBT 4.0.0.Beta2 and EAP 5.2.0.ER4.
I opened a related issue JBIDE-13013. But it may not really be a bug.
Fix Version/s: 4.0.0.Beta2
(was: 4.0.x)
Resolution: Done
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Len DiMaggio
Priority: Blocker
Fix For: 3.3.2, 4.0.0.Beta2
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{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
2:39 p.m.
New subject: [JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
[
https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-11215.
---------------------------------
Verified.
JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
--------------------------------------------------------------
Key: JBIDE-11215
URL: https://issues.jboss.org/browse/JBIDE-11215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Windows XP, Eclipse 3.7.sr2
Reporter: Jesper Skov
Assignee: Len DiMaggio
Priority: Blocker
Fix For: 3.3.2, 4.0.0.Beta2
Attachments: eclipseproblem.zip
JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many
successful deployments).
Similar behavior from the nightly build 2012.02.27.
M4 is working without problems, and this is the version we revert to when restarts of
Eclipse with M5 gets too tedious.
The Eclipse log shows JMX console login problems as the (propable) cause, see below.
We use admin/admin credentials for the JMX console, and don't change these during the
day.
Hard to reproduce, but (obviously) we are willing and happy to test any build you might
feel should fix this. We don't want to get stranded at M4 :)
(I will attach a snapshot of the server configuration page when I get a chance.)
Let me know if there is any logging we can tweak to help you find and fix the cause of
this.
Log output from the 2012.02.27 nightly build:
{code}
java.lang.SecurityException: Failed to authenticate principal=null,
securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown
Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
at $Proxy30.invoke(Unknown Source)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
at
org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
at
org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
at
org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
at
org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at
org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
at
org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
at
org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
at
org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
at
org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
{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
4252
days inactive
4497
days old
jbosstools-issues@lists.jboss.org
56 comments
5 participants
participants (5)
-
Jesper Skov (JIRA) -
Martin Malina (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)
-
Vlado Pakan (JIRA)