Ref http://groups.google.com/group/liftweb/browse_thread/thread/0e8ea02486ae37b4

Tomcat fix in ticket 1001 causes Jetty JNDI issues for LiftActor's scheduler. Jetty 6.1.24-6 on Ubuntu 11.04, Java 1.6.0_22, MySQL driver configured via JNDI and DefaultConnectionIdentifier.jndiName.

On Jun 7, 8:52 pm, David Pollak <feeder.of.the.be...@gmail.com> wrote:
> Can you put together a reproducible example? I'd like to see what the core
> issue is.

Sure. Please check https://github.com/terjesb/lift-actor-classpath.
Let it run with jetty-run. This works for 2.3, but fails after a few
seconds with 2.4-M1.
If I comment
d setContextClassLoader null
in core/actor/src/main/scala/net/liftweb/actor/LAPinger.scala it also
works against a local 2.4-SNAPSHOT.

> Okay... looks like the JNDI code is looking to figure out its context via
> the thread's contextclasspath and when it's null, bad things (tm) happen.