April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-758) GuidedDecisionTreeModelUnmarshallingVisitor doesn't support unmarshalling of oneline rules

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-758?page=com.atlassian.jira.plugin... ] Michael Anstis resolved DROOLS-758. ----------------------------------- Fix Version/s: 6.3.0.Beta1 Resolution: Done http://github.com/droolsjbpm/drools/commit/7c48450a2 > GuidedDecisionTreeModelUnmarshallingVisitor doesn't support unmarshalling of oneline rules > ------------------------------------------------------------------------------------------ > > Key: DROOLS-758 > URL: https://issues.jboss.org/browse/DROOLS-758 > Project: Drools > Issue Type: Bug > Reporter: Tibor Zimányi > Assignee: Michael Anstis > Priority: Minor > Fix For: 6.3.0.Beta1 > > > Method visit() from GuidedDecisionTreeModelUnmarshallingVisitor doesn't support rules, that are written in one line (so it doesn't unmarshall them correctly). According to documentation [1] (Block 7.1.2), rule can be written without line separators. Also depending on line separators introduce problems with rules from DRL files that are written on operating systems with different line separator that is on a system where drools engine runs (this can be seen running GuidedDecisionTreeDRLPersistenceUnmarshallingMessagesTest in Windows environment). > The problematic part of the code: [2] > But there are also other places, where there is parsing line by line used. I.e. [3]. > Rules should be parsed by keywords without depending on line separator or generally on lines. > [1] https://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html_single... > [2] https://github.com/droolsjbpm/drools/blob/007148f6e910a4706f6a20862abc002... > [3] https://github.com/droolsjbpm/drools/blob/9019854d3427a6079eeea19f548a102... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1257) SemaphoreConcurrentLinkedQueueManagedConnectionPool

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1257?page=com.atlassian.jira.plugin... ] Radim Vansa updated JBJCA-1257: ------------------------------- Description: With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this {code} log.throwableWhileAttemptingGetNewGonnection(clw.getConnectionListener(), t); {code} https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. was: With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this {code} log.throwableWhileAttemptingGetNewGonnection(clw.getConnectionListener(), t); {code} https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. > SemaphoreConcurrentLinkedQueueManagedConnectionPool > --------------------------------------------------- > > Key: JBJCA-1257 > URL: https://issues.jboss.org/browse/JBJCA-1257 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.31.Final > Reporter: Radim Vansa > Assignee: Jesper Pedersen > Priority: Minor > Fix For: 1.2.4.Final > > > With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this > {code} > log.throwableWhileAttemptingGetNewGonnection(clw.getConnectionListener(), t); > {code} > https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... > causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1257) SemaphoreConcurrentLinkedQueueManagedConnectionPool

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1257?page=com.atlassian.jira.plugin... ] Radim Vansa updated JBJCA-1257: ------------------------------- Description: With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this {code} log.throwableWhileAttemptingGetNewGonnection(clw.getConnectionListener(), t); {code} https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. was: With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this {code} log.throwableWhileTryingMatchManagedConnectionThenDestroyingConnection(clw.getConnectionListener(), t); {code} https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. > SemaphoreConcurrentLinkedQueueManagedConnectionPool > --------------------------------------------------- > > Key: JBJCA-1257 > URL: https://issues.jboss.org/browse/JBJCA-1257 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.31.Final > Reporter: Radim Vansa > Assignee: Jesper Pedersen > Priority: Minor > Fix For: 1.2.4.Final > > > With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this > {code} > log.throwableWhileAttemptingGetNewGonnection(clw.getConnectionListener(), t); > {code} > https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... > causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1257) SemaphoreConcurrentLinkedQueueManagedConnectionPool

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1257?page=com.atlassian.jira.plugin... ] Radim Vansa commented on JBJCA-1257: ------------------------------------ I don't have the stack trace anymore - it is a bug in error handling, so after I've found the cause I've fixed it. However, swallowing the original exception because of NPE in error handling makes it harder to find the cause. Looking on the links above - I apologize, I've linked wrong line, the NPE is thrown at {code} log.throwableWhileAttemptingGetNewGonnection(clw.getConnectionListener(), t); {code} at https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... because an exception is thrown at https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... I'll fix the bug description right away... > SemaphoreConcurrentLinkedQueueManagedConnectionPool > --------------------------------------------------- > > Key: JBJCA-1257 > URL: https://issues.jboss.org/browse/JBJCA-1257 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.31.Final > Reporter: Radim Vansa > Assignee: Jesper Pedersen > Priority: Minor > Fix For: 1.2.4.Final > > > With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this > {code} > log.throwableWhileTryingMatchManagedConnectionThenDestroyingConnection(clw.getConnectionListener(), t); > {code} > https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... > causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-877) AdvancedLdapLodinMogule is Logging LDAP Bind Credential Password during authentication.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-877?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-877: -------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1199641|https://bugzilla.redhat.com/show_bug.cgi?id=1199641] from ASSIGNED to POST > AdvancedLdapLodinMogule is Logging LDAP Bind Credential Password during authentication. > --------------------------------------------------------------------------------------- > > Key: SECURITY-877 > URL: https://issues.jboss.org/browse/SECURITY-877 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_2_3_6_Final > Environment: Wildfly is logging the bindCredentials when using SPNEGO > Reporter: Filippe Spolti > Assignee: Filippe Spolti > Fix For: Negotiation_2_3_7_Final > > > The bind Credential are being logged: > 2015-03-19 19:33:28,569 TRACE [org.jboss.security.auth.spi.AbstractServerLoginModule] (http-localhost/127.0.0.1:8080-1) Logging into LDAP server, env={baseFilter=(userPrincipalName={0}), java.naming.security.credentials=***, jboss.security.security_domain=SPNEGO, java.naming.ldap.attributes.binary=objectSid, password-stacking=useFirstPass, recurseRoles=false, java.naming.security.authentication=simple, baseCtxDN=DC=example,DC=com, roleAttributeIsDN=true, rolesCtxDN=DC=example,DC=com, java.naming.security.principal=bindUser, allowEmptyPassword=true, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.provider.url=ldap://127.0.0.1:389, roleNameAttributeID=cn, roleAttributeID=memberOf, bindDN=bindUser, bindCredential=password} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1257) SemaphoreConcurrentLinkedQueueManagedConnectionPool

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1257?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1257: ----------------------------------- Issue Type: Bug (was: Feature Request) What is the full stack trace of this ? > SemaphoreConcurrentLinkedQueueManagedConnectionPool > --------------------------------------------------- > > Key: JBJCA-1257 > URL: https://issues.jboss.org/browse/JBJCA-1257 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.31.Final > Reporter: Radim Vansa > Assignee: Jesper Pedersen > Priority: Minor > Fix For: 1.2.4.Final > > > With SemaphoreConcurrentLinkedQueueManagedConnectionPool, if creating a new connection fails with exception, logging this > {code} > log.throwableWhileTryingMatchManagedConnectionThenDestroyingConnection(clw.getConnectionListener(), t); > {code} > https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... > causes NPE since clw == null. This way, the NPE is eventually swallowed on https://github.com/ironjacamar/ironjacamar/blob/1.0/core/src/main/java/or... and only generic ResourceException (without much info) is thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-758) GuidedDecisionTreeModelUnmarshallingVisitor doesn't support unmarshalling of oneline rules

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-758?page=com.atlassian.jira.plugin... ] Michael Anstis reassigned DROOLS-758: ------------------------------------- Assignee: Michael Anstis (was: Mark Proctor) > GuidedDecisionTreeModelUnmarshallingVisitor doesn't support unmarshalling of oneline rules > ------------------------------------------------------------------------------------------ > > Key: DROOLS-758 > URL: https://issues.jboss.org/browse/DROOLS-758 > Project: Drools > Issue Type: Bug > Reporter: Tibor Zimányi > Assignee: Michael Anstis > Priority: Minor > > Method visit() from GuidedDecisionTreeModelUnmarshallingVisitor doesn't support rules, that are written in one line (so it doesn't unmarshall them correctly). According to documentation [1] (Block 7.1.2), rule can be written without line separators. Also depending on line separators introduce problems with rules from DRL files that are written on operating systems with different line separator that is on a system where drools engine runs (this can be seen running GuidedDecisionTreeDRLPersistenceUnmarshallingMessagesTest in Windows environment). > The problematic part of the code: [2] > But there are also other places, where there is parsing line by line used. I.e. [3]. > Rules should be parsed by keywords without depending on line separator or generally on lines. > [1] https://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html_single... > [2] https://github.com/droolsjbpm/drools/blob/007148f6e910a4706f6a20862abc002... > [3] https://github.com/droolsjbpm/drools/blob/9019854d3427a6079eeea19f548a102... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1255) Ant build cannot be performed for IronJacamar samples because of encoding property missed

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1255?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1255. ------------------------------------ Resolution: Done > Ant build cannot be performed for IronJacamar samples because of encoding property missed > ----------------------------------------------------------------------------------------- > > Key: JBJCA-1255 > URL: https://issues.jboss.org/browse/JBJCA-1255 > Project: IronJacamar > Issue Type: Bug > Components: AS > Affects Versions: 1.2.2.Final > Environment: MacOS > Reporter: Nickolay Laptev > Assignee: Jesper Pedersen > Fix For: 1.2.4.Final > > > Downloaded IronJacamar archive and, following commands from user guide, ended with "ant" command. > Got an error that javac.encoding property is not set. > Actually this property is used in "build.xml" but it's not initialised within this file. > The same problem exist for all sample projects from the archive. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4373) WildFly CLI API ModelControllerClient deadlock?

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-4373?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-4373: ----------------------------------- Summary: WildFly CLI API ModelControllerClient deadlock? (was: WildFly CLI API ModelControllerClient memory leak?) > WildFly CLI API ModelControllerClient deadlock? > ----------------------------------------------- > > Key: WFLY-4373 > URL: https://issues.jboss.org/browse/WFLY-4373 > Project: WildFly > Issue Type: Bug > Components: Domain Management, IO > Affects Versions: 8.2.0.Final > Environment: Ubuntu 14.04 LTS, Java 1.8, xnio-api and xnio-nio are 3.3.0.Final > Reporter: Georgy Go > Assignee: Tomaz Cerar > Labels: cli, dmr > Attachments: threaddump.zip > > > The following snippet of code to redeploy an application: > ModelControllerClient cl = ModelControllerClient.Factory.create("localhost", 9999); > ModelNode operation = new ModelNode(); > operation.get("operation").set("redeploy"); > operation.get("address").add("deployment", "server.war"); > cl.execute(operation); > cl.close(); > - works fine, but .close() freezes forever. > This issue depends to not only redeploy, but also for any other operations. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-877) AdvancedLdapLodinMogule is Logging LDAP Bind Credential Password during authentication.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-877?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-877: -------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1199641|https://bugzilla.redhat.com/show_bug.cgi?id=1199641] from NEW to ASSIGNED > AdvancedLdapLodinMogule is Logging LDAP Bind Credential Password during authentication. > --------------------------------------------------------------------------------------- > > Key: SECURITY-877 > URL: https://issues.jboss.org/browse/SECURITY-877 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_2_3_6_Final > Environment: Wildfly is logging the bindCredentials when using SPNEGO > Reporter: Filippe Spolti > Assignee: Filippe Spolti > Fix For: Negotiation_2_3_7_Final > > > The bind Credential are being logged: > 2015-03-19 19:33:28,569 TRACE [org.jboss.security.auth.spi.AbstractServerLoginModule] (http-localhost/127.0.0.1:8080-1) Logging into LDAP server, env={baseFilter=(userPrincipalName={0}), java.naming.security.credentials=***, jboss.security.security_domain=SPNEGO, java.naming.ldap.attributes.binary=objectSid, password-stacking=useFirstPass, recurseRoles=false, java.naming.security.authentication=simple, baseCtxDN=DC=example,DC=com, roleAttributeIsDN=true, rolesCtxDN=DC=example,DC=com, java.naming.security.principal=bindUser, allowEmptyPassword=true, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.provider.url=ldap://127.0.0.1:389, roleNameAttributeID=cn, roleAttributeID=memberOf, bindDN=bindUser, bindCredential=password} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 April 2015