[
https://jira.jboss.org/jira/browse/JBAS-7701?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-7701:
------------------------------------
I think I misinterpreted this. I think it actually JBoss Remoting that's throwing the
InterruptedException, because another thread in my application (a thread that was told to
timeout the thread in question after 30 seconds) had sent an interrupt to the thread. So
disregard this :-)
ProfileService - ManagementView.load() throws mysterious
InterruptedException when called by remote client
----------------------------------------------------------------------------------------------------------
Key: JBAS-7701
URL:
https://jira.jboss.org/jira/browse/JBAS-7701
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-6.0.0.M1
Reporter: Ian Springer
Assignee: Emanuel Muckenhuber
Priority: Critical
I've seen this several times today. When the jboss-as-5 plugin tried to connect to a
remote AS 6.0.0.M1 instance, the remote call to ManagementView.load() sometimes throws an
InterruptedException. Here's the stack trace:
java.lang.RuntimeException: java.lang.InterruptedException
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:823)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167)
at org.jboss.remoting.Client.invoke(Client.java:1917)
at org.jboss.remoting.Client.invoke(Client.java:768)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$1.load(AOPProxy$1.java)
The AS6 server is running find with no issues. This is pretty serious from the RHQ/Jopr
perspective, because it results in the AS6 instance to be incorrectly reported as being
down.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira