That's my take too. The stack doesn't really give us much to go on. If there was an ORA error code somewhere I might be able to help - but right now it'd be just a shot in the dark.
Might be worth checking with your DBA and see if there's anything else in the server logs. Upgrading the JDBC driver to match the server might be worth trying too. Regards, -mike On Thu, Jan 13, 2011 at 1:08 AM, Trenton D. Adams <[email protected]>wrote: > Just an FYI, I don't think this is a jpa issue. I see this with plain old > oracle thin JDBC as well. I have a feeling it's temporary network glitches, > as it happens rarely. > > We also occasionally get a tonne of these when our database goes down for > cold backup. > > > On 11-01-12 07:26 PM, Angelo K. Huang wrote: > >> >> Thanks for your reply. It is an intermittent thing. It recently occurred >> in >> one of our production servers. It might be just work load is big that >> caused >> the connection dead or some other reason that protocol engine is out of >> syn >> with RDBMS. Our env is openjpa 1.2.1, ojdbc 11.2.0.1.0 and oracle server >> 11.2.0.2.0. >> > >
