November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5641) Cleanup is not done properly after test have finished

by Ivan Straka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5641?page=com.atlassian.jira.plugin.... ] Ivan Straka updated WFLY-5641: ------------------------------ Affects Version/s: 10.0.0.CR4 > Cleanup is not done properly after test have finished > ----------------------------------------------------- > > Key: WFLY-5641 > URL: https://issues.jboss.org/browse/WFLY-5641 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR4 > Reporter: Ivan Straka > Assignee: Paul Ferraro > Priority: Minor > > There are several tests failing because cleanup process was not done properly. > This can be caused by ibmjdk1.8 that do not run test in different order. Therefore problem is shown. > two exceptions: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... > whole run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-tcpgossip-mav... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5634) Allow the default HTTP security domain to be set

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5634?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-5634: ----------------------------------- Labels: affects_elytron (was: ) > Allow the default HTTP security domain to be set > ------------------------------------------------ > > Key: WFLY-5634 > URL: https://issues.jboss.org/browse/WFLY-5634 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Labels: affects_elytron > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5634) Allow the default HTTP security domain to be set

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5634?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-5634: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/8380 > Allow the default HTTP security domain to be set > ------------------------------------------------ > > Key: WFLY-5634 > URL: https://issues.jboss.org/browse/WFLY-5634 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Labels: affects_elytron > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-198) Correct or remove usage of finalize in VFS, TempDir, and TempFileProvider

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBVFS-198?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated JBVFS-198: ------------------------------ Fix Version/s: 3.2.12.Final (was: 3.2.10.Final) > Correct or remove usage of finalize in VFS, TempDir, and TempFileProvider > ------------------------------------------------------------------------- > > Key: JBVFS-198 > URL: https://issues.jboss.org/browse/JBVFS-198 > Project: JBoss VFS > Issue Type: Task > Reporter: Jason Greene > Assignee: Tomaz Cerar > Fix For: 3.2.12.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-201) VirtualFile and SuffixMatchFilter not necessary char allocation

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBVFS-201?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved JBVFS-201. ------------------------------- Fix Version/s: 3.2.11.Final Resolution: Done > VirtualFile and SuffixMatchFilter not necessary char allocation > --------------------------------------------------------------- > > Key: JBVFS-201 > URL: https://issues.jboss.org/browse/JBVFS-201 > Project: JBoss VFS > Issue Type: Enhancement > Affects Versions: 3.2.9.Final > Reporter: Konstantin Bulanov > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 3.2.11.Final > > > org.jboss.vfs.util.SuffixMatchFilter#accepts duplicate formating and string concationation > org.jboss.vfs.VirtualFile#getPathName(boolean) use recursive string concatenation with new StringBuilder for eacht step, as result we allocate annesesary char[] during start server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5640) No EJB receiver available for handling

by Ivan Straka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5640?page=com.atlassian.jira.plugin.... ] Ivan Straka moved JBEAP-1775 to WFLY-5640: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-5640 (was: JBEAP-1775) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: Clustering EJB Test Suite (was: Clustering) (was: EJB) (was: Test Suite) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR4 (was: 7.0.0.DR12) > No EJB receiver available for handling > -------------------------------------- > > Key: WFLY-5640 > URL: https://issues.jboss.org/browse/WFLY-5640 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB, Test Suite > Affects Versions: 10.0.0.CR4 > Environment: hp-ux 11v3 - hpjdk1.8 > solaris 10,11 - x86 and x86_64, rhel 6 - x86 and x86_64, rhel 7 x86_64 - openjdk1.8, ibmjdk1.8, oraclejdk1.8 > Reporter: Ivan Straka > Assignee: Paul Ferraro > Attachments: logs > > > There are two tests failing in exteded tests in clusteringejb2 package in AS TS. > org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceSpecifiedByDescriptor > org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceAnnotatedBean > both with exception > {code} > Error Message > EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@54acff7d > Stacktrace > java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@54acff7d > at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:112) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) > at com.sun.proxy.$Proxy28.create(Unknown Source) > at org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.loadbalance(RemoteStatelessFailoverTestCase.java:262) > at org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.testLoadbalanceAnnotatedBean(RemoteStatelessFailoverTestCase.java:224) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5590) Shared object store recovery problem

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5590?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan closed WFLY-5590. -------------------------------- Resolution: Rejected Problem was on side of Test XA Resource. > Shared object store recovery problem > ------------------------------------ > > Key: WFLY-5590 > URL: https://issues.jboss.org/browse/WFLY-5590 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.CR3 > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Critical > Attachments: Server1.log, Server2.log > > > There is a problem with recovery of crashed transactions on two servers when they share the same object store. > The server which starts the recovery second, has problems with processing the logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1049) ConcreteResourceRegistration#registerSubModel is not thread safe

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1049?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1049: ------------------------------------- Short term solution could be that we just make sure that registerDeploymentModel stuff is thread safe. > ConcreteResourceRegistration#registerSubModel is not thread safe > ---------------------------------------------------------------- > > Key: WFCORE-1049 > URL: https://issues.jboss.org/browse/WFCORE-1049 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Stuart Douglas > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > registerSubModel checks for existing, then registers, however it is invoked by two threads at the same time it is possible they will both see the resource as not existing and both register. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-970) Missing date coercion in constraint using an instance field or a declaration

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-970?page=com.atlassian.jira.plugin... ] Mario Fusco closed DROOLS-970. ------------------------------ Resolution: Done > Missing date coercion in constraint using an instance field or a declaration > ---------------------------------------------------------------------------- > > Key: DROOLS-970 > URL: https://issues.jboss.org/browse/DROOLS-970 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > Automatic String to Date coercion is not performed in case the accessed field is not a getter method but an instance field of the class as in: > {code} > public class Person { > public java.util.Date date; > } > rule x when > Person( date < "1-Jan-2000" ) // Error flagged here, if... > then ...end > {code} > or when the class has proper a getter method but the constraint is expressed with a binding declaration as in: > {code} > rule x when > Person( $date: date, $date < "1-Jan-2000" ) > then ...end > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1049) ConcreteResourceRegistration#registerSubModel is not thread safe

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1049?page=com.atlassian.jira.plugi... ] Stuart Douglas commented on WFCORE-1049: ---------------------------------------- Maybe this method should just be synchronized for now? I doubt it will have any measurable impact on startup time. > ConcreteResourceRegistration#registerSubModel is not thread safe > ---------------------------------------------------------------- > > Key: WFCORE-1049 > URL: https://issues.jboss.org/browse/WFCORE-1049 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Stuart Douglas > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > registerSubModel checks for existing, then registers, however it is invoked by two threads at the same time it is possible they will both see the resource as not existing and both register. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015