voyent
Setting serverErrorRetryTimeouts causes bridge to loop connecting  XML
Forum Index -> General Help
Author Message
dwight

Joined: 13/Oct/2008 00:00:00
Messages: 81
Offline


I want to change the value of serverErrorRetryTimeouts, but if I set it to anything other than the default, the bridge seems to go into a continuous loop of connecting and disconnecting.

Running ICEfaces EE 3.2.0.GA (with 1.8 compatibility on) + MyFaces 2.1.10.

My web.xml fragment:
Code:
 	<context-param>
 		<param-name>org.icepush.serverErrorRetryTimeouts</param-name>
 		<param-value>1000 2000 5000</param-value>
 	</context-param>
 	<context-param>
 		<param-name>org.icepush.heartbeatTimeout</param-name>
 		<param-value>30000</param-value>
 	</context-param>
 	<context-param>
 		<param-name>org.icefaces.strictSessionTimeout</param-name>
 		<param-value>true</param-value>
 	</context-param>
 


What I see in the console log is a continuous (and very rapid) repetition like this:
Code:
 [icepush.44112.async-connection] closing previous connection... icepush.uncompressed.js.jsf:627
 [icepush.44112.async-connection] connect... icepush.uncompressed.js.jsf:627
 [icepush.44112.async-connection] closing previous connection... icepush.uncompressed.js.jsf:627
 [icepush.44112.async-connection] connect... icepush.uncompressed.js.jsf:627
 


I've tried several different values, but it seems like anything except "1000 2000 4000" (the default) causes the same problem.

Any suggestions?
philip.breau


Joined: 08/May/2006 00:00:00
Messages: 2989
Offline


Have you tried clearing your cookies?

.
dwight

Joined: 13/Oct/2008 00:00:00
Messages: 81
Offline


Thanks for the quick response ... I had not tried that ... so I cleared the cookies, but it had no effect. I tried both Safari and Chrome browsers. As soon as I load my first (login) page, I get the messages below, then it begins "looping" as described above. (I know the cookies got cleared, as I had to re-enter usernames for all my secure websites.)

Code:
 [icepush.2a636.async-connection] Blocking connection cannot be shared among multiple web-contexts.
 Initiating blocking connection for "."  web-context... icepush.uncompressed.js.jsf:634
 [icepush.2a636.async-connection] connection monitoring started within window 2a636 icepush.uncompressed.js.jsf:634
 [icepush.2a636] bridge loaded! icepush.uncompressed.js.jsf:634
 [window] persisted focus for element "loginForm:userName" bridge.uncompressed.js.jsf:1289
 [icepush.2a636.async-connection] initialize connection within window 2a636 icepush.uncompressed.js.jsf:634
 [icepush.2a636.async-connection] closing previous connection... icepush.uncompressed.js.jsf:627
 [icepush.2a636.async-connection] connect... icepush.uncompressed.js.jsf:627
 


I also just tried switching PROJECT_STAGE to Production, instead of Development, but that didn't help either.
philip.breau


Joined: 08/May/2006 00:00:00
Messages: 2989
Offline


I can reproduce this problem on 3.2, but not on 3.3 RC1. Could you try 3.3 RC1 to see if that fixes the problem?

.
dwight

Joined: 13/Oct/2008 00:00:00
Messages: 81
Offline


Ok, it now accepts the parameter without "looping". I saw that EE 3.3 is not available yet, so after downloading 3.3 RC1, I thought I would try replacing only the icepush.jar file. We actually don't use push for much, except that it's needed (I believe) for the file upload progress bars, and for session expiration to actually change the browser's displayed page immediately.

So, after replacing the 3.2 icepush-ee.jar with the 3.3.0.RC1 icepush.jar, I can override the serverErrorRetryTimeouts setting and the bridge is running normally.

Thanks for the help!
philip.breau


Joined: 08/May/2006 00:00:00
Messages: 2989
Offline


Great. 3.3 GA should be out very shortly. I'd recommend keeping all the ice jars in sync and there'll be a jump in the MyFaces version as well.

Thanks

.
 
Forum Index -> General Help
Go to:   
Powered by JForum 2.1.7ice © JForum Team