March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4282) Add listDeliveringMessages and listScheduledMessages to JMS queues

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4282?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4282: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Add listDeliveringMessages and listScheduledMessages to JMS queues > ------------------------------------------------------------------ > > Key: WFLY-4282 > URL: https://issues.jboss.org/browse/WFLY-4282 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 9.0.0.CR1 > > > Requires HornetQ upgrade (currently 2.4.5.Final) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4186) Improve Infinispan module compatibility with older releases

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4186?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4186: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Improve Infinispan module compatibility with older releases > ----------------------------------------------------------- > > Key: WFLY-4186 > URL: https://issues.jboss.org/browse/WFLY-4186 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > Infinispan 7 moved a bunch of classes from the org.infinispan:infinispan-core maven module into the org.infinispan:infinispan-commons module (which, itself, was introduced in Infinispan 6), which can cause user deployments that previously depended on org.infinispan to fail with mysterious NoClassDefFoundErrors if the org.infinispan.commons module was not also previously declared as a deployment dependency. > I suggest we either: > 1. Export org.infinispan.commons from the org.infinispan module > 2. Rename org.infinispan to org.infinispan.core, and create a new org.infinispan that exports both org.infinispan.core and org.infinispan.commons. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4304) Servlet authentication kicked off when *not* a part of any security-constraint

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4304?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4304: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Servlet authentication kicked off when *not* a part of any security-constraint > ------------------------------------------------------------------------------ > > Key: WFLY-4304 > URL: https://issues.jboss.org/browse/WFLY-4304 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Brett Meyer > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > Artificer runs on Wildfly 8.2 and uses Keycloak for auth. If our WAR contains a servlet that is *not* protected by a security-constraint in web.xml, Wildfly still attempts to authenticate the call (using Wireshark, I see the GET/POST get funneled through the Keycloak realm redirection) if basic auth credentials are in the header. In a keycloak-dev thread this past Dec., [~bill.burke] suggested this was most likely an issue within Wildfly auth itself. > A credentialed call on an un-protected servlet does sound like an edge case. However, this came up possibly due to a secondary symptom: > If I protect the servlet in web.xml, the call's Authorization header is stripped. I'm not currently able to figure out exactly where that's occurring... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4316) InvalidBytecodeException when an EJB local interface declares static method

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4316?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4316: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > InvalidBytecodeException when an EJB local interface declares static method > --------------------------------------------------------------------------- > > Key: WFLY-4316 > URL: https://issues.jboss.org/browse/WFLY-4316 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: 9.0.0.CR1 > > > {noformat} > Caused by: org.jboss.classfilewriter.InvalidBytecodeException: Cannot load variable at 1. Local Variables: Local Variables: [StackEntry [descriptor=Ljava/lang/String;, type=OBJECT]] > at org.jboss.classfilewriter.code.CodeAttribute.aload(CodeAttribute.java:185) > at org.jboss.invocation.proxy.ProxyFactory$ProxyMethodBodyCreator.overrideMethod(ProxyFactory.java:150) > at org.jboss.invocation.proxy.AbstractSubclassFactory.overrideMethod(AbstractSubclassFactory.java:106) > at org.jboss.invocation.proxy.AbstractSubclassFactory.addInterface(AbstractSubclassFactory.java:363) > at org.jboss.invocation.proxy.ProxyFactory.generateClass(ProxyFactory.java:286) > at org.jboss.invocation.proxy.AbstractClassFactory.buildClassDefinition(AbstractClassFactory.java:207) > at org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:160) > at org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:150) > at org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:150) > at org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:68) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81) > ... 6 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4305) Script rumbles on after error

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4305?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4305: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Script rumbles on after error > ----------------------------- > > Key: WFLY-4305 > URL: https://issues.jboss.org/browse/WFLY-4305 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > Fix For: 9.0.0.CR1 > > > After a failure in the script it rumbles on. > {noformat} > (master) carlo@devel01:~/work/wildfly$ ./build.sh clean > ./tools/download-maven.sh: 20: ./tools/download-maven.sh: curl: not found > Archive: maven.zip > End-of-central-directory signature not found. Either this file is not > a zipfile, or it constitutes one disk of a multi-part archive. In the > latter case the central directory and zipfile comment will be found on > the last disk(s) of this archive. > unzip: cannot find zipfile directory in one of maven.zip or > maven.zip.zip, and cannot find maven.zip.ZIP, period. > mv: cannot stat ‘apache-maven*’: No such file or directory > build.sh: Could not locate Maven; check $MVN or $MAVEN_HOME. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4404) View does not inherit 'default' methods from interfaces( JDK8 )

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4404?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4404: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > View does not inherit 'default' methods from interfaces( JDK8 ) > --------------------------------------------------------------- > > Key: WFLY-4404 > URL: https://issues.jboss.org/browse/WFLY-4404 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 9.0.0.CR1 > > > View and View service do not inherit JDK8 'default' methods from interfaces. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4407) Upgrade wildfly-core to 1.0.0.Beta1

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4407?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4407: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Upgrade wildfly-core to 1.0.0.Beta1 > ----------------------------------- > > Key: WFLY-4407 > URL: https://issues.jboss.org/browse/WFLY-4407 > Project: WildFly > Issue Type: Component Upgrade > Affects Versions: 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4392) Make use of TCCL in ARQ ManagedContainer configurable

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4392?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4392: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Make use of TCCL in ARQ ManagedContainer configurable > ----------------------------------------------------- > > Key: WFLY-4392 > URL: https://issues.jboss.org/browse/WFLY-4392 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR1 > > > In WildFly it is considerred intended behaviour that test code gets called with the TCCL set to the test deployment. IMHO this shadows potential problems when the functionality under test is not called from an ARQ test case (i.e. from an normal javaee endpoint) > For Camel integration this behaviour is not acceptable. > CrossLink: https://github.com/wildfly-extras/wildfly-camel/issues/340 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4438) Singleton EJB constructor called per method invocation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4438?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4438: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Singleton EJB constructor called per method invocation > ------------------------------------------------------ > > Key: WFLY-4438 > URL: https://issues.jboss.org/browse/WFLY-4438 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.2.0.Final, 9.0.0.Alpha1 > Reporter: Kirill Gaevskii > Assignee: Martin Kouba > Fix For: 9.0.0.CR1 > > > @Singleton EJB constructor and @PostConstruct method call not once. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-311) JspConfig init isn't thread safe and can cause ConcurrentModificationException

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/JBWEB-311?page=com.atlassian.jira.plugin.... ] Aaron Ogburn updated JBWEB-311: ------------------------------- Attachment: (was: reproducer.zip) > JspConfig init isn't thread safe and can cause ConcurrentModificationException > ------------------------------------------------------------------------------ > > Key: JBWEB-311 > URL: https://issues.jboss.org/browse/JBWEB-311 > Project: JBoss Web > Issue Type: Bug > Affects Versions: JBossWeb-2.1.13.GA > Reporter: Aaron Ogburn > Assignee: Aaron Ogburn > Attachments: reproducer.zip > > > JspConfig init isn't thread safe and can cause the following ConcurrentModificationException: > {code} > java.util.ConcurrentModificationException > at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) > at java.util.AbstractList$Itr.next(AbstractList.java:343) > at org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:303) > at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:112) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:333) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:313) > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:300) > at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:585) > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312) > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322) > {code} > Issue occurs like so: > 1) thread a starts JspConfig.init/proccessWebDotXml > 2) thread b starts JspConfig.init/proccessWebDotXml > 3) thread a finishes JspConfig.init/proccessWebDotXml and then calls JspConfig.findJspProperty > 4) thread b sets the jspProperties vector before thread a gets an iterator of it > 5) thread b modifies the jspProperties vector, causing the ConcurrentModificationException in thread a -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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