JBoss7.1.1Final thread leak issue

[thinksteep]

Hi Community,

I am having similiar issue described in following JIRA

https://issues.jboss.org/browse/REMJMX-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

I have standalone client on machineA which establishes connection with JBossAS7.1.1Final on machineB. Client on machineA is threaded program.

When client is done with the call, threads are not clearing up.  Every call I am seeing thread count increased in JConsole and respective threads are Remoting "endpoint" read-1 and Remoting "endpoint" write-1.

I looked jboss-client.jar but there is no way to findout which "remoting-jmx" version this jar has. Entries I am seeing in jboss-client.jar README.txt are:

org.jboss.spec.javax.jms:jboss-jms-api_1.1_spec

org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec

org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec

org.jboss:jboss-remote-naming

org.jboss.logging:jboss-logging

org.jboss.marshalling:jboss-marshalling

org.jboss.marshalling:jboss-marshalling-river

org.jboss.remoting3:jboss-remoting

org.jboss.remoting3:remoting-jmx

org.jboss.sasl:jboss-sasl

org.jboss.xnio:xnio-api

org.jboss.xnio:xnio-nio

org.jboss.netty:netty

org.hornetq:hornetq-core-client

org.hornetq:hornetq-jms-client

Could someone please help in getting jboss-client.jar with fix for above JIRA?

Thank you for your time and help.

[wdfink]

The jboss-client.jar is a cumulated lib where all necessary classes for a client are collected from the different sub-modules.

Looks like that the packaging has changed with 7.2/EAP6.1.

I recommend to use the latest version EAP6.1 Alpha or Beta.

Also you can build from git or use a nightly build.

Another option is to compile the remoting project and replace the classes in the jboss-client.jar, but I think this will have compatibility issues as there is a long time between that versions.

[thinksteep]

Hi Wolf-Dieter Fink and community,

It seems EAP 6.1 jboss-client.jar fixed this issue but HornetQ calls are failing because of incompatability (I guess). I am getting same exception as specified in following JIRA.

Here is relevant JIRA:

https://issues.jboss.org/browse/HORNETQ-1148

Any input on how this can be fixed with Jboss 7.1.1Final?

Thank you for your time and help.

[jbertram]

I'm not sure I understand what you're doing here.  Did you take the jboss-client.jar from Red Hat JBoss EAP 6.1 and use it from a client which is connecting to JBoss AS 7.1.1?

[thinksteep]

Hi Justin,

Yes that is correct. I did this to avoid thread leaks (which is fixed), but I am getting HORNETQ exceptions when I try to connect to JMS.

Please let me know if more information required.

Thank for your time and help.

[jbertram]

The HornetQ client libraries in the jboss-client.jar from Red Hat JBoss EAP 6.1 are for HornetQ version 2.3.x.  They won't work with the version of HornetQ shipped in JBoss AS 7.1.1. 

[thinksteep]

Thanks Justin! That is what I have figured out so far.

Is there any way I can get jboss-client.jar for JBoss7.1.1Final with following JIRA fix?

https://issues.jboss.org/browse/REMJMX-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

At this moment we are not in a position to do JBoss upgrades. That is why I am trying to limit required changes.

Any input would be really appreciated.

Thank you for your time and help.