X-Application Version: 3.1.3
Tamino Version : 4.1.1, 3.1
Platform : Win2k, WinXP, Solaris, Linux, …
WebContainer : Tamocat 4.0.6, Tomcat 3.3.1
JDK Version : 1.4.1, 1.3.1

Hello,
I upgraded Tamino from version 3.1.2 to version 4.1.1 today.
Then I tested if the X-Application project was still working.
This is a project written in X-Application and has been running for months.

But now I get an error if my directcommand query returns no documents.
The error is following:

Uncaught runtime error –
URI: /Innkaupakort/jsp/faerslur.jsp
Extra path: null
Stack: XJspException:
java.lang.ArithmeticException: / by zero
at com.softwareag.tamino.db.API.response.TXMLObjectFetchingIterator.fetchBlockWith(TXMLObjectFetchingIterator.java:279)
at com.softwareag.tamino.db.API.response.TXMLObjectFetchingIterator.reset(TXMLObjectFetchingIterator.java:235)
at com.softwareag.xtools.xapplication.store.TaminoElementIterator.reset(TaminoElementIterator.java:110)
at com.softwareag.xtools.xapplication.businessdocument.BusinessDocumentCursor.reset(BusinessDocumentCursor.java:237)
at com.softwareag.xtools.xapplication.businessdocument.BusinessDocumentPage.(BusinessDocumentPage.java:86)
at com.softwareag.xtools.xapplication.plugin.StandardWorkspacePlugin.queryDocuments(StandardWorkspacePlugin.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.softwareag.xtools.xapplication.plugin.Action.invoke(Action.java:180)
at com.softwareag.xtools.xapplication.plugin.Dispatcher.execute(Dispatcher.java:158)
at com.softwareag.xtools.xapplication.jsp.SessionContext.processWorkspaceAction(SessionContext.java:389)
at com.softwareag.xtools.xapplication.jsp.taglib.DirectCommandTag.processAction(DirectCommandTag.java:192)
at com.softwareag.xtools.xapplication.jsp.taglib.CommandTag.doAfterBodyCore(CommandTag.java:122)
at com.softwareag.xtools.xapplication.jsp.JspTag.doAfterBody(JspTag.java:188)
at org.apache.jsp.faerslur$jsp._jspService(faerslur$jsp.java:513)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:431)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:355)
at is.visa.invoice.event.EventHandlerBase._dispatch(EventHandlerBase.java:39)
at is.visa.invoice.event.EventHandlerBase.forward(EventHandlerBase.java:27)
at is.visa.invoice.Controller.doPost(Controller.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:536)


I would be very grateful if you could read this stacktrace and give me hints on whats going on.
Maybe the response is different in version 4.1.1 of Tamino?

Best regards
eagle

Hello,
Here is some additional information if it is on any help:

I sometimes get this warning:

WARNING: finalizing un-closed() BusinessDocumentCursor

best regards
eagle

Hello,

which version of Tamino are you using with X-Application 4.1.1?

- Is it a database of version 3 oder 4?

If it is version 4 we could try to adapt your query from x-Query to XQuery. XQuery is the new standardized query language of the W3C. Using XQuery implies another cursor handling.

If you don’t want to switch to XQuery because you are using a database of version 3, we must analyze the error which is an internal error reported from the Tamino API for Java.

Useful information for such kind of errors is the protocol of the communication between the Tamino Java API and the Tamino Server. This protocol is created via HttpSniffer. For more information about using a sniffer follow the link to the topic

Protocolling the HTTP transfer between Tamino and X-Application

Many thanks.

Bye,
Christian.

Hello Christian,
Thanks for your reply. I think I will have to add a little bit more of information to my question, before we continue.

I am upgraded Tamino Server from version 3.1.2 to version 4.1.1.
I am currently using X-Application version 3.1.3 but I am planning to change to version 4 as soon as I can.

So I can switch to XQuery, if that is recommended.

Best regards
Eagle

Hello,

my recommendation is to use X-Application 4.1.1 after updating the database to a version 4 database.

However, it could be possible for you to use X-Application 3.1.3 with Tamino 4.x if you change the Tamino API for Java and some other jar-files. Please have a look at the following Sub-Topic

Zip Files for Tamino Version 4

It contains the required jar files. Your ‘devision by zero’ error does also occur within this context. The jar files should solve this problem.

Bye,
Christian.