November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1748) Change size of printed views dynamically

by Bela Ban (JIRA)

Bela Ban created JGRP-1748: ------------------------------ Summary: Change size of printed views dynamically Key: JGRP-1748 URL: https://issues.jboss.org/browse/JGRP-1748 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.5 Currently, when a view or digest is longer than Util.MAX_LIST_PRINT_SIZE (20 by default) elements, we don't print the entire list, but only the first 20 elements, followed by an ellipsis. Util.MAX_LIST_PRINT_SIZE is defined via system prop "max.list.print_size". Use probe / JMX to dynamically change the value of Util.MAX_LIST_PRINT_SIZE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1747) Diagnostics: provide managed operation to start/stop diagnostics

by Bela Ban (JIRA)

Bela Ban created JGRP-1747: ------------------------------ Summary: Diagnostics: provide managed operation to start/stop diagnostics Key: JGRP-1747 URL: https://issues.jboss.org/browse/JGRP-1747 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.5 Provide methods to start and stop the DiagnosticsHandler in TP, e.g. via JMX or byteman. This allows for delivery of a system with diagnostics disabled, and to dynamically enable it at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1746) Diagnostics: reset stats in all protocols

by Bela Ban (JIRA)

Bela Ban created JGRP-1746: ------------------------------ Summary: Diagnostics: reset stats in all protocols Key: JGRP-1746 URL: https://issues.jboss.org/browse/JGRP-1746 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Trivial Fix For: 3.5 Add a key to probe.sh (e.g. reset-all-stats) which calls resetStats() in all protocols, plus the channel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2587) ManagedServerBootCmdFactory alters system property values

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2587: -------------------------------------- Summary: ManagedServerBootCmdFactory alters system property values Key: WFLY-2587 URL: https://issues.jboss.org/browse/WFLY-2587 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.0.CR1 When ManagedServerBootCmdFactory iterates through system properties to use in the server launch command it adds a value of "true" for any properties that have no value. This is incorrect. In particular it breaks SecurityManager usage as -Djava.security.manager is a valid setting while -Djava.security.manager=true will result in [Host Controller] 15:09:01,758 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-one 15:10:55,691 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-one' [Server:server-one] Error occurred during initialization of VM [Server:server-one] java.lang.InternalError: Could not create SecurityManager: true [Server:server-one] at sun.misc.Launcher.<init>(Launcher.java:106) [Server:server-one] at sun.misc.Launcher.<clinit>(Launcher.java:57) [Server:server-one] at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1486) [Server:server-one] at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1468) [Server:server-one] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2585) Correct the identification of the current caller when a security manager is enabled.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2585?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2585: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1034700, https://bugzilla.redhat.com/show_bug.cgi?id=1035231 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1034700, https://bugzilla.redhat.com/show_bug.cgi?id=1035231, https://bugzilla.redhat.com/show_bug.cgi?id=1035232) > Correct the identification of the current caller when a security manager is enabled. > ------------------------------------------------------------------------------------ > > Key: WFLY-2585 > URL: https://issues.jboss.org/browse/WFLY-2585 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2561) Subdeployment DeploymentUnitPhaseService.INSTALL and WeldStartService dependency deadlock resulting in failed EAR deployments

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2561?page=com.atlassian.jira.plugin.... ] Eduardo Martins reopened WFLY-2561: ----------------------------------- > Subdeployment DeploymentUnitPhaseService.INSTALL and WeldStartService dependency deadlock resulting in failed EAR deployments > ----------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2561 > URL: https://issues.jboss.org/browse/WFLY-2561 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 8.0.0.CR1 > > > In case of EARs with multiple subdeployments, a msc service dependency deadlock may occurs between a subdeployment's DeploymentUnitPhaseService at INSTALL phase, and WeldStartService. This happens because WeldStartService depends on each subdeployment's jndiDependencyService. Such dependency may conflict with a subdeployment's DeploymentUnitPhaseService at INSTALL to complete, and the EAR deployment ultimately fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2272) component upgrade to Hibernate ORM 4.3.0.CR2

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2272?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-2272: ------------------------------------ CCE no longer occurs due to Hibernate ORM working around it. > component upgrade to Hibernate ORM 4.3.0.CR2 > -------------------------------------------- > > Key: WFLY-2272 > URL: https://issues.jboss.org/browse/WFLY-2272 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2272) component upgrade to Hibernate ORM 4.3.0.CR2

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2272?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-2272: ------------------------------- Summary: component upgrade to Hibernate ORM 4.3.0.CR2 (was: component upgrade to Hibernate ORM 4.3.0.Beta6) > component upgrade to Hibernate ORM 4.3.0.CR2 > -------------------------------------------- > > Key: WFLY-2272 > URL: https://issues.jboss.org/browse/WFLY-2272 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-835) @Resource UserTransaction error when file passivation store is selected

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-835?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on WFLY-835: ----------------------------------- There is a currently @Ignored test case for this here: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/clus... > @Resource UserTransaction error when file passivation store is selected > ----------------------------------------------------------------------- > > Key: WFLY-835 > URL: https://issues.jboss.org/browse/WFLY-835 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Environment: Ubuntu 11.10, Intel® Core™ i3-2120 CPU @ 3.30GHz × 4 > Reporter: Abraham Cabanillas Piera > Assignee: David Lloyd > Priority: Critical > Labels: jboss > > The following exception is launched when the server tries to passivate into the file passivation storage a stateful EJB session with UserTransaction injected as a resource: > {noformat} > [org.jboss.as.ejb3.cache.spi.impl.PassivateTask] (pool-10-thread-1) JBAS014538: Failed to passivate {[-36, 0, 14, -43, 72, 10, 76, -28, -105, -108, 24, 45, -70, -58, -48, -107]}: java.lang.RuntimeException: JBAS014538: Failed to passivate {[-36, 0, 14, -43, 72, 10, 76, -28, -105, -108, 24, 45, -70, -58, -48, -107]} > at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:248) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:52) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.cache.impl.backing.SimpleBackingCacheEntryStore.passivate(SimpleBackingCacheEntryStore.java:155) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.passivate(SerializationGroupMemberContainer.java:288) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.passivate(SerializationGroupMemberContainer.java:50) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:60) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.ejb3.cache.spi.impl.PassivateTask.run(PassivateTask.java:45) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_13] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_13] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_13] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [rt.jar:1.7.0_13] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.io.NotSerializableException: org.jboss.tm.usertx.client.ServerVMClientUserTransaction > at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:891) > at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019) > at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885) > at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019) > at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885) > at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019) > at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885) > at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:69) > at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:60) > at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:54) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342) [rt.jar:1.7.0_13] > at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberImpl.writeObject(SerializationGroupMemberImpl.java:368) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_13] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_13] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_13] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_13] > at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:175) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1007) > at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885) > at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62) > at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119) > at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:239) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final] > ... 15 more > Caused by: an exception which occurred: > in field userTransaction > in field instance > in field instance > in object org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberImpl@6a4de0c9 > {noformat} > The EJB subsystem configuration is: > {code:xml} > <subsystem xmlns="urn:jboss:domain:ejb3:1.2"> > <session-bean> > <stateless> > <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/> > </stateless> > <stateful default-access-timeout="10000" cache-ref="passivating"/> > <singleton default-access-timeout="5000"/> > </session-bean> > <mdb> > <resource-adapter-ref resource-adapter-name="hornetq-ra"/> > <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> > </mdb> > <pools> > <bean-instance-pools> > <strict-max-pool name="slsb-strict-max-pool" max-pool-size="50" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> > <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> > </bean-instance-pools> > </pools> > <caches> > <cache name="simple" aliases="NoPassivationCache"/> > <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/> > </caches> > <passivation-stores> > <file-passivation-store name="file" idle-timeout="10" idle-timeout-unit="SECONDS"/> > </passivation-stores> > <async thread-pool-name="default"/> > <timer-service thread-pool-name="default"> > <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/> > </timer-service> > <remote connector-ref="remoting-connector" thread-pool-name="default"/> > <thread-pools> > <thread-pool name="default"> > <max-threads count="100"/> > <keepalive-time time="100" unit="milliseconds"/> > </thread-pool> > </thread-pools> > <iiop enable-by-default="false" use-qualified-name="false"/> > </subsystem> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2488) Adding a datasource fails in a composite operation

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2488?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-2488: ------------------------------------- Maybe it's changed, but at one point a data source needed to be enabled after it was added. The {{enabled}} attribute didn't seem to have an affect. > Adding a datasource fails in a composite operation > -------------------------------------------------- > > Key: WFLY-2488 > URL: https://issues.jboss.org/browse/WFLY-2488 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: James Perkins > Assignee: Stefano Maestri > Attachments: wfly2488-sources.jar, wfly2488.jar > > > Executing a composite operation fails when adding a datasource. > Stack Trace: > {code} > 08:38:49,787 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) JBAS014612: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "ds-test") > ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source-config.ds-test is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2384) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:1422) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.connector.subsystems.datasources.DataSourceEnable.addServices(DataSourceEnable.java:188) > at org.jboss.as.connector.subsystems.datasources.DataSourceEnable$1.execute(DataSourceEnable.java:84) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:609) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:487) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:258) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:143) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:205) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:110) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$2.run(ModelControllerClientOperationHandler.java:157) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$2.run(ModelControllerClientOperationHandler.java:153) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_45] > at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_45] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [wildfly-protocol-8.0.0.Beta1.jar:8.0.0.Beta1] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [wildfly-protocol-8.0.0.Beta1.jar:8.0.0.Beta1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 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 November 2013