November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5069) Missing service to represent the TransactionListenerRegistry

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5069?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5069: -------------------------------- Fix Version/s: 11.0.0.CR1 > Missing service to represent the TransactionListenerRegistry > ------------------------------------------------------------ > > Key: WFLY-5069 > URL: https://issues.jboss.org/browse/WFLY-5069 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.Alpha6 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 11.0.0.CR1 > > > JBTM-2343 added an observer SPI for tracking transaction state association changes for use by the JPA subsystem. This needs to be available as a wildfly service for consumption by other subsystems (currently JPA casts the TM to get hold of the TransactionListenerRegistry). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5141) Custom operation for setting of process-id-*

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5141?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5141: -------------------------------- Fix Version/s: 11.0.0.CR1 > Custom operation for setting of process-id-* > -------------------------------------------- > > Key: WFLY-5141 > URL: https://issues.jboss.org/browse/WFLY-5141 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Beta1 > Reporter: Ondřej Chaloupka > Assignee: Amos Feng > Priority: Minor > Labels: ux > Fix For: 11.0.0.CR1 > > > When you want to set generation of process-id-* - either as uuid or as socket id the way to set it and set it back is inconsistent. In one direction you need to use composite operation in other direction you can't use it. > All this is discussed in jiras WFLY-2623 and WFLY-5126 > As result of discussion https://issues.jboss.org/browse/WFLY-2623#comment-13100037 this issue is raised. > It would be much better for user to have single way how to do this switching and custom operation could solve this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5704) InfinispanBatchContext trying to resume committed tx

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5704: ---------------------------------- Summary: InfinispanBatchContext trying to resume committed tx Key: WFLY-5704 URL: https://issues.jboss.org/browse/WFLY-5704 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR4 Environment: Linux x86_64 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical When running the test case RemoteFailoverTestCase.testStatefulFailover, the test hangs due to an exception occurring. The exception is the following: {noformat} [31m11:24:05,814 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (EJB default - 3) ISPN000136: Execution error: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=47}, status=3} is not in a valid state to be invoking cache operations on. {noformat} This exception arose some time ago and was linked to incorrect suspend/resume of threads by the InfinispanBatching mechanism. This is just a suggestion as to what might be the root cause. Attached is a log of the test case run with TRACE logging on DummyTransactionManager which coordinates the suspends and resumes. I have also performed a stack trace dump on every call to suspend and resume to highlight the origin of the call. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5703) Add an IBM ORB configuration to WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5703?page=com.atlassian.jira.plugin.... ] Tom Jenkinson moved JBTM-2537 to WFLY-5703: ------------------------------------------- Project: WildFly (was: JBoss Transaction Manager) Key: WFLY-5703 (was: JBTM-2537) Component/s: Transactions (was: JTS) Fix Version/s: (was: 5.next) > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: WFLY-5703 > URL: https://issues.jboss.org/browse/WFLY-5703 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Optional > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5679) Classloading issue when running test by using both wildfly-arquillian-container-managed and jboss-as-arquillian-container-managed at the same time

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/WFLY-5679?page=com.atlassian.jira.plugin.... ] Matous Jobanek updated WFLY-5679: --------------------------------- Affects Version/s: 10.0.0.CR4 > Classloading issue when running test by using both wildfly-arquillian-container-managed and jboss-as-arquillian-container-managed at the same time > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5679 > URL: https://issues.jboss.org/browse/WFLY-5679 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.CR4 > Reporter: Matous Jobanek > Assignee: Jason Greene > Labels: arquillian > > When there is a test starting both containers WF9 and JBoss AS 7 (eg. for migration verification) the deployment and stopping of the containers don't behave correctly. To start both of the containers I need relevant container adapters: > - {{org.jboss.as:jboss-as-arquillian-container-managed}} > - {{org.wildfly.arquillian:wildfly-arquillian-container-managed (or org.wildfly:wildfly-arquillian-container-managed for WF8)}} > however, in the case of the WF's adapter the packages haven't been renamed (when there was the migration from the JBoss AS to WF, even though the maven artifact had been renamed). > The situation of using both of the artifacts leads to the situation that there are two Java classes with the very same name (eg. {{org.jboss.as.arquillian.container.managed.ManagedContainerExtension}}) and only one of them is used - the one that belongs to the artifact used as the first one there in the pom.xml file. > So, currently there is no easy way how to run two or more containers in a combination of WF8+ and JBoss AS 7 (and older). > This leads me to the main question - why the packages haven't been renamed after the migration to org.wildfly(.arquillian) ? Current situation is quite confusing and in some cases problematic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5141) Custom operation for setting of process-id-*

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5141?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5141: -------------------------------- Priority: Minor (was: Major) > Custom operation for setting of process-id-* > -------------------------------------------- > > Key: WFLY-5141 > URL: https://issues.jboss.org/browse/WFLY-5141 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Beta1 > Reporter: Ondřej Chaloupka > Assignee: Amos Feng > Priority: Minor > Labels: ux > > When you want to set generation of process-id-* - either as uuid or as socket id the way to set it and set it back is inconsistent. In one direction you need to use composite operation in other direction you can't use it. > All this is discussed in jiras WFLY-2623 and WFLY-5126 > As result of discussion https://issues.jboss.org/browse/WFLY-2623#comment-13100037 this issue is raised. > It would be much better for user to have single way how to do this switching and custom operation could solve this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5680) InfinispanBatchContext trying to resume committed tx

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5680?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5680: ------------------------------- Summary: InfinispanBatchContext trying to resume committed tx (was: InfinispanBatchContext trying to resume commited txn) > InfinispanBatchContext trying to resume committed tx > ---------------------------------------------------- > > Key: WFLY-5680 > URL: https://issues.jboss.org/browse/WFLY-5680 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Environment: Linux x86_64 > Reporter: Richard Achmatowicz > Assignee: Paul Ferraro > Priority: Critical > Attachments: resume-commited-txn-output.txt > > > When running the test case RemoteFailoverTestCase.testStatefulFailover, the test hangs due to an exception occurring. The exception is the following: > {noformat} > [31m11:24:05,814 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (EJB default - 3) ISPN000136: Execution error: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=47}, status=3} is not in a valid state to be invoking cache operations on. > {noformat} > This exception arose some time ago and was linked to incorrect suspend/resume of threads by the InfinispanBatching mechanism. This is just a suggestion as to what might be the root cause. > Attached is a log of the test case run with TRACE logging on DummyTransactionManager which coordinates the suspends and resumes. I have also performed a stack trace dump on every call to suspend and resume to highlight the origin of the call. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5680) InfinispanBatchContext trying to resume commited txn

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5680?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5680: ------------------------------- Priority: Critical (was: Major) > InfinispanBatchContext trying to resume commited txn > ---------------------------------------------------- > > Key: WFLY-5680 > URL: https://issues.jboss.org/browse/WFLY-5680 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Environment: Linux x86_64 > Reporter: Richard Achmatowicz > Assignee: Paul Ferraro > Priority: Critical > Attachments: resume-commited-txn-output.txt > > > When running the test case RemoteFailoverTestCase.testStatefulFailover, the test hangs due to an exception occurring. The exception is the following: > {noformat} > [31m11:24:05,814 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (EJB default - 3) ISPN000136: Execution error: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=47}, status=3} is not in a valid state to be invoking cache operations on. > {noformat} > This exception arose some time ago and was linked to incorrect suspend/resume of threads by the InfinispanBatching mechanism. This is just a suggestion as to what might be the root cause. > Attached is a log of the test case run with TRACE logging on DummyTransactionManager which coordinates the suspends and resumes. I have also performed a stack trace dump on every call to suspend and resume to highlight the origin of the call. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5686) InfinispanRegionFactory not registering externalizers used by Hibernate 5

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5686?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-5686. ------------------------------ Resolution: Rejected Actually, this is only an issue in Hibernate master, not 5.0. We will handle this within hibernate-infinispan via ModuleInitializer > InfinispanRegionFactory not registering externalizers used by Hibernate 5 > ------------------------------------------------------------------------- > > Key: WFLY-5686 > URL: https://issues.jboss.org/browse/WFLY-5686 > Project: WildFly > Issue Type: Bug > Components: Clustering, JPA / Hibernate > Affects Versions: 10.0.0.CR4 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Labels: clustering_performance > Fix For: 10.0.0.CR5 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1141) Operation ("clean-obsolete-content") failed NPE

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-1141: ----------------------------------------- Summary: Operation ("clean-obsolete-content") failed NPE Key: WFCORE-1141 URL: https://issues.jboss.org/browse/WFCORE-1141 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.2.Final Environment: Centos 6.7, OpenJDK 1.7, Wildfly 9.0.1.Final, nginx-plus Domain, Full-ha, 2 nodes, one war Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet NPE happens randomly knocking the instance off line and has to be restarted. [Server:server-one] 13:03:37,900 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 1) WFLYCTL0013: Operation ("clean-obsolete-content") failed - address: ([]): java.lang.NullPointerException [Server:server-one] at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.listLocalContents(ContentRepository.java:428) [Server:server-one] at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.cleanObsoleteContent(ContentRepository.java:390) [Server:server-one] at org.jboss.as.server.mgmt.domain.RemoteFileRepositoryService.cleanObsoleteContent(RemoteFileRepositoryService.java:160) [Server:server-one] at org.jboss.as.server.operations.CleanObsoleteContentHandler.execute(CleanObsoleteContentHandler.java:76) [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:803) [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) [Server:server-one] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1183) [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362) [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:205) [Server:server-one] at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:626) [Server:server-one] at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:616) [Server:server-one] at org.jboss.as.server.deployment.ContentRepositoryCleaner.cleanObsoleteContent(ContentRepositoryCleaner.java:132) [Server:server-one] at org.jboss.as.server.deployment.ContentRepositoryCleaner$ContentRepositoryCleanerTask.run(ContentRepositoryCleaner.java:67) [Server:server-one] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [Server:server-one] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [Server:server-one] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) [Server:server-one] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [Server:server-one] at java.lang.Thread.run(Thread.java:745) [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320) [Server:server-one] [Server:server-one] 13:03:37,931 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 1) WFLYSRV0216: Error cleaning obsolete content WFLYCTL0158: Operation handler failed: java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2015