Make initial OO connection timeout configurable
Closed this issue · 7 comments
GoogleCodeExporter commented
Currently the timeout for connecting to OO is set to 30 seconds.
This is managed in: ManagedOfficeProcess.doStartProcessAndConnect() via
ManagedOfficeProcessSettings.getRetryTimeout, and the settings are created in
ProcessPoolOfficeManager.
On some machines it takes longer (even on newer onces, if there are a lot of
other tasks) and then the whole startup process breaks down.
Original issue reported on code.google.com by adam...@gmail.com on 3 Feb 2011 at 9:25
GoogleCodeExporter commented
Mirko, if you accept this, I can implement it
Original comment by shervin.asgari@gmail.com on 22 Mar 2011 at 12:01
GoogleCodeExporter commented
Original comment by mirko.na...@gmail.com on 22 Mar 2011 at 12:10
- Changed state: Accepted
GoogleCodeExporter commented
Fixed in branch sigar commit nr 178
Original comment by shervin.asgari@gmail.com on 22 Mar 2011 at 12:59
- Changed state: Fixed
- Added labels: Priority-Medium, Type-Enhancement
GoogleCodeExporter commented
Setting newly-added status "FixedInBranch" to be able to tell what still needs
to be merged into trunk.
Original comment by mirko.na...@gmail.com on 27 Mar 2011 at 11:13
- Changed state: FixedInBranch
GoogleCodeExporter commented
merged into trunk
Original comment by mirko.na...@gmail.com on 27 Mar 2011 at 1:04
- Changed state: Fixed
GoogleCodeExporter commented
Original comment by mirko.na...@gmail.com on 27 Mar 2011 at 1:05
- Added labels: Target-3.0-rc-1, Version-3.0-beta-3
GoogleCodeExporter commented
Original comment by mirko.na...@gmail.com on 27 Mar 2011 at 1:12
- Added labels: Target-3.0-beta-4