[JBoss JIRA] (AS7-6840) Backup can't start after fallback and another failover
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6840?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated AS7-6840:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=948247
> Backup can't start after fallback and another failover
> ------------------------------------------------------
>
> Key: AS7-6840
> URL: https://issues.jboss.org/browse/AS7-6840
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
>
> 1. start AS7 + HornetQ configured as backup + allow-tailback
> 2. start AS7 + HornetQ configured as live
> 3. Shutdown AS7 + HornetQ live
> => AS7 + HornetQ backup becomes active
> 4. Restart AS7 + HornetQ live
> => AS7 + HornetQ backup fails back
> => AS7 + HornetQ live becomes active
> 3. Shutdown AS7 + HornetQ live again
> => AS7 + HornetQ backup does not failover properly:
> {noformat}
> 18:15:03,296 ERROR [org.hornetq.core.server] (HQ119000: Activation for server
> HornetQServerImpl::serverUUID=7c2c4c70-9c79-11e2-abd5-538a3c182844) HQ224000: Failure in initialisation: java.lang.IllegalStateEx
> ception: ServiceBuilder is already installed
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:302)
> at org.jboss.as.messaging.jms.JMSService$1.activated(JMSService.java:89) [jboss-as-messaging-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
> at org.hornetq.core.server.impl.HornetQServerImpl.callActivateCallbacks(HornetQServerImpl.java:1358) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1]
> at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1581) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1]
> at org.hornetq.core.server.impl.HornetQServerImpl.access$1300(HornetQServerImpl.java:169) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1]
> at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation.run(HornetQServerImpl.java:2117) [hornetq-server-2.3.0.CR2-redhat-1.jar:2.3.0.CR2-redhat-1]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (AS7-6590) JSR-349 Bean Validation 1.1 API support and integration
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/AS7-6590?page=com.atlassian.jira.plugin.s... ]
Jesper Pedersen commented on AS7-6590:
--------------------------------------
[~gunnar.morling] JCAValidationFactory is used for bean validation integration with resource adapter deployments as per JCA 1.6. LazyValidationFactory isn't a service, so therefore there is a local copy in connector/. I would start with changing both, and then we can look at various cleanups
> JSR-349 Bean Validation 1.1 API support and integration
> -------------------------------------------------------
>
> Key: AS7-6590
> URL: https://issues.jboss.org/browse/AS7-6590
> Project: Application Server 7
> Issue Type: Sub-task
> Components: EE
> Reporter: David Lloyd
> Assignee: Emmanuel Bernard
> Fix For: 8.0.0.Alpha1
>
>
> Integrate Bean Validation 1.1 and Hibernate Validator 5 to support the BV 1.1 requirement of Java EE 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (AS7-6711) Unable to restart server group in domain mode
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6711?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6711:
----------------------------------------------
Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 913236|https://bugzilla.redhat.com/show_bug.cgi?id=913236] from ON_QA to VERIFIED
> Unable to restart server group in domain mode
> ---------------------------------------------
>
> Key: AS7-6711
> URL: https://issues.jboss.org/browse/AS7-6711
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Brian Stansberry
> Assignee: Emanuel Muckenhuber
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
> Attachments: AS7-6711-threads.txt
>
>
> Restarting the servers in the standard domain.xml main-server-group will result in a hang in the CLI and in the master HC.
> To reproduce start the standard domain.sh and in another window launch the CLI and:
> [domain@localhost:9999 /] /server-group=main-server-group:restart-servers
> Resulting console log output:
> [Host Controller] 18:17:30,511 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010923: Stopping server server-one
> 18:17:30,515 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012018: Stopping process 'Server:server-one'
> [Server:server-one] 18:17:30,599 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
> [Server:server-one] 18:17:30,600 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
> [Server:server-one] 18:17:30,611 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003075: Coyote HTTP/1.1 pausing on: http-localhost/127.0.0.1:8080
> [Server:server-one] 18:17:30,612 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003077: Coyote HTTP/1.1 stopping on : http-localhost/127.0.0.1:8080
> [Server:server-one] 18:17:30,616 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 79) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> [Server:server-one] 18:17:30,615 INFO [org.apache.catalina.core] (MSC service thread 1-2) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
> [Server:server-one] 18:17:30,640 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2
> [Server:server-one] 18:17:30,664 INFO [org.hornetq.ra] (MSC service thread 1-4) HQ151005: HornetQ resource adaptor stopped
> [Server:server-one] 18:17:30,704 INFO [org.hornetq.core.server] (MSC service thread 1-3) HQ221004: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [93f152f7-8aa1-11e2-8c0e-99b598ec3b97] stopped
> [Host Controller] 18:17:30,722 INFO [org.jboss.as.host.controller] (Remoting "pingguo.local:MANAGEMENT" read-1) JBAS010926: Unregistering server server-one
> [Server:server-one] 18:17:30,754 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015950: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" stopped in 189ms
> [Server:server-one]
> 18:17:30,815 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) JBAS012010: Process 'Server:server-one' finished with an exit status of 0
> [Host Controller] 18:17:30,818 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server server-one
> [Host Controller] 18:17:30,836 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010922: Starting server server-one
> 18:17:30,845 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012017: Starting process 'Server:server-one'
> [Server:server-one] 18:17:31,676 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR2
> [Server:server-one] 18:17:32,178 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.1.Final
> [Server:server-one] 18:17:32,332 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
> [Server:server-one] 18:17:32,530 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.1.0.Beta9
> [Server:server-one] 18:17:32,538 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.1.0.Beta9
> [Server:server-one] 18:17:32,559 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.15.GA
> [Host Controller] 18:17:33,607 INFO [org.jboss.as.domain.controller.mgmt] (Remoting "pingguo.local:MANAGEMENT" task-16) JBAS010920: Server [Server:server-one] registered using connection [Channel ID 2bacdeb7 (inbound) of Remoting connection 49660c5f to /127.0.0.1:60647]
> After that everything hangs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (AS7-6711) Unable to restart server group in domain mode
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6711?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6711:
----------------------------------------------
Radim Hatlapatka <rhatlapa(a)redhat.com> made a comment on [bug 913236|https://bugzilla.redhat.com/show_bug.cgi?id=913236]
Verified in EAP 6.1.0 ER4
> Unable to restart server group in domain mode
> ---------------------------------------------
>
> Key: AS7-6711
> URL: https://issues.jboss.org/browse/AS7-6711
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Brian Stansberry
> Assignee: Emanuel Muckenhuber
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
> Attachments: AS7-6711-threads.txt
>
>
> Restarting the servers in the standard domain.xml main-server-group will result in a hang in the CLI and in the master HC.
> To reproduce start the standard domain.sh and in another window launch the CLI and:
> [domain@localhost:9999 /] /server-group=main-server-group:restart-servers
> Resulting console log output:
> [Host Controller] 18:17:30,511 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010923: Stopping server server-one
> 18:17:30,515 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012018: Stopping process 'Server:server-one'
> [Server:server-one] 18:17:30,599 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
> [Server:server-one] 18:17:30,600 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
> [Server:server-one] 18:17:30,611 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003075: Coyote HTTP/1.1 pausing on: http-localhost/127.0.0.1:8080
> [Server:server-one] 18:17:30,612 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003077: Coyote HTTP/1.1 stopping on : http-localhost/127.0.0.1:8080
> [Server:server-one] 18:17:30,616 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 79) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> [Server:server-one] 18:17:30,615 INFO [org.apache.catalina.core] (MSC service thread 1-2) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
> [Server:server-one] 18:17:30,640 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2
> [Server:server-one] 18:17:30,664 INFO [org.hornetq.ra] (MSC service thread 1-4) HQ151005: HornetQ resource adaptor stopped
> [Server:server-one] 18:17:30,704 INFO [org.hornetq.core.server] (MSC service thread 1-3) HQ221004: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [93f152f7-8aa1-11e2-8c0e-99b598ec3b97] stopped
> [Host Controller] 18:17:30,722 INFO [org.jboss.as.host.controller] (Remoting "pingguo.local:MANAGEMENT" read-1) JBAS010926: Unregistering server server-one
> [Server:server-one] 18:17:30,754 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015950: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" stopped in 189ms
> [Server:server-one]
> 18:17:30,815 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) JBAS012010: Process 'Server:server-one' finished with an exit status of 0
> [Host Controller] 18:17:30,818 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server server-one
> [Host Controller] 18:17:30,836 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010922: Starting server server-one
> 18:17:30,845 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012017: Starting process 'Server:server-one'
> [Server:server-one] 18:17:31,676 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR2
> [Server:server-one] 18:17:32,178 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.1.Final
> [Server:server-one] 18:17:32,332 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
> [Server:server-one] 18:17:32,530 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.1.0.Beta9
> [Server:server-one] 18:17:32,538 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.1.0.Beta9
> [Server:server-one] 18:17:32,559 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.15.GA
> [Host Controller] 18:17:33,607 INFO [org.jboss.as.domain.controller.mgmt] (Remoting "pingguo.local:MANAGEMENT" task-16) JBAS010920: Server [Server:server-one] registered using connection [Channel ID 2bacdeb7 (inbound) of Remoting connection 49660c5f to /127.0.0.1:60647]
> After that everything hangs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (AS7-6770) Recovery manager service may not always use the correct orphan filters
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-6770?page=com.atlassian.jira.plugin.s... ]
jaikiran pai resolved AS7-6770.
-------------------------------
Fix Version/s: 8.0.0.Alpha1
Resolution: Done
> Recovery manager service may not always use the correct orphan filters
> ----------------------------------------------------------------------
>
> Key: AS7-6770
> URL: https://issues.jboss.org/browse/AS7-6770
> Project: Application Server 7
> Issue Type: Bug
> Components: Transactions
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: jaikiran pai
> Assignee: jaikiran pai
> Fix For: 8.0.0.Alpha1
>
>
> I've been looking into certain transaction recovery use cases (with EJB remote beans involved) and while investigating the issues, I noticed that the orphan filters being set in the JTAEnvironmentBean might not be available to the Recovery manager service. That's because the MSC service which sets up the transaction recovery manager service runs before the JTAEnvironmentBean is setup with the orphan filters, which actually happens in a separate MSC service (Arjuna tx manager service) which starts *after* the recovery manager MSC service.
> (Sorry, don't have the code in front of me, else would have added the exact class names - will do so later).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months