I've been using Turbine with EJBs successfully for the last few months. But I recently tried using the scheduler service and am having trouble connecting to EJBs from the ScheduledJob extension class. I'm wondering what's different about the job's thread...
In the run(JobEntry job) method I'm using the same code to get a remote reference to an EJB that's used everywhere else but an exception is being thrown during name lookup. Looking at turbine.log I see something like this: 2002-03-05 12:08:14,754 [Thread-18] ERROR rotation - Error in WorkerThread for sheduled job #null, task: SendAlerts java.lang.NullPointerException at com.iona.j2ee.ejb.environment.EnvironmentContext.lookup(EnvironmentContext.j ava:51) at com.iona.j2ee.jndi.url.java.JavaContext.lookup(JavaContext.java:35) at com.iona.j2ee.jndi.url.java.JavaContext.lookup(JavaContext.java:51) at javax.naming.InitialContext.lookup(Unknown Source) at <snip> The thing that stands out is the thread name. All other entries in the log list threads like this: [ORBThreadPool-4::thread-25]. Might this be the problem? Why does the scheduler service spawn threads differently than the rest of Turbine? Thanks in advance for any feedback. Blair Martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
