The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here

Timeout after night with server enabled

Pawel_KPawel_K Member Posts: 5 Contributor I
edited November 2018 in Help

Hello,

 

I left server enabled on whole night and next day after unlocking computer I got these warnings:

07:50:26,531 WARN  [org.jboss.as.ejb3] (EJB default - 48) JBAS014143: A previous execution of timer [rapidminer-server-ear.rapidminer-server-ejb.TriggerEJBImpl eaf3da6f-3175-4fe8-95db-e59f44ddf77c] is still in progress, skipping this overlapping scheduled execution at: Mon Jun 05 07:50:26 CEST 2017 as timer state is IN_TIMEOUT
07:50:26,531 WARN  [org.jboss.as.ejb3] (EJB default - 3) JBAS014143: A previous execution of timer [rapidminer-server-ear.rapidminer-server-ejb.TriggerEJBImpl eaf3da6f-3175-4fe8-95db-e59f44ddf77c] is still in progress, skipping this overlapping scheduled execution at: Mon Jun 05 07:50:26 CEST 2017 as timer state is IN_TIMEOUT
07:50:26,546 WARN  [org.jboss.as.ejb3] (EJB default - 1) JBAS014143: A previous execution of timer [rapidminer-server-ear.rapidminer-server-ejb.TriggerEJBImpl eaf3da6f-3175-4fe8-95db-e59f44ddf77c] is still in progress, skipping this overlapping scheduled execution at: Mon Jun 05 07:50:26 CEST 2017 as timer state is IN_TIMEOUT
07:50:26,546 WARN  [org.jboss.as.ejb3] (EJB default - 50) JBAS014143: A previous execution of timer [rapidminer-server-ear.rapidminer-server-ejb.TriggerEJBImpl eaf3da6f-3175-4fe8-95db-e59f44ddf77c] is still in progress, skipping this overlapping scheduled execution at: Mon Jun 05 07:50:26 CEST 2017 as timer state is IN_TIMEOUT
07:50:26,546 WARN  [org.jboss.as.ejb3] (EJB default - 2) JBAS014143: A previous execution of timer [rapidminer-server-ear.rapidminer-server-ejb.TriggerEJBImpl eaf3da6f-3175-4fe8-95db-e59f44ddf77c] is still in progress, skipping this overlapping scheduled execution at: Mon Jun 05 07:50:26 CEST 2017 as timer state is IN_TIMEOUT

To log on RapidMiner server I need to restart standalone.bat file. Does anyone know solution to the problem?

Tagged:

Answers

  • Thomas_OttThomas_Ott RapidMiner Certified Analyst, RapidMiner Certified Expert, Member Posts: 1,761 Unicorn

    It could be that a scheduled process is dependent on another one first finishing. Is there enough of a delay between processes starting and finishing?

  • Pawel_KPawel_K Member Posts: 5 Contributor I

    Except that I don't have scheduled process or at least I don't know about it. I use apps only.

     

    Last night I ran RM Server as windows service. I still got these warnings but server seems to work properly.

  • Pawel_KPawel_K Member Posts: 5 Contributor I

    I'm wondering about this property

    com.rapidanalytics.ajax.default_refresh_interval

    What is default value for above property?

    On stackoverflow (https://stackoverflow.com/a/24494864) I found: 

     

    Consider using setTimeout instead - it's more reliable. setInterval timers can stack when the window doesn't have focus and then all run at once when it gets focus back again

    What fits to my problem.

  • Marco_BoeckMarco_Boeck Administrator, Moderator, Employee-RapidMiner, Member, University Professor Posts: 1,996 RM Engineering

    Hi,

     

    no that Ajax thing is something entirely different :)

    The warning you see in your log can be safely ignored, there is no problem. The method is for checking triggers defined in RapidMiner Server.

     

    Regards,

    Marco

  • Pawel_KPawel_K Member Posts: 5 Contributor I

    Today after logging to system I couldn't connect to server or use web app from link again.

    Is there any option in XML files or wherever that causes server shutdown after some time of inactivity?

    I've already tried to change this

    - <session-bean>
    - <stateless>
      <bean-instance-pool-ref pool-name="slsb-strict-max-pool" /> 
      </stateless>
      <stateful default-access-timeout="500000" cache-ref="simple" /> 
      <singleton default-access-timeout="500000" /> 
      </session-bean>

    in standalone.xml file and com.rapidanalytics.web.session.timeout property in server administration.

  • Marco_BoeckMarco_Boeck Administrator, Moderator, Employee-RapidMiner, Member, University Professor Posts: 1,996 RM Engineering

    Hi,

     

    please revert those changes to avoid unintended problems, those are not relevant for your case.

    What exactly do you mean by you could not connect to Server? The session timeout setting in RM Server is simply deciding when to log you out after your browser session has been inactive for a set amount of time. It will then tell you once you come back and you can simply log in again.

    The server itself does not have any idle shutdown mechanisms, it is designed to run forever unless you manually shut it down.

     

    Would you happen to have the server.log content (RM_SERVER/standalone/log/server.log) from when the server apparently became unresponsive?

     

    Regards,

    Marco

  • Pawel_KPawel_K Member Posts: 5 Contributor I

    Problem solved. My stupid mistake. I had set sleep function of system after 30 min.

     

    Thank you all for help.

Sign In or Register to comment.