atom feed3 messages in net.java.dev.opendmk.usersRe: OpenDMK - CascadingService
FromSent OnAttachments
daniel fuchsApr 10, 2009 6:25 am 
Gabr...@sybase.comApr 10, 2009 4:56 pm 
Gabr...@sybase.comApr 14, 2009 6:09 pm 
Subject:Re: OpenDMK - CascadingService
From:Gabr...@sybase.com (Gabr@sybase.com)
Date:Apr 10, 2009 4:56:15 pm
List:net.java.dev.opendmk.users

Hi Daniel:

JConsole = "detect deadlocks" - No deadlock detected. Thank you for the response.

I will go over my code.

Thanks, Gabe

daniel fuchs <Dani@Sun.COM> Sent by: Dani@Sun.COM 04/10/2009 06:25 AM Please respond to Dani@Sun.COM

To Gabr@sybase.com cc dfu@dev.java.net, use@opendmk.dev.java.net Subject Re: OpenDMK - CascadingService

Hi Gabriel,

This is not a known issue.

You could try to connect to your application with JConsole - when you suspect it is hanging - go to the thread tab, and click on "detect deadlocks".

You can also try to switch on the trace to try to understand what is happening. Note also that if your remote application is down - because e.g. the machine is rebooting - you could have very long timeouts...

Cheers,

--daniel

Gabr@sybase.com wrote:

Hi:

We are using the OpenDMK CascadingService and the DiscoveryResponder. We use the passive mode, the responder sends notification when it starts

and when it stops, and the cascadingservice mount and unmount, respectively.

We found that if the cascadingService.unmount(mountPointID) hangs quite frequently.

Is this a known issue? Could you please point me to the discussion on how to rsolve this?

Thanks, Gabe