June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-727) Some commands throws NPE on tab completion once disconnected

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-727?page=com.atlassian.jira.plugin... ] Petr Kremensky moved JBEAP-233 to WFCORE-727: --------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-727 (was: JBEAP-233) Workflow: GIT Pull Request workflow (was: CDW v1) Affects Version/s: 2.0.0.Alpha3 (was: EAP 7.0.0.DR2) Component/s: CLI (was: CLI) Target Release: (was: EAP 7.0.0.GA) > Some commands throws NPE on tab completion once disconnected > ------------------------------------------------------------ > > Key: WFCORE-727 > URL: https://issues.jboss.org/browse/WFCORE-727 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha3 > Reporter: Petr Kremensky > Assignee: Alexey Loubyansky > > Some commands throws NullPointerException when CLI is disconnected from controller and user tries to use tab completion (so far I found these: ls, read-attribute, read-operation). > No exception is thrown with 6.4.0.GA -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-726) Remove temporary code to make compatible with WF core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-726?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-726: ------------------------------ Description: Some temporary code is needed in core to preserve compatibility with Wildfly. This should be removed and WildFly should be adjusted once this is all in a core release. Similarly, some temporary code is needed in WildFly so it does not break when core is released. was:Some temporary code is needed in core to preserve compatibility with Wildfly. This should be removed and WildFly should be adjusted once this is all in a core release. > Remove temporary code to make compatible with WF core > ----------------------------------------------------- > > Key: WFCORE-726 > URL: https://issues.jboss.org/browse/WFCORE-726 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha4 > > > Some temporary code is needed in core to preserve compatibility with Wildfly. This should be removed and WildFly should be adjusted once this is all in a core release. > Similarly, some temporary code is needed in WildFly so it does not break when core is released. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3549) Deadlock during shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3549?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3549: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1213817|https://bugzilla.redhat.com/show_bug.cgi?id=1213817] from NEW to POST > Deadlock during shutdown > ------------------------ > > Key: WFLY-3549 > URL: https://issues.jboss.org/browse/WFLY-3549 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: David Lloyd > Fix For: 8.2.0.Final > > > This deadlock appeared in an Arquillian test: > {noformat} > Found one Java-level deadlock: > ============================= > "undefined": > waiting to lock monitor 0x00007f67a421bfa8 (object 0x00000000e0700480, a org.jboss.as.threads.ScheduledThreadPoolService), > which is held by "MSC service thread 1-2" > "MSC service thread 1-2": > waiting for ownable synchronizer 0x00000000e0700618, (a java.util.concurrent.locks.ReentrantLock$NonfairSync), > which is held by "undefined" > Java stack information for the threads listed above: > =================================================== > "undefined": > at org.jboss.as.threads.ScheduledThreadPoolService$ExecutorImpl.terminated(ScheduledThreadPoolService.java:121) > - waiting to lock <0x00000000e0700480> (a org.jboss.as.threads.ScheduledThreadPoolService) > at java.util.concurrent.ThreadPoolExecutor.tryTerminate(ThreadPoolExecutor.java:704) > at java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1006) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1163) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > "MSC service thread 1-2": > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000e0700618> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197) > at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214) > at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290) > at java.util.concurrent.ThreadPoolExecutor.interruptIdleWorkers(ThreadPoolExecutor.java:781) > at java.util.concurrent.ThreadPoolExecutor.tryTerminate(ThreadPoolExecutor.java:695) > at java.util.concurrent.ThreadPoolExecutor.shutdown(ThreadPoolExecutor.java:1397) > at java.util.concurrent.ScheduledThreadPoolExecutor.shutdown(ScheduledThreadPoolExecutor.java:759) > at org.jboss.as.threads.ManagedScheduledExecutorService.internalShutdown(ManagedScheduledExecutorService.java:53) > at org.jboss.as.threads.ScheduledThreadPoolService.stop(ScheduledThreadPoolService.java:67) > - locked <0x00000000e0700480> (a org.jboss.as.threads.ScheduledThreadPoolService) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Found 1 deadlock. > {noformat} > Looks like two MSC service threads exited and tried to terminate the thread pool at the same time. And because the MSC threads are not daemon threads, the entire JVM hangs and blocks the Arquillian test that was waiting for the container to shut down. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-726) Remove temporary code to make compatible with WF core

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-726: --------------------------------- Summary: Remove temporary code to make compatible with WF core Key: WFCORE-726 URL: https://issues.jboss.org/browse/WFCORE-726 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.0.0.Alpha4 Some temporary code is needed in core to preserve compatibility with Wildfly. This should be removed and WildFly should be adjusted once this is all in a core release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1929) Add a simple properties-based CallbackHandler for the SASL protocol

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1929?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1929: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1176161|https://bugzilla.redhat.com/show_bug.cgi?id=1176161] from MODIFIED to ON_QA > Add a simple properties-based CallbackHandler for the SASL protocol > ------------------------------------------------------------------- > > Key: JGRP-1929 > URL: https://issues.jboss.org/browse/JGRP-1929 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 3.6.4 > > > Add a properties-based CallbackHandler for the SASL protocol which supports a properties file for credentials and one for roles so that nodes can be authenticated and authorized in a simple way -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-801) Attempt to remove KnowledgePackage causes ClassCastException

