January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1034) Kie server test improvement for Oracle RAC

by Jakub Schwan (JIRA)

Jakub Schwan created DROOLS-1034: ------------------------------------ Summary: Kie server test improvement for Oracle RAC Key: DROOLS-1034 URL: https://issues.jboss.org/browse/DROOLS-1034 Project: Drools Issue Type: Feature Request Components: kie server Environment: Oracle 11g R2 RAC Reporter: Jakub Schwan Assignee: Jakub Schwan Sometimes some tests failed on Oracle RAC database due invalid id ordering from db. Some older data has higher id then the newer data. It's caused by identifying of Oracle RAC. On other databases tests run fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6037) User with Slash char in LDAP name cannot log in through security-realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6037?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-6037: ---------------------------------------- Security realm issues need to be raised under WFCORE - please move this issue over. > User with Slash char in LDAP name cannot log in through security-realm > ---------------------------------------------------------------------- > > Key: WFLY-6037 > URL: https://issues.jboss.org/browse/WFLY-6037 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > According to LDAP specification [1], DN can contain slash char without escaping, etc. > I am not able to log in to management console with username "Slash/Char". But I would be able to log in there. > I can see this in Wireshark > {code} > LDAPMessage bindRequest(1) ""uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple > LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : "uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x22 0x75 0x69 0x64 0x3D 0x53 0x6C 0x61 0x73 0x68 0x2F 0x43 0x68 0x61 0x72 0x2 > {code} > You can see there quotation marks around *uid=Slash/Char*. > In my opinion problem can be somewhere around this > {code} > javax.naming.NameImpl.stringifyComp(String comp) > {code} > [1] https://tools.ietf.org/html/rfc2253#section-3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6037) User with Slash char in LDAP name cannot log in through security-realm

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-6037: ---------------------------------- Summary: User with Slash char in LDAP name cannot log in through security-realm Key: WFLY-6037 URL: https://issues.jboss.org/browse/WFLY-6037 Project: WildFly Issue Type: Bug Components: Security Reporter: Hynek Švábek Assignee: Darran Lofthouse According to LDAP specification [1], DN can contain slash char without escaping, etc. I am not able to log in to management console with username "Slash/Char". But I would be able to log in there. I can see this in Wireshark {code} LDAPMessage bindRequest(1) ""uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : "uid=Slash/Char",ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x22 0x75 0x69 0x64 0x3D 0x53 0x6C 0x61 0x73 0x68 0x2F 0x43 0x68 0x61 0x72 0x2 {code} You can see there quotation marks around *uid=Slash/Char*. In my opinion problem can be somewhere around this {code} javax.naming.NameImpl.stringifyComp(String comp) {code} [1] https://tools.ietf.org/html/rfc2253#section-3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5766) ManagedExecutorService's max-threads attribute is not honored if an unbounded queue is used

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-5766?page=com.atlassian.jira.plugin.... ] Jan Martiska closed WFLY-5766. ------------------------------ > ManagedExecutorService's max-threads attribute is not honored if an unbounded queue is used > ------------------------------------------------------------------------------------------- > > Key: WFLY-5766 > URL: https://issues.jboss.org/browse/WFLY-5766 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 10.0.0.CR4 > Reporter: Jan Martiska > Assignee: James Perkins > > If you set a max-threads attribute to a managed-executor-service and the number is higher than core-threads, and its queue is unbounded (queue-length is undefined), it won't use any more threads than the number from core-threads. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6031) WeldProvider.containerShutDown() not invoked if the deployment fails

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-6031?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-6031: ------------------------------------ For the record, this is a regression introduced by the fix for WFLY-5232 (the method was originally called in WeldBootstrapService.stop()). > WeldProvider.containerShutDown() not invoked if the deployment fails > -------------------------------------------------------------------- > > Key: WFLY-6031 > URL: https://issues.jboss.org/browse/WFLY-6031 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.CR5 > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: 10.0.0.Final > > > We've run into this problem when executing Weld and CDI TCK test suites on a specific HP-UX machine. Both test suites contain a lot of scenarios where the deployment fails. HP-UX jvm cannot handle this load and the test suite fails with OutOfMemoryError. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5604) Weld deployment services not cleaned up properly if a deployment fails

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-5604?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-5604: ------------------------------------ For the record, this was a regression introduced by the fix for WFLY-5232 (the cleanup was originally performed in {{WeldBootstrapService.stop()}}). > Weld deployment services not cleaned up properly if a deployment fails > ---------------------------------------------------------------------- > > Key: WFLY-5604 > URL: https://issues.jboss.org/browse/WFLY-5604 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.CR4 > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: 10.0.0.CR5 > > > The cleanup is currently only performed as a part of {{org.jboss.as.weld.WeldStartService.stop(StopContext)}} invocation. However, if {{WeldStartService.start()}} fails (e.g. because of a validation error) the stop method is never invoked. Some Weld bootstrap services need to clean up resources even if the deployment fails, e.g. {{org.jboss.weld.bootstrap.events.ContainerLifecycleEvents}} (deactivable optimization) maintains a separate thread pool and so the referenced {{ExecutorService}} is never shut down explicitly and the only hope to free resources is the GC and finalizers whose execution is deferred and may never even occur. > We've run into this problem when executing Weld and CDI TCK test suites on a specific HP-UX machine. Both test suites contain a lot of scenarios where the deployment fails. HP-UX jvm cannot handle this load and the test suite fails with _"java.lang.OutOfMemoryError: unable to create new native thread"_. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6034) Listener secure attribute doesn't work as expected

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6034: ------------------------------------ Summary: Listener secure attribute doesn't work as expected Key: WFLY-6034 URL: https://issues.jboss.org/browse/WFLY-6034 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.0.0.CR5 Reporter: Radim Hatlapatka Assignee: Stuart Douglas When setting {{secure}} attributed on {{http-listener}} and deploying web application which requires secured connection ({{<transport-guarantee>CONFIDENTIAL</transport-guarantee>}}. The web application should be accessible even from the {{http}} as the listener is defined as secured, but instead it results to redirect to https (when having redirect-socket defined) or to internal server error (when no redirect-socket). Steps to reproduce: # start eap and deploy attached confidential.war # configure http-listener default as secured => /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=secure, value=true) # reload the server # go to http://127.0.0.1:8080/confidential/index.jsp # you should get 200 response code, still you get 302, which is not correct as the listener is defined as secured -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6015) Testing JDBC connection is causing it to be created

