March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4331) EJB Asynchronous pass POJO by reference leading to ClassCastException errors in remote invocations

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4331?page=com.atlassian.jira.plugin.... ] Tomasz Adamski commented on WFLY-4331: -------------------------------------- Yeah I look at this part of spec to and I'm a bit confused as TCK returns non serializable object in EJB invocation. Is it possible that arguments passed as parameters are treated differently that returned values? > EJB Asynchronous pass POJO by reference leading to ClassCastException errors in remote invocations > -------------------------------------------------------------------------------------------------- > > Key: WFLY-4331 > URL: https://issues.jboss.org/browse/WFLY-4331 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Beta1 > > > When invoking EJB asynchronous in different deployments and returning a POJO object, which will be retrieved using future.get, we have ClassCastException error. > {code} > 12:53:50,147 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /testejb-web/async: java.lang.ClassCastException: rh.test.ReturnObject cannot be cast to rh.test.ReturnObject > at rh.test.AsyncServlet.doGet(AsyncServlet.java:29) [classes:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:259) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:246) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:75) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:165) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:737) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4331) EJB Asynchronous pass POJO by reference leading to ClassCastException errors in remote invocations

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4331?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFLY-4331: --------------------------------- Comment: was deleted (was: Yeah I look at this part of spec to and I'm a bit confused as TCK returns non serializable object in EJB invocation. Is it possible that arguments passed as parameters are treated differently that returned values?) > EJB Asynchronous pass POJO by reference leading to ClassCastException errors in remote invocations > -------------------------------------------------------------------------------------------------- > > Key: WFLY-4331 > URL: https://issues.jboss.org/browse/WFLY-4331 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Beta1 > > > When invoking EJB asynchronous in different deployments and returning a POJO object, which will be retrieved using future.get, we have ClassCastException error. > {code} > 12:53:50,147 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /testejb-web/async: java.lang.ClassCastException: rh.test.ReturnObject cannot be cast to rh.test.ReturnObject > at rh.test.AsyncServlet.doGet(AsyncServlet.java:29) [classes:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:259) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:246) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:75) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:165) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:737) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-575) Include bin/client/jboss-cli-client.jar in WildFly Core dist

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-575?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFCORE-575. ------------------------------------- Resolution: Rejected Changed my mind; adds bloat, and I found a workaround for testing the CLI as a non-modular app. Just use cli/target/wildfly-cli-<version>-client.jar. > Include bin/client/jboss-cli-client.jar in WildFly Core dist > ------------------------------------------------------------ > > Key: WFCORE-575 > URL: https://issues.jboss.org/browse/WFCORE-575 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Beta1 > > > Put the jboss-cli-client.jar in the core dist (but not core-feature-pack). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-575) Include bin/client/jboss-cli-client.jar in WildFly Core dist

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-575: --------------------------------------- Summary: Include bin/client/jboss-cli-client.jar in WildFly Core dist Key: WFCORE-575 URL: https://issues.jboss.org/browse/WFCORE-575 Project: WildFly Core Issue Type: Enhancement Components: CLI Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.Beta1 Put the jboss-cli-client.jar in the core dist (but not core-feature-pack). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-127) Consider introducing SASL GS2 support

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-127?page=com.atlassian.jira.plugin.sy... ] Farah Juma reassigned ELY-127: ------------------------------ Assignee: Farah Juma > Consider introducing SASL GS2 support > ------------------------------------- > > Key: ELY-127 > URL: https://issues.jboss.org/browse/ELY-127 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: David Lloyd > Assignee: Farah Juma > Fix For: 1.0.0.Beta1 > > > RFC 5801 (http://tools.ietf.org/html/rfc5801) specifies a GSS based SASL mechanism that has several improvements over GSSAPI that are worth considering. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-574) Upgrade jboss-invocation with version that includes fix for WFLY-4316

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-574?page=com.atlassian.jira.plugin... ] Tomaz Cerar updated WFCORE-574: ------------------------------- Component/s: Server > Upgrade jboss-invocation with version that includes fix for WFLY-4316 > --------------------------------------------------------------------- > > Key: WFCORE-574 > URL: https://issues.jboss.org/browse/WFCORE-574 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Tomaz Cerar > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > Upgrade jboss-invocation with version that includes https://github.com/jbossas/jboss-invocation/pull/7 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-574) Upgrade jboss-invocation with version that includes fix for WFLY-4316

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-574: ---------------------------------- Summary: Upgrade jboss-invocation with version that includes fix for WFLY-4316 Key: WFCORE-574 URL: https://issues.jboss.org/browse/WFCORE-574 Project: WildFly Core Issue Type: Component Upgrade Reporter: Tomaz Cerar Assignee: David Lloyd Fix For: 1.0.0.Beta1 Upgrade jboss-invocation with version that includes https://github.com/jbossas/jboss-invocation/pull/7 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-573) ReadResourceHandler should deal with resources that disappear in the middle of the request

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-573: --------------------------------------- Summary: ReadResourceHandler should deal with resources that disappear in the middle of the request Key: WFCORE-573 URL: https://issues.jboss.org/browse/WFCORE-573 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry ReadResourceHandler works by adding a number of steps and assembling the results. Steps are added to read each attribute and to read children (if recursive=true). With runtime resources, the resource associated with each added step may have disappeared between when the code decided to do the read and when the step executes. We should detect and handle this, treating it as if the resource in question never existed. See discussion on https://github.com/wildfly/wildfly/pull/6607. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-572) Review usage of the two different NoSuchResourceException's

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-572?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-572: ----------------------------------------- No need. There are no uses of org.jboss.as.controller.NoSuchResourceException outside of WildFly Core. That's one factor in why I elected to make it the one that gets deprecated. > Review usage of the two different NoSuchResourceException's > ----------------------------------------------------------- > > Key: WFCORE-572 > URL: https://issues.jboss.org/browse/WFCORE-572 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > > There are two versions of the {{NoSuchResourceException}}, [{{org.jboss.as.controller.NoSuchResourceException}}|https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/NoSuchResourceException.java] and [{{org.jboss.as.controller.registry.Resource.NoSuchResourceException}}|https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/registry/Resource.java#L299]. The usages should be reviewed as some code seems to catch one where the other is likely thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-572) Review usage of the two different NoSuchResourceException's

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-572?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-572: -------------------------------------- Should we clone this to WildFly too as there is probably some usages there as well? > Review usage of the two different NoSuchResourceException's > ----------------------------------------------------------- > > Key: WFCORE-572 > URL: https://issues.jboss.org/browse/WFCORE-572 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > > There are two versions of the {{NoSuchResourceException}}, [{{org.jboss.as.controller.NoSuchResourceException}}|https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/NoSuchResourceException.java] and [{{org.jboss.as.controller.registry.Resource.NoSuchResourceException}}|https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/registry/Resource.java#L299]. The usages should be reviewed as some code seems to catch one where the other is likely thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2015