| Author |
Message |
|
|
I am also getting this same error...I have installed the push-server.war file, added
<context-param>
<param-name>com.icesoft.faces.blockingRequestHandler</param-name>
<param-value>push-server</param-value>
</context-param>
to my web.xml and still get:
java.lang.RuntimeException: no message available
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:56)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
Truncated. see log file for complete stacktrace
any ideas would be most appreciated.....
Thx
|
 |
|
|
|
I cannot try on Tomcat at this time due to company policies. I would say that it is a problem with the new version, Push-Server and BEA. We are running fine currently with 1.7.2, the only change was to 1.8. I will try and put together a sample app as time permits.
|
 |
|
|
I have actually tried switching to the SessionRenderer and found the same issues. I am using the new Push Server, but the same issues still seem to remain. I am only running one application on my BEA 10.2 server. I can deploy my application and sometimes the Async will work and other times it will not. I see this also when I shutdown my server and then restart it. I have never seen this behavior before using the 1.8 jars. any suggestions would be most appreciated.
Thx,
Scott
|
 |
|
|
Our current code uses RenderManager and an onDemandRenderer to push updates to our pages. Currently we are using 1.7.2 and the following code works fine:
renderer = renderManager.getOnDemandRenderer(
FacesContext.getCurrentInstance().getExternalContext
().getSession(false).toString());
renderer.add(this);
Then to push new information, I call:
renderer.requestRender();
All works fine in 1.7.2. Once I switched to the 1.8 jars, I did not get any renders....
After some research, I found that naming the OnDemandRenderer with the session name caused the problem. Why would this now cause an issue? I was able to get it working with the following code changes, but is this what I should be doing?
renderer = renderManager.getOnDemandRenderer(
FacesContext.getCurrentInstance().getExternalContext
().getSession(false).toString() + new DateTime().toString());
renderer.addCurrentSession();
UPDATE: The push is happening randomly and cannot find a pattern. I can get the original code to work some of the time. I can shutdown my server and then start it and the async push works fine. Once I stop and start the server again, now it does not work. Putting back the 1.7.2 jars, fixes the issue. I am also using the blockrequesthandler with auto-detect.
|
 |
|
|
I am getting:
java.lang.RuntimeException: Query does not contain parameter named: TngpfGmKTsVRqmxLLabCxA
My version information is:
Name: com.icesoft.faces
Implementation-Title: ICEfaces
Implementation-Version: 1.7.2_17 (2008-10-08 16:02 MDT)
Implementation-Vendor: ICEsoft Technologies, Inc.
|
 |
|
|