I figured this one out by downloading the JBoss source and stepping through
everything. It turned out my Intellij build was picking up some old code that
was trying to lookup an invalid JNDI name. You were right, I think that bug was
coming into play. Thanks for your help.
View the original
jaikiran wrote : I don't think this is the code that is throwing the
exception. Going by the exception stacktrace you posted, the exception is being
thrown when some object is being injected
|
| anonymous wrote : at
I also occasionally see this come up:
|
| 14:33:07,135 ERROR [STDERR] java.lang.ClassCastException: $Proxy104 cannot
be cast to com.csatp.service.policy.FundingService
| 14:33:07,135 ERROR [STDERR] at
com.csatp.service.scheduler.checkHandlerBean.execute(checkHandlerBean.java:58)
Ok, thanks here is the Quartz job execute method.
| public void execute(JobExecutionContext jobExecutionContext) throws
JobExecutionException {
| try {
| Context ctx = getInitialContext(jnp://localhost:1099);
| FundingService fs = (FundingService)
I don't think this is the code that is throwing the exception. Going by the
exception stacktrace you posted, the exception is being thrown when some object
is being injected
anonymous wrote : at
org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:65)
|
Please post your code. I remember that there was a bug where if the jndi name
used for injection was incorrect, then instead of a NameNotFoundException, this
NullPointerException was being raised. I don't remember which version had this
problem and which version had the fix. Let me see if i can