[#GDS-134] Stateful session beans are cached in application context (should be in session cache) - Granite Data Services

GraniteDS

Stateful session beans are cached in application context (should be in session cache)

Created: 08/Jul/08 11:38 AM Updated: 14/Oct/08 11:26 AM Resolved: 03/Aug/08 10:22 PM

Component/s:

EJB3 Services

Affects Version/s:

1.1.0_RC3

Fix Version/s:

1.1.0_RC4

Sort Order:

[ Permalink | « Hide ]

Franck Wolff added a comment - 16/Jul/08 11:54 AM

Done.

[ Permalink | « Hide ]

Franck Wolff added a comment - 03/Aug/08 10:00 PM

Previous fix doesn't work with remote stateful ejbs.

[ Permalink | « Hide ]

Franck Wolff added a comment - 03/Aug/08 10:22 PM

Done.

[ Permalink | « Hide ]

Björn Abt added a comment - 14/Oct/08 11:26 AM

Hello Franck,

either I'm doing something wrong or this problem doesn't seem to be fixed.
My setup is as follows:
- JBoss 4.2.2 on JDK1.5 (Windows and Linux)
- Flex 3
- GraniteDS 1.1.0.GA
- Stateful session bean as the remote service

Now what happens is that all the clients get routed to the same stateful session bean, although the AMF3Serializer shows different clientId's. Is there an option in the config to enable that stateful session are cached in the session?

Nevertheless I pretty much appreciate the great job you guys do.