1 Reply Latest reply on Feb 26, 2008 11:20 AM by vickyk

    JCA close/destroy

    chavali

      We have a requirement to maintain the session with the legacy system and the client. We want to persist the same connection for multiple requests from client. Upon clients logoff the legacy system to be notified may be by calling destroy instead of close. Upon the notification to (EIS)legacy system, the legacy system will processing and do some cleanup.

      I donot know with the connection pooling will the destroy close the physical connection with the EIS legacy system.

      Calling the destroy() instead of close() in JCA will the physical connection gets closed with the legacy system?

      Will the EIS (legacy system) socket desc gets closed by calling the destroy().

      Can some body help in this regard.