[JBoss JIRA] (DROOLS-670) Generalize inline casts to work with traits
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-670?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-670:
------------------------------------------
Fix Version/s: 6.4.0.CR1
(was: 6.4.0.Beta2)
> Generalize inline casts to work with traits
> -------------------------------------------
>
> Key: DROOLS-670
> URL: https://issues.jboss.org/browse/DROOLS-670
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.2.0.CR3
> Reporter: Davide Sottara
> Assignee: Davide Sottara
> Fix For: 6.4.0.CR1
>
>
> The following constraint
> {code}
> Person( this#Worker( wage > 1000 ) )
> {code}
> is admissible when Worker is a subtype of Person.
> It should also be possible to use "#" when Worker is a donned trait.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFLY-6268) There is no validation of some of messaging server attributes
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-6268?page=com.atlassian.jira.plugin.... ]
Chao Wang commented on WFLY-6268:
---------------------------------
For the journal-file-size, it's a bit tricky that it validates against mod result from AIOSequentialFileFactory and NIOSequentialFileFactory getAlignment() return value. 512 or 1 as:
{code:title=JournalImpl.java|borderStyle=solid}
if (fileSize % fileFactory.getAlignment() != 0) {
throw new IllegalArgumentException("Invalid journal-file-size " + fileSize + ", It should be multiple of " +
fileFactory.getAlignment());
}
{code}
> There is no validation of some of messaging server attributes
> -------------------------------------------------------------
>
> Key: WFLY-6268
> URL: https://issues.jboss.org/browse/WFLY-6268
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> There is no validation of some attributes of messaging provider. Setting of these attributes to non valid value causes an error during next reload. Some of these attributes are: {{journal-file-size}} or {{journal-compact-percentage}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFLY-6268) There is no validation of some of messaging server attributes
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-6268?page=com.atlassian.jira.plugin.... ]
Chao Wang moved JBEAP-3562 to WFLY-6268:
----------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6268 (was: JBEAP-3562)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: JMS)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 10.0.0.Final
(was: 7.0.0.ER5)
> There is no validation of some of messaging server attributes
> -------------------------------------------------------------
>
> Key: WFLY-6268
> URL: https://issues.jboss.org/browse/WFLY-6268
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> There is no validation of some attributes of messaging provider. Setting of these attributes to non valid value causes an error during next reload. Some of these attributes are: {{journal-file-size}} or {{journal-compact-percentage}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFLY-6212) Wrong behaviour of transaction synchronization when txn is timeouted
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6212?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka commented on WFLY-6212:
----------------------------------------
Hi [~swd847], may I assign this issue back to you? My commits are only about adding integration tests for checking transaction timeout behaviour. I haven't done any deep investigation on causes of the trouble.
> Wrong behaviour of transaction synchronization when txn is timeouted
> --------------------------------------------------------------------
>
> Key: WFLY-6212
> URL: https://issues.jboss.org/browse/WFLY-6212
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Ondřej Chaloupka
> Assignee: Ondřej Chaloupka
>
> There is wrong (or maybe strange) behavior of EJB when transaction timeout happens. There are several strange things happen but I'm creating only one jira that it seems that everything is based on one cause. Symptoms are following:
> When timeout occurs server log contains exception [1] (found out that have been reported at WFLY-5319).
> Second point is that it seems that in some cases {{javax.ejb.EJBException}} is thrown from the EJB method (no synchronization) and {{javax.ejb.EJBTransactionRolledbackException}} when {{javax.transaction.Synchronization}} is used. At least I have this impression. I think that behavior should be consistent and probably {{javax.ejb.EJBException}} should be used (feeling taken based of _spec EJB3.1, 14.3.7: Exceptions from Other Container-invoked Callbacks_).
> Third point is that rollback timeout exception does not remove stateful bean (spec EJB3.1, 4.6 Stateful session bean state diagram). Such bean is available and instead of throwing {{NoSuchEJBException}} there is thrown {{javax.ejb.ConcurrentAccessTimeoutException}}.
> The fourth and probably the most critical thing is that when transaction timeout happens then {{@AfterCompletion}} is not called. This is strangely not true when {{TransactionSynchronizationRegistry}} or {{javax.transaction.Synchronization}} is used. At such cases the after transaction synchronization method is invoked.
> I have created test cases under my repo and the code could be consulted and tested with from the branch here:
> https://github.com/ochaloup/jboss-as/tree/transaction-timeout-tests
> The testcase {{org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulTimeoutTestCase}} contains cases that when being run show the troubles described in this jira.
> [1]
> {code}
> 2016-02-15 13:55:12,084 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff0a2805ab:-141e1320:56c1caa9:c in state RUN
> 2016-02-15 13:55:12,088 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffff0a2805ab:-141e1320:56c1caa9:c invoked while multiple threads active within it.
> 2016-02-15 13:55:12,092 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012381: Action id 0:ffff0a2805ab:-141e1320:56c1caa9:c completed with multiple threads - thread pool-3-thread-1 was in progress with java.lang.Thread.sleep(Native Method)
> org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.TxTestUtil.waitForTimeout(TxTestUtil.java:71)
> org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulBean.testTransactionTimeout(StatefulBean.java:58)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82)
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:57)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:125)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
> org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64)
> org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:65)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
> org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
> org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
> org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
> org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulBean$$$view3.testTransactionTimeout(Unknown Source)
> org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulTimeoutTestCase.timeout(StatefulTimeoutTestCase.java:123)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:370)
> org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
> org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363)
> org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245)
> org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259)
> org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315)
> org.jboss.arquillian.container.test.impl.execution.BeforeLifecycleEventExecuter.on(BeforeLifecycleEventExecuter.java:35)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
> org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311)
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204)
> org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218)
> org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166)
> org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66)
> org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180)
> org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:247)
> org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162)
> org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141)
> org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:223)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:497)
> sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1503)
> org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724)
> org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168)
> org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:75)
> org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:70)
> java.security.AccessController.doPrivileged(Native Method)
> javax.security.auth.Subject.doAs(Subject.java:422)
> org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:70)
> org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> java.lang.Thread.run(Thread.java:745)
> 2016-02-15 13:55:12,093 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffff0a2805ab:-141e1320:56c1caa9:c aborting with 1 threads active!
> 2016-02-15 13:55:12,103 INFO [org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.TestXAResource] (Transaction Reaper Worker 0) end xid:[< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805ab:-141e1320:56c1caa9:c, node_name=1, branch_uid=0:ffff0a2805ab:-141e1320:56c1caa9:e, subordinatenodename=null, eis_name=unknown eis name >], flag: 536870912
> 2016-02-15 13:55:12,104 INFO [org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.TestXAResource] (Transaction Reaper Worker 0) rollback xid: [< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805ab:-141e1320:56c1caa9:c, node_name=1, branch_uid=0:ffff0a2805ab:-141e1320:56c1caa9:e, subordinatenodename=null, eis_name=unknown eis name >]
> 2016-02-15 13:55:12,116 INFO [org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.TestXAResource] (Transaction Reaper Worker 0) end xid:[< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805ab:-141e1320:56c1caa9:c, node_name=1, branch_uid=0:ffff0a2805ab:-141e1320:56c1caa9:12, subordinatenodename=null, eis_name=unknown eis name >], flag: 536870912
> 2016-02-15 13:55:12,117 INFO [org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.TestXAResource] (Transaction Reaper Worker 0) rollback xid: [< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805ab:-141e1320:56c1caa9:c, node_name=1, branch_uid=0:ffff0a2805ab:-141e1320:56c1caa9:12, subordinatenodename=null, eis_name=unknown eis name >]
> 2016-02-15 13:55:12,118 WARN [org.jboss.as.txn] (Transaction Reaper Worker 0) WFLYTX0027: The pre-jca synchronization org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization@368a2392 associated with tx TransactionImple < ac, BasicAction: 0:ffff0a2805ab:-141e1320:56c1caa9:c status: ActionStatus.ABORTED > failed during after completion: java.lang.IllegalMonitorStateException
> at org.jboss.as.ejb3.tx.OwnableReentrantLock.unlock(OwnableReentrantLock.java:120)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.releaseLock(StatefulSessionSynchronizationInterceptor.java:181)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.releaseInstance(StatefulSessionSynchronizationInterceptor.java:173)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization.afterCompletion(StatefulSessionSynchronizationInterceptor.java:250)
> at org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList.afterCompletion(JCAOrderedLastSynchronizationList.java:147)
> at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:545)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:476)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:130)
> at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215)
> at com.arjuna.ats.arjuna.coordinator.TransactionReaper.doCancellations(TransactionReaper.java:381)
> at com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:78)
> 2016-02-15 13:55:12,119 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff0a2805ab:-141e1320:56c1caa9:c
> 2016-02-15 13:55:12,118 ERROR [org.jboss.as.ejb3.invocation] (pool-3-thread-1) WFLYEJB0034: EJB Invocation failed on component StatefulBean for method public void org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulBean.testTransactionTimeout() throws javax.transaction.SystemException,java.lang.InterruptedException: javax.ejb.EJBException: WFLYEJB0448: Transaction 'TransactionImple < ac, BasicAction: 0:ffff0a2805ab:-141e1320:56c1caa9:c status: ActionStatus.ABORTED >' is in unexpected state (STATUS_ROLLING_BACK)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:114)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:279)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
> at org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulBean$$$view3.testTransactionTimeout(Unknown Source)
> at org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulTimeoutTestCase.timeout(StatefulTimeoutTestCase.java:123)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:370)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
> at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259)
> at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315)
> at org.jboss.arquillian.container.test.impl.execution.BeforeLifecycleEventExecuter.on(BeforeLifecycleEventExecuter.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
> at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:247)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:223)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1503)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724)
> at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:75)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:70)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:70)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> 2016-02-15 13:55:12,130 SEVERE [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-3-thread-1) Failed: org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulTimeoutTestCase.timeout: java.lang.AssertionError: Expecting rollback happened and transaction rollback exception being thrown expected:<class javax.ejb.EJBTransactionRolledbackException> but was:<class javax.ejb.EJBException>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.jboss.as.test.integration.ejb.transaction.cmt.timeout.xa.StatefulTimeoutTestCase.timeout(StatefulTimeoutTestCase.java:127)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:370)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
> at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259)
> at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315)
> at org.jboss.arquillian.container.test.impl.execution.BeforeLifecycleEventExecuter.on(BeforeLifecycleEventExecuter.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
> at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:247)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:223)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1503)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724)
> at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:75)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:70)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:70)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-1407) Test coverage for syslog reconnection
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFCORE-1407:
------------------------------------
Summary: Test coverage for syslog reconnection
Key: WFCORE-1407
URL: https://issues.jboss.org/browse/WFCORE-1407
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Reporter: Ondrej Lukas
Assignee: Tomaz Cerar
Added test coverage for syslog reconnection issues - https://issues.jboss.org/browse/LOGMGR-123.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-1407) Test coverage for syslog reconnection
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1407?page=com.atlassian.jira.plugi... ]
Ondrej Lukas reassigned WFCORE-1407:
------------------------------------
Assignee: Ondrej Lukas (was: Tomaz Cerar)
> Test coverage for syslog reconnection
> -------------------------------------
>
> Key: WFCORE-1407
> URL: https://issues.jboss.org/browse/WFCORE-1407
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 2.1.0.CR2
> Reporter: Ondrej Lukas
> Assignee: Ondrej Lukas
>
> Added test coverage for syslog reconnection issues - https://issues.jboss.org/browse/LOGMGR-123.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-1407) Test coverage for syslog reconnection
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1407?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-1407:
---------------------------------
Affects Version/s: 2.1.0.CR2
> Test coverage for syslog reconnection
> -------------------------------------
>
> Key: WFCORE-1407
> URL: https://issues.jboss.org/browse/WFCORE-1407
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 2.1.0.CR2
> Reporter: Ondrej Lukas
> Assignee: Ondrej Lukas
>
> Added test coverage for syslog reconnection issues - https://issues.jboss.org/browse/LOGMGR-123.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-433) git backend for loading/storing the configuration XML for wildfly
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-433?page=com.atlassian.jira.plugin... ]
James Strachan edited comment on WFCORE-433 at 2/24/16 3:17 AM:
----------------------------------------------------------------
Thanks [~bstansberry]. So a way to do a similar thing with Kubernetes using a git repo is :
* use a gitRepo volume in the Replication Controller YAML file: http://kubernetes.io/v1.1/docs/user-guide/volumes.html#gitrepo so that each pod has a specific git revision (SHA) cloned at a specific folder. The WildFly container then just loads config from disk as usual.
* when someone makes a change via the WildFly Admin Console a new git commit is done
* update the git revision in the Replication Controller and do a 'Rolling Update' in Kubernetes like this example https://github.com/fabric8io/kubernetes-client/blob/2e79032968bb2dfc299dc... only you'd be updating the spec.template.container's git volume rather than the image
* this basically then creates a new Replication Controller for the new git revision and starts spinning up new containers with the new configuration; as each one starts, is running and is 'ready' (using Readiness Probes to know if the WildFly container is up and running - e.g. is it listening on all the ports, is it ready to receive HTTP requests and whatnot) http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#liveness-a... - when the container is ready then it takes part in the Kubernetes services for load balancing. Then when its ready, the old RC is scaled down; so that 1 container rolls over from the old to the new configuration.
* the process running the rolling upgrade can monitor the newly created pods and check they startup OK; if they don't it can rollback the change and if need be rollback the git revision (or you can use branches if you want, kinda "Pull Request" stylee that changes only get merged to master after the rolling upgrade succeeds?)
You could run the above in the wildfly container that gets the git commit change from the Admin Console; though it might be better to elect a leader using Kubernetes' leadership election and letting that container watch for changes in git and perform the above steps.
http://blog.kubernetes.io/2016/01/simple-leader-election-with-Kubernetes....
You already have code to do dynamic updates of configuration on the fly to WildFly containers; you could keep doing that if you like - though its kinda easier to just adopt the immutable container model as there's less chance of incremental change bugs; plus you can the reuse the 'rolling upgrade' mechanism to do more than just deal with config changes - e.g. for testing out rolling upgrades of new docker images of wildfly too. As you need to be able to easily scale up / down the number of containers anyway; so the clean shutdown of containers needs implementing anyway; in which case you could simplify things by just rolling from old containers to new containers.
BTW you might want to look at using Kubernetes lifecycle hooks to ensure that containers are sufficiently drained before they are stopped. e.g. http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#lifecycle-... - then you can make kubernetes wait for the containers to have completed processing requests before it shuts down etc.
was (Author: jastrachan):
Thanks [~bstansberry]. So a way to do a similar thing with Kubernetes using a git repo is :
* use a gitRepo volume in the Replication Controller YAML file: http://kubernetes.io/v1.1/docs/user-guide/volumes.html#gitrepo so that each pod has a specific git revision (SHA) cloned at a specific folder. The WildFly container then just loads config from disk as usual.
* when someone makes a change via the WildFly Admin Console a new git commit is done
* update the git revision in the Replication Controller and do a 'Rolling Update' in Kubernetes like this example https://github.com/fabric8io/kubernetes-client/blob/2e79032968bb2dfc299dc... only you'd be updating the spec.template.container's git volume rather than the image
* this basically then creates a new Replication Controller for the new git revision and starts spinning up new containers with the new configuration; as each one starts, is running and is 'ready' (using Readiness Probes to know if the WildFly container is up and running - e.g. is it listening on all the ports, is it ready to receive HTTP requests and whatnot) http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#liveness-a... - when the container is ready then it takes part in the Kubernetes services for load balancing. Then when its ready, the old RC is scaled down; so that 1 container rolls over from the old to the new configuration.
* the process running the rolling upgrade can monitor the newly created pods and check they startup OK; if they don't it can rollback the change and if need be rollback the git revision (or you can use branches if you want, kinda "Pull Request" stylee that changes only get merged to master after the rolling upgrade succeeds?)
You could run the above in the wildfly container that gets the git commit change from the Admin Console; though it might be better to elect a leader using Kubernetes' leadership election and letting that container watch for changes in git and perform the above steps.
http://blog.kubernetes.io/2016/01/simple-leader-election-with-Kubernetes....
You already have code to do dynamic updates of configuration on the fly to WildFly containers; you could keep doing that if you like - though its kinda easier to just adopt the immutable container model as there's less chance of incremental change bugs; plus you can the reuse the 'rolling upgrade' mechanism to do more than just deal with config changes - e.g. for testing out rolling upgrades of new docker images of wildfly too.
BTW you might want to look at using Kubernetes lifecycle hooks to ensure that containers are sufficiently drained before they are stopped. e.g. http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#lifecycle-... - then you can make kubernetes wait for the containers to have completed processing requests before it shuts down etc.
> git backend for loading/storing the configuration XML for wildfly
> -----------------------------------------------------------------
>
> Key: WFCORE-433
> URL: https://issues.jboss.org/browse/WFCORE-433
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: James Strachan
> Assignee: Jason Greene
>
> when working with wildfly in a cloud/paas environment (like openshift, fabric8, docker, heroku et al) it'd be great to have a git repository for the configuration folder so that writes work something like:
> * git pull
> * write the, say, standalone.xml file
> * git commit -a -m "some comment"
> * git push
> (with a handler to deal with conflicts; such as last write wins).
> Then an optional periodic 'git pull' and reload configuration if there is a change.
> This would then mean that folks could use a number of wildfly containers using docker / openshift / fabric8 and then have a shared git repository (e.g. the git repo in openshift or fabric8) to configure a group of wildfly containers. Folks could then reuse the wildfly management console within cloud environments (as the management console would, under the covers, be loading/saving from/to git)
> Folks could then benefit from git tooling when dealing with versioning and audit logs of changes to the XML; along with getting the benefit of branching, tagging.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-433) git backend for loading/storing the configuration XML for wildfly
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-433?page=com.atlassian.jira.plugin... ]
James Strachan edited comment on WFCORE-433 at 2/24/16 3:16 AM:
----------------------------------------------------------------
Thanks [~bstansberry]. So a way to do a similar thing with Kubernetes using a git repo is :
* use a gitRepo volume in the Replication Controller YAML file: http://kubernetes.io/v1.1/docs/user-guide/volumes.html#gitrepo so that each pod has a specific git revision (SHA) cloned at a specific folder. The WildFly container then just loads config from disk as usual.
* when someone makes a change via the WildFly Admin Console a new git commit is done
* update the git revision in the Replication Controller and do a 'Rolling Update' in Kubernetes like this example https://github.com/fabric8io/kubernetes-client/blob/2e79032968bb2dfc299dc... only you'd be updating the spec.template.container's git volume rather than the image
* this basically then creates a new Replication Controller for the new git revision and starts spinning up new containers with the new configuration; as each one starts, is running and is 'ready' (using Readiness Probes to know if the WildFly container is up and running - e.g. is it listening on all the ports, is it ready to receive HTTP requests and whatnot) http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#liveness-a... - when the container is ready then it takes part in the Kubernetes services for load balancing. Then when its ready, the old RC is scaled down; so that 1 container rolls over from the old to the new configuration.
* the process running the rolling upgrade can monitor the newly created pods and check they startup OK; if they don't it can rollback the change and if need be rollback the git revision (or you can use branches if you want, kinda "Pull Request" stylee that changes only get merged to master after the rolling upgrade succeeds?)
You could run the above in the wildfly container that gets the git commit change from the Admin Console; though it might be better to elect a leader using Kubernetes' leadership election and letting that container watch for changes in git and perform the above steps.
http://blog.kubernetes.io/2016/01/simple-leader-election-with-Kubernetes....
You already have code to do dynamic updates of configuration on the fly to WildFly containers; you could keep doing that if you like - though its kinda easier to just adopt the immutable container model as there's less chance of incremental change bugs; plus you can the reuse the 'rolling upgrade' mechanism to do more than just deal with config changes - e.g. for testing out rolling upgrades of new docker images of wildfly too.
BTW you might want to look at using Kubernetes lifecycle hooks to ensure that containers are sufficiently drained before they are stopped. e.g. http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#lifecycle-... - then you can make kubernetes wait for the containers to have completed processing requests before it shuts down etc.
was (Author: jastrachan):
Thanks [~bstansberry]. So a way to do a similar thing with Kubernetes using a git repo is :
* use a gitRepo volume in the Replication Controller YAML file: http://kubernetes.io/v1.1/docs/user-guide/volumes.html#gitrepo so that each pod has a specific git revision (SHA) cloned at a specific folder. The WildFly container then just loads config from disk as usual.
* when someone makes a change via the WildFly Admin Console a new git commit is done
* update the git revision in the Replication Controller and do a 'Rolling Update' in Kubernetes like this example https://github.com/fabric8io/kubernetes-client/blob/2e79032968bb2dfc299dc... only you'd be updating the spec.template.container's git volume rather than the image
* this basically then creates a new Replication Controller for the new git revision and starts spinning up new containers with the new configuration; as each one starts, is running and is 'ready' (using Readiness Probes to know if the WildFly container is up and running - e.g. is it listening on all the ports, is it ready to receive HTTP requests and whatnot) http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#liveness-a... - when the container is ready then it takes part in the Kubernetes services for load balancing. Then when its ready, the old RC is scaled down; so that 1 container rolls over from the old to the new configuration.
* the process running the rolling upgrade can monitor the newly created pods and check they startup OK; if they don't it can rollback the change and if need be rollback the git revision (or you can use branches if you want, kinda "Pull Request" stylee that changes only get merged to master after the rolling upgrade succeeds?)
You could run the above in the wildfly container that gets the git commit change from the Admin Console; though it might be better to elect a leader using Kubernetes' leadership election and letting that container watch for changes in git and perform the above steps.
You already have code to do dynamic updates of configuration on the fly to WildFly containers; you could keep doing that if you like - though its kinda easier to just adopt the immutable container model as there's less chance of incremental change bugs; plus you can the reuse the 'rolling upgrade' mechanism to do more than just deal with config changes - e.g. for testing out rolling upgrades of new docker images of wildfly too.
BTW you might want to look at using Kubernetes lifecycle hooks to ensure that containers are sufficiently drained before they are stopped. e.g. http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#lifecycle-... - then you can make kubernetes wait for the containers to have completed processing requests before it shuts down etc.
> git backend for loading/storing the configuration XML for wildfly
> -----------------------------------------------------------------
>
> Key: WFCORE-433
> URL: https://issues.jboss.org/browse/WFCORE-433
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: James Strachan
> Assignee: Jason Greene
>
> when working with wildfly in a cloud/paas environment (like openshift, fabric8, docker, heroku et al) it'd be great to have a git repository for the configuration folder so that writes work something like:
> * git pull
> * write the, say, standalone.xml file
> * git commit -a -m "some comment"
> * git push
> (with a handler to deal with conflicts; such as last write wins).
> Then an optional periodic 'git pull' and reload configuration if there is a change.
> This would then mean that folks could use a number of wildfly containers using docker / openshift / fabric8 and then have a shared git repository (e.g. the git repo in openshift or fabric8) to configure a group of wildfly containers. Folks could then reuse the wildfly management console within cloud environments (as the management console would, under the covers, be loading/saving from/to git)
> Folks could then benefit from git tooling when dealing with versioning and audit logs of changes to the XML; along with getting the benefit of branching, tagging.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-433) git backend for loading/storing the configuration XML for wildfly
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-433?page=com.atlassian.jira.plugin... ]
James Strachan commented on WFCORE-433:
---------------------------------------
Thanks [~bstansberry]. So a way to do a similar thing with Kubernetes using a git repo is :
* use a gitRepo volume in the Replication Controller YAML file: http://kubernetes.io/v1.1/docs/user-guide/volumes.html#gitrepo so that each pod has a specific git revision (SHA) cloned at a specific folder. The WildFly container then just loads config from disk as usual.
* when someone makes a change via the WildFly Admin Console a new git commit is done
* update the git revision in the Replication Controller and do a 'Rolling Update' in Kubernetes like this example https://github.com/fabric8io/kubernetes-client/blob/2e79032968bb2dfc299dc... only you'd be updating the spec.template.container's git volume rather than the image
* this basically then creates a new Replication Controller for the new git revision and starts spinning up new containers with the new configuration; as each one starts, is running and is 'ready' (using Readiness Probes to know if the WildFly container is up and running - e.g. is it listening on all the ports, is it ready to receive HTTP requests and whatnot) http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#liveness-a... - when the container is ready then it takes part in the Kubernetes services for load balancing. Then when its ready, the old RC is scaled down; so that 1 container rolls over from the old to the new configuration.
* the process running the rolling upgrade can monitor the newly created pods and check they startup OK; if they don't it can rollback the change and if need be rollback the git revision (or you can use branches if you want, kinda "Pull Request" stylee that changes only get merged to master after the rolling upgrade succeeds?)
You could run the above in the wildfly container that gets the git commit change from the Admin Console; though it might be better to elect a leader using Kubernetes' leadership election and letting that container watch for changes in git and perform the above steps.
You already have code to do dynamic updates of configuration on the fly to WildFly containers; you could keep doing that if you like - though its kinda easier to just adopt the immutable container model as there's less chance of incremental change bugs; plus you can the reuse the 'rolling upgrade' mechanism to do more than just deal with config changes - e.g. for testing out rolling upgrades of new docker images of wildfly too.
BTW you might want to look at using Kubernetes lifecycle hooks to ensure that containers are sufficiently drained before they are stopped. e.g. http://kubernetes.io/v1.1/docs/user-guide/production-pods.html#lifecycle-... - then you can make kubernetes wait for the containers to have completed processing requests before it shuts down etc.
> git backend for loading/storing the configuration XML for wildfly
> -----------------------------------------------------------------
>
> Key: WFCORE-433
> URL: https://issues.jboss.org/browse/WFCORE-433
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: James Strachan
> Assignee: Jason Greene
>
> when working with wildfly in a cloud/paas environment (like openshift, fabric8, docker, heroku et al) it'd be great to have a git repository for the configuration folder so that writes work something like:
> * git pull
> * write the, say, standalone.xml file
> * git commit -a -m "some comment"
> * git push
> (with a handler to deal with conflicts; such as last write wins).
> Then an optional periodic 'git pull' and reload configuration if there is a change.
> This would then mean that folks could use a number of wildfly containers using docker / openshift / fabric8 and then have a shared git repository (e.g. the git repo in openshift or fabric8) to configure a group of wildfly containers. Folks could then reuse the wildfly management console within cloud environments (as the management console would, under the covers, be loading/saving from/to git)
> Folks could then benefit from git tooling when dealing with versioning and audit logs of changes to the XML; along with getting the benefit of branching, tagging.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
- 1
- 0