June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3443) JCA "tracking" should default to false

by Scott Marlow (JIRA)

Scott Marlow created WFLY-3443: ---------------------------------- Summary: JCA "tracking" should default to false Key: WFLY-3443 URL: https://issues.jboss.org/browse/WFLY-3443 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA Reporter: Scott Marlow Assignee: Jesper Pedersen Fix For: 9.0.0.Alpha1 The [txtracking|http://www.ironjacamar.org/doc/roadto12/txtracking.html] feature is causing failures when IronJacamar closes the database connection in a Synchronization.afterCompletion() when a Hibernate Synchronization.afterCompletion() call already closed the connection. See attached server.log for example of "IJ000315: Pool cts-derby-pool has 1 active handles" error. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-837) Release JBoss Negotiation 2.3.3.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-837?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-837: -------------------------------------- Fix Version/s: Negotiation_2_3_4_Final (was: Negotiation_2_3_3_Final) > Release JBoss Negotiation 2.3.3.Final > ------------------------------------- > > Key: SECURITY-837 > URL: https://issues.jboss.org/browse/SECURITY-837 > Project: PicketBox > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_4_Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-837) Release JBoss Negotiation 2.3.3.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-837: ----------------------------------------- Summary: Release JBoss Negotiation 2.3.3.Final Key: SECURITY-837 URL: https://issues.jboss.org/browse/SECURITY-837 Project: PicketBox Issue Type: Release Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_3_3_Final -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-836) AdvancedLdapLoginModule querying too many attributes.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-836?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-836. --------------------------------------- Resolution: Done > AdvancedLdapLoginModule querying too many attributes. > ----------------------------------------------------- > > Key: SECURITY-836 > URL: https://issues.jboss.org/browse/SECURITY-836 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_3_2_Final > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Fix For: Negotiation_2_3_3_Final > > > During the roles search all attributes are being queried instead of the small subset actually required. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-836) AdvancedLdapLoginModule querying too many attributes.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-836?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-836: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1086787 > AdvancedLdapLoginModule querying too many attributes. > ----------------------------------------------------- > > Key: SECURITY-836 > URL: https://issues.jboss.org/browse/SECURITY-836 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_3_2_Final > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Fix For: Negotiation_2_3_3_Final > > > During the roles search all attributes are being queried instead of the small subset actually required. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3442) Move Java EE API Deps out of JavaEEDependencyProcessor and into subsystem DUPS

by John Doyle (JIRA)

John Doyle created WFLY-3442: -------------------------------- Summary: Move Java EE API Deps out of JavaEEDependencyProcessor and into subsystem DUPS Key: WFLY-3442 URL: https://issues.jboss.org/browse/WFLY-3442 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Reporter: John Doyle Assignee: Jason Greene Fix For: 9.0.0.Alpha1 This allows for a subsystem removal/exclusion to remove the API it brings with it. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-836) AdvancedLdapLoginModule querying too many attributes.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-836?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-836: -------------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > AdvancedLdapLoginModule querying too many attributes. > ----------------------------------------------------- > > Key: SECURITY-836 > URL: https://issues.jboss.org/browse/SECURITY-836 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_3_2_Final > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Fix For: Negotiation_2_3_3_Final > > > During the roles search all attributes are being queried instead of the small subset actually required. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-836) AdvancedLdapLoginModule querying too many attributes.

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-836: ----------------------------------------- Summary: AdvancedLdapLoginModule querying too many attributes. Key: SECURITY-836 URL: https://issues.jboss.org/browse/SECURITY-836 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2_3_2_Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_3_3_Final During the roles search all attributes are being queried instead of the small subset actually required. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-835) Release JBoss Negotiation 2.3.2.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-835?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-835: -------------------------------------- Fix Version/s: Negotiation_2_3_2_Final (was: Negotiation_2_3_3_Final) > Release JBoss Negotiation 2.3.2.Final > ------------------------------------- > > Key: SECURITY-835 > URL: https://issues.jboss.org/browse/SECURITY-835 > Project: PicketBox > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_2_Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBFORUMS-305) No Jboss Cache bridge between 2 clusterd Jboss nodes on JBoss 5.1.0.GA

