Orbeon Forms community mailing list

AssertionError exception when loading a builder or runner page

Classic

List

Threaded

4 messages Options

Meiching Sin

AssertionError exception when loading a builder or runner page

Hello,

We had integrated Orbeon into our application, and for the most part accessing the orbeon builder and runner pages work fine, and posting URL links for editing and viewing templates and documents work as expected.

However intermittently, we will encounter an AssertionError, like below, and it seems to put orbeon in a bad state and can't recover. We must restart the tomcat server and orbeon to continue. This does not happen consistently, we could be viewing the same template or document fine for a few times, then get the exception and can't recover.

Orbeon log (with debug) doesn't indicate the cause of the error, or at least it is not obvious.

What could be the cause of this AssertionError? or how do I find it?

What is the best approach to "handle" this kind of error in order to recover from it? or is it possible to recover?

Thanks,

Mei

2015-10-06 12:07:01,923 ERROR PageFlowControllerProcessor - error caught {controller: "oxf:/apps/fr/page-flow.xml", method: "GET", path: "/fr/voacis/test2/view/0d242fe501c7c38c1236371f857eb6d33cf271ba"}

2015-10-06 12:07:01,933 ERROR PageFlowControllerProcessor -

+----------------------------------------------------------------------------------------------------------------------+

|An Error has Occurred |

|----------------------------------------------------------------------------------------------------------------------|

|assertion failed |

|----------------------------------------------------------------------------------------------------------------------|

|Application Call Stack |

|----------------------------------------------------------------------------------------------------------------------|

|Exception: java.lang.AssertionError |

|----------------------------------------------------------------------------------------------------------------------|

|scala.Option |map |Option.scala | 146|

|---8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<---|

|.apache.tomcat.util.net.NioEndpoint$SocketProcessor|run |NioEndpoint.java |1686|

|java.util.concurrent.ThreadPoolExecutor$Worker |run |ThreadPoolExecutor.java | 615|

|java.lang.Thread |run |Thread.java | 722|

+----------------------------------------------------------------------------------------------------------------------+

2015-10-06 12:52:48,984 INFO ProcessorService - /home/ - Timing: 21

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Erik Bruchez

Re: AssertionError exception when loading a builder or runner page

Administrator

Mei,

I have never seen this issue. Which version of Orbeon Forms are you using?

The assertion is happening here I think:

https://github.com/scala/scala/blob/2.11.x/src/library/scala/collection/immutable/HashSet.scala#L525

And that would be as a result of this:

https://github.com/orbeon/orbeon-forms/blob/4.10-ce/src/main/scala/org/orbeon/oxf/util/Connection.scala#L462

But why it would happen is unclear. Is there no particular reproducible condition where it happens?

Also, I cannot explain why Orbeon Forms would be completely unresponsive after that. Usually when an exception occurs, other subsequent requests succeed, certainly new requests for forms.

-Erik

Meiching Sin

Re: AssertionError exception when loading a builder or runner page

Hi Erik,

Thanks for the quick reply. We are using 4.10PE.

What I mean by "unresponsive" is, after we get this AssertionError, any subsequent request of document or template to the orbeon server will give the same AssertionError, so it becomes unusable. And we must restart the tomcat/orbeon.

We have narrowed down the steps to trigger it, we created a very simple template, with only 1 input text field on it. And from our application, send URL to orbeon to edit/save this template, and to create/update/view documents using this template. After after a few times (like 10 or 15 times), we will get the error.

Btw, we have also added some additional parameters to the http header to our application internal use. The additional parameters are added to every request to orbeon URL calls. Not sure if that plays any kind of role in triggering the exception.

Mei

Meiching Sin

Re: AssertionError exception when loading a builder or runner page

Some more updates on this issue.

After more testing, we are able to reproduce this issue consistently with Orbeon along.

And please be aware that we are in the process of evaluating orbeon and are working on adding orbeon into our application and distributing to production. However this issue causes orbeon engine to crash and become unusable, and it is a major blocker. This issue must be resolved in order for us to move forward with orbeon.

We can consistently reproduce the issue with Orbeon along, without other integration pieces from our application. We had created a simulation test program to trigger the issue. The test program is attached. The test program sends http requests directly to orbeon engine for a new template, passing the template parameters in the URL, hence bypassing the template parameter dialog. It continuously sends the same requests for new template and reads the response.

The test program shows that when request is processed successfully by orbeon, the response code is 200 received. And at request ~#5 (anywhere between #4 and #8), the request gets a response code 500, and orbeon.log shows the AssertionException. And this point, orbeon engine is still able to continue and process additional requests. Then when it gets to about request ~#30 or so, request will get response code 500, and orbeon engine continues to return the response code 500 for all requests, basically becoming unusable. Orbeon.log shows “broken pipe” exception at this point.

When it gets to this stage, we have to reload orbeon or restart tomcat.

It seems there is a bug in the orbeon engine, where it encounters an issue and is unable to recover and rashes.

Again this is a block for adding orbeon into our application. Quick assistance will be greatly appreciated.

Below is some information of the test program and our test environment:

Orbeon:

4.10 PE, original package downloaded from Orbeon, and using a trial license.

The only change to orbeon is adding license file to Orbeon folder, no other changes.

Java JRE: 7u22

Server: apache-tomcat-7.0.42

Database: orbeon’s default eXist database

To run the Test.jar:

java -jar Test.jar hostname

e.g. java -jar Test.jar http://oe312:8880

Test.jar (5K) Download Attachment