"A server error 500 occurred: ...."

ozzy

Hi,
found a peculiar server problem which shows up sometimes when I try to edit visualization in App designer. For a while as I am building an app everything is fine and sometimes after a while when I go to edit a visualization I get :
A server error 500 occurred: . The error has been recorded

The error looks like this :

15:35:20,521 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-/0.0.0.0:8080-8) /WEB-INF/facelets/components/editComponentButton.xhtml @12,106 target="#{reportEditorBean.currentComponent}": org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.rapidanalytics.entity.PropertiesMap.properties, could not initialize proxy - no Session: javax.el.ELException: /WEB-INF/facelets/components/editComponentButton.xhtml @12,106 target="#{reportEditorBean.currentComponent}": org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.rapidanalytics.entity.PropertiesMap.properties, could not initialize proxy - no Session
	at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:101) [jsf-facelets-1.1.15.B1.jar:1.1.15.B1]
	at com.sun.facelets.tag.jsf.core.SetPropertyActionListenerHandler$SetPropertyListener.processAction(SetPropertyActionListenerHandler.java:113) [jsf-facelets-1.1.15.B1.j........
etc..
etc...

Did anyone come across something like this?

Ozzy

Marco_Boeck

Hi,

you are running into the session timeout. After some time idling, your session is removed and you have to log back in again. You can increase the timeout (defaults to 30 minutes) in the server properties: "com.rapidanalytics.web.session.timeout" is the key.

Regards,
Marco

ozzy

Hmm..
this happens right after I log in into the server. Once this starts on a particular visualization, happens every time, meanwhile, I can happily open other visualizations or user input, text etc ..no problem.
The only "workaround" that I found so far is to delete complete view and rebuild it....
Ozzy

ozzy

Hi,
did some more digging into this issue, definitely looks like it might be a bug.

Once a component goes into this "error mode" there is nothing that will make it editable again. I tried new browser sessions, different browser session, restarting the server altogether and trying again... No matter what I do I always get the same error. It is almost like some record related to this component gets corrupted and the only thing you can do is delete the whole view. Even deleting the component results in the same error.

Has anyone seen this kind of problem?

Ozzy

Marco_Boeck

Hi,

is it always the same error in the log, even after a server restart? The message combined with the reproducibility is weird.

Regards,
Marco

sCapatina

Im experiencing this problem as well. The only solution for me is to delete the view and start from scratch... until I get the 500 error again.

This happens even after restarting the server.

Here is the shortened log of the error:

17:18:23,185 INFO  [com.rapidminer] (http-/0.0.0.0:8080-1) The parameter 'parallelize_main_process' is unknown for operator 'Process' (" Process ")."
17:18:23,185 INFO  [com.rapidminer.Process.116] (http-/0.0.0.0:8080-1) No filename given for result file, using stdout for logging results!
17:18:23,185 INFO  [com.rapidminer.Process.116] (http-/0.0.0.0:8080-1) Loading initial data.
17:18:23,188 INFO  [com.rapidminer.Process.116] (http-/0.0.0.0:8080-1) Assigning //_LOCAL/home/admin/KPI Master/Course Value/Universities/cv_13 to input port Process.input 1.
17:18:23,375 INFO  [com.rapidminer.Process.116] (http-/0.0.0.0:8080-1) Process //_LOCAL/home/admin/KPI Master/Course Value/Calculation/York University (13) starts
17:18:23,485 INFO  [com.rapidminer.Process.116] (http-/0.0.0.0:8080-1) Process //_LOCAL/home/admin/KPI Master/Course Value/Calculation/York University (13) finished successfully after 0 s
17:18:23,489 INFO  [de.rapidanalytics.web.beans.AbstractFileOperationsBean] (http-/0.0.0.0:8080-1) Opened app with assigned id report_1454359651891
17:18:28,615 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-/0.0.0.0:8080-1) /WEB-INF/facelets/components/deleteComponentButton.xhtml @15,106 target="#{reportEditorBean.currentComponent}": org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.rapidanalytics.entity.PropertiesMap.properties, could not initialize proxy - no Session: javax.el.ELException: /WEB-INF/facelets/components/deleteComponentButton.xhtml @15,106 target="#{reportEditorBean.currentComponent}": org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.rapidanalytics.entity.PropertiesMap.properties, could not initialize proxy - no Session
at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:101) [jsf-facelets-1.1.15.B1.jar:1.1.15.B1]
at com.sun.facelets.tag.jsf.core.SetPropertyActionListenerHandler$SetPropertyListener.processAction(SetPropertyActionListenerHandler.java:113) [jsf-facelets-1.1.15.B1.jar:1.1.15.B1]
at javax.faces.event.ActionEvent.processListener(ActionEvent.java:88) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final]
at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:775) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final
....
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_79]
Caused by: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.rapidanalytics.entity.PropertiesMap.properties, could not initialize proxy - no Session
at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:566) [hibernate-core-4.2.0.Final.jar:4.2.0.Final]
.....
... 82 more

17:18:28,617 ERROR [org.ajax4jsf.webapp.BaseXMLFilter] (http-/0.0.0.0:8080-1) Exception in the filter chain: javax.servlet.ServletException: failed to lazily initialize a collection of role: de.rapidanalytics.entity.PropertiesMap.properties, could not initialize proxy - no Session
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:606) [jboss-jsf-api_2.1_spec-2.1.18.Final.jar:2.1.18.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final.jar:7.2.0.Final]
...
...
17:18:49,618 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[ra-host].[/].[Faces Servlet]] (http-/0.0.0.0:8080-1) JBWEB000236: Servlet.service() for servlet Faces Servlet threw exception: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.rapidanalytics.entity.PropertiesMap.properties, could not initialize proxy - no Session
at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:566) [hibernate-core-4.2.0.Final.jar:4.2.0.Final]
at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:186) [hibernate-core-4.2.0.Final.jar:4.2.0.Final]
at org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:545) [hibernate-core-4.2.0.Final.jar:4.2.0.Final]
at org.hibernate.collection.internal.AbstractPersistentCollection.read(AbstractPersistentCollection.java:124) [hibernate-core-4.2.


...

Marco_Boeck

Hi,

thanks for the reports! We have identified a possible cause for this error and have included a fix for it in the next release.

Regards,
Marco

mariariaz

This issue hasn't been resolved till now . I get the same error everytime I try making a new web app and it automatically disappears after some time

Marco_Boeck

Hi,

which version are you running? RapidMiner Server 7.1 contains a fix for a cause for this problem.

Regards,
Marco

mariariaz

I am using rapidminer server  version 7.0.1

mariariaz

Would I have to update Java as well or updating the server alone could fix the problem ?  :-\

Marco_Boeck

Hi,

for all functionality it is strongly advised to install 7.1 fresh on a machine with Java 8. You can obviously keep using your DB so all your stuff will still be there.
But it is also possible to just upgrade the EAR file and keep using Java 7 for compatiblity reasons. Just note that once you use 7.1, you cannot downgrade again to 7.0.

Regards,
Marco