| [CDO] TimeoutRuntimeException in openChannel [message #1719924] |
Wed, 13 January 2016 09:15  |
|
Hi
on a Jenkins running on a quite old machine, my tests involving CDO
started to fail with
org.eclipse.net4j.channel.ChannelException:
org.eclipse.net4j.util.concurrent.TimeoutRuntimeException: Channel
registration timeout after 1000 milliseconds
at
org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:176)
at
org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:1)
at org.eclipse.net4j.signal.SignalProtocol.open(SignalProtocol.java:178)
at
org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.createProtocol(CDONet4jSessionImpl.java:216)
at
org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.openSession(CDONet4jSessionImpl.java:242)
at
org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.doActivate(CDONet4jSessionImpl.java:143)
at
org.eclipse.net4j.util.lifecycle.Lifecycle.internalActivate(Lifecycle.java:76)
at
org.eclipse.net4j.util.lifecycle.ShareableLifecycle.internalActivate(ShareableLifecycle.java:43)
at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycle.java:162)
at
org.eclipse.emf.internal.cdo.session.CDOSessionConfigurationImpl.openSession(CDOSessionConfigurationImpl.java:359)
at
org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionConfigurationImpl.openNet4jSession(CDONet4jSessionConfigurationImpl.java:104)
If I understand correctly, I should set the timeout on the CDOSession,
but I was wondering if there's a way to specify the timeout with a Java
property, so that it is configurable from the "outside".
Thanks in advance
cheers
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
| Re: [CDO] TimeoutRuntimeException in openChannel [message #1729239 is a reply to message #1719924] |
Tue, 12 April 2016 10:58  |
|
Hi Lorenzo,
Sorry, I must have overlooked your post without intending it!
Please see my inline comments below...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 13.01.2016 um 10:15 schrieb Lorenzo Bettini:
> Hi
>
> on a Jenkins running on a quite old machine, my tests involving CDO
> started to fail with
>
> org.eclipse.net4j.channel.ChannelException:
> org.eclipse.net4j.util.concurrent.TimeoutRuntimeException: Channel
> registration timeout after 1000 milliseconds
> at
> org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:176)
> at
> org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:1)
> at org.eclipse.net4j.signal.SignalProtocol.open(SignalProtocol.java:178)
> at
> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.createProtocol(CDONet4jSessionImpl.java:216)
> at
> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.openSession(CDONet4jSessionImpl.java:242)
> at
> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.doActivate(CDONet4jSessionImpl.java:143)
> at
> org.eclipse.net4j.util.lifecycle.Lifecycle.internalActivate(Lifecycle.java:76)
> at
> org.eclipse.net4j.util.lifecycle.ShareableLifecycle.internalActivate(ShareableLifecycle.java:43)
> at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycle.java:162)
> at
> org.eclipse.emf.internal.cdo.session.CDOSessionConfigurationImpl.openSession(CDOSessionConfigurationImpl.java:359)
> at
> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionConfigurationImpl.openNet4jSession(CDONet4jSessionConfigurationImpl.java:104)
With what version of CDO was that?
> If I understand correctly, I should set the timeout on the CDOSession,
> but I was wondering if there's a way to specify the timeout with a Java
> property, so that it is configurable from the "outside".
We have this in ChannelMultiplexer, which is the base class for all IConnectors:
public long getOpenChannelTimeout()
{
if (openChannelTimeout == IChannelMultiplexer.DEFAULT_OPEN_CHANNEL_TIMEOUT)
{
return OM.BUNDLE.getDebugSupport().getDebugOption("open.channel.timeout", 10000); //$NON-NLS-1$
}
return openChannelTimeout;
}
public void setOpenChannelTimeout(long openChannelTimeout)
{
this.openChannelTimeout = openChannelTimeout;
}
So you can set the timeout via the *debug option* "open.channel.timeout". But I would first try to reproduce the problem
with a recent CDO integration build.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: [CDO] TimeoutRuntimeException in openChannel [message #1729626 is a reply to message #1729239] |
Sat, 16 April 2016 09:54 |
|
Never mind Eike :)
I myself had forgotten this post, and forgotten to say that it was only
due to the way we started the same server in two different testcases.
Starting the server only once fixed the problems :)
Thank you anyway for the additional information, which I'll surely use
in the future!
cheers
Lorenzo
On 12/04/2016 12:58, Eike Stepper wrote:
> Hi Lorenzo,
>
> Sorry, I must have overlooked your post without intending it!
>
> Please see my inline comments below...
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
> Am 13.01.2016 um 10:15 schrieb Lorenzo Bettini:
>> Hi
>>
>> on a Jenkins running on a quite old machine, my tests involving CDO
>> started to fail with
>>
>> org.eclipse.net4j.channel.ChannelException:
>> org.eclipse.net4j.util.concurrent.TimeoutRuntimeException: Channel
>> registration timeout after 1000 milliseconds
>> at
>> org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:176)
>>
>> at
>> org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:1)
>>
>> at
>> org.eclipse.net4j.signal.SignalProtocol.open(SignalProtocol.java:178)
>> at
>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.createProtocol(CDONet4jSessionImpl.java:216)
>>
>> at
>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.openSession(CDONet4jSessionImpl.java:242)
>>
>> at
>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.doActivate(CDONet4jSessionImpl.java:143)
>>
>> at
>> org.eclipse.net4j.util.lifecycle.Lifecycle.internalActivate(Lifecycle.java:76)
>>
>> at
>> org.eclipse.net4j.util.lifecycle.ShareableLifecycle.internalActivate(ShareableLifecycle.java:43)
>>
>> at
>> org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycle.java:162)
>> at
>> org.eclipse.emf.internal.cdo.session.CDOSessionConfigurationImpl.openSession(CDOSessionConfigurationImpl.java:359)
>>
>> at
>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionConfigurationImpl.openNet4jSession(CDONet4jSessionConfigurationImpl.java:104)
>>
> With what version of CDO was that?
>
>> If I understand correctly, I should set the timeout on the CDOSession,
>> but I was wondering if there's a way to specify the timeout with a Java
>> property, so that it is configurable from the "outside".
> We have this in ChannelMultiplexer, which is the base class for all
> IConnectors:
>
> public long getOpenChannelTimeout()
> {
> if (openChannelTimeout ==
> IChannelMultiplexer.DEFAULT_OPEN_CHANNEL_TIMEOUT)
> {
> return
> OM.BUNDLE.getDebugSupport().getDebugOption("open.channel.timeout",
> 10000); //$NON-NLS-1$
> }
>
> return openChannelTimeout;
> }
>
> public void setOpenChannelTimeout(long openChannelTimeout)
> {
> this.openChannelTimeout = openChannelTimeout;
> }
>
> So you can set the timeout via the *debug option*
> "open.channel.timeout". But I would first try to reproduce the problem
> with a recent CDO integration build.
--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
| Re: [CDO] TimeoutRuntimeException in openChannel [message #1729652 is a reply to message #1729626] |
Sun, 17 April 2016 05:05 |
|
Am 16.04.2016 um 11:54 schrieb Lorenzo Bettini:
> Never mind Eike :)
>
> I myself had forgotten this post, and forgotten to say that it was only
> due to the way we started the same server in two different testcases.
> Starting the server only once fixed the problems :)
I'm glad to hear that your problem is solved ;-)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
>
> Thank you anyway for the additional information, which I'll surely use
> in the future!
>
> cheers
> Lorenzo
>
> On 12/04/2016 12:58, Eike Stepper wrote:
>> Hi Lorenzo,
>>
>> Sorry, I must have overlooked your post without intending it!
>>
>> Please see my inline comments below...
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>
>> Am 13.01.2016 um 10:15 schrieb Lorenzo Bettini:
>>> Hi
>>>
>>> on a Jenkins running on a quite old machine, my tests involving CDO
>>> started to fail with
>>>
>>> org.eclipse.net4j.channel.ChannelException:
>>> org.eclipse.net4j.util.concurrent.TimeoutRuntimeException: Channel
>>> registration timeout after 1000 milliseconds
>>> at
>>> org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:176)
>>>
>>> at
>>> org.eclipse.spi.net4j.ChannelMultiplexer.openChannel(ChannelMultiplexer.java:1)
>>>
>>> at
>>> org.eclipse.net4j.signal.SignalProtocol.open(SignalProtocol.java:178)
>>> at
>>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.createProtocol(CDONet4jSessionImpl.java:216)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.openSession(CDONet4jSessionImpl.java:242)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionImpl.doActivate(CDONet4jSessionImpl.java:143)
>>>
>>> at
>>> org.eclipse.net4j.util.lifecycle.Lifecycle.internalActivate(Lifecycle.java:76)
>>>
>>> at
>>> org.eclipse.net4j.util.lifecycle.ShareableLifecycle.internalActivate(ShareableLifecycle.java:43)
>>>
>>> at
>>> org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycle.java:162)
>>> at
>>> org.eclipse.emf.internal.cdo.session.CDOSessionConfigurationImpl.openSession(CDOSessionConfigurationImpl.java:359)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.net4j.CDONet4jSessionConfigurationImpl.openNet4jSession(CDONet4jSessionConfigurationImpl.java:104)
>>>
>> With what version of CDO was that?
>>
>>> If I understand correctly, I should set the timeout on the CDOSession,
>>> but I was wondering if there's a way to specify the timeout with a Java
>>> property, so that it is configurable from the "outside".
>> We have this in ChannelMultiplexer, which is the base class for all
>> IConnectors:
>>
>> public long getOpenChannelTimeout()
>> {
>> if (openChannelTimeout ==
>> IChannelMultiplexer.DEFAULT_OPEN_CHANNEL_TIMEOUT)
>> {
>> return
>> OM.BUNDLE.getDebugSupport().getDebugOption("open.channel.timeout",
>> 10000); //$NON-NLS-1$
>> }
>>
>> return openChannelTimeout;
>> }
>>
>> public void setOpenChannelTimeout(long openChannelTimeout)
>> {
>> this.openChannelTimeout = openChannelTimeout;
>> }
>>
>> So you can set the timeout via the *debug option*
>> "open.channel.timeout". But I would first try to reproduce the problem
>> with a recent CDO integration build.
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.04281 seconds
] 
Search
Help
Register
Login
Home
