Data selection throws a blank screen

[Joel]

Hello List,

At times we encounter an issue where the data selection of a batch version gives a blank screen when launched from the web (See attached screen dump). The report submission does not go through and gives a message box "Your report has not been submitted successfully". The issue is limited to a few batch versions that had been working fine in the past.

The same batch version works fine from a fat client and this issue is not specific to any one web server. I have tried deploying a package for this but it did not help. Some of these are schedular versions that work fine when launched by the schedular so it seems like an issue only with the web.

We are on 8.12 and 8.98.1.1 tools release. Has anyone seen this error before.

The errors in the JAS logs are:

HTMLClientHandler:doService: Exception: java.lang.NullPointerException
java.lang.NullPointerException
at com.jdedwards.runtime.vtcomponent.version.VTDataSelRenderAdaptee.addRightOperandCell(Unknown Source)
at com.jdedwards.runtime.vtcomponent.version.VTDataSelRenderAdaptee.addCriterionElements(Unknown Source)
at com.jdedwards.runtime.vtcomponent.version.VTDataSelRenderAdaptee.renderHTML4NormalMode(Unknown Source)
at com.jdedwards.runtime.vtcomponent.version.VTDataSelRenderAdaptee.renderHTML4(Unknown Source)
at com.jdedwards.runtime.vtcomponent.version.VTDataSelection.renderHTML4(Unknown Source)
at com.jdedwards.runtime.virtual.output.HTML4OutputRenderer.render(Unknown Source)
at com.jdedwards.runtime.virtual.HTMLClientHandler.doService(Unknown Source)
at com.jdedwards.runtime.virtual.HTMLClientHandler.doService(Unknown Source)
at com.jdedwards.runtime.virtual.HTMLClientMAFComponentInstance.getData(Unknown Source)
at com.jdedwards.maflet.maf.E1Client.doGetData(Unknown Source)
at com.jdedwards.maflet.maf.E1Client.service(Unknown Source)
at com.peoplesoft.e1.container.MafletServiceContainer.doService(Unknown Source)
at com.peoplesoft.e1.container.MafletServiceContainer.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at com.jdedwards.base.JDEFilter.doFilter(Unknown Source)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at com.jdedwards.util.filters.GZIPFilter.doFilter(Unknown Source)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:619)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)

 

[Tom_Davidson]

Joel, You can reference our call 3-1621524641. The 'solution' was to recreate the version from scratch. Hopefully if enough of us report this Oracle will actually fix the issue.

Tom

 

[Joel]

Hi Tom,
Thanks for the info. I found another work around to the problem - move all the versions to an OMW project, do a check out and check in and then promote the OMW project. Deploying a package after doing this fixes the issue.
Did Oracle give any explanation what causes this issue to occur ?
BR,
Joel

 

[eSky]

Joel,

I saw this error some time back and I found the space of DataSource Central Object - PD900 (JDE_PD900 or PD900 depending on database) was full.

Rather than DataSource grow automatically keep some free space of central object on database.

 

[Tom_Davidson]

Joel,

They had no idea what caused it. So when we had a workaround, they just closed the call (with solution no less <sigh>)

Note: We are 400 based so I know we had plenty of space available (in reference to the other response)

Tom

 

[Joel]

We have enough of disk space on the drive on which the Central objects reside. The database is set to unrestricted growth. So I don't think its a size issue. Moreover the issue is isolated to only a few batch versions and is solved when we promote them again... Its looks like some corruption when the web server tries to generate the specs.