October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3925) JAX-RS bean implemented as Stateless is destroyed after response

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3925?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-3925: ------------------------------ Steps to Reproduce: 1. Create this test bean: {code} @Path("/test2") @Stateless public class Test2 { @GET public String hello() { return "hello !"; } @PostConstruct protected void postConstruct() { System.out.println("Test2().postConstruct() " + this); } @PreDestroy protected void preDestroy() { System.out.println("Test2().preDestroy() " + this); } } {code} 2. Hit the URL (ex: http://localhost:8080/TestRest3/rest/test2) and look at the server output, something like this will show: {noformat} 16:21:46,430 INFO [stdout] (default task-41) Test1().postConstruct() test.Test2@890a1e2 16:21:46,432 INFO [stdout] (default task-41) Test1().preDestroy() test.Test2@890a1e2 {noformat} AFAIK SLSB shouldn't be destroyed after service request. was: 1. Create this test bean: @Path("/test2") @Stateless public class Test2 { @GET public String hello() { return "hello !"; } @PostConstruct protected void postConstruct() { System.out.println("Test2().postConstruct() " + this); } @PreDestroy protected void preDestroy() { System.out.println("Test2().preDestroy() " + this); } } 2. Hit the URL (ex: http://localhost:8080/TestRest3/rest/test2) and look at the server output, something like this will show: 16:21:46,430 INFO [stdout] (default task-41) Test1().postConstruct() test.Test2@890a1e2 16:21:46,432 INFO [stdout] (default task-41) Test1().preDestroy() test.Test2@890a1e2 AFAIK SLSB shouldn't be destroyed after service request. > JAX-RS bean implemented as Stateless is destroyed after response > ---------------------------------------------------------------- > > Key: WFLY-3925 > URL: https://issues.jboss.org/browse/WFLY-3925 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Sergio Samayoa > Assignee: Jason Greene > > A JAX-RS bean implemented as stateless EJB is destroyed after response is sent. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3925) JAX-RS bean implemented as Stateless is destroyed after response

by Sergio Samayoa (JIRA)

[ https://issues.jboss.org/browse/WFLY-3925?page=com.atlassian.jira.plugin.... ] Sergio Samayoa updated WFLY-3925: --------------------------------- Description: A JAX-RS bean implemented as stateless EJB is destroyed after response is sent. Steps to Reproduce: 1. Create this test bean: @Path("/test2") @Stateless public class Test2 { @GET public String hello() { return "hello !"; } @PostConstruct protected void postConstruct() { System.out.println("Test2().postConstruct() " + this); } @PreDestroy protected void preDestroy() { System.out.println("Test2().preDestroy() " + this); } } 2. Hit the URL (ex: http://localhost:8080/TestRest3/rest/test2) and look at the server output, something like this will show: 16:21:46,430 INFO [stdout] (default task-41) Test1().postConstruct() test.Test2@890a1e2 16:21:46,432 INFO [stdout] (default task-41) Test1().preDestroy() test.Test2@890a1e2 AFAIK SLSB shouldn't be destroyed after service request. Affects Version/s: 8.1.0.Final > JAX-RS bean implemented as Stateless is destroyed after response > ---------------------------------------------------------------- > > Key: WFLY-3925 > URL: https://issues.jboss.org/browse/WFLY-3925 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Sergio Samayoa > Assignee: Jason Greene > > A JAX-RS bean implemented as stateless EJB is destroyed after response is sent. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3925) JAX-RS bean implemented as Stateless is destroyed after response

by Sergio Samayoa (JIRA)

Sergio Samayoa created WFLY-3925: ------------------------------------ Summary: JAX-RS bean implemented as Stateless is destroyed after response Key: WFLY-3925 URL: https://issues.jboss.org/browse/WFLY-3925 Project: WildFly Issue Type: Bug Reporter: Sergio Samayoa Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3924) Facility to suppress interruption on EJB methods

by David Lloyd (JIRA)

David Lloyd created WFLY-3924: --------------------------------- Summary: Facility to suppress interruption on EJB methods Key: WFLY-3924 URL: https://issues.jboss.org/browse/WFLY-3924 Project: WildFly Issue Type: Enhancement Components: EJB Reporter: David Lloyd Assignee: David Lloyd Priority: Optional We should provide an annotation to mark an EJB method as uninterruptible, which prevents interruption from being delivered to the thread during the invocation (via forthcoming mechanism in JBoss Threads). Or, this could be a CDI facility, or both. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3923) Option for suppressing thread interruption during JDBC driver operations

by David Lloyd (JIRA)

David Lloyd created WFLY-3923: --------------------------------- Summary: Option for suppressing thread interruption during JDBC driver operations Key: WFLY-3923 URL: https://issues.jboss.org/browse/WFLY-3923 Project: WildFly Issue Type: Enhancement Components: JCA Reporter: David Lloyd Assignee: Jesper Pedersen Fix For: 9.0.0.CR1 The data source and JCA subsystems should provide a facility to suppress thread interruption during driver operations. The data source attribute should have values "on", "off", and "auto", where "auto" indicates that the subsystem should make a decision based on the driver. A list of drivers which are known to fail in the presence of interruption is forthcoming. A facility in JBoss Threads to suppress interruption for the duration of a task is forthcoming. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3922) Add a CheckedAction to each transaction upon creation/inflow to interrupt the transaction's associated threads

by David Lloyd (JIRA)

David Lloyd created WFLY-3922: --------------------------------- Summary: Add a CheckedAction to each transaction upon creation/inflow to interrupt the transaction's associated threads Key: WFLY-3922 URL: https://issues.jboss.org/browse/WFLY-3922 Project: WildFly Issue Type: Enhancement Components: Transactions Reporter: David Lloyd Assignee: Tom Jenkinson Fix For: 9.0.0.CR1 This will allow the application to receive a notification on transaction timeout or termination. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-622) DRLDumper does not output enum type declarations

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-622: ------------------------------------- Summary: DRLDumper does not output enum type declarations Key: DROOLS-622 URL: https://issues.jboss.org/browse/DROOLS-622 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final, 6.0.1.Final, 6.0.0.Final Reporter: Davide Sottara Assignee: Mark Proctor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-621) DRLDumper does not output trait type declarations correctly

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-621: ------------------------------------- Summary: DRLDumper does not output trait type declarations correctly Key: DROOLS-621 URL: https://issues.jboss.org/browse/DROOLS-621 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final, 6.0.1.Final, 6.0.0.Final Reporter: Davide Sottara Assignee: Davide Sottara -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-136) Create a new error message for suffix attribute on size-rotating-file-handler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-136?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-136: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1147806|https://bugzilla.redhat.com/show_bug.cgi?id=1147806] from POST to MODIFIED > Create a new error message for suffix attribute on size-rotating-file-handler > ------------------------------------------------------------------------------ > > Key: WFCORE-136 > URL: https://issues.jboss.org/browse/WFCORE-136 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha9 > > > As part of WFCORE-113, the suffix attribute on size-rotating-file-handler has a little bit different functionality than on other handlers (seconds or milliseconds are allowed). However the validation error message is the same as on other handlers ("seconds or milliseconds are not allowed"). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-132) BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-132?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-132: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1147067|https://bugzilla.redhat.com/show_bug.cgi?id=1147067] from POST to MODIFIED > BoundedQueueThreadPoolWriteAttributeHandler does not deal with undefined core-threads correctly > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-132 > URL: https://issues.jboss.org/browse/WFCORE-132 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha9 > > > BoundedQueueThreadPoolWriteAttributeHandler doesn't deal with undefined values for core-threads correctly. It assumes the attribute will be defined, and that's not required. > The attribute doesn't have a fixed default value. Instead, the behavior in add is to set the runtime value to match max-threads of core-threads is undefined. BoundedQueueThreadPoolWriteAttributeHandler should do the same. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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 October 2014