April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1257) NPE in SemaphoreConcurrentLinkedQueueManagedConnectionPool

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1257?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1257. ------------------------------------ Fix Version/s: 1.0.32.Final (was: 1.2.4.Final) Resolution: Done > NPE in 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.0.32.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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-629) Enabled automatic encryption of passwords stored in configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-629?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFCORE-629: --------------------------------------- Assignee: Darran Lofthouse > Enabled automatic encryption of passwords stored in configuration > ----------------------------------------------------------------- > > Key: WFCORE-629 > URL: https://issues.jboss.org/browse/WFCORE-629 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Environment: Wildfly 9 > Reporter: Jason Shepherd > Assignee: Darran Lofthouse > > Currently encrypting passwords such as Datasource passwords can only be done 'after the fact'. You have to create the datasource first, then retrospectively store the password in the vault and dereference it in the configuration. > It would be great if could turn on automatic storage of passwords in the vault so that when you create a Datasource password, or add a resource adapter which specifies a remote resource password, those passwords were automatically added to the vault, and deferenced in the configuration file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-750) Cannot resolve custom accumulate functions after declaring metadata for an existing type

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-750?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-750: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1205961|https://bugzilla.redhat.com/show_bug.cgi?id=1205961] from ON_QA to VERIFIED > Cannot resolve custom accumulate functions after declaring metadata for an existing type > ---------------------------------------------------------------------------------------- > > Key: DROOLS-750 > URL: https://issues.jboss.org/browse/DROOLS-750 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.3.0.Beta1 > > > Importing a custom accumulate function and a pojo from a different package the DRL compilation fails with the following message: "Error: Unknown accumulate function: 'myfunc' on rule 'test'. All accumulate functions must be registered before building a resource" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-749) Events deserialization is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-749?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-749: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1205666|https://bugzilla.redhat.com/show_bug.cgi?id=1205666] from ON_QA to VERIFIED > Events deserialization is broken > -------------------------------- > > Key: DROOLS-749 > URL: https://issues.jboss.org/browse/DROOLS-749 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.3.0.Beta1 > > > When a KieSession is deserialized the events present in the old serialized session are reasserted into the new session. Then if one of this event causes a scheduler to be immediately triggered this is done in a callback out of the main evaluation loop. This implies that the left tuples resulting from the triggering of the scheduler aren't propagated to the sink of the TimerNode which created the scheduler itself. This missing propagation can, in some circumstances, cause a NullPointerException like the following: > {code} > java.lang.NullPointerException > at org.drools.core.phreak.PhreakTimerNode.doLeftDeletes(PhreakTimerNode.java:197) > at org.drools.core.phreak.PhreakTimerNode.doNode(PhreakTimerNode.java:63) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:364) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:163) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:118) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:254) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:108) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1022) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1352) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1318) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1301) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1280) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

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 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)

9 years, 9 months

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)

9 years, 9 months

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)

9 years, 9 months

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)

9 years, 9 months

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)

9 years, 9 months

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)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015