[
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