November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-121) Ensure anonymous authentication will only be used if a callback handler has not been specified and no credentials have been provided

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/REMJMX-121?page=com.atlassian.jira.plugin... ] Farah Juma resolved REMJMX-121. ------------------------------- Fix Version/s: 3.0.0.Alpha3 Resolution: Done > Ensure anonymous authentication will only be used if a callback handler has not been specified and no credentials have been provided > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: REMJMX-121 > URL: https://issues.jboss.org/browse/REMJMX-121 > Project: Remoting JMX > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 3.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-707) PeerIdentity should not be wrapping RuntimeException(s) with PrivilegedActionException(s)

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-707: ------------------------------------ Summary: PeerIdentity should not be wrapping RuntimeException(s) with PrivilegedActionException(s) Key: ELY-707 URL: https://issues.jboss.org/browse/ELY-707 Project: WildFly Elytron Issue Type: Bug Components: API / SPI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta13 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5227) Move security-manager subsystem from WildFly to WildFly Core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-5227?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFLY-5227: --------------------------------- After a chat with Darran and Kabir, we're looking at doing this in the 2nd week or so of November. > Move security-manager subsystem from WildFly to WildFly Core > ------------------------------------------------------------ > > Key: WFLY-5227 > URL: https://issues.jboss.org/browse/WFLY-5227 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Reporter: Josef Cacek > Assignee: Ken Wills > Priority: Critical > > It's not possible to define security permissions in WildFly Core without {{security-manager}} subsystem. Therefore the subsystem should be moved from WildFly to the Core. > More details in the [Permissions in WildFly Core|http://lists.jboss.org/pipermail/wildfly-dev/2015-August/thread.html...] thread on {{wildfly-dev}} mailing list. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-835?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-835: ---------------------------------------------- Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1235886|https://bugzilla.redhat.com/show_bug.cgi?id=1235886] from MODIFIED to ON_QA > @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 > Components: EJB > Affects Versions: 9.0.0.CR2 > Environment: Ubuntu 11.10, Intel® Core™ i3-2120 CPU @ 3.30GHz × 4 > Reporter: Abraham Cabanillas Piera > Assignee: Michael Musgrove > Priority: Critical > Labels: jboss > Fix For: 11.0.0.Alpha1 > > Attachments: serializationerr_server.log > > > 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 was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6214) Change CMTTxInterceptor.endTransaction() handling of Status.ROLLING_BACK

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6214?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6214: ----------------------------------------------- Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1387319|https://bugzilla.redhat.com/show_bug.cgi?id=1387319] from MODIFIED to ON_QA > Change CMTTxInterceptor.endTransaction() handling of Status.ROLLING_BACK > ------------------------------------------------------------------------ > > Key: WFLY-6214 > URL: https://issues.jboss.org/browse/WFLY-6214 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 10.1.0.CR1, 10.1.0.Final > > > See recent comment [https://developer.jboss.org/message/950898#950898] > {quote} > Status.STATUS_COMMITTING: > Status.STATUS_COMMITTED: > Status.STATUS_PREPARED: > Status.STATUS_PREPARING: > * Someone has called commit in parallel and the transaction is trying to commit so try to commit too: call tm.commit > {quote} > I think that TimerCMTTxInterceptor/LifecycleCMTTxInterceptor are using CMTTxInterceptor.endTransaction(), so they shouldn't need changes. > Status.STATUS_ROLLING_BACK can happen if the reaper has started to rollback the transaction -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-920) Add a management subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-920?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-920: --------------------------------------- Assignee: Jeff Mesnil (was: Darran Lofthouse) I'm reassigning this as Jeff is actually creating a subsystem. > Add a management subsystem > -------------------------- > > Key: WFCORE-920 > URL: https://issues.jboss.org/browse/WFCORE-920 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Jeff Mesnil > Labels: affects_elytron > > As subsystems can also be defined in a host controller we can now move the management configuration into a subsystem, legacy resources however such as security realms can be omitted. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-122) Upgrade to WildFly Elytron 1.1.0.Beta12

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-122?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-122. ------------------------------------- Resolution: Done > Upgrade to WildFly Elytron 1.1.0.Beta12 > --------------------------------------- > > Key: REMJMX-122 > URL: https://issues.jboss.org/browse/REMJMX-122 > Project: Remoting JMX > Issue Type: Component Upgrade > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-123) Configure the JBOSS_LOCAL_USER mechanism for silent authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-123?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-123. ------------------------------------- Resolution: Done > Configure the JBOSS_LOCAL_USER mechanism for silent authentication > ------------------------------------------------------------------ > > Key: REMJMX-123 > URL: https://issues.jboss.org/browse/REMJMX-123 > Project: Remoting JMX > Issue Type: Bug > Components: Tests > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-123) Configure the JBOSS_LOCAL_USER mechanism for silent authentication

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-123: --------------------------------------- Summary: Configure the JBOSS_LOCAL_USER mechanism for silent authentication Key: REMJMX-123 URL: https://issues.jboss.org/browse/REMJMX-123 Project: Remoting JMX Issue Type: Bug Components: Tests Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha3 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-122) Upgrade to WildFly Elytron 1.1.0.Beta12

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-122: --------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta12 Key: REMJMX-122 URL: https://issues.jboss.org/browse/REMJMX-122 Project: Remoting JMX Issue Type: Component Upgrade Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha3 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 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 2016