June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3434) Add xsd schemas on wildlfy.org

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3434?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3434: ------------------------------ Description: we should have all wildfly releated schemas to wildfly.org/schema. As part of this task, we need to update all docs to point to new URL. have as much automated as possible process for uploading new schemas when new releases is done. consolidate this over various (sub)projects that provide schemas that should be here. What is not expected to be done is to host all old schemas that have nothing do do with WildFly on new location. Example are most of pre AS7 jboss specific descriptors that WildFly no longer honors. was:we should have all wildfly releated schemas to wildfly.org/schema > Add xsd schemas on wildlfy.org > ------------------------------ > > Key: WFLY-3434 > URL: https://issues.jboss.org/browse/WFLY-3434 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 9.0.0.Alpha1 > > > we should have all wildfly releated schemas to wildfly.org/schema. > As part of this task, we need to update all docs to point to new URL. > have as much automated as possible process for uploading new schemas when new releases is done. > consolidate this over various (sub)projects that provide schemas that should be here. > What is not expected to be done is to host all old schemas that have nothing do do with WildFly on new location. > Example are most of pre AS7 jboss specific descriptors that WildFly no longer honors. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3441) Upgrade to JBoss Negotiation 2.3.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3441?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3441: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1104269|https://bugzilla.redhat.com/show_bug.cgi?id=1104269] from ON_QA to VERIFIED > Upgrade to JBoss Negotiation 2.3.3.Final > ---------------------------------------- > > Key: WFLY-3441 > URL: https://issues.jboss.org/browse/WFLY-3441 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3014) jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3014?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-3014: --------------------------------- Assignee: Tomaz Cerar (was: Jason Greene) > jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd > --------------------------------------------------------------------------------- > > Key: WFLY-3014 > URL: https://issues.jboss.org/browse/WFLY-3014 > Project: WildFly > Issue Type: Documentation > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Environment: Not applicable > Reporter: Ray DeCampo > Assignee: Tomaz Cerar > Priority: Minor > Labels: xml, xml_schema > > The docs/schema/jboss-web_8_0.xsd file included with WildFly 8.0.0.Final indicates that the schema location is http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd. However, that URI does not return the schema file but a 404 instead (see http://www.jboss.org/j2ee/schema/ for a listing of the files there). > The file should be hosted where the schema document indicates or the schema should be updated to reflect the proper URI of the schema. Without it third party tools cannot assist in ensuring that the XML is well-formed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3472) JBOSS_HOME is not available in domain.conf

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3472?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3472: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1083474|https://bugzilla.redhat.com/show_bug.cgi?id=1083474] from NEW to ASSIGNED > JBOSS_HOME is not available in domain.conf > ------------------------------------------- > > Key: WFLY-3472 > URL: https://issues.jboss.org/browse/WFLY-3472 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.1.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > Description from linked BZ: > Move the domain.conf call in domain.sh (and also domain.conf.bat in domain.bat) so it's called after the JBOSS_HOME is set. Then it's possible to use it in the configuration file. > E.g. we use following line to enable security manager: > JAVA_OPTS="$JAVA_OPTS -Djava.security.manager -Djava.security.policy==/tmp/security.policy -Djboss.home.dir=$JBOSS_HOME -Djboss.modules.policy-permissions=true" > The order is correct in the scripts for standalone (so the JBOSS_HOME is available in its conf file). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3472) JBOSS_HOME is not available in domain.conf

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3472?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3472: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1083474 > JBOSS_HOME is not available in domain.conf > ------------------------------------------- > > Key: WFLY-3472 > URL: https://issues.jboss.org/browse/WFLY-3472 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.1.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > Description from linked BZ: > Move the domain.conf call in domain.sh (and also domain.conf.bat in domain.bat) so it's called after the JBOSS_HOME is set. Then it's possible to use it in the configuration file. > E.g. we use following line to enable security manager: > JAVA_OPTS="$JAVA_OPTS -Djava.security.manager -Djava.security.policy==/tmp/security.policy -Djboss.home.dir=$JBOSS_HOME -Djboss.modules.policy-permissions=true" > The order is correct in the scripts for standalone (so the JBOSS_HOME is available in its conf file). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3472) JBOSS_HOME is not available in domain.conf

by Chao Wang (JIRA)

Chao Wang created WFLY-3472: ------------------------------- Summary: JBOSS_HOME is not available in domain.conf Key: WFLY-3472 URL: https://issues.jboss.org/browse/WFLY-3472 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Scripts Affects Versions: 8.1.0.Final Reporter: Chao Wang Assignee: Chao Wang Priority: Minor Description from linked BZ: Move the domain.conf call in domain.sh (and also domain.conf.bat in domain.bat) so it's called after the JBOSS_HOME is set. Then it's possible to use it in the configuration file. E.g. we use following line to enable security manager: JAVA_OPTS="$JAVA_OPTS -Djava.security.manager -Djava.security.policy==/tmp/security.policy -Djboss.home.dir=$JBOSS_HOME -Djboss.modules.policy-permissions=true" The order is correct in the scripts for standalone (so the JBOSS_HOME is available in its conf file). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[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 MODIFIED to ON_QA > 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)

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 commented on SECURITY-836: -------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1086787|https://bugzilla.redhat.com/show_bug.cgi?id=1086787] from MODIFIED to ON_QA > 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-819) LdapExt login module fetches to many attributes in RoleSearch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-819?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-819: -------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1086787|https://bugzilla.redhat.com/show_bug.cgi?id=1086787] from MODIFIED to ON_QA > LdapExt login module fetches to many attributes in RoleSearch > ------------------------------------------------------------- > > Key: SECURITY-819 > URL: https://issues.jboss.org/browse/SECURITY-819 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: PicketBox_4_0_21.Beta3 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > An LDAP server with (lets say) 1000 users in a group. > When authentication, a query is done to retrieve the groups for the user. > Most LDAP servers will limit the attributes send back based on authorization of the user, but can be configured to return *all* information. > The cause is: > / Query for roles matching the role filter > SearchControls constraints = new SearchControls(); > constraints.setSearchScope(searchScope); > constraints.setTimeLimit(searchTimeLimit); > rolesSearch(ctx, constraints, username, userDN, recursion, 0); > this used to also have: > constraints.setReturningAttributes(new String[0]); > at some time this was taken out. > It needs to go back in -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-516) 6.1.0.beta4 and identified a rule pattern inducing memory leaks

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-516?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-516: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > 6.1.0.beta4 and identified a rule pattern inducing memory leaks > --------------------------------------------------------------- > > Key: DROOLS-516 > URL: https://issues.jboss.org/browse/DROOLS-516 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta3, 6.1.0.Beta4 > Reporter: Matteo Mortari > Assignee: Mario Fusco > Attachments: 20140604.anotherleak.zip, 20140604.anotherleak_erratacorrige.zip, Java_VisualVM_2014-06-05_11-38-12.png, Java_VisualVM_2014-06-05_11-43-06.png > > > Ciao I'm using 6.1.0.beta4 and I identified in my application a rule pattern inducing memory leaks. I will attach rule, screenshots, and javacode to replicate the issue. > Steps to replicate identification of issue: > * IF the rule {{After No data received within the last 1 hour Error, now resumed}} is included, memory leaks happens, and pretty quickly. > * IF such rule is commented out, application do manage to keep alive. > Same problem happens even on 6.1.0.beta3 - I did not test with previous versions. > Thanks a lot in advance, > Ciao > Matteo -- 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