June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6386) NoSuchMethodException when configuring a filter in undertow subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6386?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-6386. ----------------------------- Resolution: Rejected you should use expression filter <expression-filter name="ranges" expression="byte-range(send-accept-ranges=true|false)" /> > NoSuchMethodException when configuring a filter in undertow subsystem > --------------------------------------------------------------------- > > Key: WFLY-6386 > URL: https://issues.jboss.org/browse/WFLY-6386 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Jason Holmberg > Assignee: Tomaz Cerar > Priority: Critical > > Configuring a filter in the undertow subsystem that does not have a single arg constructor that takes HttpHandler will produce a runtime exception similar to this: > {noformat} > 11:09:46,832 ERROR [io.undertow.request] (default I/O-7) UT005071: Undertow request failed HttpServerExchange{ GET /vidtest/ request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8], Accept-Language=[en-US,en;q=0.8], Cache-Control=[max-age=0], Accept-Encoding=[gzip, deflate, sdch], User-Agent=[Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36], If-Modified-Since=[Wed, 16 Mar 2016 14:48:13 GMT], Connection=[keep-alive], If-None-Match=[W/"266-1458139693000"], Upgrade-Insecure-Requests=[1], Host=[localhost:8080]} response {}}: java.lang.RuntimeException: WFLYUT0064: Failed to configure handler class io.undertow.server.handlers.ByteRangeHandler > at org.wildfly.extension.undertow.deployment.ConfiguredHandlerWrapper.wrap(ConfiguredHandlerWrapper.java:78) > at org.wildfly.extension.undertow.filters.CustomFilterDefinition.createHttpHandler(CustomFilterDefinition.java:100) > at org.wildfly.extension.undertow.filters.FilterService.createHttpHandler(FilterService.java:57) > at org.wildfly.extension.undertow.filters.FilterRef.createHttpHandler(FilterRef.java:69) > at org.wildfly.extension.undertow.LocationService.configureHandlerChain(LocationService.java:96) > at org.wildfly.extension.undertow.Host.configureRootHandler(Host.java:117) > at org.wildfly.extension.undertow.Host.getOrCreateRootHandler(Host.java:171) > at org.wildfly.extension.undertow.Host$HostRootHandler.handleRequest(Host.java:285) > at io.undertow.server.handlers.NameVirtualHostHandler.handleRequest(NameVirtualHostHandler.java:54) > at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:76) > at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49) > at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:158) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:232) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:130) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:145) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:92) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:51) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:121) > at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:580) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:464) > Caused by: java.lang.NoSuchMethodException: io.undertow.server.handlers.ByteRangeHandler.<init>(io.undertow.server.HttpHandler) > at java.lang.Class.getConstructor0(Class.java:3082) > at java.lang.Class.getConstructor(Class.java:1825) > at org.wildfly.extension.undertow.deployment.ConfiguredHandlerWrapper.wrap(ConfiguredHandlerWrapper.java:55) > ... 24 more > {noformat} > The problem seems to be [here|https://github.com/wildfly/wildfly/blob/master/undertow/src/main/jav...] in the {{org.wildfly.extension.undertow.deployment.ConfiguredHandlerWrapper}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6697) @PreDestroy beans not called when performing disable in domain mode

by Robert Smith (JIRA)

[ https://issues.jboss.org/browse/WFLY-6697?page=com.atlassian.jira.plugin.... ] Robert Smith edited comment on WFLY-6697 at 6/14/16 8:34 AM: ------------------------------------------------------------- Disable is an option from the web console under Deployments. was (Author: rsmith1): Disable is an option from the web console. > @PreDestroy beans not called when performing disable in domain mode > ------------------------------------------------------------------- > > Key: WFLY-6697 > URL: https://issues.jboss.org/browse/WFLY-6697 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.2.Final > Reporter: Robert Smith > Assignee: Brian Stansberry > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6697) @PreDestroy beans not called when performing disable in domain mode

by Robert Smith (JIRA)

[ https://issues.jboss.org/browse/WFLY-6697?page=com.atlassian.jira.plugin.... ] Robert Smith commented on WFLY-6697: ------------------------------------ Disable is an option from the web console. > @PreDestroy beans not called when performing disable in domain mode > ------------------------------------------------------------------- > > Key: WFLY-6697 > URL: https://issues.jboss.org/browse/WFLY-6697 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.2.Final > Reporter: Robert Smith > Assignee: Brian Stansberry > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4316?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4316: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1346242 Bugzilla Update: Perform > 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.Beta1 > > > {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.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1593) Update the default variable value in .jbossclirc file

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1593?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-1593: ------------------------------ Labels: downstream_dependency (was: ) > Update the default variable value in .jbossclirc file > ----------------------------------------------------- > > Key: WFCORE-1593 > URL: https://issues.jboss.org/browse/WFCORE-1593 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > Labels: downstream_dependency > > $JBOSS_HOME/bin/.jbossclirc file can be used to set up CLI variables or to run a set of CLI commands at the beginning of every new CLI session. It contain a *commented out* CLI variable declaration part. > Although the _myvar_ is commented out by default, we should update it's value to some real working example to improve the quality of example (one user was already confused :) ). > {code:diff} > -# set myvar=/subsystem=datasources/data-source=myDS > +# set myvar=/subsystem=datasources/data-source=ExampleDS > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1593) Update the default variable value in .jbossclirc file

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1593?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-4987 to WFCORE-1593: ------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1593 (was: JBEAP-4987) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Target Release: (was: 7.backlog.GA) Affects Version/s: 3.0.0.Alpha1 (was: 7.0.0.GA) > Update the default variable value in .jbossclirc file > ----------------------------------------------------- > > Key: WFCORE-1593 > URL: https://issues.jboss.org/browse/WFCORE-1593 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > $JBOSS_HOME/bin/.jbossclirc file can be used to set up CLI variables or to run a set of CLI commands at the beginning of every new CLI session. It contain a *commented out* CLI variable declaration part. > Although the _myvar_ is commented out by default, we should update it's value to some real working example to improve the quality of example (one user was already confused :) ). > {code:diff} > -# set myvar=/subsystem=datasources/data-source=myDS > +# set myvar=/subsystem=datasources/data-source=ExampleDS > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6697) @PreDestroy beans not called when performing disable in domain mode

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-6697?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-6697: ------------------------------------ Been a while since I last checked the management operations on deployments - how exactly do you disable deployment in standalone mode (and in domain mode)? > @PreDestroy beans not called when performing disable in domain mode > ------------------------------------------------------------------- > > Key: WFLY-6697 > URL: https://issues.jboss.org/browse/WFLY-6697 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.2.Final > Reporter: Robert Smith > Assignee: Brian Stansberry > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6113) TransactionAttributeMergingProcessor fails when using generics

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-6113?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-6113: ------------------------------------ The linked Jandex issue has been resolved and the newer version of that library has been merged to WildFly upstream https://github.com/wildfly/wildfly/pull/8829, so this will be available in the next WildFly 10.x release. In fact, you can verify this against the latest nightly builds of WildFly https://developer.jboss.org/thread/224262 > TransactionAttributeMergingProcessor fails when using generics > -------------------------------------------------------------- > > Key: WFLY-6113 > URL: https://issues.jboss.org/browse/WFLY-6113 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Markus Chur > Assignee: Fedor Gavrilov > Priority: Minor > Attachments: log.txt, reproducer.zip > > > Deployment fails when using type safe generics on session beans with transaction attributes. See reproducer. Works with 9.0.2.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6113) TransactionAttributeMergingProcessor fails when using generics

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-6113?page=com.atlassian.jira.plugin.... ] jaikiran pai edited comment on WFLY-6113 at 6/13/16 10:56 PM: -------------------------------------------------------------- [~jamesbaxter], The linked Jandex issue has been resolved and the newer version of that library has been merged to WildFly upstream https://github.com/wildfly/wildfly/pull/8829, so this will be available in the next WildFly 10.x release. In fact, you can verify this against the latest nightly builds of WildFly https://developer.jboss.org/thread/224262 was (Author: jaikiran): The linked Jandex issue has been resolved and the newer version of that library has been merged to WildFly upstream https://github.com/wildfly/wildfly/pull/8829, so this will be available in the next WildFly 10.x release. In fact, you can verify this against the latest nightly builds of WildFly https://developer.jboss.org/thread/224262 > TransactionAttributeMergingProcessor fails when using generics > -------------------------------------------------------------- > > Key: WFLY-6113 > URL: https://issues.jboss.org/browse/WFLY-6113 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Markus Chur > Assignee: Fedor Gavrilov > Priority: Minor > Attachments: log.txt, reproducer.zip > > > Deployment fails when using type safe generics on session beans with transaction attributes. See reproducer. Works with 9.0.2.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6706) Domain mode stack trace on session invalidate

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-6706?page=com.atlassian.jira.plugin.... ] jaikiran pai updated WFLY-6706: ------------------------------- Issue Type: Bug (was: Feature Request) > Domain mode stack trace on session invalidate > --------------------------------------------- > > Key: WFLY-6706 > URL: https://issues.jboss.org/browse/WFLY-6706 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Web (Undertow) > Affects Versions: 9.0.2.Final > Reporter: Robert Smith > Assignee: Brian Stansberry > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 June 2016