[JBoss JIRA] (JBJCA-1294) caching the value of isTraceEnabled
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1294?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBJCA-1294:
------------------------------------------------
Martin Simka <msimka(a)redhat.com> changed the Status of [bug 1259840|https://bugzilla.redhat.com/show_bug.cgi?id=1259840] from ON_QA to VERIFIED
> caching the value of isTraceEnabled
> -----------------------------------
>
> Key: JBJCA-1294
> URL: https://issues.jboss.org/browse/JBJCA-1294
> Project: IronJacamar
> Issue Type: Bug
> Affects Versions: 1.2.6.Final
> Reporter: Johnathon Lee
> Assignee: Bartosz Baranowski
> Fix For: WildFly/IronJacamar 1.3.2.Final, 1.0.35.Final
>
>
> caching the value of isTraceEnabled does not allow for complete dynamic control of the logging level. This has ramifications in support scenarios where diagnostics are needed and the ability to reload an instance to enable TRACE level logging is prohibitive.
> see examples of TRACE being cached:
> grep 'log.isTraceEnabled();' -r * --include='*.java'
> Replacement of all if (trace) with calls to log.tracef would be needed.
> Note, that some "if (trace)" would have to be replaced by if (log.isTraceEnabled()) calls, as they guard multiple lines of code, and even synchronization blocks
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1032) WebSphere JMS on Kie server produces errors in log
by Karel Suta (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1032?page=com.atlassian.jira.plugi... ]
Karel Suta updated DROOLS-1032:
-------------------------------
Description:
When I run WebSphere JMS tests for Kie server then SystemOut log gets filled by exception listed in attachment.
It doesn't cause any error in Kie server functionality as error is created by WebSphereSecurityAdapter while JMS use JMSSecurityAdapter to get needed info, it just spam log making it almost unusable for searching for any real issue logged there.
Caused by https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv...
Maybe would be good to reduce log level there to be able to filter out this error.
Edit: After deeper analysis has been revealed that this error actually signals failure in authentication on WebSphere when using JMS. Tests passed because users and their roles has beech cached when running REST tests and for JMS there has been used values from cache.
If user would use just JMS for Kie server then he wouldn't be able to use any functionality based on user authentication and its roles like claiming task.
was:
When I run WebSphere JMS tests for Kie server then SystemOut log gets filled by exception listed in attachment.
It doesn't cause any error in Kie server functionality as error is created by WebSphereSecurityAdapter while JMS use JMSSecurityAdapter to get needed info, it just spam log making it almost unusable for searching for any real issue logged there.
Caused by https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv...
Maybe would be good to reduce log level there to be able to filter out this error.
> WebSphere JMS on Kie server produces errors in log
> --------------------------------------------------
>
> Key: DROOLS-1032
> URL: https://issues.jboss.org/browse/DROOLS-1032
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.4.0.Beta1
> Environment: WebSphere 8.5.5.7
> Reporter: Karel Suta
> Assignee: Maciej Swiderski
> Labels: reported-by-qe
> Fix For: 6.4.0.CR1
>
> Attachments: stacktrace.txt
>
>
> When I run WebSphere JMS tests for Kie server then SystemOut log gets filled by exception listed in attachment.
> It doesn't cause any error in Kie server functionality as error is created by WebSphereSecurityAdapter while JMS use JMSSecurityAdapter to get needed info, it just spam log making it almost unusable for searching for any real issue logged there.
> Caused by https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv...
> Maybe would be good to reduce log level there to be able to filter out this error.
> Edit: After deeper analysis has been revealed that this error actually signals failure in authentication on WebSphere when using JMS. Tests passed because users and their roles has beech cached when running REST tests and for JMS there has been used values from cache.
> If user would use just JMS for Kie server then he wouldn't be able to use any functionality based on user authentication and its roles like claiming task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1313) User with slash or backslash char in LDAP name cannot log in through security-realm
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1313?page=com.atlassian.jira.plugi... ]
Hynek Švábek updated WFCORE-1313:
---------------------------------
Summary: User with slash or backslash char in LDAP name cannot log in through security-realm (was: User with Slash char in LDAP name cannot log in through security-realm)
> User with slash or backslash char in LDAP name cannot log in through security-realm
> -----------------------------------------------------------------------------------
>
> Key: WFCORE-1313
> URL: https://issues.jboss.org/browse/WFCORE-1313
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Attachments: users.ldif
>
>
> According to LDAP specification [1], DN can contain slash char without escaping or escaped backslash, etc.
> I am not able to log in to management console with username "Slash/Char" or "Back\Slash". But I would be able to log in there.
> I can see this in Wireshark
> *Slash/Char*
> {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*.
> *Back\Slash*
> {code}
> LDAPMessage bindRequest(1) "uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple
> LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x75 0x69 0x64 0x3D 0x42 0x61 0x63 0x6B 0x5C 0x5C 0x5C 0x53 0x6C 0x61 0x73 0x6
> {code}
> You can see there three backslash chars.
> 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
[JBoss JIRA] (JBAS-9570) (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms,
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBAS-9570?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBAS-9570.
-------------------------------
Assignee: Tom Jenkinson (was: Stefano Maestri)
Resolution: Incomplete Description
> (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms,
> ------------------------------------------------------------------------------------
>
> Key: JBAS-9570
> URL: https://issues.jboss.org/browse/JBAS-9570
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Components: Transaction Manager (JBossTM)
> Environment: Jboss: 3.2.5
> Jdk: 1.4
> Reporter: usman hassan
> Assignee: Tom Jenkinson
>
> I have a issue in my jboss where my current transaction gets
> interrupted. I am getting the following error from my logs.
> 2015-03-10 07:13:15,911 FATAL [SDES.HubManager.DynamicTransactionDelegate] [01A713400A03140CD99F6EC4013F8919] finderException while stamping delivery Find failed: org.jboss.util.NestedSQLException: Interrupted while requesting permit! Waited 0 ms, invocation time: 1425957195897; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms, invocation time: 1425957195897
> In addition to above below connection factory not bound error is also frequent in the logs
> 2015-03-09 14:48:51,386 WARN [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] javax.naming.NameNotFoundException: XAConnectionFactory not bound
> Effect on Application:
> Even though the above errors are there but application seems to be working fine for some days but it suddenly starts misbehaving when the load is high.
> Any suggestion/hint to resolve the issue will be more then welcomed. Thanks in Advance.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBAS-9570) (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms,
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBAS-9570?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBAS-9570:
-------------------------------------
Not enough information here. Please can you re-open and provide a reproducer if the issue persists?
> (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms,
> ------------------------------------------------------------------------------------
>
> Key: JBAS-9570
> URL: https://issues.jboss.org/browse/JBAS-9570
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Components: Transaction Manager (JBossTM)
> Environment: Jboss: 3.2.5
> Jdk: 1.4
> Reporter: usman hassan
> Assignee: Stefano Maestri
>
> I have a issue in my jboss where my current transaction gets
> interrupted. I am getting the following error from my logs.
> 2015-03-10 07:13:15,911 FATAL [SDES.HubManager.DynamicTransactionDelegate] [01A713400A03140CD99F6EC4013F8919] finderException while stamping delivery Find failed: org.jboss.util.NestedSQLException: Interrupted while requesting permit! Waited 0 ms, invocation time: 1425957195897; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms, invocation time: 1425957195897
> In addition to above below connection factory not bound error is also frequent in the logs
> 2015-03-09 14:48:51,386 WARN [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] javax.naming.NameNotFoundException: XAConnectionFactory not bound
> Effect on Application:
> Even though the above errors are there but application seems to be working fine for some days but it suddenly starts misbehaving when the load is high.
> Any suggestion/hint to resolve the issue will be more then welcomed. Thanks in Advance.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1313) User with Slash char in LDAP name cannot log in through security-realm
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1313?page=com.atlassian.jira.plugi... ]
Hynek Švábek updated WFCORE-1313:
---------------------------------
Attachment: users.ldif
> User with Slash char in LDAP name cannot log in through security-realm
> ----------------------------------------------------------------------
>
> Key: WFCORE-1313
> URL: https://issues.jboss.org/browse/WFCORE-1313
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Attachments: users.ldif
>
>
> 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
[JBoss JIRA] (WFCORE-1313) User with Slash char in LDAP name cannot log in through security-realm
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1313?page=com.atlassian.jira.plugi... ]
Hynek Švábek updated WFCORE-1313:
---------------------------------
Steps to Reproduce:
1. Start LDAP server which uses attached users.ldif
2. Add these to EAP configuration file
* Security realm - "ldap-realm"
* Outbound-connection - ldap - "ldap-connection"
{code}
<management>
....
<security-realms>
....
<security-realm name="ldap-realm">
<authentication>
<ldap connection="ldap-connection" base-dn="ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org">
<advanced-filter filter="(uid={0})"/>
</ldap>
</authentication>
</security-realm>
</security-realms>
<outbound-connections>
<ldap name="ldap-connection" url="ldap://localhost:10389" search-dn="uid=admin,ou=system" search-credential="secret"/>
</outbound-connections>
....
</management>
{code}
Change ManagementRealm in <management-interfaces>
{code}
<http-interface security-realm="ManagementRealm" http-upgrade-enabled="true">
{code}
to our ldap-realm
{code}
<http-interface security-realm="ldap-realm" http-upgrade-enabled="true">
{code}
3. Try to log in to management localhost:9990
* jduke with Password1 -> OK
* Slash/Char with Password1 -> NOK (but it would be OK)
* Back\Slash with Password1 -> NOK (but it would be OK)
was:
1. Start LDAP server which uses attached users.ldif
2. Add these to EAP configuration file
* Security realm - "ldap-realm"
* Outbound-connection - ldap - "ldap-connection"
{code}
<management>
....
<security-realms>
....
<security-realm name="ldap-realm">
<authentication>
<ldap connection="ldap-connection" base-dn="ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org">
<advanced-filter filter="(uid={0})"/>
</ldap>
</authentication>
</security-realm>
</security-realms>
<outbound-connections>
<ldap name="ldap-connection" url="ldap://localhost:10389" search-dn="uid=admin,ou=system" search-credential="secret"/>
</outbound-connections>
....
</management>
{code}
Change ManagementRealm in <management-interfaces>
{code}
<http-interface security-realm="ManagementRealm" http-upgrade-enabled="true">
{code}
to our ldap-realm
{code}
<http-interface security-realm="ldap-realm" http-upgrade-enabled="true">
{code}
3. Try to log in to management localhost:9990
* jduke with Password1 -> OK
* Slash/Char with Password1 -> NOK (but it would be OK)
> User with Slash char in LDAP name cannot log in through security-realm
> ----------------------------------------------------------------------
>
> Key: WFCORE-1313
> URL: https://issues.jboss.org/browse/WFCORE-1313
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Attachments: users.ldif
>
>
> 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
[JBoss JIRA] (WFCORE-1313) User with Slash char in LDAP name cannot log in through security-realm
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1313?page=com.atlassian.jira.plugi... ]
Hynek Švábek updated WFCORE-1313:
---------------------------------
Description:
According to LDAP specification [1], DN can contain slash char without escaping or escaped backslash, etc.
I am not able to log in to management console with username "Slash/Char" or "Back\Slash". But I would be able to log in there.
I can see this in Wireshark
*Slash/Char*
{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*.
*Back\Slash*
{code}
LDAPMessage bindRequest(1) "uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple
LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x75 0x69 0x64 0x3D 0x42 0x61 0x63 0x6B 0x5C 0x5C 0x5C 0x53 0x6C 0x61 0x73 0x6
{code}
You can see there three backslash chars.
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
was:
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
> User with Slash char in LDAP name cannot log in through security-realm
> ----------------------------------------------------------------------
>
> Key: WFCORE-1313
> URL: https://issues.jboss.org/browse/WFCORE-1313
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Attachments: users.ldif
>
>
> According to LDAP specification [1], DN can contain slash char without escaping or escaped backslash, etc.
> I am not able to log in to management console with username "Slash/Char" or "Back\Slash". But I would be able to log in there.
> I can see this in Wireshark
> *Slash/Char*
> {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*.
> *Back\Slash*
> {code}
> LDAPMessage bindRequest(1) "uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org" simple
> LDAPMessage bindResponse(1) invalidDNSyntax (Incorrect DN given : uid=Back\\\Slash,ou=People,o=LdapRealmSpecialNameManualTest7d339efa,o=primary,dc=jboss,dc=org (0x75 0x69 0x64 0x3D 0x42 0x61 0x63 0x6B 0x5C 0x5C 0x5C 0x53 0x6C 0x61 0x73 0x6
> {code}
> You can see there three backslash chars.
> 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
[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-470?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet commented on DROOLS-470:
-----------------------------------------
This issue still hurts. Any chance we can get it for 6.4?
> Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-470
> URL: https://issues.jboss.org/browse/DROOLS-470
> Project: Drools
> Issue Type: Enhancement
> Components: decision tables
> Affects Versions: 6.1.0.Beta2
> Reporter: Geoffrey De Smet
> Assignee: Michael Anstis
> Labels: optaplanner-request-for-drools
> Fix For: 6.4.0.CR1
>
>
> This DT should work:
> ||CONDITION||CONDITION||ACTION|
> |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))||
> |guestName == "$param"|guestName == "$param"|doSomething();|
> It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed.
> Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule:
> ||CONDITION||CONDITION||CONDITION||ACTION|
> |$guest : SeatDesignation()|$neighbor : SeatDesignation()|||
> |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();|
> Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months