You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Chris Wilk <ch...@gmail.com> on 2010/12/21 10:35:33 UTC
[daemon] problem with Java debugging
Hello,
I have a problem with Commons Daemon 1.0.4 and JDK 6u21 / 6u23 (both
32-bit and 64-bit). I have observed it both on Microsoft Windows 7 and
Windows Server 2008 R2. It did not exist with Commons Daemon 1.0.2 on
Windows Server 2008 R2.
I cannot use Java Debug Wire Protocol (JDWP) for the purpose of remote
service debugging.As soon as I am starting newly installed service it
stops executing.
In both procrun log and service specific logs I have no clear
errors/warnings messages. It looks to me as
if the actual service did not even start executing.
Could you give me some hints why JDWP might stopped working with new Commons
Daemon release? I cannot go back to previous (1.0.2) release because
it does not work on Windows 7.
Best regards,
Chris M. Wilk
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: [daemon] problem with Java debugging
Posted by Chris Wilk <ch...@gmail.com>.
Of course I meant Happy New Year 2011 :)
Chris
On 31 December 2010 15:52, Chris Wilk <ch...@gmail.com> wrote:
> Hi Mladen,
>
> You are right. I have changed working environment and was inconsistent
> with talking about it. Sorry for confusion.
>
> Now I am testing on Windows Server 2008 SP2 (easier for me than
> testing on Windows 7).
>
> Regarding security, I have double checked that I have Windows
> Firewall disabled (my only firewall), UAC disabled, and McAffee
> provided with exclusion for entire directory where my services are
> installed.
>
> Should I have specific DEP configuration for the sake of Common Daemon?
>
> Best,
> Chris
> ps. Happy New Year 2010.
>
> On 30 December 2010 17:08, Mladen Turk <mt...@apache.org> wrote:
>> On 12/30/2010 04:38 PM, Chris Wilk wrote:
>>>
>>> Hello Mladen,
>>>
>>> Sorry for slight delay. I was swallowed by other tasks.
>>>
>>> I have re-checked my start class and even System.out.println statement
>>> put at the very begin of static main method is not printed at all.
>>>
>>
>> Your JVM is failing to start so that won't help.
>> I can reproduce the same behaviour (error log) if turning
>> on the firewall and not enabling access to prunsrv.exe.
>>
>> JVM just silently drops off and daemon exits.
>>
>>
>>> As I have stated before everything works for me with Commons Daemon 1.0.2
>>>
>>
>> No you have said:
>> "I cannot go back to previous (1.0.2) release because
>> it does not work on Windows 7."
>>
>> Now, windows7 == windows2008R2, so I have no clue
>> what are you talking about.
>> Are you sure you are testing those on the same boxes?
>>
>>
>> Regards
>> --
>> ^TM
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
>> For additional commands, e-mail: user-help@commons.apache.org
>>
>>
>
>
>
> --
> Chris M. Wilk
>
--
Chris M. Wilk
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: [daemon] problem with Java debugging
Posted by Chris Wilk <ch...@gmail.com>.
Hi Mladen,
You are right. I have changed working environment and was inconsistent
with talking about it. Sorry for confusion.
Now I am testing on Windows Server 2008 SP2 (easier for me than
testing on Windows 7).
Regarding security, I have double checked that I have Windows
Firewall disabled (my only firewall), UAC disabled, and McAffee
provided with exclusion for entire directory where my services are
installed.
Should I have specific DEP configuration for the sake of Common Daemon?
Best,
Chris
ps. Happy New Year 2010.
On 30 December 2010 17:08, Mladen Turk <mt...@apache.org> wrote:
> On 12/30/2010 04:38 PM, Chris Wilk wrote:
>>
>> Hello Mladen,
>>
>> Sorry for slight delay. I was swallowed by other tasks.
>>
>> I have re-checked my start class and even System.out.println statement
>> put at the very begin of static main method is not printed at all.
>>
>
> Your JVM is failing to start so that won't help.
> I can reproduce the same behaviour (error log) if turning
> on the firewall and not enabling access to prunsrv.exe.
>
> JVM just silently drops off and daemon exits.
>
>
>> As I have stated before everything works for me with Commons Daemon 1.0.2
>>
>
> No you have said:
> "I cannot go back to previous (1.0.2) release because
> it does not work on Windows 7."
>
> Now, windows7 == windows2008R2, so I have no clue
> what are you talking about.
> Are you sure you are testing those on the same boxes?
>
>
> Regards
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>
--
Chris M. Wilk
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: [daemon] problem with Java debugging
Posted by Mladen Turk <mt...@apache.org>.
On 12/30/2010 04:38 PM, Chris Wilk wrote:
> Hello Mladen,
>
> Sorry for slight delay. I was swallowed by other tasks.
>
> I have re-checked my start class and even System.out.println statement
> put at the very begin of static main method is not printed at all.
>
Your JVM is failing to start so that won't help.
I can reproduce the same behaviour (error log) if turning
on the firewall and not enabling access to prunsrv.exe.
JVM just silently drops off and daemon exits.
> As I have stated before everything works for me with Commons Daemon 1.0.2
>
No you have said:
"I cannot go back to previous (1.0.2) release because
it does not work on Windows 7."
Now, windows7 == windows2008R2, so I have no clue
what are you talking about.
Are you sure you are testing those on the same boxes?
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: [daemon] problem with Java debugging
Posted by Chris Wilk <ch...@gmail.com>.
Hello Mladen,
Sorry for slight delay. I was swallowed by other tasks.
I have re-checked my start class and even System.out.println statement
put at the very begin of static main method is not printed at all.
As I have stated before everything works for me with Commons Daemon 1.0.2
Do you any hints for me how could I check what is the damon doing at
more granular level?
Thanks in advance,
Best regards,
Chris M. Wilk
On 21 December 2010 14:14, Mladen Turk <mt...@apache.org> wrote:
> On 12/21/2010 10:35 AM, Chris Wilk wrote:
>>
>> Hello,
>>
>> I have a problem with Commons Daemon 1.0.4 and JDK 6u21 / 6u23 (both
>> 32-bit and 64-bit). I have observed it both on Microsoft Windows 7 and
>> Windows Server 2008 R2. It did not exist with Commons Daemon 1.0.2 on
>> Windows Server 2008 R2.
>>
>> I cannot use Java Debug Wire Protocol (JDWP) for the purpose of remote
>> service debugging.As soon as I am starting newly installed service it
>> stops executing.
>>
>> In both procrun log and service specific logs I have no clear
>> errors/warnings messages. It looks to me as
>> if the actual service did not even start executing.
>>
>> Could you give me some hints why JDWP might stopped working with new
>> Commons
>> Daemon release? I cannot go back to previous (1.0.2) release because
>> it does not work on Windows 7.
>>
>
> But you said it works on Windows 2008R2.
> Note that Windows 7 == Windows 2008R2
>
> Anyhow, I'd first start the service in console mode.
> eg.
> prunsvr.exe //TS//YourService
>
> It is likely that your firewall is preventing the
> service to start.
> It that's the case you should see the Security window
> opened for confirmation which cannot be shown from
> service mode cause services run in Session0 (no GUI).
>
>
> The log you posted
> [2010-12-21 10:08:41] [info] ( :0 ) Service started in 1032 ms.
> [2010-12-21 10:08:41] [debug] ( prunsrv.c:1364) Waiting for worker to
> finish...
> [2010-12-21 10:08:41] [debug] ( prunsrv.c:1369) Worker finished.
> [2010-12-21 10:08:41] [debug] ( prunsrv.c:1392) Waiting for all threads to
> exit
> [2010-12-21 10:08:41] [debug] ( prunsrv.c:1396) JVM destroyed.
>
> Says that from Daemon POV everything went well.
>
>
>
> Regards
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>
--
Chris M. Wilk
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: [daemon] problem with Java debugging
Posted by Mladen Turk <mt...@apache.org>.
On 12/21/2010 10:35 AM, Chris Wilk wrote:
> Hello,
>
> I have a problem with Commons Daemon 1.0.4 and JDK 6u21 / 6u23 (both
> 32-bit and 64-bit). I have observed it both on Microsoft Windows 7 and
> Windows Server 2008 R2. It did not exist with Commons Daemon 1.0.2 on
> Windows Server 2008 R2.
>
> I cannot use Java Debug Wire Protocol (JDWP) for the purpose of remote
> service debugging.As soon as I am starting newly installed service it
> stops executing.
>
> In both procrun log and service specific logs I have no clear
> errors/warnings messages. It looks to me as
> if the actual service did not even start executing.
>
> Could you give me some hints why JDWP might stopped working with new Commons
> Daemon release? I cannot go back to previous (1.0.2) release because
> it does not work on Windows 7.
>
But you said it works on Windows 2008R2.
Note that Windows 7 == Windows 2008R2
Anyhow, I'd first start the service in console mode.
eg.
prunsvr.exe //TS//YourService
It is likely that your firewall is preventing the
service to start.
It that's the case you should see the Security window
opened for confirmation which cannot be shown from
service mode cause services run in Session0 (no GUI).
The log you posted
[2010-12-21 10:08:41] [info] ( :0 ) Service started in 1032 ms.
[2010-12-21 10:08:41] [debug] ( prunsrv.c:1364) Waiting for worker to finish...
[2010-12-21 10:08:41] [debug] ( prunsrv.c:1369) Worker finished.
[2010-12-21 10:08:41] [debug] ( prunsrv.c:1392) Waiting for all threads to exit
[2010-12-21 10:08:41] [debug] ( prunsrv.c:1396) JVM destroyed.
Says that from Daemon POV everything went well.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org