Help to debug submission error

Submitted by Sherman on Thu, 02/20/2014 - 14:25
I have a form that will sometimes produce the following error on submission to the save form controller (same error info is in the Tomcat log). This seems to be data related as the error occurs only some of the time and when it does it will always occur for that specific case. Is there any way to get more info than the error below? I tried re-examining recent changes but I don't see any obvious issue. I don't know where to go next to try and solve this one.

Error:
HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

com.hyfinity.xpath.XPathException: org.jaxen.XPathSyntaxException: Unexpected ''
com.hyfinity.xpath.jaxen.XPathFactoryImpl.newXPath(XPathFactoryImpl.java:65)
com.hyfinity.sxforms.InputProcessor.processGroup(InputProcessor.java:592)
com.hyfinity.sxforms.InputProcessor.processStructure(InputProcessor.java:336)
com.hyfinity.sxforms.SXForms.processInput(SXForms.java:104)
com.hyfinity.xgate.InputProcessor.performSXFormsProcessing(InputProcessor.java:241)
com.hyfinity.xgate.InputProcessor.processInput(InputProcessor.java:183)
com.hyfinity.xgate.HTTP2Java.processAction(HTTP2Java.java:1075)
com.hyfinity.xgate.HTTP2Java.doPost(HTTP2Java.java:637)
javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

note The full stack trace of the root cause is available in the Apache Tomcat/5.5.27 logs.

Hi Sherman,

I+?+?+?m sorry you are getting this problem, but hopefully we can get it resolved.

Can you first confirm what WebMaker version you are using?

My initial thought from looking at that stack trace is that the error is related to an invalid (possibly blank) submission binding for a group.
Can you check through your page to see if you have any groups with the +?+?++Submit data if group not visible+?+?+? option unticked? If so, make sure that these groups have the Context Location and Group XML Fragment submission binding settings correctly specified for each action.
My guess would be that there is a matching group which does not have the Context Location provided.

Unticking the +?+?++Submit data if group not visible+?+?+? means that you only want the structure for this group to end up in the resulting XML message if the group is visible on screen. (See http://www.hyfinity.net/mvcdocumentation_v6/MVC/FormMaker%20User%20Guide/More%20Group%20Visibility%20Options.html)
If you don+?+?+?t need this capability, you can tick this option, and then the group submission settings will no longer be required.

I hope this helps resolve your issue.

Please let me know how you get on.

Regards,
Gerard

Thanks Gerard, you hit the nail on the head. There was one group with that option unchecked. It seems it did not need to be so (debugging a form I did not develop). In any case, setting that checkbox solved the problem.

For the record, I am using WM 5 with BF 12.1

Hi Gerard,

I have a similar issue, with webmaker5. When trying to view the debugger.

"This page contains the following errors:
error on line 4 at column 175: Opening and ending tag mismatch: HR line 0 and body
Below is a rendering of the page up to the first error.
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet execution threw an exception
com.hyfinity.studio.URLVersioningFilter.doFilter(URLVersioningFilter.java:104)
root cause
java.lang.OutOfMemoryError: Java heap space
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.27 logs."

As you have suggested I tried to look for 'submit data if group not visible' option and I don't have any unticked.

Can you please suggest what other areas can I look for errors.

Thanks,
Rakesh.

Hi Rakesh,

This seems to be a similar problem to your other thread at http://www.hyfinity.com/node/368
If it is ok by you, we can use that thread to track this problem.

Regards,
Gerard

We use cookies and analytics on our website to support technical features that enhance your user experience.

-