[gatein-issues] [JBoss JIRA] (GTNPORTAL-3523) Default value of property "jboss.as.management.blocking.timeout" (300 s) may be insufficient for portal startup with more data

[Peter Palaga (JIRA)]

Peter Palaga created GTNPORTAL-3523:
---------------------------------------

             Summary: Default value of property "jboss.as.management.blocking.timeout" (300 s) may be insufficient for portal startup with more data
                 Key: GTNPORTAL-3523
                 URL: https://issues.jboss.org/browse/GTNPORTAL-3523
             Project: GateIn Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Packaging
    Affects Versions: 3.8.4.Final
            Reporter: Peter Palaga
            Assignee: Peter Palaga
             Fix For: 3.8.5.Final, 3.9.0.Final


Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1117945

In EAP 6.3.0.ER8 (present in JBoss Portal 6.2.0.ER4) there is new class in jboss.as.controller: BlockingTimeout.

This class loads value of system property "jboss.as.management.blocking.timeout" or defaults to 300 (seconds).

This will cause a problem during portal startup if for any reason (more data, slower db) it takes more than 5 minutes.

How reproducible:
with more data (e.g. with >1000 users)


Steps to Reproduce:
1. create a circumstance where portal startup takes longer than 5 minutes
2. start portal

Actual results:
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")
]'

After that the container is shut down.


Expected results:
Portal has enough time to start up.



Additional info:
The value of "jboss.as.management.blocking.timeout" property can be set to higher value. This should be either documented as workaround or it should be increased in portal configuration.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)