that looks like a database pool, where connections are in and after a while a specific connection isn't used for a long time and oracle terminates or makes in invalid.
configure your database pool that way that you test the connection before it gives you the connection johan On Jan 26, 2008 9:47 AM, <[EMAIL PROTECTED]> wrote: > Hello: > I have several bookmarkable links that would bring up page with data > retrieved from database via JPA/TOPLINK (EntityManager is always created > fresh evertime data is retrieved). The servlet session time is 30 minutes > but after several days when accessing some links, I got this > WicketMessage: Error attaching this container for rendering ..... > Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build > 060830)): oracle.toplink.essentials.exceptions.DatabaseException > Internal Exception: java.sql.SQLException: ORA-02396: exceeded maximum > idle time, please connect again > Error Code: 2396 > It appears that somewhere the page object is still holding on something > causing this. After a few repeated clicking of browser refreshing button, > the error would go away and a normal page is displayed without any other > intervention. I'd think after a few days, all session related page > objects would be no factors and it would work like the first time ever > accessing it. Maybe I have problem with my jpa setup but I used similar > methods under Seam(no EJB3) without issues so I think there maybe some > issues with page caching? > Thanks
