0 Replies Latest reply on Oct 3, 2008 12:53 AM by Andy Conn

    HELP! No ClassLoaders Exception on @MessageDriven Timer Bean

    Andy Conn Newbie


      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.