by Renann Prado (JIRA)

[ https://issues.jboss.org/browse/WFLY-6015?page=com.atlassian.jira.plugin.... ] Renann Prado updated WFLY-6015: ------------------------------- Description: Testing JDBC connection is causing it to be created. (was: Testing JDBC connection is causing it to be added.) > Testing JDBC connection is causing it to be created > --------------------------------------------------- > > Key: WFLY-6015 > URL: https://issues.jboss.org/browse/WFLY-6015 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.CR5 > Environment: Mac OS X El Captain with latest update > java version "1.8.0_66" > Java(TM) SE Runtime Environment (build 1.8.0_66-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) > MariaDB - with MariaDB JDBC driver deployed > Reporter: Renann Prado > Assignee: Jason Greene > > Testing JDBC connection is causing it to be created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6015) Testing JDBC connection is causing it to be added

by Renann Prado (JIRA)

[ https://issues.jboss.org/browse/WFLY-6015?page=com.atlassian.jira.plugin.... ] Renann Prado updated WFLY-6015: ------------------------------- Steps to Reproduce: 1 - Create a new datasource through web admin console 2 - When in final step, click to test the connection 3 - Even it being a *test* it seems that it tries to add the datasource, so if you try to test again you'll get: Unexpected HTTP response: 500 {code:json} Request { "name" => "MySqlDS", "use-ccm" => false, "pool-name" => "MySqlDS_Pool", "connection-url" => "jdbc:mariadb://192.168.0.119:3306", "jta" => false, "driver-class" => "org.mariadb.jdbc.Driver", "driver-name" => "mariadb-java-client-1.3.4.jar", "valid-connection-checker-class-name" => "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker", "background-validation" => true, "exception-sorter-class-name" => "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter", "jndi-name" => "java:/MySqlDS", "user-name" => "root", "password" => "123", "enabled" => true, "operation" => "add", "address" => [ ("subsystem" => "datasources"), ("data-source" => "MySqlDS") ] } Response Internal Server Error { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.data-source.MySqlDS is already registered", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {code} {code:java} 01:52:14,722 ERROR [org.jboss.as.controller.management-operation] (XNIO-3 task-10) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "MySqlDS") ]): org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.data-source.MySqlDS is already registered {code} was: 1 - Create a new datasource through web admin console 2 - When in final step, click to test the connect 3 - Even it being a *test* it seems that it tries to add the datasource, so if you try to test again you'll get: Unexpected HTTP response: 500 {code:json} Request { "name" => "MySqlDS", "use-ccm" => false, "pool-name" => "MySqlDS_Pool", "connection-url" => "jdbc:mariadb://192.168.0.119:3306", "jta" => false, "driver-class" => "org.mariadb.jdbc.Driver", "driver-name" => "mariadb-java-client-1.3.4.jar", "valid-connection-checker-class-name" => "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker", "background-validation" => true, "exception-sorter-class-name" => "org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter", "jndi-name" => "java:/MySqlDS", "user-name" => "root", "password" => "123", "enabled" => true, "operation" => "add", "address" => [ ("subsystem" => "datasources"), ("data-source" => "MySqlDS") ] } Response Internal Server Error { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.data-source.MySqlDS is already registered", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {code} {code:java} 01:52:14,722 ERROR [org.jboss.as.controller.management-operation] (XNIO-3 task-10) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "MySqlDS") ]): org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.data-source.MySqlDS is already registered {code} > Testing JDBC connection is causing it to be added > ------------------------------------------------- > > Key: WFLY-6015 > URL: https://issues.jboss.org/browse/WFLY-6015 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.CR5 > Environment: Mac OS X El Captain with latest update > java version "1.8.0_66" > Java(TM) SE Runtime Environment (build 1.8.0_66-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) > MariaDB - with MariaDB JDBC driver deployed > Reporter: Renann Prado > Assignee: Jason Greene > > Testing JDBC connection is causing it to be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6015) Testing JDBC connection is causing it to be created

by Renann Prado (JIRA)

[ https://issues.jboss.org/browse/WFLY-6015?page=com.atlassian.jira.plugin.... ] Renann Prado updated WFLY-6015: ------------------------------- Summary: Testing JDBC connection is causing it to be created (was: Testing JDBC connection is causing it to be added) > Testing JDBC connection is causing it to be created > --------------------------------------------------- > > Key: WFLY-6015 > URL: https://issues.jboss.org/browse/WFLY-6015 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.CR5 > Environment: Mac OS X El Captain with latest update > java version "1.8.0_66" > Java(TM) SE Runtime Environment (build 1.8.0_66-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) > MariaDB - with MariaDB JDBC driver deployed > Reporter: Renann Prado > Assignee: Jason Greene > > Testing JDBC connection is causing it to be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 January 2016