This content has been marked as final.
Show 22 replies
-
15. Re: Socket Read Timeout on stressing calls for validating pr
vink Jan 14, 2009 8:47 AM (in response to vink)Sorry, for the other post
-
16. Re: Socket Read Timeout on stressing calls for validating pr
vink Jan 14, 2009 9:22 AM (in response to vink)You have addressed my problem in other thread; http://www.jboss.com/index.html?module=bb&op=viewtopic&t=147397
But, the JIRA issue created by you don't talk about its fix in 2.4.x, whereas you have exposed invokerDestructionDelay in this version. -
17. Re: Socket Read Timeout on stressing calls for validating pr
vink Jan 14, 2009 9:23 AM (in response to vink)Extremely sorry, seems browser issue with temporary files or cookies.
-
18. Re: Socket Read Timeout on stressing calls for validating pr
ron_sigal Jan 14, 2009 7:46 PM (in response to vink)"vink" wrote:
the JIRA issue created by you don't talk about its fix in 2.4.x,
Remoting 2.5 is essentially the same as 2.4. I jumped to 2.5 when I dropped support for Apache Tomcat. [Note that we still support JBossWeb, which is descended from Tomcat.] So, there won't be any more 2.4 releases, just 2.5 releases. -
19. Re: Socket Read Timeout on stressing calls for validating pr
vink Jan 20, 2009 5:26 AM (in response to vink)Hello Ron,
Since, the release date of 2.5.0.SP3 is not yet known; can we use the local fixed version in our product where org.jboss.remoting.Client class is working with static invokerDestructionTimer instance & other places instantiating timer object in disconnect() is commented.private static final Timer invokerDestructionTimer = new Timer(true);
-
20. Re: Socket Read Timeout on stressing calls for validating pr
ron_sigal Jan 22, 2009 5:06 PM (in response to vink)"vink" wrote:
... can we use the local fixed version in our product where org.jboss.remoting.Client class is working with static invokerDestructionTimer instance & other places instantiating timer object in disconnect() is commented.
That may be a two part question.
1. If you have a support contract and are using an EAP product, then there's no support for a nonstandard library.
2. Technically, it's not enough to just create a static Timer, because, in the absence of TimerTasks, a Timer can turn itself off and become unusable. I do something like this:private static Timer timer; private static Object timerLock = new Object(); ... { ... synchronized (timerLock) { if (timer == null) { timer = new Timer(true); } try { timer.schedule(pingTimerTask, pingFrequency, pingFrequency); } catch (IllegalStateException e) { log.debug("Unable to schedule TimerTask on existing Timer", e); timer = new Timer(true); timer.schedule(pingTimerTask, pingFrequency, pingFrequency); } } ... }
-
21. Re: Socket Read Timeout on stressing calls for validating pr
vink Jan 22, 2009 11:46 PM (in response to vink)Thanks for the suggestion, I've incorporated the changes.
-
22. Re: Socket Read Timeout on stressing calls for validating pr
immortalex Jan 28, 2009 7:33 AM (in response to vink)"ron.sigal@jboss.com" wrote:
I'll fix it in the next release.
Thanks! Good thing is that I can wait :)