Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 2.0.0.Beta1, 1.0.17.Final
Affects Version/s: 1.0.15.Final
Labels:
None

Steps to Reproduce:

Hide

Get the JNDI environment hashtable (env) with all properties for the current JBossAS 7 cluster
ctx = new InitialContext(env);
beanProxy = ctx.lookup("ejb:...");

For each call to ctx.lookup(...) a new EjbNamingContext with its own connections and registry to the JBoss cluster is generated. A call to netstat shows a growing number of established connections.

Show
Get the JNDI environment hashtable (env) with all properties for the current JBossAS 7 cluster ctx = new InitialContext(env); beanProxy = ctx.lookup("ejb:..."); For each call to ctx.lookup(...) a new EjbNamingContext with its own connections and registry to the JBoss cluster is generated. A call to netstat shows a growing number of established connections.
Forum Reference:
https://community.jboss.org/message/787547, https://community.jboss.org/message/764451#764451
Git Pull Request:
https://github.com/jbossas/jboss-ejb-client/pull/33, https://github.com/jbossas/jboss-ejb-client/pull/34

Description

When I create an InitialContext with the description of https://community.jboss.org/message/764451#764451 and even when I reuse the InitialContext instance a new EjbNamingContext is created and regsistered for each lookup.

I'm not a committer, so I add possible workarounds here:

Make a lookup to "ejb:" and use the resulting EjbNamingContext instance instead of InitialContext. But this may be broken because you don't get to know when its closed.

Call ejbURLContextFactory.getObjectInstance directly, but this cuts off all JNDI handling by the JDK.

Attachments

Activity

People

Assignee:: Jaikiran Pai (Inactive)

Reporter:: Bernd Köcke (Inactive)

Votes:: 1 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2013/01/04 4:58 AM

Updated:: 2013/03/14 9:15 AM

Resolved:: 2013/03/11 5:29 AM