February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8124) Unify arquillian defaultProtocol in TS

by Marek Kopecký (JIRA)

Marek Kopecký created WFLY-8124: ----------------------------------- Summary: Unify arquillian defaultProtocol in TS Key: WFLY-8124 URL: https://issues.jboss.org/browse/WFLY-8124 Project: WildFly Issue Type: Enhancement Components: Test Suite Reporter: Marek Kopecký Assignee: Marek Kopecký Unify arquillian defaultProtocol in TS xts a rts module use servlet protocol. Jmx protocol is standard protocol: {noformat} [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -i servlet testsuite/integration/rts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" /> testsuite/integration/xts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" /> [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -iv servlet | wc -l 13 [mkopecky@dhcp-10-40-5-170 base] (7.x)$ {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-964) Coverity static analysis, Resource leak on an exceptional path, FileAuditEndpoint (elytron)

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-964?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reassigned ELY-964: --------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Coverity static analysis, Resource leak on an exceptional path, FileAuditEndpoint (elytron) > ------------------------------------------------------------------------------------------- > > Key: ELY-964 > URL: https://issues.jboss.org/browse/ELY-964 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Choma > Assignee: Ilia Vassilev > > Coverity static analysis found possible occurence of resource leak. > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=96902... > In constructor when {{fos.getFD()}} will throw exception {{FileOutputStream fos}} won't be closed. > {code:java|title=FileAuditEndpoint.java} > FileAuditEndpoint(Builder builder) throws IOException { > this.dateFormatSupplier = builder.dateFormatSupplier; > this.syncOnAccept = builder.syncOnAccept; > FileOutputStream fos = new FileOutputStream(builder.location.toFile(), true); > this.fileDescriptor = fos.getFD(); > this.outputStream = new BufferedOutputStream(fos); > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1890) wildfly-10.0.0.Final deployment crash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1890?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1890: ------------------------------------------------- Miroslav Sochurek <msochure(a)redhat.com> changed the Status of [bug 1408222|https://bugzilla.redhat.com/show_bug.cgi?id=1408222] from POST to CLOSED > wildfly-10.0.0.Final deployment crash > ------------------------------------- > > Key: WFCORE-1890 > URL: https://issues.jboss.org/browse/WFCORE-1890 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 2.2.0.Final > Reporter: Jason Morgan > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Alpha23 > > > Having a war in the deployment directory and then "replacing" a deployment through the web console causes the server to crash without any logging on restart -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1441) Nested accumulate makes DRL twice as slow in statefull session

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1441?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1441: ------------------------------------- Description: To reproduce: comment out to replace the 2 rules in this DRL: https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-example... and run TennisApp In the sampler profiling, see attachement 350, the original way does setObject() 60% of the time and determineIdentityHashcode 20%, but in the new one way it's vica versa. so the number of setObjects() calls is probably the same, it's just the determineIdentityHashCode() that blow up. was: To reproduce: comment out to replace the 2 rules in this DRL: https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-example... and run TennisApp > Nested accumulate makes DRL twice as slow in statefull session > -------------------------------------------------------------- > > Key: DROOLS-1441 > URL: https://issues.jboss.org/browse/DROOLS-1441 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Attachments: Selection_350.png > > > To reproduce: comment out to replace the 2 rules in this DRL: > https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-example... > and run TennisApp > In the sampler profiling, see attachement 350, the original way does setObject() 60% of the time and determineIdentityHashcode 20%, but in the new one way it's vica versa. > so the number of setObjects() calls is probably the same, it's just the determineIdentityHashCode() that blow up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8123) Upgrade Artemis 1.5.3.jbossorg-002

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8123?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-8854 to WFLY-8123: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8123 (was: JBEAP-8854) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) > Upgrade Artemis 1.5.3.jbossorg-002 > ---------------------------------- > > Key: WFLY-8123 > URL: https://issues.jboss.org/browse/WFLY-8123 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-172) Unable to find unambiguous method: class java.lang.String.replace(java.lang.String, java.lang.String)

by Ramesh khot (JIRA)

