Bea-000610

[threaded]

Sounds to me like a connection leak (but it could indeed be many other things) - try enabling leak profiling, if you've not already.

Tried that, unfortunately nearly all the code is springified hibernate stuff so it tells me not a lot.

Yet both suggestions have been helpful, thanks.

[threaded]

Put a

try
{
    ....
}
catch (Throwable e)
{
    e.printStackTrace();

    throw e;
}

in some deep down base class in the application. Sounds like it's throwing an error rather than an exception - could be the JVM running out of usable heap and WebLogic is managing to recover somehow.

Tried that, and nothing, so it must be internal to BEA.

[EqualOpportunities]

Nah, no stack trace. The server just halts for 20 seconds, then spits out a log line containing this, loses 5M of memory and carries on.

If you know a way to make it give up a stack trace for this that'd be nice as it currently appears randomly.

Sounds to me like a connection leak (but it could indeed be many other things) - try enabling leak profiling, if you've not already.

[Cowboy Bob]

Put a

try
{
    ....
}
catch (Throwable e)
{
    e.printStackTrace();

    throw e;
}

in some deep down base class in the application. Sounds like it's throwing an error rather than an exception - could be the JVM running out of usable heap and WebLogic is managing to recover somehow.

[threaded]

Give us the whole stack trace and I'll have a go - BEA-000610 is the standard "something's up but I don't know what"...

Nah, no stack trace. The server just halts for 20 seconds, then spits out a log line containing this, loses 5M of memory and carries on.

If you know a way to make it give up a stack trace for this that'd be nice as it currently appears randomly.

[EqualOpportunities]

Anyone know a way to prevent this BEA-000610?

Give us the whole stack trace and I'll have a go - BEA-000610 is the standard "something's up but I don't know what"...

[freakydancer]

Anyone know a way to prevent this BEA-000610?

Erm, 2:16pm?

[threaded]

Anyone know a way to prevent this BEA-000610?