January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Heiko Braun reassigned AS7-3042: -------------------------------- Assignee: Darran Lofthouse (was: Heiko Braun) > IPv6: Invalid redirect to Admin console (wrong IP address) > ---------------------------------------------------------- > > Key: AS7-3042 > URL: https://issues.jboss.org/browse/AS7-3042 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Web > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Priority: Blocker > > This issue is some derivation from AS7-3040. Lets imagine starting server like this: > {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code} > So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990. > This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1). -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1415) NakreceiverWindow: replace ReadWriteLock with ReentrantLock

by Bela Ban (JIRA)

Bela Ban created JGRP-1415: ------------------------------ Summary: NakreceiverWindow: replace ReadWriteLock with ReentrantLock Key: JGRP-1415 URL: https://issues.jboss.org/browse/JGRP-1415 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0.3, 3.1 We have many writes, so replacing the (more complex and costly) RWL with a simple RL should help. Tested this with MPerf; performance is about the same. -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3119) Recurring timer might executed concurrent if the duration of the timeout method will be longer than the interval

by Wolf-Dieter Fink (Created) (JIRA)

Recurring timer might executed concurrent if the duration of the timeout method will be longer than the interval ---------------------------------------------------------------------------------------------------------------- Key: AS7-3119 URL: https://issues.jboss.org/browse/AS7-3119 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Beta1b Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink Timer with a short interval might be called before the previous execution is finished. This concurrent execution might harm the Bean provider expectations and implementation. In previous releases (AS5 EAP5) the execution is dropped in this case. -- 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

14 years, 3 months

4
4
0 / 0

[JBoss JIRA] (AS7-3313) CLONE - Add option to use Http11Protocol even if Http11AprProtocol can be used

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3313: -------------------------------------- Summary: CLONE - Add option to use Http11Protocol even if Http11AprProtocol can be used Key: AS7-3313 URL: https://issues.jboss.org/browse/AS7-3313 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.0.Beta1b Reporter: Rostislav Svoboda Assignee: Remy Maucherat Fix For: 7.1.0.Final Currently if APR is installed on machine and can be used by AS7 (AprLifecycleListener.isAprInitialized()) Http11AprProtocol is set as protocol handler. Please introduce option to force usage of Http11Protocol instead of Http11AprProtocol. On machines with apr installed we are not able to work with java based implementation. Possible place for code change: - org.apache.catalina.connector.Connector -- setProtocol -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3312) CLONE - User insn't properly informed that APR is used

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3312: -------------------------------------- Summary: CLONE - User insn't properly informed that APR is used Key: AS7-3312 URL: https://issues.jboss.org/browse/AS7-3312 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Beta1b Reporter: Rostislav Svoboda Assignee: Remy Maucherat Fix For: 7.1.0.Final AS7 log doesn't show sufficient information that APR is used or not. Currently the only clue is that org.apache.coyote.http11.Http11AprProtocol is used instead of org.apache.coyote.http11.Http11Protocol. But it's implementation details and many users can miss that. Add log message to inform users if APR is used or not! For example APR affect https connector definition which must use openssl based keys and not keystore. And if users do not know APR is used they can be easily confused and blame AS7 as broken. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2504) Intermittent failures in org.jboss.as.test.integration.management.cli tests

by Brian Stansberry (Created) (JIRA)

Intermittent failures in org.jboss.as.test.integration.management.cli tests --------------------------------------------------------------------------- Key: AS7-2504 URL: https://issues.jboss.org/browse/AS7-2504 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Brian Stansberry Assignee: Dominik Pospisil Fix For: 7.1.0.CR1 I'm seeing frequent intermittent failures in the CLI tests, along these lines: testConnect(org.jboss.as.test.integration.management.cli.BasicOpsTestCase) Time elapsed: 11.968 sec <<< ERROR! java.lang.Exception: CLI read timeout. at org.jboss.as.test.integration.management.util.CLIWrapper.readLine(CLIWrapper.java:147) at org.jboss.as.test.integration.management.cli.BasicOpsTestCase.testConnect(BasicOpsTestCase.java:48) A 1 sec timeout is inadequate. As an initial fix I'm going to increase it. To something big. If we want to test the response time of the CLI we need to move it out of the main testsuite. We can't trigger failures in the main testsuite that are due to external factors on the machine. -- 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

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3212) Add jconsole launch scripts to the AS7 distribution.

by Darran Lofthouse (Created) (JIRA)

