May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBAS-9585) CDI injection not working in WebListeners

by Archimedes Trajano (JIRA)

[ https://issues.jboss.org/browse/JBAS-9585?page=com.atlassian.jira.plugin.... ] Archimedes Trajano closed JBAS-9585. ------------------------------------ Resolution: Duplicate Issue > CDI injection not working in WebListeners > ----------------------------------------- > > Key: JBAS-9585 > URL: https://issues.jboss.org/browse/JBAS-9585 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: Weld/CDI > Affects Versions: 6.0.0.Final > Reporter: Archimedes Trajano > Assignee: Marius Bogoevici > > CDI injection is not performed for WebListeners, e.g. > @WebListener > public class BugListener implements HttpSessionListener > { > @Inject > BeanManager beanManager; > ... > } > Will have beanManager==null when the methods are hit -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBAS-9585) CDI injection not working in WebListeners

by Archimedes Trajano (JIRA)

Archimedes Trajano created JBAS-9585: ---------------------------------------- Summary: CDI injection not working in WebListeners Key: JBAS-9585 URL: https://issues.jboss.org/browse/JBAS-9585 Project: Application Server 3 4 5 and 6 Issue Type: Bug Components: Weld/CDI Affects Versions: 6.0.0.Final Reporter: Archimedes Trajano Assignee: Marius Bogoevici CDI injection is not performed for WebListeners, e.g. @WebListener public class BugListener implements HttpSessionListener { @Inject BeanManager beanManager; ... } Will have beanManager==null when the methods are hit -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8730) Upgrade Netty to 4.1.9 Final

by Amos Feng (JIRA)

Amos Feng created WFLY-8730: ------------------------------- Summary: Upgrade Netty to 4.1.9 Final Key: WFLY-8730 URL: https://issues.jboss.org/browse/WFLY-8730 Project: WildFly Issue Type: Component Upgrade Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6494) Improve Undertow subsystem plugability

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6494?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-6494. ---------------------------------- Resolution: Rejected This will be dealt with on a case by case basis > Improve Undertow subsystem plugability > -------------------------------------- > > Key: WFLY-6494 > URL: https://issues.jboss.org/browse/WFLY-6494 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > It should be easy for other subsystems/MSC based code to plug into the Undertow subsystem -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8729) The undertow attributes: "processing-time" and "max-processing-time" do not have "unit" defined

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8729?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-8729. ---------------------------------- Resolution: Duplicate Issue Duplicate of WFLY-8150 > The undertow attributes: "processing-time" and "max-processing-time" do not have "unit" defined > ----------------------------------------------------------------------------------------------- > > Key: WFLY-8729 > URL: https://issues.jboss.org/browse/WFLY-8729 > Project: WildFly > Issue Type: Bug > Reporter: Biljana Kramer > Assignee: Stuart Douglas > > The undertow attributes: "processing-time" and "max-processing-time" do not have "unit" defined. For instance, if you execute: > /subsystem=undertow/server=default-server/http-listener=default:read-resource-description > this will return: > ... > "max-processing-time" => { > "type" => LONG, > "description" => "The maximum processing time taken by a request on this listener", > "expressions-allowed" => false, > "nillable" => false, > "access-type" => "metric", > "storage" => "runtime" > }, > "no-request-timeout" => { > "type" => INT, > "description" => "The length of time in milliseconds that the connection can be idle before it is closed by the container, defaults to 60000 (one minute)", > "expressions-allowed" => true, > "nillable" => true, > "default" => 60000, > "unit" => "MILLISECONDS", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > "processing-time" => { > "type" => LONG, > "description" => "The total processing time of all requests handed by this listener", > "expressions-allowed" => false, > "nillable" => false, > "access-type" => "metric", > "storage" => "runtime" > ... > According to the code: > https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io... > attributes "processing-time" and "max-processing-time" should be shown as nano seconds. > I have just realised that only few attributes have "unit" defined - like "no-request-timeout" while the most of them is without it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8729) The undertow attributes: "processing-time" and "max-processing-time" do not have "unit" defined

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8729?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved UNDERTOW-985 to WFLY-8729: ----------------------------------------------- Project: WildFly (was: Undertow) Key: WFLY-8729 (was: UNDERTOW-985) > The undertow attributes: "processing-time" and "max-processing-time" do not have "unit" defined > ----------------------------------------------------------------------------------------------- > > Key: WFLY-8729 > URL: https://issues.jboss.org/browse/WFLY-8729 > Project: WildFly > Issue Type: Bug > Reporter: Biljana Kramer > Assignee: Stuart Douglas > > The undertow attributes: "processing-time" and "max-processing-time" do not have "unit" defined. For instance, if you execute: > /subsystem=undertow/server=default-server/http-listener=default:read-resource-description > this will return: > ... > "max-processing-time" => { > "type" => LONG, > "description" => "The maximum processing time taken by a request on this listener", > "expressions-allowed" => false, > "nillable" => false, > "access-type" => "metric", > "storage" => "runtime" > }, > "no-request-timeout" => { > "type" => INT, > "description" => "The length of time in milliseconds that the connection can be idle before it is closed by the container, defaults to 60000 (one minute)", > "expressions-allowed" => true, > "nillable" => true, > "default" => 60000, > "unit" => "MILLISECONDS", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > "processing-time" => { > "type" => LONG, > "description" => "The total processing time of all requests handed by this listener", > "expressions-allowed" => false, > "nillable" => false, > "access-type" => "metric", > "storage" => "runtime" > ... > According to the code: > https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io... > attributes "processing-time" and "max-processing-time" should be shown as nano seconds. > I have just realised that only few attributes have "unit" defined - like "no-request-timeout" while the most of them is without it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6671) ajp connection hangs if a post HTTP request header contains 'Transfer-Encoding: chunked'

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6671?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-6671. ---------------------------------- Fix Version/s: 11.0.0.Beta1 Resolution: Done > ajp connection hangs if a post HTTP request header contains 'Transfer-Encoding: chunked' > ----------------------------------------------------------------------------------------- > > Key: WFLY-6671 > URL: https://issues.jboss.org/browse/WFLY-6671 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Environment: Apache HTTP server 2.2.22 with mod_jk 1.2.37 > Reporter: river shen > Assignee: Stuart Douglas > Fix For: 11.0.0.Beta1 > > Attachments: service-1.0-SNAPSHOT.war, src.zip, stacks.txt, standalone.xml, workers.properties > > > When upgrading from JBOSS 7 to WILDFLY10, we observed following behavior: > if an HTTP post contains 'Transfer-Encoding: chunked' and 'Content-Type:appliation/octet-stream' in its head, A servlet which handles it will hang for ever ( until the client drop the connection) if it calls HttpServletRequest.getInputStream() and tries to read the whole content of the returned InputStream. The InputStream's read() method will block for ever at the end of the stream as opposed to return -1. > It only happens when the request is routed by apache web server through ajp; it does not happen if the client talks to wildfly directly through its 8080 http port. > We have attached a minimal web application that reproduce this issue. > Also attached is the standalone.xml and the apache configuration file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8728) Add support for legacy security realms to the EJB over HTTP invoker

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8728?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-10794 to WFLY-8728: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8728 (was: JBEAP-10794) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) > Add support for legacy security realms to the EJB over HTTP invoker > ------------------------------------------------------------------- > > Key: WFLY-8728 > URL: https://issues.jboss.org/browse/WFLY-8728 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBAS-8818) CDI injection not working in WebListeners