by Tom Hartwell (JIRA)

[ https://issues.jboss.org/browse/DROOLS-801?page=com.atlassian.jira.plugin... ] Tom Hartwell updated DROOLS-801: -------------------------------- Attachment: class-cast-exception-trace-log.txt Adding trace log of JUnit run > Attempt to remove KnowledgePackage causes ClassCastException > ------------------------------------------------------------ > > Key: DROOLS-801 > URL: https://issues.jboss.org/browse/DROOLS-801 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.2.0.Final > Reporter: Tom Hartwell > Assignee: Mario Fusco > Attachments: class-cast-exception-trace-log.txt, ClassCastExceptionTest.java > > > Running the JUnit attached to this issue causes a Java ClassCastException -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-801) Attempt to remove KnowledgePackage causes ClassCastException

by Tom Hartwell (JIRA)

[ https://issues.jboss.org/browse/DROOLS-801?page=com.atlassian.jira.plugin... ] Tom Hartwell updated DROOLS-801: -------------------------------- Attachment: ClassCastExceptionTest.java Adding JUnit that causes failure > Attempt to remove KnowledgePackage causes ClassCastException > ------------------------------------------------------------ > > Key: DROOLS-801 > URL: https://issues.jboss.org/browse/DROOLS-801 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.2.0.Final > Reporter: Tom Hartwell > Assignee: Mario Fusco > Attachments: ClassCastExceptionTest.java > > > Running the JUnit attached to this issue causes a Java ClassCastException -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-801) Attempt to remove KnowledgePackage causes ClassCastException

by Tom Hartwell (JIRA)

Tom Hartwell created DROOLS-801: ----------------------------------- Summary: Attempt to remove KnowledgePackage causes ClassCastException Key: DROOLS-801 URL: https://issues.jboss.org/browse/DROOLS-801 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.2.0.Final Reporter: Tom Hartwell Assignee: Mario Fusco Running the JUnit attached to this issue causes a Java ClassCastException -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4549) Not possible to reload server when JTS transactions are active

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4549?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned WFLY-4549: ------------------------------------ Assignee: Ondřej Chaloupka (was: Tomasz Adamski) Fix Version/s: 9.0.0.CR2 Resolution: Done > Not possible to reload server when JTS transactions are active > -------------------------------------------------------------- > > Key: WFLY-4549 > URL: https://issues.jboss.org/browse/WFLY-4549 > Project: WildFly > Issue Type: Bug > Components: IIOP, Transactions > Affects Versions: 9.0.0.Beta2 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > Fix For: 9.0.0.CR2 > > > Reloading WFLY server with active JTS transactions fails. > I have tried to run reload operation just after server started and when some attribute which needs reload was changed (e.g. {{/subsystem=datasources/data-source=ExampleDS:write-attribute(name=spy, value=true)}}) and in both cases server was started with errors > {code} > WARN [com.arjuna.ats.jts] (MSC service thread 1-4) ARJUNA022083: JacOrbRCServiceInit - Failed to start RC service: java.lang.NullPointerException > at com.sun.corba.se.impl.orb.ORBImpl.checkShutdownState(ORBImpl.java:1329) > at com.sun.corba.se.impl.orb.ORBImpl.getCorbaContactInfoListFactory(ORBImpl.java:1889) > at com.sun.corba.se.impl.orbutil.ORBUtility.makeClientDelegate(ORBUtility.java:678) > at com.sun.corba.se.impl.orbutil.ORBUtility.makeObjectReference(ORBUtility.java:687) > at com.sun.corba.se.impl.ior.ObjectReferenceProducerBase.make_object(ObjectReferenceProducerBase.java:60) > at com.sun.corba.se.spi.oa.ObjectAdapterBase.makeObject(ObjectAdapterBase.java:142) > at com.sun.corba.se.impl.oa.poa.POAImpl.create_reference_with_id(POAImpl.java:1353) > at com.arjuna.ats.internal.jts.orbspecific.javaidl.recoverycoordinators.JavaIdlRCServiceInit.startRCservice(JavaIdlRCServiceInit.java:195) > at com.arjuna.ats.internal.jts.orbspecific.recovery.RecoveryEnablement.startRCservice(RecoveryEnablement.java:141) > at com.arjuna.ats.internal.arjuna.recovery.RecActivatorLoader.startRecoveryActivators(RecActivatorLoader.java:66) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:102) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.initialize(RecoveryManager.java:226) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.start(RecoveryManagerService.java:65) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:145) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:148) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: ARJUNA012364: RecoveryActivator init failed for com.arjuna.ats.internal.jts.orbspecific.recovery.RecoveryEnablement > at com.arjuna.ats.internal.arjuna.recovery.RecActivatorLoader.startRecoveryActivators(RecActivatorLoader.java:67) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:102) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.initialize(RecoveryManager.java:226) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.start(RecoveryManagerService.java:65) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:145) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4548) Error messages on server shutdown when JTS is used

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4548?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFLY-4548: --------------------------------- Fix Version/s: 9.0.0.CR2 > Error messages on server shutdown when JTS is used > -------------------------------------------------- > > Key: WFLY-4548 > URL: https://issues.jboss.org/browse/WFLY-4548 > Project: WildFly > Issue Type: Bug > Components: IIOP, Transactions > Affects Versions: 9.0.0.Beta2 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > Fix For: 9.0.0.CR2 > > > During time of shutting down WFLY server when JTS transactions are enabled I experience these two [1] [2] errors/exceptions being shown in server log/console. > The first one [1] is shown each time when JTS is configured and server is put to be stopped. > The second one [2] is intermittent and probably it could be shown when JTA is under use as well. > [1] > {code} > WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (Thread-84) "IOP01210228: (BAD_OPERATION) This ORB instance has been destroyed, so no operations can be performed on it": org.omg.CORBA.BAD_OPERATION: vmcid: SUN minor code: 228 completed: No > at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbDestroyed(ORBUtilSystemException.java:586) > at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbDestroyed(ORBUtilSystemException.java:608) > at com.sun.corba.se.impl.orb.ORBImpl.checkShutdownState(ORBImpl.java:1329) > at com.sun.corba.se.impl.orb.ORBImpl.isDuringDispatch(ORBImpl.java:1340) > at com.sun.corba.se.impl.oa.poa.POAImpl.destroy(POAImpl.java:959) > at com.arjuna.orbportability.internal.orbspecific.oa.implementations.POABase.destroyRootPOA(POABase.java:68) > at com.arjuna.orbportability.oa.core.OA.destroyRootPOA(OA.java:97) > at com.arjuna.orbportability.RootOA.destroy(RootOA.java:91) > at com.arjuna.ats.internal.jts.orbspecific.javaidl.recoverycoordinators.ORBRunner.run(ORBRunner.java:59) > {code} > [2] > {code} > INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-5) ARJUNA032018: Destroying TransactionManagerService > INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032014: Stopping transaction recovery manager > ERROR [stderr] (Thread-98) Exception in thread "Thread-98" java.lang.NullPointerException > ERROR [stderr] (Thread-98) at com.sun.corba.se.impl.oa.poa.POAImpl$DestroyThread.run(POAImpl.java:566) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2015