Category Archives: BlazeDs
This annoying particular problem is quite easy to solve in most cases. What makes it complicated sometimes, is either the misleading message tail:
generally due to the remote host disabling session cookies. Session cookies must be enabled to manage the client connection correctly.
which will guide you to a wrong road generally, either the initial concurrent calls to BlazeDs Server associating two different flex ID with the same JEE session.
Identifying the root cause
- Install flash player debugger version on your Firefox
- Enable BlazeDs debug traces
<target class="flex.messaging.log.ConsoleTarget" level="DEBUG">
- Enable log4j debug traces
- Identify Flex remote object calls
Must-know before troubleshooting
- Flex Session is different from JEE session (JSEESSIONID)
- You don’t have to disable duplicate session check in BlazeDs, that’s why I won’t tell you how to do it.
- Each Endpoint is associated with a distinct flex client; So if you are using two endpoints for example you have two flex client at the same time created on first method call.
Flex Session mechanism
- On the first call for JEE server, the Flex application has a null Session ID.
- When BlazeDs receives a call from a session with a null ID, it generates a new Flex session ID and binds it with the current Java server session.
- The SWF holds this id for the relative Endpoint and assign it on every call to that endpoint.
Somehow, BlazeDS received two calls from the SWF with null ID, “at the same time”, so he creates and ID for the first call and another one for the second call. Those IDs are binded to the active Java session.
On the next remote object call, BlaseDS will check the Flex session associated with this Java session and will detect that two different flex session IDs are associated with the same Java session… and throw the famous “Detectd duplicate HTTP-based FlexSessions”, but that’s not due to host disabling session cookies.
How to solve the issue
- Load you application inside a JSP: Instead of calling your HTML main project page, let’s say it FlexProject.html, load your page inside a JSP page FlexProject.jsp
<%@ include file="FlexProject.html" %>
Step By Step:
1) Create New Dynamic Web Application:
2) Right click on the new created application, go to Flex Project Nature > Add Flex Project Nature
Choose the J2EE Application server Type. Then check the “use remote object access service” and keep LCDS selected. It’s not really LCDS, but its Open Source version (BlazeDs).
3) Click Next, Browse, Navigate to the blazeds.war:
then click Finish.
5) Go to project properties > Flex Server > Context Root and change the “/WebContent” to “/[YourProjectName]”
6) Go to the WebContent/WEB-INF, add a directory(config) and create an xml file (webApplicationContext.xml)
9) Now, unzip the spring integration with dependencies files and copy all the jars into your lib directory. You’ll find some double version jars, so just choose the newest.
10) Add a java entity to your src dir. In this project, we start with a small sample class “Document”:
and then create a database table called Document with three fields (id:Integer,type:varchar(20), title:varchar(50));
That’s all with Spring and hibernate code. we need just to add those entities to our configuration file:
add the annotated class to your session factory:
12)Now move to the Flex part and create the corresponding AS3(ActionScript 3) entity to your Java ‘Document’ class.
Note the meta-tag RemoteClass that describes the corresponding class on the Java side. It’s crucial to keep the same names of attributes, but don’t care that much about the scope (private/public/…) of the AS class attribute.
and then declare the mx:RemoteObject and some code for insert operation: