URGENT! FinderException.

[Pavanapuresan]

Hi all,
I know I have posted this problem before, but i didnt get any reply at that
time and i have more information now.

The problem is this:
1. I have a Session Bean, whose methods call a number of finder methods on
many entity beans.
2. When these methods of the session bean are called from the servlet, the
following error is thrown, whenever ANY finder method is encountered except
for findByPrimaryKey.

javax.ejb.FinderException: com.ibm.ejs.persitence.EnumeratorException
original exception:
com.ibm.ejs.container.ContainerInternalError: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0113E An invalid
datetime format was detected; that is, an invalid string representation or
value was specified. SQLSTATE=22007
at javax.ejb.FinderException.<init>(FinderException.java:44)
at
com.ibm.ejs.persistence.EnumeratorFactory.createLazyEnumerator(EnumeratorFac
tory.java:111)
at
com.ibm.ejs.persistence.EnumeratorFactory.create(EnumeratorFactory.java:61)
at com.ibm.ejs.container.EJSHome.getEnumeration(EJSHome.java:1381)
at
com.mki.ebanking.beans.lognchlnge.EJSLognchlngeHomeBean.findByLchlogin(EJSLo
gnchlngeHomeBean.java:89)
at
com.mki.ebanking.beans.lognchlnge.EJSRemoteLognchlngeHome.findByLchlogin(EJS
RemoteLognchlngeHome.java:116)
at
com.mki.ebanking.beans.manager.UserChallengesManagerBean.getExpiredChallenge
Values(UserChallengesManagerBean.java:1085)
at
com.mki.ebanking.beans.manager.EJSRemoteUserChallengesManager.getExpiredChal
lengeValues(EJSRemoteUserChallengesManager.java:169)
at com.mki.ebanking.servlets.login.FinderTest.doGet(FinderTest.java:57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:580)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:35
3)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:729)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:655)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:338)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:175)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:93)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:77)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:155)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:212)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:347)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:216)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

3. Since it said that some datetime format is wrong, i initially made all
the date fields null and then when that didnt work, i made all the date
fields as current date using the command "CURRENT TIMESTAMP". This also
didnt make any difference.
3. So i wrote a servlet that called the entity beans individually and called
the same finder methods again. This time it worked without a hitch.
4. So thinking that it had something to do with beans, i wrote a session
bean which inturn had methods calling those finders of the entity beans. I
called these methods of the session bean from the above servlet. This also
WORKS FINE.
5. The problem thus, seems to be localised to that particular session bean
alone.
6. This problem suddenly cropped up one day and since then has quite
steadfastly refused resolution for over a week now.
7. Im at my wits end, if anybody has any ideas at all on this knotty
problem, PLEASE post your thoughts as soon as u can.

Thanks.

Pavan

[Pavanapuresan]

Some more information about this weird error:
The finder exception doesnt get thrown when the transaction attribute of the
bean is set to TX_SUPPORTS. When I set it to TX_REQUIRED or TX_REQUIRES_NEW,
the exception is thrown. So now i set it to TX_SUPPORTS and it works for
now.
Does anybody know why?

regards
Pavan
Pavanapuresan <pav...@midas-kapiti.com> wrote in message
news:9jjg8r$1sqs$1...@news.boulder.ibm.com...