Unavailable cookie state

Question

What does this mean? I cannot seem to consistently make it happen. Only after a session has been going for a while. Closing the browser and coming back shows everything to be fine. Running on OC4J 903, BC4J from the latest Jdev production 904
oracle.jbo.common.ampool.ApplicationPoolException: JBO-30019: An unavailable cookie state was detected while attempting to use a cookie. applicationId: 5244abc132fc45febc3d9f870bad0bcd, sessionId: WebsiteService.
     at oracle.jbo.common.ampool.ApplicationPoolImpl.validateSessionCookieAvailable(ApplicationPoolImpl.java:3669)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:2353)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:427)
     at oracle.jbo.http.HttpSessionCookieImpl.useApplicationModule(HttpSessionCookieImpl.java:228)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:398)

Answer 1

Hi,
This exception is thrown by the ApplicationPool if you try to use a SessionCookie that is simultaneously being used by the ApplicationPool for internal administration. For example, it may be that the ApplicationPool is passivating the cookie state when the user request was made. The AMPoolMessageBundle text for this exception documents the following steps:
** <b>JBO-30019: ApplicationPoolException</b>
** <p>
** <b>Cause:</b>An ApplicationPool method was invoked for a cookie that was
** not currently available. A cookie can be in an unavailable state
** if another thread is currently updating the cookie. For example, consider
** the following scenario:
** <p>
** 1. cookie 1 releases an ApplicationModule with the managed state option
** 2. cookie 2 targets that ApplicationModule for recycling
** 3. Before cookie 2 has passivated the ApplicationModule state for
** cookie 1, cookie 1 requests another ApplicationModule
** <p>
** In this instance the ApplicationPool could throw an unavailable
** exception.
** <p>
** Most of the occurences of this exception should be handled by the BC4J
** pooling framework. If you do encounter this exception please report
** the exception to technical support. A workaround for the exception would
** be to attempt to the invalid operation again.
** <p>
** <b>Action:</b> Report the exception to technical support. Attempt the
** invalid operation again.
It does look like this is a case where the exception is not handled by the pooling framework. We will fix for the next release. In the meantime, please use the workaround mentioned above.
Hope this helps,
JR