Ramesh khot created JBEE-172: -------------------------------- Summary: Unable to find unambiguous method: class java.lang.String.replace(java.lang.String, java.lang.String) Key: JBEE-172 URL: https://issues.jboss.org/browse/JBEE-172 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-el-api Affects Versions: jboss-el-api_3.0_spec-1.0.7.Final Environment: Wildfly 10, Jdk 8 Reporter: Ramesh khot Assignee: Scott Marlow I am using String.replace('-',' ') function inside jstl/core forEach tag but getting Unable to find unambiguous method: class java.lang.String.replace(java.lang.String, java.lang.String) at com.sun.faces.facelets.tag.TagAttributeImpl.getObject(TagAttributeImpl.java:358) at com.sun.faces.facelets.tag.TagAttributeImpl.getValue(TagAttributeImpl.java:322) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.assignUniqueId(ComponentTagHandlerDelegateImpl.java:434) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:180) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-965) Coverity static analysis, Resource leak, LdapsecurityRealm (Elytron)

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-965?page=com.atlassian.jira.plugin.sy... ] Jan Kalina moved WFLY-8094 to ELY-965: -------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-965 (was: WFLY-8094) Component/s: Realms (was: Security) > Coverity static analysis, Resource leak, LdapsecurityRealm (Elytron) > -------------------------------------------------------------------- > > Key: ELY-965 > URL: https://issues.jboss.org/browse/ELY-965 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Reporter: Martin Choma > Assignee: Jan Kalina > > Coverity static analysis found 8 occurence of Closeable object LdapIdentity not closing properly. > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > {{LdapIdentity}} in {{close()}} method just close provided dirContext. {{LdapIdentity}} does not create dirContext by itself. So it looks to me it is no necessary to implement Closeable in {{LdapIdentity}}, as code where dirContext was created should be responsible for closing it (and according to coverity it is closed properly everywhere). > {code:java|title=LdapSecurityRealm.java} > private class LdapIdentity implements Closeable { > private final String name; > private final DirContext dirContext; > private final String distinguishedName; > private final SearchResult entry; > LdapIdentity(String name, DirContext dirContext, String distinguishedName, SearchResult entry) { > this.name = name; > this.dirContext = dirContext; > this.distinguishedName = distinguishedName; > this.entry = entry; > } > String getName() { > return this.name; > } > DirContext getDirContext() { > return this.dirContext; > } > String getDistinguishedName() { > return this.distinguishedName; > } > SearchResult getEntry() { > return this.entry; > } > @Override > public void close() throws IOException { > try { > dirContext.close(); > } catch (NamingException e) { > log.debug("LdapSecurityRealm failed to close DirContext", e); > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2299) Backport Latest Elytron and Invocation Integration Changes

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2299: ---------------------------------------- Summary: Backport Latest Elytron and Invocation Integration Changes Key: WFCORE-2299 URL: https://issues.jboss.org/browse/WFCORE-2299 Project: WildFly Core Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1442) ServiceRegistry references non existent classes

by Anton Giertli (JIRA)

Anton Giertli created DROOLS-1442: ------------------------------------- Summary: ServiceRegistry references non existent classes Key: DROOLS-1442 URL: https://issues.jboss.org/browse/DROOLS-1442 Project: Drools Issue Type: Bug Reporter: Anton Giertli Assignee: Mario Fusco This code {code:java} SystemEventListener listener = SystemEventListenerFactory.getSystemEventListener(); {code} Fails with: Caused by: java.lang.ClassNotFoundException: org.drools.core.impl.SystemEventListenerServiceImpl Because ServiceRegistryImpl https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/master/kie-intern... references class SystemEventListenerServiceImpl which does not exist anymore in drools-core. The interface SystemEventListenerService still exists in kie-internal but there is no implementation whatsoever in drools. First impression is that both SystemEventListenerService + SystemEventListenerServiceImpl are "dead" code and should probably be removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8094) Coverity static analysis, Resource leak, LdapsecurityRealm (Elytron)

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8094?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-8094: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Coverity static analysis, Resource leak, LdapsecurityRealm (Elytron) > -------------------------------------------------------------------- > > Key: WFLY-8094 > URL: https://issues.jboss.org/browse/WFLY-8094 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > > Coverity static analysis found 8 occurence of Closeable object LdapIdentity not closing properly. > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=95643... > {{LdapIdentity}} in {{close()}} method just close provided dirContext. {{LdapIdentity}} does not create dirContext by itself. So it looks to me it is no necessary to implement Closeable in {{LdapIdentity}}, as code where dirContext was created should be responsible for closing it (and according to coverity it is closed properly everywhere). > {code:java|title=LdapSecurityRealm.java} > private class LdapIdentity implements Closeable { > private final String name; > private final DirContext dirContext; > private final String distinguishedName; > private final SearchResult entry; > LdapIdentity(String name, DirContext dirContext, String distinguishedName, SearchResult entry) { > this.name = name; > this.dirContext = dirContext; > this.distinguishedName = distinguishedName; > this.entry = entry; > } > String getName() { > return this.name; > } > DirContext getDirContext() { > return this.dirContext; > } > String getDistinguishedName() { > return this.distinguishedName; > } > SearchResult getEntry() { > return this.entry; > } > @Override > public void close() throws IOException { > try { > dirContext.close(); > } catch (NamingException e) { > log.debug("LdapSecurityRealm failed to close DirContext", e); > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017