Perhaps influenced by the late hour, a Groucho Marx bit comes to mind:
I said: "Doctor, it hurts when I do that.:" (patient moves his arm)
Doctor: "Then don't do that."
If you have to have the underscore in your context: the message being returned is associated with the settingSessionDataMsg, which is only returned in one place in the app - out
of index.gsp as part of an xhr post to SessionServlet, to set up, well, an attribute associated with the session. Nothing in there looks suspicious - see https://github.com/ozoneplatform/owf/blob/ea1d4500f72b393ba2eab725de1d57cfee92e779/src/java/ozone/owf/filter/servlet/SessionServlet.java.
I'd try setting a breakpoint in the javascript for index.gsp to see what actually gets returned in the error which is getting masked by the 'Error setting session data' message.
One more thought: that path is only getting triggered if showAccessAlert is on... if you don't need one, turn it off. That's configurable in OwfConfig.groovy.
Tina Coleman
NEXTCENTURYCORPORATION
7075 Samuel Morse Drive, Suite 250
| Columbia, MD 21046
m 443.545.3100
|
f 443.285.0799
|www.nextcentury.com
In the bundled distribution straight off of ozoneplatform.org or owfgoss.org, it ships within the tomcat/lib directory. If you've got a downstream / rebundled, I'd do a find . -name OwfConfig.groovy.