Catching generic Exceptions is mostly a bad practice. But I agree we
should prolly do it in the command dispatcher and just write a -ERR
Response to the client on an Exception.
Bye,
Norman
2010/5/18 Vanuj van.n...@yahoo.com:
Hi Norman,
Verified it and the fix works. Thanks so much for that.
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.
Hi Norman,
I enabled trace and found that there are two exceptions happening. One
on james startup and the other when the LIST or RETR command gets
called. Only the one on startup gets logged.
Also, There is this message during printed during server startup that
looked interesting. (Is is
Hi Vanuj,
Seems like your eclipse has some confusion with openjpa1 and openjpa2.
(James uses openjpa2 since 1 week).
I also activated the TRACE log, and didn't receive your message [main]
openjpa.Runtime - Not creating a ValidatorImpl because this app is using
the JPA 1.0 Spec
Both
Hi Vanuj,
The error below is fixed:
312 James TRACE [main] openjpa.Runtime - Not creating a
ValidatorImpl because this app is using the JPA 1.0 Spec
The error message about Weaver can be ignored:
Caused by: java.lang.IllegalStateException: Cannot apply class transformer
without
Hi Vanuj,
I found the problem with pop3. At least I know why it happens. But I
have to think a bit about how to fix it. Fix will come soon.
Thx,
Norman
2010/5/17 Norman Maurer nor...@apache.org:
Hi Vanuj,
The error below is fixed:
312 James TRACE [main] openjpa.Runtime - Not creating a
Hi Vanuj,
I think I fixed the bug. Please update you source tree and build it again.
Wait for your feedback
Thx,
Norman
2010/5/17 Norman Maurer nor...@apache.org:
Hi Vanuj,
I found the problem with pop3. At least I know why it happens. But I
have to think a bit about how to fix it.
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
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=openjpa.Log