Add jconsole launch scripts to the AS7 distribution. ---------------------------------------------------- Key: AS7-3212 URL: https://issues.jboss.org/browse/AS7-3212 Project: Application Server 7 Issue Type: Task Components: JMX, Remoting Reporter: Darran Lofthouse Assignee: Stuart Douglas Fix For: 7.1.0.Final Launching jconsole with remoting-jmx requires additional jars to be on the classpath (see the jconsole.sh in the remoting-jmx project). So that AS7 users don't need to manually set this up we should provide a .sh and a .bat with the correct classpath in the AS7 distribution to launch jconsole (Will require JAVA_HOME has been set) - if there is any way we can get this launch to use jboss-modules that would be even better so we don't need the versions of the jars within the scripts or a way to generate the scripts based on the versions but that may be too much for now. -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-3308) Deployment of the same named bean in two jar files problem

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3308: ------------------------------------- Summary: Deployment of the same named bean in two jar files problem Key: AS7-3308 URL: https://issues.jboss.org/browse/AS7-3308 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: jaikiran pai In case of deploying jar and ear files when each of them contains bean with the same name the deploy fails with following exception occurs: {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."ejb3.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ejb3.ear".POST_ at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.app.ejb3 is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.as.ee.naming.ApplicationContextProcessor.deploy(ApplicationContextProcessor.java:63) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more {code} Test could be check on: https://github.com/ochaloup/jboss-as/commit/6edb077f9cced40a18858de1bdeb6... In case that this issue is caused by not correct configuration in the test please close the issue. -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-2299) Cannot start OSGI console in JBoss 7.0.2

by Peter Penzov (Created) (JIRA)

