[openjms-developer] [ openjms-Bugs-921517 ] TCP JNDI IntialContext using static variables for obj. scope

[SourceForge.net]

Bugs item #921517, was opened at 2004-03-23 13:51
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=921517&group_id=54559

Category: jndi
Group: v0.7.6

Status: Closed
Resolution: Fixed

Priority: 5
Submitted By: C. Paris (curtis-paris)

Assigned to: Tim Anderson (tanderson)

Summary: TCP JNDI IntialContext using static variables for obj. scope

Initial Comment:
org.exolab.jms.jndi.mipc.IpcJndiInitialContextFactory has
references for the _host and _port for connecting as
static variables.

If you have multiple tcp connections occuring at once
(redundancy, briding, etc), it is possible for the TCP
(Ipc) factory to connect to the same server for all
connections, depending on thread timings.

Observed behavor includes returning connections to
servers you know are down, or connecting to the wrong
server.

The static conditions are not needed and compiles fine
with them as non-static. With them static you have to
insure that only one OpenJMS connection is being
created via TCP at a time.





----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)

Date: 2004-05-01 16:11

Message:
Logged In: YES
user_id=557161

Patch applied thanks. Fix will be available in the 0.7.6.1
release.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=921517&group_id=54559