On Fri, Jul 8, 2011 at 6:59 AM, [email protected] <[email protected]> wrote: > I build james-app after build james server 3.0-beta2,
Thanks :-) Until we have some form of continuous delivery setup, this is *really* helpful > but I can't start > james server, is this related with james server or just the problem of > james-app? Hopefully, a configuration issue in app... > The console log is below: <snip> > <openjpa-2.1.0-r422266:1071316 fatal user error> org.apache.openj > pa.persistence.InvalidStateException: Could not perform automatic lookup of > EJB container's javax.transaction.TransactionManager implementation. > Please ensure that you are running the application from > within an EJB 1.1 compliant EJB container, and then set the > org.apache.openjpa.ManagedRuntime property to the appropriate > value to obtain the TransactionManager. This symptom is a OpenJPA configuration issue but previously, the app used an InMemory mailbox by default. A recent change [1] looks to have switched to use store components. I'm out of time now to investigate more but I suspect that this configuration change is the cause of these problems. Robert [1] http://svn.apache.org/viewvc/james/app/trunk/src/main/config/james/context/james-mailbox-memory-context.xml?r1=1142483&r2=1142484&pathrev=1142484&; --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
