carodriguez18 / jca-sockets

Automatically exported from code.google.com/p/jca-sockets
0 stars 0 forks source link

MDB Redeploy fails on Geronimo #15

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Redeploy of a jca-sockets driven MDB fails on Geronimo, the RA complains:  A 
socket activation spec already exists with the same port

On redeploy Geronimo calls
org.apache.openejb.core.mdb.MdbContainer.createActivationSpec(DeploymentInfo)
which goes into
com.googlecode.jcasockets.SocketResourceAdapter.endpointActivation(MessageEndpoi
ntFactory, ActivationSpec)
and the Exception happens in 
com.googlecode.jcasockets.SocketResourceAdapter.addToKnownListeners(SocketActiva
tionSpec, SocketListener)

Probably the RA should find out if this is a redeploy and then stop and restart 
the sockets.

A redeploy operation happens quite often during development, so you have to 
change the port on each redeploy to get around this bug.

Original issue reported on code.google.com by webe...@gmail.com on 22 Jun 2010 at 8:55

GoogleCodeExporter commented 9 years ago
The exact same thing happens on Glassfish v2.

Original comment by suhai.ga...@gmail.com on 12 Apr 2011 at 11:37

GoogleCodeExporter commented 9 years ago
I suggested a patch to resolve this issue.

Original comment by suhai.ga...@gmail.com on 12 Apr 2011 at 12:47

GoogleCodeExporter commented 9 years ago
am definitely seeing this too, where's the patch?

Original comment by jweissma...@gmail.com on 21 Jun 2011 at 2:43

GoogleCodeExporter commented 9 years ago
http://code.google.com/p/jca-sockets/issues/detail?id=17

Original comment by suhai.ga...@gmail.com on 21 Jun 2011 at 2:45