[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)
9 years, 11 months
[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)
9 years, 11 months
[JBoss JIRA] (WFLY-3205) For xa-datasource testConnection should account for deployment classloader
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3205?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3205:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1083457|https://bugzilla.redhat.com/show_bug.cgi?id=1083457] from POST to MODIFIED
> For xa-datasource testConnection should account for deployment classloader
> --------------------------------------------------------------------------
>
> Key: WFLY-3205
> URL: https://issues.jboss.org/browse/WFLY-3205
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.1.0.CR1
> Environment: All
> Reporter: Jay Kumar SenSharma
> Assignee: Jay Kumar SenSharma
> Fix For: 8.1.0.Final
>
>
> - The fix mentioned in https://issues.jboss.org/browse/WFLY-2047 is resolves the issue for plain Non-XA dataSources. However if an XA-DataSource is configured with the "ldap" based database connection URL then it fails with the following Error:
> {code}
> 13:49:41,399 ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: java:/OracleXA_DS (Could not create connection): javax.resource.ResourceException: Could not create connection
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:461)
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:398)
> at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.open(XAResourceRecoveryImpl.java:343)
> at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:170)
> at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [narayana-jts-integration-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:516) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> Caused by: java.sql.SQLRecoverableException: Io exception: JNDI Package failurejavax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.jboss.jts:main" from local module loader @3b70c (finder: local module finder @1e6a820 (roots: /home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules,/home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory from [Module "org.jboss.jts:main" from local module loader @3b70c (finder: local module finder @1e6a820 (roots: /home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules,/home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base))]]
> at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101)
> at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:458)
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411)
> at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:490)
> at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:202)
> at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:474)
> at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:275)
> at oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:454)
> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:159)
> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:130)
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:444)
> ... 8 morec
> {code}
> - The XA dataSource configuration looks like following:
> {code}
> <subsystem xmlns="urn:jboss:domain:datasources:2.0">
> <datasources>
> <xa-datasource jndi-name="java:/OracleXA_DS" pool-name="OracleXA_DS" enabled="true">
> <xa-datasource-property name="ServerName">
> example.com
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> TestDB
> </xa-datasource-property>
> <xa-datasource-property name="URL">
> jdbc:oracle:thin:@ldap://example.com:3060/test,cn=OracleA,dc=worldA
> </xa-datasource-property>
> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
> <driver>oracle</driver>
> <security>
> <user-name>jboss</user-name>
> <password>jboss</password>
> </security>
> </xa-datasource>
> <drivers>
> <driver name="oracle" module="com.oracle.jdbc6"/>
> </drivers>
> </datasources>
> </subsystem>
> {code}
> - When the above datasource is tested via CLI like following then aht above mentioned error is noticed:
> {code}
> /subsystem=datasources/xa-data-source=OracleXA_DS:test-connection-in-pool
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months