by Manek Kooner (JIRA)

Manek Kooner created JBFORUMS-305: ------------------------------------- Summary: No Jboss Cache bridge between 2 clusterd Jboss nodes on JBoss 5.1.0.GA Key: JBFORUMS-305 URL: https://issues.jboss.org/browse/JBFORUMS-305 Project: JBoss Forums Issue Type: Bug Components: Documentation Environment: Jboss 1.5 Reporter: Manek Kooner Assignee: Luca Stancapiano Hi, I am using Jboss cache on 2 clustered nodes i.e. 111.111.111.111 and 222.222.222.222 IP's in STAR-CACHE-CLUSTER. If I change anything in either of the nodes, then jboss cahe should replicate the change to the other node. But, this is happening only 1 time. In the below log, you can see that the bridge is established between the 2 nodes initially. Then we are getting "No bridge info was associated with this node" and finally "RMI TCP Connection(1)-222.222.222.222: (port 1501) connection closed". Any idea why the connection is closing, and the bridge does not work. Nothing has been changed in the code in this regards. Using JBoss 5.1.0.GA. 2014-04-18 11:44:13,239 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.STAR-CACHE-CLUSTER] New cluster view for partition STAR-CACHE-CLUSTER (id: 1, delta: 1) : [111.111.111.111:1499, 222.222.222.222:2599] 2014-04-18 11:44:13,239 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.STAR-CACHE-CLUSTER] I am (111.111.111.111:1499) received membershipChanged event: 2014-04-18 11:44:13,239 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.STAR-CACHE-CLUSTER] Dead members: 0 ([]) 2014-04-18 11:44:13,239 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.STAR-CACHE-CLUSTER] New Members : 1 ([222.222.222.222:2599]) 2014-04-18 11:44:13,239 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.STAR-CACHE-CLUSTER] All Members : 2 ([111.111.111.111:1499, 222.222.222.222:2599]) 2014-04-18 11:44:13,270 DEBUG [org.jboss.cache.RPCManagerImpl] Block received at 111.111.111.111:53972 2014-04-18 11:44:13,270 DEBUG [org.jboss.cache.RPCManagerImpl] Block processed at 111.111.111.111:53972 2014-04-18 11:44:13,270 INFO [org.jboss.cache.RPCManagerImpl] Received new cluster view: [111.111.111.111:53972|1] [111.111.111.111:53972, 222.222.222.222:59090] 2014-04-18 11:44:13,286 DEBUG [org.jboss.cache.statetransfer.DefaultStateTransferManager] locking the / subtree to return the in-memory (transient) state 2014-04-18 11:44:13,286 DEBUG [org.jboss.cache.statetransfer.DefaultStateTransferManager] Successfully generated state in 0 milliseconds 2014-04-18 11:44:13,317 DEBUG [org.jboss.cache.RPCManagerImpl] UnBlock received at 111.111.111.111:53972 2014-04-18 11:44:13,317 DEBUG [org.jboss.cache.RPCManagerImpl] UnBlock processed at 111.111.111.111:53972 2014-04-18 11:44:13,364 FINE [sun.rmi.transport.tcp] RMI TCP Connection(1)-222.222.222.222: accepted socket from [222.222.222.222:57913] 2014-04-18 11:44:13,364 FINE [sun.rmi.transport.tcp] RMI TCP Connection(1)-222.222.222.222: (port 1501) op = 80 2014-04-18 11:44:13,380 FINE [sun.rmi.loader] RMI TCP Connection(1)-222.222.222.222: name = "[Ljava.rmi.server.ObjID;", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@1a45a877 2014-04-18 11:44:13,380 FINE [sun.rmi.loader] RMI TCP Connection(1)-222.222.222.222: name = "java.rmi.server.ObjID", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@1a45a877 2014-04-18 11:44:13,380 FINE [sun.rmi.loader] RMI TCP Connection(1)-222.222.222.222: name = "java.rmi.server.UID", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@1a45a877 2014-04-18 11:44:13,380 FINE [sun.rmi.loader] RMI TCP Connection(1)-222.222.222.222: name = "java.rmi.dgc.Lease", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@1a45a877 2014-04-18 11:44:13,380 FINE [sun.rmi.loader] RMI TCP Connection(1)-222.222.222.222: name = "java.rmi.dgc.VMID", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@1a45a877 2014-04-18 11:44:13,380 FINE [sun.rmi.loader] RMI TCP Connection(1)-222.222.222.222: name = "[B", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@1a45a877 2014-04-18 11:44:13,426 DEBUG [org.jboss.cache.invalidation.bridges.JGCacheInvalidationBridge] The list of replicants for the JG bridge has changed, computing and updating local info... 2014-04-18 11:44:13,426 DEBUG [org.jboss.cache.invalidation.bridges.JGCacheInvalidationBridge] ... No bridge info was associated with this node 2014-04-18 11:44:13,442 FINE [sun.rmi.client.ref] Incoming-8,111.111.111.111:53972: get connection 2014-04-18 11:44:13,442 FINE [sun.rmi.transport.tcp] Incoming-8,111.111.111.111:53972: create connection 2014-04-18 11:44:13,442 FINE [sun.rmi.transport.tcp.proxy] Incoming-8,111.111.111.111:53972: host: PTA-TESTVM10, port: 2601 2014-04-18 11:44:13,442 FINE [sun.rmi.loader] Incoming-8,111.111.111.111:53972: name = "java.rmi.dgc.Lease", codebase = "", defaultLoader = BaseClassLoader@584ba778{vfsfile:/D:/jboss-5.1.0.GA/server/STAR/conf/jboss-service.xml} 2014-04-18 11:44:13,442 FINE [sun.rmi.loader] Incoming-8,111.111.111.111:53972: name = "java.rmi.dgc.VMID", codebase = "", defaultLoader = BaseClassLoader@584ba778{vfsfile:/D:/jboss-5.1.0.GA/server/STAR/conf/jboss-service.xml} 2014-04-18 11:44:13,442 FINE [sun.rmi.loader] Incoming-8,111.111.111.111:53972: name = "[B", codebase = "", defaultLoader = BaseClassLoader@584ba778{vfsfile:/D:/jboss-5.1.0.GA/server/STAR/conf/jboss-service.xml} 2014-04-18 11:44:13,442 FINE [sun.rmi.loader] Incoming-8,111.111.111.111:53972: name = "java.rmi.server.UID", codebase = "", defaultLoader = BaseClassLoader@584ba778{vfsfile:/D:/jboss-5.1.0.GA/server/STAR/conf/jboss-service.xml} 2014-04-18 11:44:13,442 FINE [sun.rmi.client.ref] Incoming-8,111.111.111.111:53972: free connection (reuse = true) 2014-04-18 11:44:13,442 FINE [sun.rmi.transport.tcp] Incoming-8,111.111.111.111:53972: reuse connection 2014-04-18 11:44:13,442 FINE [sun.rmi.transport.tcp] Incoming-8,111.111.111.111:53972: create reaper 2014-04-18 11:44:13,442 DEBUG [org.jboss.cache.invalidation.bridges.JGCacheInvalidationBridge] The list of replicants for the JG bridge has changed, computing and updating local info... 2014-04-18 11:44:13,442 DEBUG [org.jboss.cache.invalidation.bridges.JGCacheInvalidationBridge] ... No bridge info was associated with this node 2014-04-18 11:44:28,395 FINE [sun.rmi.transport.tcp] RMI TCP Connection(1)-222.222.222.222: (port 1501) connection closed 2014-04-18 11:44:28,395 FINE [sun.rmi.transport.tcp] RMI TCP Connection(1)-222.222.222.222: close connection 2014-04-18 11:44:28,458 FINE [sun.rmi.transport.tcp] RMI Scheduler(0): close connection -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

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 June 2014