Re: J2C - Connection to EIS (FileNet IS) getting closed

I experienced a very similar problem while developing against JBoss 3.2.1. As it turns out, if you don't actually implement the ConnectionEventListener contract, as well as the matchManagedConnections() method, the container has no way of knowing the condition of your adapter. It will call close() at completely random times and (this one really baffled me) won't call destroy() like it should.

If you have implemented those methods accurately, and it's still doing that, post again and I'll make up some other answer. :-)

  HTH,
  -- /v\atthew

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".