Cannot start OSGI console in JBoss 7.0.2 ---------------------------------------- Key: AS7-2299 URL: https://issues.jboss.org/browse/AS7-2299 Project: Application Server 7 Issue Type: Bug Reporter: Peter Penzov Hi, I configured OSGI support in JBoss 7.0.2 but there is an error when I tried to start the server. [root@Testserver bin]# ./domain.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /opt/jboss-as-web-7.0.2.Final JAVA: /opt/jdk1.7.0_01/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 15:52:02,335 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.2.GA 15:52:02,578 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller' [Host Controller] 15:52:03,048 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.2.GA [Host Controller] 15:52:03,335 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.1.GA [Host Controller] 15:52:03,798 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2 [Host Controller] 15:52:03,819 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3 [Host Controller] 15:52:03,834 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3 [Host Controller] 15:52:04,602 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for native management service, all access will be unrestricted. [Host Controller] 15:52:04,675 INFO [org.jboss.as] (Controller Boot Thread) creating http management service using network interface (management) port (9990) [Host Controller] 15:52:04,677 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for http management service, all access will be unrestricted. [Host Controller] 15:52:04,721 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-one [Host Controller] 15:52:04,796 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /10.15.203.13:9999 15:52:04,816 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 4) JBAS012017: Starting process 'Server:server-one' [Host Controller] 15:52:04,832 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-two 15:52:04,858 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-two' [Server:server-one] 15:52:05,433 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.2.GA [Server:server-two] 15:52:05,602 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.2.GA [Server:server-one] 15:52:06,194 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.1.GA [Server:server-one] 15:52:06,263 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.2.Final "Arc" starting [Server:server-two] 15:52:06,497 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.1.GA [Server:server-two] 15:52:06,561 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.2.Final "Arc" starting [Server:server-one] 15:52:07,727 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib [Server:server-one] 15:52:07,799 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--10.15.203.13-8080 [Server:server-two] 15:52:07,949 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib [Server:server-two] 15:52:08,001 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--10.15.203.13-8230 [Server:server-one] 15:52:08,042 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc. [Server:server-one] 15:52:08,056 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA12324: Start RecoveryActivators [Server:server-one] 15:52:08,065 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Wed, 26 Oct 2011 15:52:08 [Server:server-one] 15:52:08,102 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off. [Server:server-one] 15:52:08,103 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA32013: Starting transaction recovery manager [Server:server-one] 15:52:08,130 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc. [Server:server-one] 15:52:08,209 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem [Server:server-one] 15:52:08,273 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2 [Server:server-one] 15:52:08,284 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3 [Server:server-one] 15:52:08,300 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3 [Server:server-two] 15:52:08,298 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc. [Server:server-two] 15:52:08,311 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-3) ARJUNA12324: Start RecoveryActivators [Server:server-two] 15:52:08,348 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem [Server:server-two] 15:52:08,547 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2 [Server:server-two] 15:52:08,557 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3 [Server:server-two] 15:52:08,572 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3 [Server:server-two] 15:52:08,586 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Wed, 26 Oct 2011 15:52:08 [Server:server-two] 15:52:08,613 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-3) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off. [Server:server-two] 15:52:08,614 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA32013: Starting transaction recovery manager [Server:server-two] 15:52:08,624 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc. [Server:server-one] 15:52:08,683 INFO [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem [Server:server-one] 15:52:08,791 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) JBossOSGi Framework Core - 1.0.0.CR8 [Server:server-one] 15:52:08,884 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: system.bundle:0.0.0 [Server:server-one] 15:52:08,934 INFO [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem [Server:server-one] 15:52:08,949 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service [Server:server-one] 15:52:09,296 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-webconsole:1.0.6 [Server:server-one] 15:52:09,308 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-as-osgi-configadmin:7.0.2.Final [Server:server-two] 15:52:08,932 INFO [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem [Server:server-two] 15:52:09,001 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) JBossOSGi Framework Core - 1.0.0.CR8 [Server:server-two] 15:52:09,081 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: system.bundle:0.0.0 [Server:server-two] 15:52:09,119 INFO [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem [Server:server-two] 15:52:09,131 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service [Server:server-two] 15:52:09,551 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.metatype:1.0.4 [Server:server-two] 15:52:09,597 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jboss-osgi-jmx:1.0.10 [Server:server-one] 15:52:09,529 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: javaee.api:0.0.0 [Server:server-one] 15:52:09,688 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-blueprint:1.0.2 [Host Controller] 15:52:09,693 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-1) Server [Server:server-one] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@4247959e] [Host Controller] 15:52:09,703 INFO [org.jboss.host.controller] (pool-3-thread-1) Registering server server-one [Server:server-one] 15:52:09,870 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jbosgi-webapp:1.0.2 [Server:server-one] 15:52:09,887 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jboss-osgi-logging:1.0.0 [Server:server-one] 15:52:10,124 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jboss-osgi-http:1.0.3 [Server:server-one] 15:52:10,303 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.aries.util:0.3.0 [Server:server-one] 15:52:10,305 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.jboss.logging:3.0.0 [Server:server-one] 15:52:10,616 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jboss-osgi-xerces:2.9.1.SP7 [Server:server-two] 15:52:09,874 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.aries.jmx:0.3.0 [Server:server-two] 15:52:09,892 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jboss-osgi-logging:1.0.0 [Server:server-two] 15:52:10,011 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.aries.util:0.3.0 [Server:server-two] 15:52:10,397 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: jboss-osgi-xerces:2.9.1.SP7 [Server:server-two] 15:52:10,415 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.apache.felix.webconsole:3.1.6.SP1 [Server:server-two] 15:52:10,444 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jbosgi-webconsole:1.0.6 [Server:server-two] 15:52:10,494 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.jboss.logging:3.0.0 [Server:server-two] 15:52:10,679 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jboss-osgi-http:1.0.3 [Server:server-two] 15:52:10,712 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.log:1.0.0 [Server:server-one] 15:52:10,651 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.aries.jmx:0.3.0 [Server:server-one] 15:52:10,929 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.felix.log:1.0.0 [Server:server-one] 15:52:10,950 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.apache.felix.configadmin:1.2.8 [Server:server-one] 15:52:11,018 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-osgi-jmx:1.0.10 [Server:server-two] 15:52:10,800 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-blueprint:1.0.2 [Server:server-two] 15:52:10,857 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.apache.felix.eventadmin:1.2.6 [Server:server-two] 15:52:10,978 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.apache.felix.configadmin:1.2.8 [Server:server-two] 15:52:11,188 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-webapp:1.0.2 [Server:server-two] 15:52:11,316 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: osgi.cmpn:4.2.0.200908310645 [Server:server-two] 15:52:11,319 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: javaee.api:0.0.0 [Server:server-two] 15:52:11,332 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jboss-as-osgi-configadmin:7.0.2.Final [Server:server-two] 15:52:11,339 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-4) Starting remote JMX connector [Server:server-one] 15:52:11,180 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.felix.metatype:1.0.4 [Server:server-one] 15:52:11,324 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: org.apache.felix.webconsole:3.1.6.SP1 [Server:server-one] 15:52:11,409 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: org.apache.felix.eventadmin:1.2.6 [Server:server-one] 15:52:11,423 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-2) Starting remote JMX connector [Host Controller] 15:52:11,471 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-1) Server [Server:server-two] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@659684cb] [Host Controller] 15:52:11,472 INFO [org.jboss.host.controller] (pool-3-thread-1) Registering server server-two [Server:server-two] 15:52:11,531 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem. [Server:server-two] 15:52:11,733 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2) [Server:server-one] 15:52:11,489 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: osgi.cmpn:4.2.0.200908310645 [Server:server-one] 15:52:11,708 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-4) Starting bundles for start level: 1 [Server:server-one] 15:52:11,829 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.configadmin:1.2.8 [Server:server-one] 15:52:11,985 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem. [Server:server-one] 15:52:12,234 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2) [Server:server-two] 15:52:12,064 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-1) Starting bundles for start level: 1 [Server:server-two] 15:52:12,075 INFO [org.jboss.as.logging] (MSC service thread 1-4) Removing bootstrap log handlers [Server:server-one] 15:52:12,308 INFO [org.jboss.as.connector] (MSC service thread 1-1) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final) [Server:server-one] 15:52:12,334 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.log:1.0.0 [Server:server-one] 15:52:12,446 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jboss-osgi-logging:1.0.0 [Server:server-one] 15:52:12,448 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-4) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.2.Final] [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-one] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-one] Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.2.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.2.Final]] package; (package=org.jboss.as.osgi.service) [Server:server-one] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) [jbosgi-resolver-felix-1.0.9.jar:1.0.9] [Server:server-one] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.9.jar:1.0.9] [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] ... 10 more [Server:server-one] [Server:server-one] 15:52:12,450 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-4) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.2.Final [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-one] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-one] [Server:server-one] 15:52:12,451 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-4) OSGi Framework started [Server:server-one] 15:52:12,455 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.2.Final [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-one] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-one] [Server:server-one] 15:52:12,457 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.2.Final] [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-one] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-one] Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.2.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.2.Final]] package; (package=org.jboss.as.osgi.service) [Server:server-one] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) [jbosgi-resolver-felix-1.0.9.jar:1.0.9] [Server:server-one] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.9.jar:1.0.9] [Server:server-one] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-one] ... 10 more [Server:server-one] [Server:server-one] 15:52:12,530 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS] [Server:server-one] 15:52:12,535 INFO [org.jboss.as.logging] (MSC service thread 1-1) Removing bootstrap log handlers [Server:server-two] 15:52:12,992 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final) [Server:server-two] 15:52:13,006 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS] [Server:server-two] 15:52:12,971 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem [Server:server-two] 15:52:13,001 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: org.apache.felix.configadmin:1.2.8 [Server:server-two] 15:52:13,126 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: org.apache.felix.log:1.0.0 [Server:server-two] 15:52:13,145 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: jboss-osgi-logging:1.0.0 [Server:server-two] 15:52:13,147 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-1) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.2.Final] [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-two] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-two] Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.2.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.2.Final]] package; (package=org.jboss.as.osgi.service) [Server:server-two] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) [jbosgi-resolver-felix-1.0.9.jar:1.0.9] [Server:server-two] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.9.jar:1.0.9] [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] ... 10 more [Server:server-two] [Server:server-two] 15:52:13,154 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-osgi-configadmin:7.0.2.Final] [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:210) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-two] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-two] Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-osgi-configadmin:7.0.2.Final]: missing requirement [Module[jboss-as-osgi-configadmin:7.0.2.Final]] package; (package=org.jboss.as.osgi.service) [Server:server-two] at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) [jbosgi-resolver-felix-1.0.9.jar:1.0.9] [Server:server-two] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.9.jar:1.0.9] [Server:server-two] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] ... 10 more [Server:server-two] [Server:server-two] 15:52:13,157 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-1) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.2.Final [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-two] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-two] [Server:server-two] 15:52:13,158 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-1) OSGi Framework started [Server:server-two] 15:52:13,159 ERROR [jboss-as-osgi-configadmin] (Thread-10) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-osgi-configadmin:7.0.2.Final [Server:server-two] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:257) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:93) [jbosgi-framework-core-1.0.0.CR8.jar:1.0.0.CR8] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_01] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_01] [Server:server-two] at java.lang.Thread.run(Thread.java:722) [:1.7.0_01] [Server:server-two] [Server:server-two] 15:52:13,197 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 8240ms - Started 89 of 139 services (50 services are passive or on-demand) [Server:server-one] 15:52:13,301 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem [Server:server-one] 15:52:13,352 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 8404ms - Started 89 of 139 services (50 services are passive or on-demand) This is the configuration file domain.xml  <domain xmlns="urn:jboss:domain:1.0"> <extensions> <extension module="org.jboss.as.clustering.infinispan"/> <extension module="org.jboss.as.clustering.jgroups"/> <extension module="org.jboss.as.connector"/> <extension module="org.jboss.as.ee"/> <extension module="org.jboss.as.ejb3"/> <extension module="org.jboss.as.jaxrs"/> <extension module="org.jboss.as.jmx"/> <extension module="org.jboss.as.jpa"/> <extension module="org.jboss.as.logging"/> <extension module="org.jboss.as.modcluster"/> <extension module="org.jboss.as.naming"/> <extension module="org.jboss.as.osgi"/> <extension module="org.jboss.as.remoting"/> <extension module="org.jboss.as.sar"/> <extension module="org.jboss.as.security"/> <extension module="org.jboss.as.threads"/> <extension module="org.jboss.as.transactions"/> <extension module="org.jboss.as.web"/> <extension module="org.jboss.as.weld"/> </extensions> <system-properties>  <property name="java.net.preferIPv4Stack" value="true"/> </system-properties> <profiles> <profile name="default"> <subsystem xmlns="urn:jboss:domain:logging:1.1"> <console-handler name="CONSOLE"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> </console-handler> <periodic-rotating-file-handler name="FILE"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> </periodic-rotating-file-handler> <logger category="com.arjuna"> <level name="WARN"/> </logger> <logger category="org.apache.tomcat.util.modeler"> <level name="WARN"/> </logger> <logger category="sun.rmi"> <level name="WARN"/> </logger> <root-logger> <level name="INFO"/> <handlers> <handler name="CONSOLE"/> <handler name="FILE"/> </handlers> </root-logger> </subsystem> <subsystem xmlns="urn:jboss:domain:datasources:1.0"> <datasources> <datasource jndi-name="java:jboss/datasources/ExampleDS" enabled="true" use-java-context="true" pool-name="H2DS"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url> <driver>h2</driver> <pool></pool> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> </drivers> </datasources> </subsystem> <subsystem xmlns="urn:jboss:domain:ee:1.0"/> <subsystem xmlns="urn:jboss:domain:ejb3:1.1" lite="true">  <pools> <bean-instance-pools> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> </bean-instance-pools> </pools>  <session-bean> <stateless> <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/> </stateless> </session-bean> </subsystem> <subsystem xmlns="urn:jboss:domain:infinispan:1.0" default-cache-container="hibernate"> <cache-container name="hibernate" default-cache="local-query"> <local-cache name="entity"> <eviction strategy="LRU" max-entries="10000"/> <expiration max-idle="100000"/> </local-cache> <local-cache name="local-query"> <eviction strategy="LRU" max-entries="10000"/> <expiration max-idle="100000"/> </local-cache> <local-cache name="timestamps"> <eviction strategy="NONE"/> </local-cache> </cache-container> </subsystem> <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/> <subsystem xmlns="urn:jboss:domain:jca:1.0"> <archive-validation enabled="true"/> <bean-validation enabled="true"/> <default-workmanager> <short-running-threads blocking="true"> <core-threads count="10" per-cpu="20"/> <queue-length count="10" per-cpu="20"/> <max-threads count="10" per-cpu="20"/> <keepalive-time time="10" unit="seconds"/> </short-running-threads> <long-running-threads blocking="true"> <core-threads count="10" per-cpu="20"/> <queue-length count="10" per-cpu="20"/> <max-threads count="10" per-cpu="20"/> <keepalive-time time="10" unit="seconds"/> </long-running-threads> </default-workmanager> </subsystem> <subsystem xmlns="urn:jboss:domain:jmx:1.0"> <jmx-connector registry-binding="jmx-connector-registry" server-binding="jmx-connector-server" /> </subsystem> <subsystem xmlns="urn:jboss:domain:jpa:1.0"> <jpa default-datasource=""/> </subsystem> <subsystem xmlns="urn:jboss:domain:naming:1.0"/> <subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="eager"> <configuration pid="org.apache.felix.webconsole.internal.servlet.OsgiManager"> <property name="manager.root">jboss-osgi</property> </configuration> <properties>  <property name="org.jboss.osgi.system.modules"> org.apache.commons.logging, org.apache.log4j, org.jboss.as.osgi, org.slf4j, </property>  <property name="org.osgi.framework.system.packages.extra"> org.apache.commons.logging;version=1.1.1, org.apache.log4j;version=1.2, org.jboss.as.osgi.service;version=7.0, org.jboss.osgi.deployment.interceptor;version=1.0, org.jboss.osgi.spi.capability;version=1.0, org.jboss.osgi.spi.util;version=1.0, org.jboss.osgi.testing;version=1.0, org.jboss.osgi.vfs;version=1.0, org.slf4j;version=1.5.10, </property>  <property name="org.osgi.framework.startlevel.beginning">2</property> </properties> <modules>  <module identifier="javaee.api"/> <module identifier="org.jboss.logging"/>  <module identifier="org.apache.aries.util"/> <module identifier="org.jboss.osgi.webconsole"/> <module identifier="org.osgi.compendium"/>  <module identifier="org.apache.felix.log" startlevel="1"/> <module identifier="org.jboss.osgi.logging" startlevel="1"/> <module identifier="org.apache.felix.configadmin" startlevel="1"/> <module identifier="org.jboss.as.osgi.configadmin" startlevel="1"/>  <module identifier="org.apache.aries.jmx" startlevel="2"/> <module identifier="org.apache.felix.eventadmin" startlevel="2"/> <module identifier="org.apache.felix.metatype" startlevel="2"/> <module identifier="org.apache.felix.webconsole" startlevel="2"/> <module identifier="org.jboss.osgi.jmx" startlevel="2"/> <module identifier="org.jboss.osgi.http" startlevel="2"/>  <module identifier="org.jboss.osgi.blueprint" startlevel="3"/> <module identifier="org.jboss.osgi.webapp" startlevel="3"/> <module identifier="org.jboss.osgi.xerces" startlevel="3"/> </modules> </subsystem> <subsystem xmlns="urn:jboss:domain:remoting:1.0"/> <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"/> <subsystem xmlns="urn:jboss:domain:sar:1.0"/> <subsystem xmlns="urn:jboss:domain:security:1.0"> <security-domains> <security-domain name="other"> <authentication> <login-module code="UsersRoles" flag="required"/> </authentication> </security-domain> </security-domains> </subsystem> <subsystem xmlns="urn:jboss:domain:threads:1.0"/> <subsystem xmlns="urn:jboss:domain:transactions:1.0"> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/> <core-environment> <process-id> <uuid /> </process-id> </core-environment> <coordinator-environment default-timeout="300"/> </subsystem> <subsystem xmlns="urn:jboss:domain:web:1.0" default-virtual-server="default-host"> <connector name="http" scheme="http" protocol="HTTP/1.1" socket-binding="http"/> <virtual-server name="default-host" enable-welcome-root="true"> <alias name="localhost" /> <alias name="example.com" /> </virtual-server> </subsystem> <subsystem xmlns="urn:jboss:domain:weld:1.0"/> </profile> <profile name="ha"> <subsystem xmlns="urn:jboss:domain:logging:1.1"> <console-handler name="CONSOLE"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> </console-handler> <periodic-rotating-file-handler name="FILE"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> </periodic-rotating-file-handler> <logger category="com.arjuna"> <level name="WARN"/> </logger> <logger category="org.apache.tomcat.util.modeler"> <level name="WARN"/> </logger> <logger category="sun.rmi"> <level name="WARN"/> </logger> <root-logger> <level name="INFO"/> <handlers> <handler name="CONSOLE"/> <handler name="FILE"/> </handlers> </root-logger> </subsystem> <subsystem xmlns="urn:jboss:domain:datasources:1.0"> <datasources> <datasource jndi-name="java:jboss/datasources/ExampleDS" enabled="true" use-java-context="true" pool-name="H2DS"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url> <driver>h2</driver> <pool></pool> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> </drivers> </datasources> </subsystem> <subsystem xmlns="urn:jboss:domain:ee:1.0"/> <subsystem xmlns="urn:jboss:domain:ejb3:1.1" lite="true">  <pools> <bean-instance-pools> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> </bean-instance-pools> </pools>  <session-bean> <stateless> <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/> </stateless> </session-bean> </subsystem> <subsystem xmlns="urn:jboss:domain:infinispan:1.0" default-cache-container="cluster"> <cache-container name="cluster" default-cache="default"> <alias>ha-partition</alias> <replicated-cache name="default" mode="SYNC" batching="true"> <locking isolation="REPEATABLE_READ"/> </replicated-cache> </cache-container> <cache-container name="web" default-cache="repl"> <alias>standard-session-cache</alias> <replicated-cache name="repl" mode="ASYNC" batching="true"> <locking isolation="REPEATABLE_READ"/> <file-store/> </replicated-cache> <distributed-cache name="dist" mode="ASYNC" batching="true"> <locking isolation="REPEATABLE_READ"/> <file-store/> </distributed-cache> </cache-container> <cache-container name="sfsb" default-cache="repl"> <alias>sfsb-cache</alias> <alias>jboss.cache:service=EJB3SFSBClusteredCache</alias> <replicated-cache name="repl" mode="ASYNC" batching="true"> <locking isolation="REPEATABLE_READ"/> <eviction strategy="LRU" max-entries="10000"/> <file-store/> </replicated-cache> </cache-container> <cache-container name="hibernate" default-cache="local-query"> <invalidation-cache name="entity" mode="SYNC"> <eviction strategy="LRU" max-entries="10000"/> <expiration max-idle="100000"/> </invalidation-cache> <local-cache name="local-query"> <eviction strategy="LRU" max-entries="10000"/> <expiration max-idle="100000"/> </local-cache> <replicated-cache name="timestamps" mode="ASYNC"> <eviction strategy="NONE"/> </replicated-cache> </cache-container> </subsystem> <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/> <subsystem xmlns="urn:jboss:domain:jca:1.0"> <archive-validation enabled="true"/> <bean-validation enabled="true"/> <default-workmanager> <short-running-threads blocking="true"> <core-threads count="10" per-cpu="20"/> <queue-length count="10" per-cpu="20"/> <max-threads count="10" per-cpu="20"/> <keepalive-time time="10" unit="seconds"/> </short-running-threads> <long-running-threads blocking="true"> <core-threads count="10" per-cpu="20"/> <queue-length count="10" per-cpu="20"/> <max-threads count="10" per-cpu="20"/> <keepalive-time time="10" unit="seconds"/> </long-running-threads> </default-workmanager> </subsystem> <subsystem xmlns="urn:jboss:domain:jgroups:1.0" default-stack="udp"> <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp" diagnostics-socket-binding="jgroups-diagnostics"/> <protocol type="PING"/> <protocol type="MERGE2"/> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> <protocol type="FD"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="BARRIER"/> <protocol type="pbcast.NAKACK"/> <protocol type="UNICAST"/> <protocol type="pbcast.STABLE"/> <protocol type="VIEW_SYNC"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="pbcast.STREAMING_STATE_TRANSFER"/> <protocol type="pbcast.FLUSH"/> </stack> <stack name="tcp"> <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/> <protocol type="MPING" socket-binding="jgroups-mping"/> <protocol type="MERGE2"/> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> <protocol type="FD"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="BARRIER"/> <protocol type="pbcast.NAKACK"/> <protocol type="UNICAST"/> <protocol type="pbcast.STABLE"/> <protocol type="VIEW_SYNC"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="pbcast.STREAMING_STATE_TRANSFER"/> <protocol type="pbcast.FLUSH"/> </stack> </subsystem> <subsystem xmlns="urn:jboss:domain:jmx:1.0"> <jmx-connector registry-binding="jmx-connector-registry" server-binding="jmx-connector-server" /> </subsystem> <subsystem xmlns="urn:jboss:domain:jpa:1.0"> <jpa default-datasource=""/> </subsystem> <subsystem xmlns="urn:jboss:domain:modcluster:1.0"> <mod-cluster-config advertise-socket="modcluster"/> </subsystem> <subsystem xmlns="urn:jboss:domain:naming:1.0"/> <subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="eager"> <configuration pid="org.apache.felix.webconsole.internal.servlet.OsgiManager"> <property name="manager.root">jboss-osgi</property> </configuration> <properties>  <property name="org.jboss.osgi.system.modules"> org.apache.commons.logging, org.apache.log4j, org.jboss.as.osgi, org.slf4j, </property>  <property name="org.osgi.framework.system.packages.extra"> org.apache.commons.logging;version=1.1.1, org.apache.log4j;version=1.2, org.jboss.as.osgi.service;version=7.0, org.jboss.osgi.deployment.interceptor;version=1.0, org.jboss.osgi.spi.capability;version=1.0, org.jboss.osgi.spi.util;version=1.0, org.jboss.osgi.testing;version=1.0, org.jboss.osgi.vfs;version=1.0, org.slf4j;version=1.5.10, </property>  <property name="org.osgi.framework.startlevel.beginning">2</property> </properties> <modules>  <module identifier="javaee.api"/> <module identifier="org.jboss.logging"/>  <module identifier="org.apache.aries.util"/> <module identifier="org.jboss.osgi.webconsole"/> <module identifier="org.osgi.compendium"/>  <module identifier="org.apache.felix.log" startlevel="1"/> <module identifier="org.jboss.osgi.logging" startlevel="1"/> <module identifier="org.apache.felix.configadmin" startlevel="1"/> <module identifier="org.jboss.as.osgi.configadmin" startlevel="1"/>  <module identifier="org.apache.aries.jmx" startlevel="2"/> <module identifier="org.apache.felix.eventadmin" startlevel="2"/> <module identifier="org.apache.felix.metatype" startlevel="2"/> <module identifier="org.apache.felix.webconsole" startlevel="2"/> <module identifier="org.jboss.osgi.jmx" startlevel="2"/> <module identifier="org.jboss.osgi.http" startlevel="2"/>  <module identifier="org.jboss.osgi.blueprint" startlevel="3"/> <module identifier="org.jboss.osgi.webapp" startlevel="3"/> <module identifier="org.jboss.osgi.xerces" startlevel="3"/> </modules> </subsystem> <subsystem xmlns="urn:jboss:domain:remoting:1.0"/> <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"/> <subsystem xmlns="urn:jboss:domain:sar:1.0"/> <subsystem xmlns="urn:jboss:domain:security:1.0"> <security-domains> <security-domain name="other"> <authentication> <login-module code="UsersRoles" flag="required"/> </authentication> </security-domain> </security-domains> </subsystem> <subsystem xmlns="urn:jboss:domain:threads:1.0"/> <subsystem xmlns="urn:jboss:domain:transactions:1.0"> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/> <core-environment> <process-id> <uuid /> </process-id> </core-environment> <coordinator-environment default-timeout="300"/> </subsystem> <subsystem xmlns="urn:jboss:domain:web:1.0" default-virtual-server="default-host"> <connector name="http" scheme="http" protocol="HTTP/1.1" socket-binding="http"/> <virtual-server name="default-host" enable-welcome-root="true"> <alias name="localhost" /> <alias name="example.com" /> </virtual-server> </subsystem> <subsystem xmlns="urn:jboss:domain:weld:1.0"/> </profile> </profiles>  <interfaces> <interface name="management"/> <interface name="public"/> </interfaces> <socket-binding-groups> <socket-binding-group name="standard-sockets" default-interface="public"> <socket-binding name="http" port="8080"/> <socket-binding name="https" port="8443"/> <socket-binding name="jmx-connector-registry" interface="management" port="1090"/> <socket-binding name="jmx-connector-server" interface="management" port="1091"/> <socket-binding name="jndi" port="1099"/> <socket-binding name="osgi-http" interface="management" port="8090"/> <socket-binding name="remoting" port="4447"/> <socket-binding name="txn-recovery-environment" port="4712"/> <socket-binding name="txn-status-manager" port="4713"/> </socket-binding-group> <socket-binding-group name="ha-sockets" default-interface="public"> <socket-binding name="http" port="8080"/> <socket-binding name="https" port="8443"/> <socket-binding name="jgroups-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/> <socket-binding name="jgroups-mping" port="0" multicast-address="230.0.0.4" multicast-port="45700"/> <socket-binding name="jgroups-tcp" port="7600"/> <socket-binding name="jgroups-tcp-fd" port="57600"/> <socket-binding name="jgroups-udp" port="55200" multicast-address="230.0.0.4" multicast-port="45688"/> <socket-binding name="jgroups-udp-fd" port="54200"/> <socket-binding name="jmx-connector-registry" interface="management" port="1090"/> <socket-binding name="jmx-connector-server" interface="management" port="1091"/> <socket-binding name="jndi" port="1099"/> <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="23364"/> <socket-binding name="osgi-http" interface="management" port="8090"/> <socket-binding name="remoting" port="4447"/> <socket-binding name="txn-recovery-environment" port="4712"/> <socket-binding name="txn-status-manager" port="4713"/> </socket-binding-group> </socket-binding-groups> <server-groups> <server-group name="main-server-group" profile="default"> <jvm name="default"> <heap size="64m" max-size="512m"/> </jvm> <socket-binding-group ref="standard-sockets"/> </server-group> <server-group name="other-server-group" profile="ha"> <jvm name="default"> <heap size="64m" max-size="512m"/> </jvm> <socket-binding-group ref="ha-sockets"/> </server-group> </server-groups> </domain> The OS is Centos 5.7 -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (JBRULES-3313) FileManager does several explicit System.gc(); calls which does a stop-the-world garbage collect halting all threads on the entire system

by Geoffrey De Smet (Created) (JIRA)

FileManager does several explicit System.gc(); calls which does a stop-the-world garbage collect halting all threads on the entire system ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3313 URL: https://issues.jboss.org/browse/JBRULES-3313 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Critical Performance tuning presentations state that System.gc() is bad as it stops all threads in the JVM for a long garbage collect, which kills the load a server can handle. FileManager does it on 2 lines: {code} while ( !file.delete() && count++ < 5 ) { System.gc(); ... } {code} Findbugs notices it too. -- 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

14 years, 3 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012