[jboss-jira] [JBoss JIRA] (AS7-5022) Server sometimes crashes during reload operation
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Thu Jun 28 05:34:12 EDT 2012
[ https://issues.jboss.org/browse/AS7-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler updated AS7-5022:
--------------------------------
Summary: Server sometimes crashes during reload operation (was: CLONE - Server sometimes crashes during reload operation)
> Server sometimes crashes during reload operation
> ------------------------------------------------
>
> Key: AS7-5022
> URL: https://issues.jboss.org/browse/AS7-5022
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Jan Martiska
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> After some number of server reloads, next reload fails.. the number seems random, for me it is between 6 and 150.
> this error message pops up during boot:
> {noformat}
> 15:21:05,036 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 53) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "osgi")]): org.jboss.msc.service.DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered
> {noformat}
> This shell script can be used for reproduction:
> {noformat}
> #!/bin/sh
> $JBOSS_HOME/bin/standalone.sh > /dev/null &
> sleep 10
> for i in `seq 1 150`; do
> echo $i
> $JBOSS_HOME/bin/jboss-cli.sh -c --command=:reload
> sleep 4
> tail --lines=50 $JBOSS_HOME/standalone/log/server.log | grep ERROR
> done
> {noformat}
> Testing environment> RHEL 5 or 6. This happens both when reloading using jboss-cli.sh and jboss-as-controller-client. It seems it has never happened to me when EAP was running in IPv6 mode (java.net.preferIPv4Stack=false), only IPv4. Affects all standalone profiles. It randomly breaks my admin console testsuite, which uses server reloads quite a lot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list