Similar issues on POP3 the last weeks with JPA exceptions not logged in
james-server.log.
I have now configured openjpa.Log in persistence.xml and added the
following line in log4j.properties
log4j.logger.org.apache.openjpa=TRACE, CONS, FILE
But I still don't see much openjpa in the logs.
Eric
On 05/17/2010 07:16 AM, Norman Maurer wrote:
Hi Vanuj,
could you give us some more informations ?
* Which revision of trunk ?
* Does it happen everytime ?
* Any changes made in persistence.xml or spring-beans.xml ?
* Could enable the TRACE logging in persistence.xml and show us the
full stack trace... :
<property name=penjpa.Log" value="DefaultLevel=TRACE,
Runtime=ACE, Tool=TRACE"/>
Thx,
Norman
2010/5/17 Apache James<[email protected]>:
Hi,
Apologies for the Spam,
I just built James from trunk and deployed it on tomcat a few hours ago.
Everything seems to be working fine but there is a problem in POP3 server.
When I hit the 'List' command does not return any response and hits an
exception in JPAMessageMapper.findMessagesInMailboxWithUID()
<openjpa-2.0.0-r422266:935683 fatal user error>
org.apache.openjpa.persistence.InvalidStateException: The context has been
closed. The stack trace at which the context was closed is available if
Runtime=ACE logging is enabled.
Has anyone faced this recently?
Thanks,
Vanuj.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]