BlazeDS: Having issues in secured WebSphere 6.0 environment

Question

I have a BlazeDS package that I verified works in Tomcat, WebSphere and over SSL.  When I deploy to our target, secured environment (WebSphere 6, Tivoli Access Manager, ...), it blows up with the following error:<br /><br />[9/11/08 17:55:17:004 GMT+00:00] 0000002f ServletWrappe E   SRVE0014E: Uncaught service() exception root cause MessageBrokerServlet: Response already committed.<br />[9/11/08 17:55:17:036 GMT+00:00] 0000002f LocalTranCoor E   WLTC0017E: Resources rolled back due to setRollbackOnly() being called.<br />[9/11/08 17:55:17:053 GMT+00:00] 0000002f WebApp        E   SRVE0026E: [Servlet Error]-[MessageBrokerServlet]: java.lang.IllegalStateException: Response already committed.<br />     at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext. java:574)<br />     at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:868)<br />     at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:851)<br />     at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:393)<br /><br />Looking at line 393 in MessageBrokerServlet, it is trying to send an error back as follows res.sendError(HttpServletResponse.SC_FORBIDDEN);.  This is part of an else block that is called only if endpoint is null.<br /><br />Very odd as the exact same code package with the same endpoint and channel definition works in the other environments I mentioned.  The only difference is this environment is secured via SSL (which I tried locally without a problem) and Tivoli Access Manager.  Since the request is getting to the logs, it doesn't appear to be a Tivoli issue as if anything was wrong with the request, it would never get to the server.<br /><br />That leaves WebSphere?  Below are the pertinent definitions from my Java service.  Any help is greatly appreciated.<br /><br />service-config.xml<br /><br />     <channels><br />          <channel-definition id="comment-amf"<br />               class="mx.messaging.channels.SecureAMFChannel"><br />               <endpoint<br />                    url="https://<url-removed-from-post>/amvcmnt/comment-service/messag ebroker/amfsecure"<br />                    class="flex.messaging.endpoints.SecureAMFEndpoint" /><br />               <properties><br />                    <polling-enabled>false</polling-enabled><br />                <!--HTTPS requests on some browsers do not work when pragma "no-cache" are set--><br />                <add-no-cache-headers>false</add-no-cache-headers><br />                <!-- Optional. Use this to limit the client channel's connect attempt<br />                     to the specified time interval.<br />                <connect-timeout-seconds>5</connect-timeout-seconds><br />                -->           <br />                <!--  removes headers from request if true --><br />                    <serialization><br />                         <enable-small-messages>false</enable-small-messages><br />                    </serialization><br />               </properties><br />          </channel-definition>     <br />     </channels><br /><br />remote-config.xml<br /><br />     <adapters><br />          <adapter-definition id="java-object"<br />     class="flex.messaging.services.remoting.adapters.JavaAdapter"<br />               default="true" /><br />     </adapters><br />     <default-channels><br />          <channel ref="comment-amf" /><br />     </default-channels><br />     <destination id="CommentService"><br />          <properties><br />               <factory>spring</factory><br />               <source>commentService</source>          <br />          </properties><br />     </destination><br />     <br />     <destination id="SecuredCommentService"><br />          <properties><br />               <factory>spring</factory><br />               <source>securedCommentService</source>          <br />          </properties><br />     </destination><br />     <destination id="EntitlementService"><br />          <properties><br />               <factory>spring</factory><br />               <source>entitlementService</source>          <br />          </properties><br />     </destination>

Answer 1

Hi,
I am facing exactly same issue. my application works fine on local and dev. however, when i deploy it on QA where TAM and clustering is in picture it throws connection failed error. Can you please help me on how to solve this issue.
Regards,
Sachin Patil.
[email protected]