by Archimedes Trajano (JIRA)

[ https://issues.jboss.org/browse/JBAS-8818?page=com.atlassian.jira.plugin.... ] Archimedes Trajano edited comment on JBAS-8818 at 5/8/17 7:38 PM: ------------------------------------------------------------------ This still applies to WildFly 10. I am attempting to port my application which works properly on WebSphere Liberty and WebSphere 9.0 to WildFly and fixed most of the weird nuances such as... JPQL not supporting `NOT p.cancelled` and having to use p.cancelled = false` Using an undocumented (at least not in https://docs.jboss.org/author/display/AS71/Deployment+Descriptors+used+In...) jboss-app descriptor to set up the reference to the data source and adding a lookup name to it which I didn't need to do in WebSphere. Changing the scope of JPA Converters and using an explicit InitialContext lookup for SessionContext since @Resource didn't work in JPA Event Listeners. This problem with EJBs not being injected in WebListener also applies to WebService, WebServlet and JAX-RS as well. If you want to see a project that uses CDI extensively https://github.com/trajano/jee/tree/for-JBAS-8818 was (Author: archimedes.trajano): This still applies to WildFly 10. I am attempting to port my application which works properly on WebSphere Liberty and WebSphere 9.0 to WildFly and fixed most of the weird nuances such as... JPQL not supporting `NOT p.cancelled` and having to use p.cancelled = false` Using an undocumented (at least not in https://docs.jboss.org/author/display/AS71/Deployment+Descriptors+used+In...) jboss-app descriptor to set up the reference to the data source and adding a lookup name to it which I didn't need to do in WebSphere. Changing the scope of JPA Converters and using an explicit InitialContext lookup for SessionContext since @Resource didn't work in JPA Event Listeners. This problem with EJBs not being injected in WebListener also applies to WebService, WebServlet and JAX-RS as well. > CDI injection not working in WebListeners > ----------------------------------------- > > Key: JBAS-8818 > URL: https://issues.jboss.org/browse/JBAS-8818 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: Weld/CDI > Affects Versions: 6.0.0.Final > Reporter: Nicklas Karlsson > Assignee: Marius Bogoevici > > CDI injection is not performed for WebListeners, e.g. > @WebListener > public class BugListener implements HttpSessionListener > { > @Inject > BeanManager beanManager; > ... > } > Will have beanManager==null when the methods are hit -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBAS-8818) CDI injection not working in WebListeners

by Archimedes Trajano (JIRA)

[ https://issues.jboss.org/browse/JBAS-8818?page=com.atlassian.jira.plugin.... ] Archimedes Trajano commented on JBAS-8818: ------------------------------------------ This still applies to WildFly 10. I am attempting to port my application which works properly on WebSphere Liberty and WebSphere 9.0 to WildFly and fixed most of the weird nuances such as... JPQL not supporting `NOT p.cancelled` and having to use p.cancelled = false` Using an undocumented (at least not in https://docs.jboss.org/author/display/AS71/Deployment+Descriptors+used+In...) jboss-app descriptor to set up the reference to the data source and adding a lookup name to it which I didn't need to do in WebSphere. Changing the scope of JPA Converters and using an explicit InitialContext lookup for SessionContext since @Resource didn't work in JPA Event Listeners. This problem with EJBs not being injected in WebListener also applies to WebService, WebServlet and JAX-RS as well. > CDI injection not working in WebListeners > ----------------------------------------- > > Key: JBAS-8818 > URL: https://issues.jboss.org/browse/JBAS-8818 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: Weld/CDI > Affects Versions: 6.0.0.Final > Reporter: Nicklas Karlsson > Assignee: Marius Bogoevici > > CDI injection is not performed for WebListeners, e.g. > @WebListener > public class BugListener implements HttpSessionListener > { > @Inject > BeanManager beanManager; > ... > } > Will have beanManager==null when the methods are hit -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 May 2017