[jboss-user] [Beginners Corner] - Persisted @MessageDrive Timer yields classpath loader error

aconn7 do-not-reply at jboss.com
Fri Oct 3 00:55:46 EDT 2008

Hi - Yes I know, duplicate post.  However I am getting desparate!

After or during JBOSS startup, any persisted timers yield a classloader error upon timeout.   

This behavior is NOT duplicated on any timers that are created (via TimerService.createTimer) and expire after completed bootup.

Some experimentation has shown that placing my entire application's jar in the lib/ folder cures the classloader problem.  However, this does not seem like the right solution.

Can someone please shed light on the problem and solution?  Why does this happen for persisted timers after startup and not new timers created (and expiring) after startup?

How do I get the persisted timers to load my application's classes without placing the entire application in the LIB/ ??


Thanks in advance.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180197#4180197

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180197

More information about the jboss-user mailing list