Thanks a lot for these traces. Sorry, I should also have asked you to do
the same for the stop() method as well, because it is interesting to
find out why a RA stop was done in the first place. The second redeploy
[or re-activation of the resource adapter] happens _because_ of the
intermediate stop. Could you also let us know through which path the
stop method was called as well [ie add a new Throwable().printStackTrace
in stop() ...]?
Thanks
--Siva.
glassfish_at_javadesktop.org wrote:
> Hi,
>
> here are the two stack traces:
>
> [#|2007-06-26T13:20:39.704+0200|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=8295d089-439d-44b7-b33f-6dc8c8058060;|java.lang.Throwable
> at net.fsc.jca.beanconnect.ResourceAdapterJBImpl.init(ResourceAdapterJBImpl.java:417)
> at net.fsc.jca.beanconnect.ResourceAdapterJBImpl.<init>(ResourceAdapterJBImpl.java:406)
> at net.fsc.jca.beanconnect.UtmResourceAdapter.<init>(UtmResourceAdapter.java:58)
...
> at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:432)
> [b]at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:461)[/b]
> at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:496)
> at com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:564)
> at com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:50)