5:49 p.m.
Need to properly test the PooledInvoker for scoped invocations
--------------------------------------------------------------
Key: JBAS-3863
URL: http://jira.jboss.com/jira/browse/JBAS-3863
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Remoting
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Adrian Brock
Since the above task shows that even the most basic marshalling of the return type is not
present
in the PooledInvoker code, there are clearly no serious tests of the PooledInvoker in
scoped environments.
These tests need to be written and any broken behaviour fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3863) Need to properly test the PooledInvoker for scoped invocations
[ http://jira.jboss.com/jira/browse/JBAS-3863?page=comments#action_12349544 ]
Tom Elrod commented on JBAS-3863:
----------------------------------
Have created testsuite tests for scoped deployments using pooled invoker. These tests are
found under the testsuite/src/main/org/jboss/test/scoped directory and contains a
readme.txt file which includes the following:
This test is for JBAS-3198. The bug that is being tested for is when using two scoped ejb
deployments and
the pooled invoker, the OptimizedObjectInputStream was caching the class definitions when
loaded in a static
cache without regard to which classloader the class was originally loaded from.
Therefore, if ejbA made a call
and loaded class Foo (with serialVersionUID = 1L) and then ejbB tried to load class Foo
(which would have
a serialVerionUID = 2L), the first Foo class loaded (i.e. serialVersionUID = 1L) would be
retreived from the
cache and used instead of loading the correct class.
For the tests themselves, have created two ejb deployments, A and B, which are both scoped
deployments.
Both return SimpleResponseDTO. The test clients (ScopedUnitTestCase and
ScopedBUnitTestCase) use
javassist to create a new copy of the SimpleResponseDTO class (one with serialiVersionUID
= 1L and the other
with serialVersionUID = 2L) that gets included its ejb deployment and on local classpath
(for the client).
To properly test, have to run both ScopedUnitTestCase and then ScopedBUnitTestCase (or
vise versa) against
same running instance of JBoss server (i.e. running one, then re-booting JBossAS and
running the other does
not test for this bug fix).
Need to properly test the PooledInvoker for scoped invocations
--------------------------------------------------------------
Key: JBAS-3863
URL: http://jira.jboss.com/jira/browse/JBAS-3863
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Remoting
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Adrian Brock
Fix For: JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-5.0.0.Beta2
Since the above task shows that even the most basic marshalling of the return type is not
present
in the PooledInvoker code, there are clearly no serious tests of the PooledInvoker in
scoped environments.
These tests need to be written and any broken behaviour fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-3863) Need to properly test the PooledInvoker for scoped invocations
[ http://jira.jboss.com/jira/browse/JBAS-3863?page=all ]
Tom Elrod resolved JBAS-3863.
------------------------------
Resolution: Done
Fix Version/s: JBossAS-4.0.5.SP1
JBossAS-5.0.0.Beta2
JBossAS-4.2.0.CR1
Need to properly test the PooledInvoker for scoped invocations
--------------------------------------------------------------
Key: JBAS-3863
URL: http://jira.jboss.com/jira/browse/JBAS-3863
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Remoting
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Adrian Brock
Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1
Since the above task shows that even the most basic marshalling of the return type is not
present
in the PooledInvoker code, there are clearly no serious tests of the PooledInvoker in
scoped environments.
These tests need to be written and any broken behaviour fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3863) Need to properly test the PooledInvoker for scoped invocations
[ http://jira.jboss.com/jira/browse/JBAS-3863?page=comments#action_12349545 ]
Tom Elrod commented on JBAS-3863:
----------------------------------
Following test files added to testsuite for:
https://svn.jboss.org/repos/jbossas/branches/Branch_4_0
https://svn.jboss.org/repos/jbossas/branches/Branch_4_2
https://svn.jboss.org/repos/jbossas/trunk
Modified:
branches/Branch_4_0/testsuite/imports/test-jars.xml
Added:
branches/Branch_4_0/testsuite/imports/sections/scoped.xml
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/ejb/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/ejb/a/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/ejb/a/SessionAEJB.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/ejb/b/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/ejb/b/SessionBEJB.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/a/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/a/SessionA.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/a/SessionAHome.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/b/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/b/SessionB.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/b/SessionBHome.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/dto/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/dto/SimpleRequestDTO.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/dto/SimpleResponseDTO.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/test/
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/test/ScopedUnitTestCase.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/readme.txt
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/interfaces/dto/SimpleResponseDTO.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/test/ScopedBUnitTestCase.java
branches/Branch_4_0/testsuite/src/main/org/jboss/test/scoped/test/ScopedUnitTestCase.java
branches/Branch_4_0/testsuite/src/resources/scoped/
branches/Branch_4_0/testsuite/src/resources/scoped/a/
branches/Branch_4_0/testsuite/src/resources/scoped/a/ear/
branches/Branch_4_0/testsuite/src/resources/scoped/a/ear/META-INF/
branches/Branch_4_0/testsuite/src/resources/scoped/a/ear/META-INF/application.xml
branches/Branch_4_0/testsuite/src/resources/scoped/a/ear/META-INF/jboss-app.xml
branches/Branch_4_0/testsuite/src/resources/scoped/a/ejb/
branches/Branch_4_0/testsuite/src/resources/scoped/a/ejb/META-INF/
branches/Branch_4_0/testsuite/src/resources/scoped/a/ejb/META-INF/ejb-jar.xml
branches/Branch_4_0/testsuite/src/resources/scoped/a/ejb/META-INF/jboss.xml
branches/Branch_4_0/testsuite/src/resources/scoped/b/
branches/Branch_4_0/testsuite/src/resources/scoped/b/ear/
branches/Branch_4_0/testsuite/src/resources/scoped/b/ear/META-INF/
branches/Branch_4_0/testsuite/src/resources/scoped/b/ear/META-INF/application.xml
branches/Branch_4_0/testsuite/src/resources/scoped/b/ear/META-INF/jboss-app.xml
branches/Branch_4_0/testsuite/src/resources/scoped/b/ejb/
branches/Branch_4_0/testsuite/src/resources/scoped/b/ejb/META-INF/
branches/Branch_4_0/testsuite/src/resources/scoped/b/ejb/META-INF/ejb-jar.xml
branches/Branch_4_0/testsuite/src/resources/scoped/b/ejb/META-INF/jboss.xml
Need to properly test the PooledInvoker for scoped invocations
--------------------------------------------------------------
Key: JBAS-3863
URL: http://jira.jboss.com/jira/browse/JBAS-3863
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Remoting
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Adrian Brock
Fix For: JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-5.0.0.Beta2
Since the above task shows that even the most basic marshalling of the return type is not
present
in the PooledInvoker code, there are clearly no serious tests of the PooledInvoker in
scoped environments.
These tests need to be written and any broken behaviour fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6350
days inactive
6399
days old
3 comments
2 participants
participants (2)
-
Adrian Brock (JIRA) -
Tom Elrod (JIRA)