You are viewing the RapidMiner Server documentation for version 9.2 - Check here for latest version
Troubleshooting
This article outlines common problems while upgrading RapidMiner Server.
Timeout during RapidMiner Server start
You might see the following log lines in the server.log file within the
RapidMiner Server home directory:
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
("core-service" => "management"),
("management-interface" => "native-interface")
]'
ERROR [org.jboss.as.controller.client] (Controller Boot Thread) JBAS014781: Step handler org.jboss.as.server.DeployerChainAddHandler$FinalRuntimeStepHandler@2821a6c1 for operation {"operation" => "add-deployer-chains","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException
Explanation: JBoss requires a lot of time to start after the initial upgrade and then times out. This can happen because a column has been added in the new version and the existing table needs to be migrated. When such tables are large, the migration can take a lot of time and exceed the JBoss deployment time which is 300 seconds by default.
Solution: The property jboss.as.management.blocking.timeout is used to determine how long a deployment might
take before JBoss aborts the deployment. A solution to the problem is to temporarily increase the default timeout.
Please use the following statement (.bat on Windows) to start RapidMiner Server for a temporary timeout increase:
./bin/standalone.sh -Djboss.as.management.blocking.timeout=3600. After the upgrade completed successfully the timeout
increase is not required anymore.