|
From: <php...@li...> - 2006-03-10 17:59:36
|
Hi,
> java.lang.Exception: Invoke failed:
>
[o(ApiOrganizationHome)]->findOrganization((IOrganizationWhere)o(ApiOrganizationWhere)).
> Cause: Failed reading response from the server.
> Nested exception is:
> java.lang.OutOfMemoryError: Java heap space
I think, the OutOfMemoryError happened in the EJB
business logic, not in the JVM running the bridge
backend. I assume the findOrganization is a EJB finder
method?
I haven't had OOM errors in the bridge backend for
some time now, but if I remember correctly the bridge
reports an OOM in its VM via:
JavaBridge ERROR: OutOfMemoryError
After that all clients should abort immediately
because the backend closes all connections to recover
from this. The above formatted error string ("Invoke
failed") makes me believe that it's not the bridge
backend that reported the OOM, but the component to
which the backend is connected, an EJB container
probably(?).
Can you please open a problem report (please use
http://sourceforge.net/tracker/?func=add&group_id=117793&atid=679233)
and attach the exception message from the
JavaBridge.log (on RHEL the log file is
/var/log/php-java-bridge.log) there?
We'll look at this asap.
Regards,
Jost Boekemeier
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
|