wrapper-user — User issues for Wrapper. (Support questions, etc.)

[Wrapper-user] WrapperSimpleApp: Shutdown hook isn't called

[Ronen I. <rit...@al...>]

Hi,

I'm using community license for WrapperSimpleApp.
I am trying to run my services with console first (as you've recommended in order to make sure everything works properly). When I press the CTRL+C my shutdown hook isn't called, and I get timeout message in the wrapper's console (nothing else significant in the log):

wrapper  | CTRL-C trapped.  Shutting down.
wrapper  | Shutdown failed: Timed out waiting for signal from JVM.
wrapper  | JVM did not exit on request, terminated
wrapper  | <-- Wrapper Stopped

Note that when I run my app from a command line or simple bat file, the shutdown hook does get executed when CTRL+C is pressed:


Details:
OS: winXP/win7
Wrapper: wrapper-windows-x86-32-3.5.15.zip
Conf file is attached

Thanks!

Ronen.


##############################################################################################
This message is intended only for the designated recipient(s).It may contain confidential or proprietary information.
If you are not the designated recipient, you may not review, copy or distribute this message.
If you have mistakenly received this message, please notify the sender by a reply e-mail and delete this message. 
Thank you.
##############################################################################################

Re: [Wrapper-user] Customizing the executable windows only?

[Christian M. <chr...@ta...>]

Hello Alex,

thank you very much for your mail.

It's currently not possible to customize the binary on other platforms
other than Windows.  Basically because those binaries don't embed resource
files as the Windows executables, containing the icon, default conf file
path and splash screen.

There are however 2 ways to achieve similar results as the --passthrough
option.

- if you call the binary directly you can use the '--' parameter. All
parameter after the '--' will be treated as application parameters and be
passed through to your application.  for instance:
bin/wrapper -c ../conf/wrapper.conf -- myparam1 myparam2 [...]

- if you use the shell script, you can set the variables PASS_THROUGH and
FIXED_COMMAND, so the script will create the command line like above and
launch the Wrapper, e.g.:
bin/myApp.sh myparam1 myparam2 [...]

FIXED_COMMAND can be either 'start' or 'console'. If you don't set that
variable, you have to specify the command on the command line, e.g. :
bin/myApp.sh console myparam1 myparam2

I hope this information helps you out.

Best Regards,

Christian Mueller
Tanuki Software, Ltd.



On Sat, Sep 22, 2012 at 12:53 AM, Alexandros Kritikos <al...@kr...>wrote:

> Hi Leif,
>
> I was wondering if its possible to customize the executable on platforms
> other than windows. If not could you elaborate on the reason for this? Also
> how can i get the same behavior of --passthrough without customizing the
> executable on platforms like OSX, Linux etc?
>
> Many thanks in advance,
>
> Alex Kritikos
> Software AG
>
>
>
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] Customizing the executable windows only?

[Alexandros K. <al...@kr...>]

Hi Leif,

I was wondering if its possible to customize the executable on platforms other than windows. If not could you elaborate on the reason for this? Also how can i get the same behavior of --passthrough without customizing the executable on platforms like OSX, Linux etc?

Many thanks in advance,

Alex Kritikos
Software AG

Re: [Wrapper-user] Fwd: Wrapper 3.5.7 cannot be started

[Christian M. <chr...@ta...>]

Hello Aawari,

I'm sorry for the delay. What is the error message you are seeing in the
Wrapper logs?
Please note however that there was a bug in version 3.5.7 which caused the
Wrapper to output an incorrect error code, in case the check failed.
Therefore, could you please try a different version of the Wrapper?
You might need to enable debug output as well, since all later versions are
actually only shutting down if the certificate check indicated a problem
directly related with our signature, not the countersigner's signature. In
that case, the result will only be logged at debug log level.

Hope this information helps you out.

Cheers,

Christian

On Tue, Sep 11, 2012 at 2:07 AM, Asawari Pawar <ass...@gm...> wrote:

>
> Hi,
>
> Since the wrapper is not started as windows service due to server security
> policy is tight.
>
> Can you guide on what exactly to check for in the security policy?
>
> Thanks,
> Asawari
>
> ---------- Forwarded message ----------
> From: Asawari Pawar <ass...@gm...>
> Date: Tue, Sep 4, 2012 at 8:09 PM
> Subject: Re: [Wrapper-user] Wrapper 3.5.7 cannot be started
> To: wra...@li...
>
>
> Hi Christian,
>
>
> I tried what you said
>
> For testing, can you try running as console application in the session of
> the currently logged on User?
> This can be easily done by running:
> $(PATH_TO_WRAPPER)\bin\wrapper.exe -c
> $(PATH_TO_WRAPPER_CONF_FILE)\wrapper.conf
>
>
> It is running as console application but it is not still running as a
> service..
>
> How should I process ahead?
>
> Thanks,
> Asawari
> On Mon, Aug 27, 2012 at 1:42 PM, Christian Mueller <
> chr...@ta...> wrote:
>
>> Hi,
>>
>> thank you for your mail.
>>
>> Could you please be a bit more specific in what you have tried and what
>> you are seeing?
>>
>> How is the system evaluating the digital signature of the binary?
>> The easiest way to display that information is if you do a right-click on
>> the Wrapper.exe file and open "Properties" from Windows Explorer.
>> On the Tab "Digital Signatures", click the "Details" button and you see
>> how the system verifies the certificate.
>> It should say "This digital signature is OK."
>>
>> There was another minor bug in 3.5.7, where the error code of the
>> certificate validation was not correctly displayed. In your case
>> "Errorcode: 0x48d5a0" isn't sufficient to actually tell the exact meaning
>> of the error.
>>
>> Have you tried to upgrade to a later version of the Wrapper?  It would
>> help very much to see what the exact error is, which leads to the
>> verification problem.
>>
>> On the production system, are you running as Service? If so, what account
>> is the service running under?
>>
>> For testing, can you try running as console application in the session of
>> the currently logged on User?
>> This can be easily done by running:
>> $(PATH_TO_WRAPPER)\bin\wrapper.exe -c
>> $(PATH_TO_WRAPPER_CONF_FILE)\wrapper.conf
>>
>>
>> Cheers,
>> Christian
>>
>>
>>
>>
>> On Sat, Aug 25, 2012 at 3:06 AM, Asawari Pawar <ass...@gm...>wrote:
>>
>>> Hello Christian,
>>>
>>> Thanks for your recommendations!
>>>
>>> I have followed most of them but still my issue persists.
>>>
>>>
>>>
>>> Thanks,
>>> Asawari
>>>
>>> On Wed, Aug 22, 2012 at 8:28 AM, Christian Mueller <
>>> chr...@ta...> wrote:
>>>
>>>> Hello Asawari,
>>>>
>>>> I'm very sorry for the trouble.
>>>>
>>>> If the Commodo code signing certificate "UTN-USERFirst-Object" is
>>>> being present in the Third Party Certificates, please make sure "Code
>>>> Signing" and "Time Stamping" is activated.
>>>>
>>>>
>>>>
>>>> If it is present this might mean, the Local (or Domain) Security Policy
>>>> of the server is too tight to allow the certificate to be verified. This
>>>> settings can be found in the Local Security Policy of the server the "Public
>>>> Key Policies"\"Certificate Path Validation Settings" and allows for
>>>> the Root Certificate Store "Third-Party Root CAs and Enterprise Root
>>>> CAs".
>>>>
>>>>
>>>> If this doesn't/can't be set to active, another option would be to move
>>>> the "UTN-USERFirst-Object Certificate" from the "Third Party Root CA"folder to the "Trusted
>>>> Root Certificate Authorities" folder.
>>>>
>>>>
>>>> After we started to sign our binaries with version 3.5.7, we received
>>>> reports from some customers about the same troubles you are having related
>>>> to the code signing certificate. Therefore starting with version 3.5.8 we
>>>> changed the way the Wrapper is handling certificate errors regarding the
>>>> code signing/timestamping certificate. The Wrapper will now only shutdown
>>>> itself if the signature of the binary was not successfully verified because
>>>> the binary or signature has been malformed but not if any problem with the
>>>> counter-signer has been found.
>>>>
>>>> There is also another slight change, which was made in version 3.5.11
>>>> and might be worth noted. If the Commodo Root certificate is not installed
>>>> on a server, the Windows API call WinVerifyTrust (
>>>> http://msdn.microsoft.com/en-us/library/aa388208%28v=vs.85%29.aspx) to
>>>> verify the certificate tries internally to retrieve the certificate online.
>>>> If the server is however not exposed to the internet, the WinVerifyTrust
>>>> may take up to 15 seconds to return, which slows down the start up quite a
>>>> bit. Therefore, we moved the certificate validation into a separate thread,
>>>> so if the WinVerifyTrust call takes longer than the configured
>>>> wrapper.startup_thread.timeout property then the Wrapper will continue to
>>>> startup without further delay.
>>>>
>>>> http://wrapper.tanukisoftware.com/doc/english/prop-startup-thread-timeout.html
>>>>
>>>> Hope this information helps you out.
>>>>
>>>> Best Regards,
>>>>
>>>> Christian Mueller
>>>> Tanuki Software, Ltd.
>>>>
>>>> On Tue, Aug 21, 2012 at 6:32 PM, Asawari Pawar <ass...@gm...>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am using wrapper 32-bit on windows 3.5.7 version.
>>>>>
>>>>> I get following exception while starting the wrapper service.
>>>>>
>>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Java Service Wrapper
>>>>> Professional Edition 32-bit 3.5.7
>>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Copyright (C) 1999-2010
>>>>> Tanuki Software, Ltd. All Rights Reserved.
>>>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>>>> http://wrapper.tanukisoftware.com
>>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Licensed to BMC Software
>>>>> India Pvt. Ltd. for BPPM
>>>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | A signature was found in
>>>>> "D:\Apps\BMCPortal\appserver\websdk\bin\wrapper.exe", but checksum failed:
>>>>> (Errorcode: 0x48d5a0) wrapper.collect_sysinfo
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Signer Certificate:
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | 00 97 06 fe b5 6e 56 cc cb 66
>>>>> 3a bb 55 a7 a0 e4 76
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name:
>>>>> UTN-USERFirst-Object
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: Tanuki Software
>>>>> Ltd.
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | TimeStamp Certificate:
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | 47 8a 8e fb 59 e1 d8 3f 0c e1
>>>>> 42 d2 a2 87 07 be
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name:
>>>>> UTN-USERFirst-Object
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: COMODO Time
>>>>> Stamping Signer
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Date of TimeStamp : 2010/12/20
>>>>> 03:31
>>>>> FATAL | wrapper | 2012/07/23 16:40:18 | The Wrapper will shutdown!
>>>>>
>>>>> I have followed the link
>>>>>
>>>>> http://wrapper.tanukisoftware.com/doc/german/troubleshooting.html#13
>>>>>
>>>>>
>>>>> which talks about installing the certificate and the server policy but
>>>>> still the issue is not resolved.
>>>>>
>>>>> Can anyone help me with the above issue?
>>>>>
>>>>> Thanks,
>>>>> Asawari
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Live Security Virtual Conference
>>>>> Exclusive live event will cover all the ways today's security and
>>>>> threat landscape has changed and how IT managers can respond.
>>>>> Discussions
>>>>> will include endpoint security, mobile security and the latest in
>>>>> malware
>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>>> _______________________________________________
>>>>> Wrapper-user mailing list
>>>>> Wra...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond.
>>>> Discussions
>>>> will include endpoint security, mobile security and the latest in
>>>> malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Fwd: Wrapper 3.5.7 cannot be started

[Asawari P. <ass...@gm...>]

Hi,

Since the wrapper is not started as windows service due to server security
policy is tight.

Can you guide on what exactly to check for in the security policy?

Thanks,
Asawari

---------- Forwarded message ----------
From: Asawari Pawar <ass...@gm...>
Date: Tue, Sep 4, 2012 at 8:09 PM
Subject: Re: [Wrapper-user] Wrapper 3.5.7 cannot be started
To: wra...@li...


Hi Christian,


I tried what you said

For testing, can you try running as console application in the session of
the currently logged on User?
This can be easily done by running:
$(PATH_TO_WRAPPER)\bin\wrapper.exe -c
$(PATH_TO_WRAPPER_CONF_FILE)\wrapper.conf


It is running as console application but it is not still running as a
service..

How should I process ahead?

Thanks,
Asawari
On Mon, Aug 27, 2012 at 1:42 PM, Christian Mueller <
chr...@ta...> wrote:

> Hi,
>
> thank you for your mail.
>
> Could you please be a bit more specific in what you have tried and what
> you are seeing?
>
> How is the system evaluating the digital signature of the binary?
> The easiest way to display that information is if you do a right-click on
> the Wrapper.exe file and open "Properties" from Windows Explorer.
> On the Tab "Digital Signatures", click the "Details" button and you see
> how the system verifies the certificate.
> It should say "This digital signature is OK."
>
> There was another minor bug in 3.5.7, where the error code of the
> certificate validation was not correctly displayed. In your case
> "Errorcode: 0x48d5a0" isn't sufficient to actually tell the exact meaning
> of the error.
>
> Have you tried to upgrade to a later version of the Wrapper?  It would
> help very much to see what the exact error is, which leads to the
> verification problem.
>
> On the production system, are you running as Service? If so, what account
> is the service running under?
>
> For testing, can you try running as console application in the session of
> the currently logged on User?
> This can be easily done by running:
> $(PATH_TO_WRAPPER)\bin\wrapper.exe -c
> $(PATH_TO_WRAPPER_CONF_FILE)\wrapper.conf
>
>
> Cheers,
> Christian
>
>
>
>
> On Sat, Aug 25, 2012 at 3:06 AM, Asawari Pawar <ass...@gm...>wrote:
>
>> Hello Christian,
>>
>> Thanks for your recommendations!
>>
>> I have followed most of them but still my issue persists.
>>
>>
>>
>> Thanks,
>> Asawari
>>
>> On Wed, Aug 22, 2012 at 8:28 AM, Christian Mueller <
>> chr...@ta...> wrote:
>>
>>> Hello Asawari,
>>>
>>> I'm very sorry for the trouble.
>>>
>>> If the Commodo code signing certificate "UTN-USERFirst-Object" is being
>>> present in the Third Party Certificates, please make sure "Code Signing"
>>> and "Time Stamping" is activated.
>>>
>>>
>>>
>>> If it is present this might mean, the Local (or Domain) Security Policy
>>> of the server is too tight to allow the certificate to be verified. This
>>> settings can be found in the Local Security Policy of the server the "Public
>>> Key Policies"\"Certificate Path Validation Settings" and allows for the
>>> Root Certificate Store "Third-Party Root CAs and Enterprise Root CAs".
>>>
>>>
>>> If this doesn't/can't be set to active, another option would be to move
>>> the "UTN-USERFirst-Object Certificate" from the "Third Party Root CA"folder to the "Trusted
>>> Root Certificate Authorities" folder.
>>>
>>>
>>> After we started to sign our binaries with version 3.5.7, we received
>>> reports from some customers about the same troubles you are having related
>>> to the code signing certificate. Therefore starting with version 3.5.8 we
>>> changed the way the Wrapper is handling certificate errors regarding the
>>> code signing/timestamping certificate. The Wrapper will now only shutdown
>>> itself if the signature of the binary was not successfully verified because
>>> the binary or signature has been malformed but not if any problem with the
>>> counter-signer has been found.
>>>
>>> There is also another slight change, which was made in version 3.5.11
>>> and might be worth noted. If the Commodo Root certificate is not installed
>>> on a server, the Windows API call WinVerifyTrust (
>>> http://msdn.microsoft.com/en-us/library/aa388208%28v=vs.85%29.aspx) to
>>> verify the certificate tries internally to retrieve the certificate online.
>>> If the server is however not exposed to the internet, the WinVerifyTrust
>>> may take up to 15 seconds to return, which slows down the start up quite a
>>> bit. Therefore, we moved the certificate validation into a separate thread,
>>> so if the WinVerifyTrust call takes longer than the configured
>>> wrapper.startup_thread.timeout property then the Wrapper will continue to
>>> startup without further delay.
>>>
>>> http://wrapper.tanukisoftware.com/doc/english/prop-startup-thread-timeout.html
>>>
>>> Hope this information helps you out.
>>>
>>> Best Regards,
>>>
>>> Christian Mueller
>>> Tanuki Software, Ltd.
>>>
>>> On Tue, Aug 21, 2012 at 6:32 PM, Asawari Pawar <ass...@gm...>wrote:
>>>
>>>> Hi,
>>>>
>>>> I am using wrapper 32-bit on windows 3.5.7 version.
>>>>
>>>> I get following exception while starting the wrapper service.
>>>>
>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Java Service Wrapper
>>>> Professional Edition 32-bit 3.5.7
>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Copyright (C) 1999-2010 Tanuki
>>>> Software, Ltd. All Rights Reserved.
>>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>>> http://wrapper.tanukisoftware.com
>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Licensed to BMC Software India
>>>> Pvt. Ltd. for BPPM
>>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | A signature was found in
>>>> "D:\Apps\BMCPortal\appserver\websdk\bin\wrapper.exe", but checksum failed:
>>>> (Errorcode: 0x48d5a0) wrapper.collect_sysinfo
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Signer Certificate:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | 00 97 06 fe b5 6e 56 cc cb 66
>>>> 3a bb 55 a7 a0 e4 76
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name:
>>>> UTN-USERFirst-Object
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: Tanuki Software
>>>> Ltd.
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | TimeStamp Certificate:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | 47 8a 8e fb 59 e1 d8 3f 0c e1
>>>> 42 d2 a2 87 07 be
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name:
>>>> UTN-USERFirst-Object
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: COMODO Time
>>>> Stamping Signer
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Date of TimeStamp : 2010/12/20
>>>> 03:31
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | The Wrapper will shutdown!
>>>>
>>>> I have followed the link
>>>>
>>>> http://wrapper.tanukisoftware.com/doc/german/troubleshooting.html#13
>>>>
>>>>
>>>> which talks about installing the certificate and the server policy but
>>>> still the issue is not resolved.
>>>>
>>>> Can anyone help me with the above issue?
>>>>
>>>> Thanks,
>>>> Asawari
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond.
>>>> Discussions
>>>> will include endpoint security, mobile security and the latest in
>>>> malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Wrapper.exe and process id

[Jim B. <Jim...@ge...>]

Please disreagrd

 

From: Jim Burns 
Sent: Monday, September 10, 2012 12:22 PM
To: wra...@li...
Cc: Jim Burns
Subject: Wrapper.exe and process id

 

Hello.

 

I am trying to monitor the status of a running Wrapper.exe, with a 3rd
party application that starts and monitors the Wrapper.exe process, it
starts the Wrapper.exe process with a command line and command line
parameters, then monitors for the initial process id to determine the
runtime status.

 

Problem is that Wrapper.exe starts up, then spawns other processes and
stops the initial process.

The monitoring tool sees the initial process stop and think the overall
process has stopped.

 

Is there any way to force this initial process to stay running or for
the start to not spawn a separate wrapper.exe process?

 

Command Line used:

c:\gcticustom\genesys-ali-adapter\bin\wrapper.exe -t
c:\gcticustom\genesys-ali-adapter\conf\wrapper.conf

 

Jim Burns

[Wrapper-user] Wrapper.exe and process id

[Jim B. <Jim...@ge...>]

Hello.

 

I am trying to monitor the status of a running Wrapper.exe, with a 3rd
party application that starts and monitors the Wrapper.exe process, it
starts the Wrapper.exe process with a command line and command line
parameters, then monitors for the initial process id to determine the
runtime status.

 

Problem is that Wrapper.exe starts up, then spawns other processes and
stops the initial process.

The monitoring tool sees the initial process stop and think the overall
process has stopped.

 

Is there any way to force this initial process to stay running or for
the start to not spawn a separate wrapper.exe process?

 

Command Line used:

c:\gcticustom\genesys-ali-adapter\bin\wrapper.exe -t
c:\gcticustom\genesys-ali-adapter\conf\wrapper.conf

 

Jim Burns

Re: [Wrapper-user] Wrapper 3.5.7 cannot be started

[Asawari P. <ass...@gm...>]

Hi Christian,


I tried what you said

For testing, can you try running as console application in the session of
the currently logged on User?
This can be easily done by running:
$(PATH_TO_WRAPPER)\bin\wrapper.exe -c
$(PATH_TO_WRAPPER_CONF_FILE)\wrapper.conf


It is running as console application but it is not still running as a
service..

How should I process ahead?

Thanks,
Asawari
On Mon, Aug 27, 2012 at 1:42 PM, Christian Mueller <
chr...@ta...> wrote:

> Hi,
>
> thank you for your mail.
>
> Could you please be a bit more specific in what you have tried and what
> you are seeing?
>
> How is the system evaluating the digital signature of the binary?
> The easiest way to display that information is if you do a right-click on
> the Wrapper.exe file and open "Properties" from Windows Explorer.
> On the Tab "Digital Signatures", click the "Details" button and you see
> how the system verifies the certificate.
> It should say "This digital signature is OK."
>
> There was another minor bug in 3.5.7, where the error code of the
> certificate validation was not correctly displayed. In your case
> "Errorcode: 0x48d5a0" isn't sufficient to actually tell the exact meaning
> of the error.
>
> Have you tried to upgrade to a later version of the Wrapper?  It would
> help very much to see what the exact error is, which leads to the
> verification problem.
>
> On the production system, are you running as Service? If so, what account
> is the service running under?
>
> For testing, can you try running as console application in the session of
> the currently logged on User?
> This can be easily done by running:
> $(PATH_TO_WRAPPER)\bin\wrapper.exe -c
> $(PATH_TO_WRAPPER_CONF_FILE)\wrapper.conf
>
>
> Cheers,
> Christian
>
>
>
>
> On Sat, Aug 25, 2012 at 3:06 AM, Asawari Pawar <ass...@gm...>wrote:
>
>> Hello Christian,
>>
>> Thanks for your recommendations!
>>
>> I have followed most of them but still my issue persists.
>>
>>
>>
>> Thanks,
>> Asawari
>>
>> On Wed, Aug 22, 2012 at 8:28 AM, Christian Mueller <
>> chr...@ta...> wrote:
>>
>>> Hello Asawari,
>>>
>>> I'm very sorry for the trouble.
>>>
>>> If the Commodo code signing certificate "UTN-USERFirst-Object" is being
>>> present in the Third Party Certificates, please make sure "Code Signing"
>>> and "Time Stamping" is activated.
>>>
>>>
>>>
>>> If it is present this might mean, the Local (or Domain) Security Policy
>>> of the server is too tight to allow the certificate to be verified. This
>>> settings can be found in the Local Security Policy of the server the "Public
>>> Key Policies"\"Certificate Path Validation Settings" and allows for the
>>> Root Certificate Store "Third-Party Root CAs and Enterprise Root CAs".
>>>
>>>
>>> If this doesn't/can't be set to active, another option would be to move
>>> the "UTN-USERFirst-Object Certificate" from the "Third Party Root CA"folder to the "Trusted
>>> Root Certificate Authorities" folder.
>>>
>>>
>>> After we started to sign our binaries with version 3.5.7, we received
>>> reports from some customers about the same troubles you are having related
>>> to the code signing certificate. Therefore starting with version 3.5.8 we
>>> changed the way the Wrapper is handling certificate errors regarding the
>>> code signing/timestamping certificate. The Wrapper will now only shutdown
>>> itself if the signature of the binary was not successfully verified because
>>> the binary or signature has been malformed but not if any problem with the
>>> counter-signer has been found.
>>>
>>> There is also another slight change, which was made in version 3.5.11
>>> and might be worth noted. If the Commodo Root certificate is not installed
>>> on a server, the Windows API call WinVerifyTrust (
>>> http://msdn.microsoft.com/en-us/library/aa388208%28v=vs.85%29.aspx) to
>>> verify the certificate tries internally to retrieve the certificate online.
>>> If the server is however not exposed to the internet, the WinVerifyTrust
>>> may take up to 15 seconds to return, which slows down the start up quite a
>>> bit. Therefore, we moved the certificate validation into a separate thread,
>>> so if the WinVerifyTrust call takes longer than the configured
>>> wrapper.startup_thread.timeout property then the Wrapper will continue to
>>> startup without further delay.
>>>
>>> http://wrapper.tanukisoftware.com/doc/english/prop-startup-thread-timeout.html
>>>
>>> Hope this information helps you out.
>>>
>>> Best Regards,
>>>
>>> Christian Mueller
>>> Tanuki Software, Ltd.
>>>
>>> On Tue, Aug 21, 2012 at 6:32 PM, Asawari Pawar <ass...@gm...>wrote:
>>>
>>>> Hi,
>>>>
>>>> I am using wrapper 32-bit on windows 3.5.7 version.
>>>>
>>>> I get following exception while starting the wrapper service.
>>>>
>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Java Service Wrapper
>>>> Professional Edition 32-bit 3.5.7
>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Copyright (C) 1999-2010 Tanuki
>>>> Software, Ltd. All Rights Reserved.
>>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>>> http://wrapper.tanukisoftware.com
>>>> STATUS | wrapper | 2012/07/23 16:40:18 | Licensed to BMC Software India
>>>> Pvt. Ltd. for BPPM
>>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | A signature was found in
>>>> "D:\Apps\BMCPortal\appserver\websdk\bin\wrapper.exe", but checksum failed:
>>>> (Errorcode: 0x48d5a0) wrapper.collect_sysinfo
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Signer Certificate:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | 00 97 06 fe b5 6e 56 cc cb 66
>>>> 3a bb 55 a7 a0 e4 76
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name:
>>>> UTN-USERFirst-Object
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: Tanuki Software
>>>> Ltd.
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | TimeStamp Certificate:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | 47 8a 8e fb 59 e1 d8 3f 0c e1
>>>> 42 d2 a2 87 07 be
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name:
>>>> UTN-USERFirst-Object
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: COMODO Time
>>>> Stamping Signer
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | Date of TimeStamp : 2010/12/20
>>>> 03:31
>>>> FATAL | wrapper | 2012/07/23 16:40:18 | The Wrapper will shutdown!
>>>>
>>>> I have followed the link
>>>>
>>>> http://wrapper.tanukisoftware.com/doc/german/troubleshooting.html#13
>>>>
>>>>
>>>> which talks about installing the certificate and the server policy but
>>>> still the issue is not resolved.
>>>>
>>>> Can anyone help me with the above issue?
>>>>
>>>> Thanks,
>>>> Asawari
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond.
>>>> Discussions
>>>> will include endpoint security, mobile security and the latest in
>>>> malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Wrapper.exe and process id

[Christian M. <chr...@ta...>]

Hello Jim,

If your monitoring tool needs a pid of the Wrapper (and Java) process, you
could also use the wrapper.pidfile and wrapper.java.pidfile.
With this properties set, the Wrapper, which runs as service will write the
PID of itself and the JVM to the specified files.
http://wrapper.tanukisoftware.com/doc/english/prop-pidfile.html

Another option on querying the Wrapper would be using the '--query' call of
the Wrapper binary:
bin\wrapper -q ../conf/wrapper.conf

http://wrapper.tanukisoftware.com/doc/english/launch-win.html#standalone-status

Please let me know if you need any further information.

Thank you,

Christian

On Wed, Aug 29, 2012 at 2:01 PM, Christian Mueller <
chr...@ta...> wrote:

> Hi Jim,
>
> thank you for your message.
> After the Wrapper has been installed as Windows Service, the Wrapper will
> be not directly started but from the Service Control Manager (SCM) and its
> context.
>
> So when you run the command line to start the service, the Wrapper is
> starting and connecting to the SCM and requesting it to start the Wrapper
> installed as service, this Wrapper process is then eventually starting your
> application. Once the SCM returns the confirmation it has successfully
> started to the initial Wrapper, it also exits.
>
> So your monitoring tool should rather monitor the wrapper.exe process,
> running as service.
>
> Hope this information helps you out.
>
> Cheers,
>
> Christian Mueller
> Tanuki Software, Ltd.
>
>  On Tue, Aug 28, 2012 at 10:05 PM, Jim Burns <Jim...@ge...>wrote:
>
>> Hello.****
>>
>> ** **
>>
>> I am trying to monitor the status of a running Wrapper.exe, and the 3rdparty application that starts and monitors the Wrapper.exe process starts
>> the process with a command line and command line parameters, then monitors
>> for the initial process id to determine the runtime status.****
>>
>> ** **
>>
>> Problem is that Wrapper.exe starts up, then spawns other processes and
>> stops the initial process.****
>>
>> Te monitoring tool sees the initial process stop and think the overall
>> process has stopped.****
>>
>> ** **
>>
>> Is there any way to force this initial process to stay running or for ***
>> *
>>
>> ** **
>>
>> Command Line used:****
>>
>> c:\gcticustom\genesys-ali-adapter\bin\wrapper.exe -t
>> c:\gcticustom\genesys-ali-adapter\conf\wrapper.conf****
>>
>> ** **
>>
>> Jim Burns****
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>

Re: [Wrapper-user] Wrapper.exe and process id

[Christian M. <chr...@ta...>]

Hi Jim,

thank you for your message.
After the Wrapper has been installed as Windows Service, the Wrapper will
be not directly started but from the Service Control Manager (SCM) and its
context.

So when you run the command line to start the service, the Wrapper is
starting and connecting to the SCM and requesting it to start the Wrapper
installed as service, this Wrapper process is then eventually starting your
application. Once the SCM returns the confirmation it has successfully
started to the initial Wrapper, it also exits.

So your monitoring tool should rather monitor the wrapper.exe process,
running as service.

Hope this information helps you out.

Cheers,

Christian Mueller
Tanuki Software, Ltd.

On Tue, Aug 28, 2012 at 10:05 PM, Jim Burns <Jim...@ge...>wrote:

> Hello.****
>
> ** **
>
> I am trying to monitor the status of a running Wrapper.exe, and the 3rdparty application that starts and monitors the Wrapper.exe process starts
> the process with a command line and command line parameters, then monitors
> for the initial process id to determine the runtime status.****
>
> ** **
>
> Problem is that Wrapper.exe starts up, then spawns other processes and
> stops the initial process.****
>
> Te monitoring tool sees the initial process stop and think the overall
> process has stopped.****
>
> ** **
>
> Is there any way to force this initial process to stay running or for ****
>
> ** **
>
> Command Line used:****
>
> c:\gcticustom\genesys-ali-adapter\bin\wrapper.exe -t
> c:\gcticustom\genesys-ali-adapter\conf\wrapper.conf****
>
> ** **
>
> Jim Burns****
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Wrapper.exe and process id

[Jim B. <Jim...@ge...>]

Hello.

 

I am trying to monitor the status of a running Wrapper.exe, and the 3rd
party application that starts and monitors the Wrapper.exe process
starts the process with a command line and command line parameters, then
monitors for the initial process id to determine the runtime status.

 

Problem is that Wrapper.exe starts up, then spawns other processes and
stops the initial process.

Te monitoring tool sees the initial process stop and think the overall
process has stopped.

 

Is there any way to force this initial process to stay running or for 

 

Command Line used:

c:\gcticustom\genesys-ali-adapter\bin\wrapper.exe -t
c:\gcticustom\genesys-ali-adapter\conf\wrapper.conf

 

Jim Burns

Re: [Wrapper-user] Running console apps

[Alexandros K. <al...@kr...>]

Hi Christian,

ideally i would like a log level that suppresses all wrapper output to the console but prints stdout from the java application.

Best Regards,

Alex Kritikos


On 28 Αυγ 2012, at 5:41 π.μ., Christian Mueller <chr...@ta...> wrote:

> Hello Alexandros, 
> 
> even if you run the Wrapper on log level INFO for console output, there is actually not much output from the Wrapper, once the application started and running.. 
> wrapper  | --> Wrapper Started as Console
> wrapper  | Java Service Wrapper Professional Edition 64-bit 3.5.15
> wrapper  |   Copyright (C) 1999-2012 Tanuki Software, Ltd. All Rights Reserved.
> wrapper  |     http://wrapper.tanukisoftware.com
> wrapper  |   Licensed to MyExample
> wrapper  | 
> wrapper  | Launching a JVM...
> jvm 1    | WrapperManager: Initializing...
> 
> 
> you can change the output format, to only show the messages and not the prefix, by setting wrapper.console.format=M in your conf file. 
> 
> What output do you want to see suppressed? 
> 
> Best Regards, 
> 
> Christian Mueller 
> Tanuki Software, Ltd.
> 
> 
> On Sat, Aug 25, 2012 at 12:28 AM, Alexandros Kritikos <al...@kr...> wrote:
> Hi Leif,
> 
> thanks for your response. I was not referring to the logs but to the console output as we do not require any log files in this case. Is it still not possible to suppress this? Not even with a --customize option?
> 
> Thanks,
> 
> Alex Kritikos
> my-Channels (A Software AG company)
> 
> On Aug 3, 2012, at 5:35 PM, Leif Mortenson <lei...@ta...> wrote:
> 
>> Alex,
>> Sorry, it is not currently possible to completely disable the Wrapper's output.   You will at least always see the startup banner in the logs.That output is logged at the STATUS log level which is as you found out, higher than the INFO log level of the JVM output.
>> 
>> The Wrapper also has the ability to pass parameters directly through to the JVM using the "--" value in the argument list.  Everything after that will be sent directly to the JVM.
>> 
>> You can also customize the JVM to make all parameters go to the JVM:
>> http://wrapper.tanukisoftware.com/doc/english/customize.html
>> 
>> Cheers,
>> Leif
>> 
>> On Fri, Aug 3, 2012 at 9:29 PM, Alexandros Kritikos <al...@kr...> wrote:
>> Hi Leif,
>> 
>> We are experimenting with using wrapper to simply launch (and detach) various console java applications. These applications expect command line arguments so if they are run without anything they print out a usage message. Is it possible to disable ALL wrapper console output but still see any System.out messages from the java application? Currently if i set the console log level to anything less than INFO it not only suppresses wrapper console messages but the application ones. We are using the latest version of the wrapper.
>> 
>> Many thanks in advance,
>> 
>> Alex Kritikos
>> my-Channels (A Software AG company)
>> ------------------------------------------------------------------------------
>> 
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and 
>> threat landscape has changed and how IT managers can respond. Discussions 
>> will include endpoint security, mobile security and the latest in malware 
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Running console apps

[Christian M. <chr...@ta...>]

Hello Alexandros,

even if you run the Wrapper on log level INFO for console output, there is
actually not much output from the Wrapper, once the application started and
running..
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Professional Edition 64-bit 3.5.15
wrapper  |   Copyright (C) 1999-2012 Tanuki Software, Ltd. All Rights
Reserved.
wrapper  |     http://wrapper.tanukisoftware.com
wrapper  |   Licensed to MyExample
wrapper  |
wrapper  | Launching a JVM...
jvm 1    | WrapperManager: Initializing...


you can change the output format, to only show the messages and not the
prefix, by setting wrapper.console.format=M in your conf file.

What output do you want to see suppressed?

Best Regards,

Christian Mueller
Tanuki Software, Ltd.


On Sat, Aug 25, 2012 at 12:28 AM, Alexandros Kritikos <al...@kr...>wrote:

> Hi Leif,
>
> thanks for your response. I was not referring to the logs but to the
> console output as we do not require any log files in this case. Is it still
> not possible to suppress this? Not even with a --customize option?
>
> Thanks,
>
> Alex Kritikos
> my-Channels (A Software AG company)
>
> On Aug 3, 2012, at 5:35 PM, Leif Mortenson <
> lei...@ta...> wrote:
>
> Alex,
> Sorry, it is not currently possible to completely disable the Wrapper's
> output.   You will at least always see the startup banner in the logs.That
> output is logged at the STATUS log level which is as you found out, higher
> than the INFO log level of the JVM output.
>
> The Wrapper also has the ability to pass parameters directly through to
> the JVM using the "--" value in the argument list.  Everything after that
> will be sent directly to the JVM.
>
> You can also customize the JVM to make all parameters go to the JVM:
> http://wrapper.tanukisoftware.com/doc/english/customize.html
>
> Cheers,
> Leif
>
> On Fri, Aug 3, 2012 at 9:29 PM, Alexandros Kritikos <al...@kr...>wrote:
>
>> Hi Leif,
>>
>> We are experimenting with using wrapper to simply launch (and detach)
>> various console java applications. These applications expect command line
>> arguments so if they are run without anything they print out a usage
>> message. Is it possible to disable ALL wrapper console output but still see
>> any System.out messages from the java application? Currently if i set the
>> console log level to anything less than INFO it not only suppresses wrapper
>> console messages but the application ones. We are using the latest version
>> of the wrapper.
>>
>> Many thanks in advance,
>>
>> Alex Kritikos
>> my-Channels (A Software AG company)
>>
>
> ------------------------------------------------------------------------------
>
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Wrapper 3.5.7 cannot be started

[Christian M. <chr...@ta...>]

Hi,

thank you for your mail.

Could you please be a bit more specific in what you have tried and what you
are seeing?

How is the system evaluating the digital signature of the binary?
The easiest way to display that information is if you do a right-click on
the Wrapper.exe file and open "Properties" from Windows Explorer.
On the Tab "Digital Signatures", click the "Details" button and you see how
the system verifies the certificate.
It should say "This digital signature is OK."

There was another minor bug in 3.5.7, where the error code of the
certificate validation was not correctly displayed. In your case
"Errorcode: 0x48d5a0" isn't sufficient to actually tell the exact meaning
of the error.

Have you tried to upgrade to a later version of the Wrapper?  It would help
very much to see what the exact error is, which leads to the verification
problem.

On the production system, are you running as Service? If so, what account
is the service running under?

For testing, can you try running as console application in the session of
the currently logged on User?
This can be easily done by running:
$(PATH_TO_WRAPPER)\bin\wrapper.exe -c
$(PATH_TO_WRAPPER_CONF_FILE)\wrapper.conf


Cheers,
Christian



On Sat, Aug 25, 2012 at 3:06 AM, Asawari Pawar <ass...@gm...> wrote:

> Hello Christian,
>
> Thanks for your recommendations!
>
> I have followed most of them but still my issue persists.
>
>
>
> Thanks,
> Asawari
>
> On Wed, Aug 22, 2012 at 8:28 AM, Christian Mueller <
> chr...@ta...> wrote:
>
>> Hello Asawari,
>>
>> I'm very sorry for the trouble.
>>
>> If the Commodo code signing certificate "UTN-USERFirst-Object" is being
>> present in the Third Party Certificates, please make sure "Code Signing"
>> and "Time Stamping" is activated.
>>
>>
>>
>> If it is present this might mean, the Local (or Domain) Security Policy
>> of the server is too tight to allow the certificate to be verified. This
>> settings can be found in the Local Security Policy of the server the "Public
>> Key Policies"\"Certificate Path Validation Settings" and allows for the
>> Root Certificate Store "Third-Party Root CAs and Enterprise Root CAs".
>>
>>
>> If this doesn't/can't be set to active, another option would be to move
>> the "UTN-USERFirst-Object Certificate" from the "Third Party Root CA"folder to the "Trusted
>> Root Certificate Authorities" folder.
>>
>>
>> After we started to sign our binaries with version 3.5.7, we received
>> reports from some customers about the same troubles you are having related
>> to the code signing certificate. Therefore starting with version 3.5.8 we
>> changed the way the Wrapper is handling certificate errors regarding the
>> code signing/timestamping certificate. The Wrapper will now only shutdown
>> itself if the signature of the binary was not successfully verified because
>> the binary or signature has been malformed but not if any problem with the
>> counter-signer has been found.
>>
>> There is also another slight change, which was made in version 3.5.11 and
>> might be worth noted. If the Commodo Root certificate is not installed on a
>> server, the Windows API call WinVerifyTrust (
>> http://msdn.microsoft.com/en-us/library/aa388208%28v=vs.85%29.aspx) to
>> verify the certificate tries internally to retrieve the certificate online.
>> If the server is however not exposed to the internet, the WinVerifyTrust
>> may take up to 15 seconds to return, which slows down the start up quite a
>> bit. Therefore, we moved the certificate validation into a separate thread,
>> so if the WinVerifyTrust call takes longer than the configured
>> wrapper.startup_thread.timeout property then the Wrapper will continue to
>> startup without further delay.
>>
>> http://wrapper.tanukisoftware.com/doc/english/prop-startup-thread-timeout.html
>>
>> Hope this information helps you out.
>>
>> Best Regards,
>>
>> Christian Mueller
>> Tanuki Software, Ltd.
>>
>> On Tue, Aug 21, 2012 at 6:32 PM, Asawari Pawar <ass...@gm...>wrote:
>>
>>> Hi,
>>>
>>> I am using wrapper 32-bit on windows 3.5.7 version.
>>>
>>> I get following exception while starting the wrapper service.
>>>
>>> STATUS | wrapper | 2012/07/23 16:40:18 | Java Service Wrapper
>>> Professional Edition 32-bit 3.5.7
>>> STATUS | wrapper | 2012/07/23 16:40:18 | Copyright (C) 1999-2010 Tanuki
>>> Software, Ltd. All Rights Reserved.
>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>> http://wrapper.tanukisoftware.com
>>> STATUS | wrapper | 2012/07/23 16:40:18 | Licensed to BMC Software India
>>> Pvt. Ltd. for BPPM
>>> STATUS | wrapper | 2012/07/23 16:40:18 |
>>> FATAL | wrapper | 2012/07/23 16:40:18 | A signature was found in
>>> "D:\Apps\BMCPortal\appserver\websdk\bin\wrapper.exe", but checksum failed:
>>> (Errorcode: 0x48d5a0) wrapper.collect_sysinfo
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Signer Certificate:
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>> FATAL | wrapper | 2012/07/23 16:40:18 | 00 97 06 fe b5 6e 56 cc cb 66 3a
>>> bb 55 a7 a0 e4 76
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: Tanuki Software
>>> Ltd.
>>> FATAL | wrapper | 2012/07/23 16:40:18 | TimeStamp Certificate:
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>>> FATAL | wrapper | 2012/07/23 16:40:18 | 47 8a 8e fb 59 e1 d8 3f 0c e1 42
>>> d2 a2 87 07 be
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: COMODO Time
>>> Stamping Signer
>>> FATAL | wrapper | 2012/07/23 16:40:18 | Date of TimeStamp : 2010/12/20
>>> 03:31
>>> FATAL | wrapper | 2012/07/23 16:40:18 | The Wrapper will shutdown!
>>>
>>> I have followed the link
>>>
>>> http://wrapper.tanukisoftware.com/doc/german/troubleshooting.html#13
>>>
>>>
>>> which talks about installing the certificate and the server policy but
>>> still the issue is not resolved.
>>>
>>> Can anyone help me with the above issue?
>>>
>>> Thanks,
>>> Asawari
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Wrapper 3.5.7 cannot be started

[Asawari P. <ass...@gm...>]

Hello Christian,

Thanks for your recommendations!

I have followed most of them but still my issue persists.



Thanks,
Asawari

On Wed, Aug 22, 2012 at 8:28 AM, Christian Mueller <
chr...@ta...> wrote:

> Hello Asawari,
>
> I'm very sorry for the trouble.
>
> If the Commodo code signing certificate "UTN-USERFirst-Object" is being
> present in the Third Party Certificates, please make sure "Code Signing"
> and "Time Stamping" is activated.
>
>
>
> If it is present this might mean, the Local (or Domain) Security Policy of
> the server is too tight to allow the certificate to be verified. This
> settings can be found in the Local Security Policy of the server the "Public
> Key Policies"\"Certificate Path Validation Settings" and allows for the
> Root Certificate Store "Third-Party Root CAs and Enterprise Root CAs".
>
>
> If this doesn't/can't be set to active, another option would be to move
> the "UTN-USERFirst-Object Certificate" from the "Third Party Root CA"folder to the "Trusted
> Root Certificate Authorities" folder.
>
>
> After we started to sign our binaries with version 3.5.7, we received
> reports from some customers about the same troubles you are having related
> to the code signing certificate. Therefore starting with version 3.5.8 we
> changed the way the Wrapper is handling certificate errors regarding the
> code signing/timestamping certificate. The Wrapper will now only shutdown
> itself if the signature of the binary was not successfully verified because
> the binary or signature has been malformed but not if any problem with the
> counter-signer has been found.
>
> There is also another slight change, which was made in version 3.5.11 and
> might be worth noted. If the Commodo Root certificate is not installed on a
> server, the Windows API call WinVerifyTrust (
> http://msdn.microsoft.com/en-us/library/aa388208%28v=vs.85%29.aspx) to
> verify the certificate tries internally to retrieve the certificate online.
> If the server is however not exposed to the internet, the WinVerifyTrust
> may take up to 15 seconds to return, which slows down the start up quite a
> bit. Therefore, we moved the certificate validation into a separate thread,
> so if the WinVerifyTrust call takes longer than the configured
> wrapper.startup_thread.timeout property then the Wrapper will continue to
> startup without further delay.
>
> http://wrapper.tanukisoftware.com/doc/english/prop-startup-thread-timeout.html
>
> Hope this information helps you out.
>
> Best Regards,
>
> Christian Mueller
> Tanuki Software, Ltd.
>
> On Tue, Aug 21, 2012 at 6:32 PM, Asawari Pawar <ass...@gm...>wrote:
>
>> Hi,
>>
>> I am using wrapper 32-bit on windows 3.5.7 version.
>>
>> I get following exception while starting the wrapper service.
>>
>> STATUS | wrapper | 2012/07/23 16:40:18 | Java Service Wrapper
>> Professional Edition 32-bit 3.5.7
>> STATUS | wrapper | 2012/07/23 16:40:18 | Copyright (C) 1999-2010 Tanuki
>> Software, Ltd. All Rights Reserved.
>> STATUS | wrapper | 2012/07/23 16:40:18 |
>> http://wrapper.tanukisoftware.com
>> STATUS | wrapper | 2012/07/23 16:40:18 | Licensed to BMC Software India
>> Pvt. Ltd. for BPPM
>> STATUS | wrapper | 2012/07/23 16:40:18 |
>> FATAL | wrapper | 2012/07/23 16:40:18 | A signature was found in
>> "D:\Apps\BMCPortal\appserver\websdk\bin\wrapper.exe", but checksum failed:
>> (Errorcode: 0x48d5a0) wrapper.collect_sysinfo
>> FATAL | wrapper | 2012/07/23 16:40:18 | Signer Certificate:
>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>> FATAL | wrapper | 2012/07/23 16:40:18 | 00 97 06 fe b5 6e 56 cc cb 66 3a
>> bb 55 a7 a0 e4 76
>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: Tanuki Software Ltd.
>> FATAL | wrapper | 2012/07/23 16:40:18 | TimeStamp Certificate:
>> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
>> FATAL | wrapper | 2012/07/23 16:40:18 | 47 8a 8e fb 59 e1 d8 3f 0c e1 42
>> d2 a2 87 07 be
>> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
>> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: COMODO Time
>> Stamping Signer
>> FATAL | wrapper | 2012/07/23 16:40:18 | Date of TimeStamp : 2010/12/20
>> 03:31
>> FATAL | wrapper | 2012/07/23 16:40:18 | The Wrapper will shutdown!
>>
>> I have followed the link
>>
>> http://wrapper.tanukisoftware.com/doc/german/troubleshooting.html#13
>>
>>
>> which talks about installing the certificate and the server policy but
>> still the issue is not resolved.
>>
>> Can anyone help me with the above issue?
>>
>> Thanks,
>> Asawari
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Running console apps

[Alexandros K. <al...@kr...>]

Hi Leif,

thanks for your response. I was not referring to the logs but to the console output as we do not require any log files in this case. Is it still not possible to suppress this? Not even with a --customize option?

Thanks,

Alex Kritikos
my-Channels (A Software AG company)

On Aug 3, 2012, at 5:35 PM, Leif Mortenson <lei...@ta...> wrote:

> Alex,
> Sorry, it is not currently possible to completely disable the Wrapper's output.   You will at least always see the startup banner in the logs.That output is logged at the STATUS log level which is as you found out, higher than the INFO log level of the JVM output.
> 
> The Wrapper also has the ability to pass parameters directly through to the JVM using the "--" value in the argument list.  Everything after that will be sent directly to the JVM.
> 
> You can also customize the JVM to make all parameters go to the JVM:
> http://wrapper.tanukisoftware.com/doc/english/customize.html
> 
> Cheers,
> Leif
> 
> On Fri, Aug 3, 2012 at 9:29 PM, Alexandros Kritikos <al...@kr...> wrote:
> Hi Leif,
> 
> We are experimenting with using wrapper to simply launch (and detach) various console java applications. These applications expect command line arguments so if they are run without anything they print out a usage message. Is it possible to disable ALL wrapper console output but still see any System.out messages from the java application? Currently if i set the console log level to anything less than INFO it not only suppresses wrapper console messages but the application ones. We are using the latest version of the wrapper.
> 
> Many thanks in advance,
> 
> Alex Kritikos
> my-Channels (A Software AG company)
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Wrapper 3.5.7 cannot be started

[Christian M. <chr...@ta...>]

Hello Asawari,

I'm very sorry for the trouble.

If the Commodo code signing certificate "UTN-USERFirst-Object" is being
present in the Third Party Certificates, please make sure "Code Signing"
and "Time Stamping" is activated.



If it is present this might mean, the Local (or Domain) Security Policy of
the server is too tight to allow the certificate to be verified. This
settings can be found in the Local Security Policy of the server the "Public
Key Policies"\"Certificate Path Validation Settings" and allows for the
Root Certificate Store "Third-Party Root CAs and Enterprise Root CAs".


If this doesn't/can't be set to active, another option would be to
move the "UTN-USERFirst-Object
Certificate" from the "Third Party Root CA" folder to the "Trusted Root
Certificate Authorities" folder.


After we started to sign our binaries with version 3.5.7, we received
reports from some customers about the same troubles you are having related
to the code signing certificate. Therefore starting with version 3.5.8 we
changed the way the Wrapper is handling certificate errors regarding the
code signing/timestamping certificate. The Wrapper will now only shutdown
itself if the signature of the binary was not successfully verified because
the binary or signature has been malformed but not if any problem with the
counter-signer has been found.

There is also another slight change, which was made in version 3.5.11 and
might be worth noted. If the Commodo Root certificate is not installed on a
server, the Windows API call WinVerifyTrust (
http://msdn.microsoft.com/en-us/library/aa388208%28v=vs.85%29.aspx) to
verify the certificate tries internally to retrieve the certificate online.
If the server is however not exposed to the internet, the WinVerifyTrust
may take up to 15 seconds to return, which slows down the start up quite a
bit. Therefore, we moved the certificate validation into a separate thread,
so if the WinVerifyTrust call takes longer than the configured
wrapper.startup_thread.timeout property then the Wrapper will continue to
startup without further delay.
http://wrapper.tanukisoftware.com/doc/english/prop-startup-thread-timeout.html

Hope this information helps you out.

Best Regards,

Christian Mueller
Tanuki Software, Ltd.

On Tue, Aug 21, 2012 at 6:32 PM, Asawari Pawar <ass...@gm...> wrote:

> Hi,
>
> I am using wrapper 32-bit on windows 3.5.7 version.
>
> I get following exception while starting the wrapper service.
>
> STATUS | wrapper | 2012/07/23 16:40:18 | Java Service Wrapper Professional
> Edition 32-bit 3.5.7
> STATUS | wrapper | 2012/07/23 16:40:18 | Copyright (C) 1999-2010 Tanuki
> Software, Ltd. All Rights Reserved.
> STATUS | wrapper | 2012/07/23 16:40:18 | http://wrapper.tanukisoftware.com
> STATUS | wrapper | 2012/07/23 16:40:18 | Licensed to BMC Software India
> Pvt. Ltd. for BPPM
> STATUS | wrapper | 2012/07/23 16:40:18 |
> FATAL | wrapper | 2012/07/23 16:40:18 | A signature was found in
> "D:\Apps\BMCPortal\appserver\websdk\bin\wrapper.exe", but checksum failed:
> (Errorcode: 0x48d5a0) wrapper.collect_sysinfo
> FATAL | wrapper | 2012/07/23 16:40:18 | Signer Certificate:
> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
> FATAL | wrapper | 2012/07/23 16:40:18 | 00 97 06 fe b5 6e 56 cc cb 66 3a
> bb 55 a7 a0 e4 76
> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: Tanuki Software Ltd.
> FATAL | wrapper | 2012/07/23 16:40:18 | TimeStamp Certificate:
> FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
> FATAL | wrapper | 2012/07/23 16:40:18 | 47 8a 8e fb 59 e1 d8 3f 0c e1 42
> d2 a2 87 07 be
> FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
> FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: COMODO Time Stamping
> Signer
> FATAL | wrapper | 2012/07/23 16:40:18 | Date of TimeStamp : 2010/12/20
> 03:31
> FATAL | wrapper | 2012/07/23 16:40:18 | The Wrapper will shutdown!
>
> I have followed the link
>
> http://wrapper.tanukisoftware.com/doc/german/troubleshooting.html#13
>
>
> which talks about installing the certificate and the server policy but
> still the issue is not resolved.
>
> Can anyone help me with the above issue?
>
> Thanks,
> Asawari
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Wrapper 3.5.7 cannot be started

[Asawari P. <ass...@gm...>]

Hi,

I am using wrapper 32-bit on windows 3.5.7 version.

I get following exception while starting the wrapper service.

STATUS | wrapper | 2012/07/23 16:40:18 | Java Service Wrapper Professional
Edition 32-bit 3.5.7
STATUS | wrapper | 2012/07/23 16:40:18 | Copyright (C) 1999-2010 Tanuki
Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/07/23 16:40:18 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2012/07/23 16:40:18 | Licensed to BMC Software India
Pvt. Ltd. for BPPM
STATUS | wrapper | 2012/07/23 16:40:18 |
FATAL | wrapper | 2012/07/23 16:40:18 | A signature was found in
"D:\Apps\BMCPortal\appserver\websdk\bin\wrapper.exe", but checksum failed:
(Errorcode: 0x48d5a0) wrapper.collect_sysinfo
FATAL | wrapper | 2012/07/23 16:40:18 | Signer Certificate:
FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
FATAL | wrapper | 2012/07/23 16:40:18 | 00 97 06 fe b5 6e 56 cc cb 66 3a bb
55 a7 a0 e4 76
FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: Tanuki Software Ltd.
FATAL | wrapper | 2012/07/23 16:40:18 | TimeStamp Certificate:
FATAL | wrapper | 2012/07/23 16:40:18 | Serial Number:
FATAL | wrapper | 2012/07/23 16:40:18 | 47 8a 8e fb 59 e1 d8 3f 0c e1 42 d2
a2 87 07 be
FATAL | wrapper | 2012/07/23 16:40:18 | Issuer Name: UTN-USERFirst-Object
FATAL | wrapper | 2012/07/23 16:40:18 | Subject Name: COMODO Time Stamping
Signer
FATAL | wrapper | 2012/07/23 16:40:18 | Date of TimeStamp : 2010/12/20 03:31
FATAL | wrapper | 2012/07/23 16:40:18 | The Wrapper will shutdown!

I have followed the link

http://wrapper.tanukisoftware.com/doc/german/troubleshooting.html#13


which talks about installing the certificate and the server policy but
still the issue is not resolved.

Can anyone help me with the above issue?

Thanks,
Asawari

Re: [Wrapper-user] Question about release notes

[Christian M. <chr...@ta...>]

Hello Ian,

thank you for your mail.

During a code review for version 3.3.6 we noticed that the Wrapper was not
checking the return value on the Windows API call SetConsoleCtrlHandler()
which registers and adds the control handler for the JVM.
I have actually never heard of any case where that function would fail.
Anyways in generas it is always a good idea to check the return value of a
function and print out a error message to the log. And if it really would
have failed before, then the control handler wasn't working and also no
indication about that written in the log file, which makes it then quite
difficult to tell from looking at the log file, what went wrong.

Hope this information helps you out.

Cheers,

Christian

On Fri, Aug 10, 2012 at 12:58 AM, <iko...@ax...> wrote:

> Hello,****
>
> I have a question regarding a fix done in version 3.3.6. In the release
> notes the fix notes state:****
>
> ** **
>
> - Fix a potential problem on Windows platforms where a failure to register
> the control handler was not being logged. If this happened, user logoffs
> would not be trapped correctly but no other problems would have occurred.*
> ***
>
> ** **
>
> The first sentence seems to imply that there are conditions where the
> handler cannot be registered and the problem that was fixed was that now
> that condition is logged whereas before it was not.  The second sentence
> seems to explain the effects of the handler not being registered correctly
> but it is not evident from those two sentences that there is now a fix to
> ensure that the handler is in fact registered correctly.****
>
> ** **
>
> My questions are, did this above fix ensure that the control handler is
> registered correctly or are there certain conditions under which the
> handler would not be registered and how likely it is to occur?  Is it
> limited to certain circumstances or environments?****
>
> ** **
>
> Thanks,****
>
> Ian Koelliker****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Question about release notes

[<iko...@ax...>]

Hello,
I have a question regarding a fix done in version 3.3.6. In the release notes the fix notes state:

- Fix a potential problem on Windows platforms where a failure to register the control handler was not being logged. If this happened, user logoffs would not be trapped correctly but no other problems would have occurred.

The first sentence seems to imply that there are conditions where the handler cannot be registered and the problem that was fixed was that now that condition is logged whereas before it was not.  The second sentence seems to explain the effects of the handler not being registered correctly but it is not evident from those two sentences that there is now a fix to ensure that the handler is in fact registered correctly.

My questions are, did this above fix ensure that the control handler is registered correctly or are there certain conditions under which the handler would not be registered and how likely it is to occur?  Is it limited to certain circumstances or environments?

Thanks,
Ian Koelliker

Re: [Wrapper-user] Updating running service

[Lars S. <Lar...@if...>]

Hi Leif

I don't seem to have any problems with the jar-files, they get copied 
fine, but the wrapper.exe and wrapper.dll are a problem. After I update 
the jar-file of my service I simply restart the computer.

If I try to do it the hard way, by killing the wrapper process, I assume 
that will cause my service to terminate too?

I am dealing with Windws XP, so the elevated account is probably not a 
problem, but it would of cause be nice if it would work on newer Windows 
too.

Lars

On 02-08-2012 10:55, Leif Mortenson wrote:
> Lars,
> Windows unfortunately does not allow this directly as all open files 
> are locked.  As long as the Wrapper.exe is running you will not be 
> able to update it.  This will be a problem with all of the jar and DLL 
> files as well.
>
> The solution is to actually stop the Wrapper and run another process 
> to do the update.   Then once the wrapper and your application have 
> been updated, you will want to restart the service.
>
> If you are running on the desktop, this will be fairly easy.  But if 
> running as a service, you will need a way to do this in the background 
> using a process that has all of the required permissions to 1) replace 
> the files, and 2) to stop and start the service.  The later will need 
> to be an elevated account.
>
> We will discuss options here as well.
>
> Cheers,
> Leif
>
> On Thu, Aug 2, 2012 at 5:02 PM, Lars Schnoor <Lar...@if... 
> <mailto:Lar...@if...>> wrote:
>
>     Hi
>
>     I have made a service that uses the service wrapper. I need to update
>     the service from time to time and for this I implemented a file
>     transfer
>     method. This works fine, I copy the files over the network to the
>     destination and restart the computer. The only problem is that the
>     wrapper.exe and wrapper.dll are in use and can not be overwritten. So
>     updating my service does not include wrapper.exe and wrapper.dll. I
>     would like to update all files including the two, is there a way to do
>     this? Can I shutdown wrapper.exe and have my service continue to run?
>     Thanks in advance!
>
>     Lars
>

Re: [Wrapper-user] How to stop the wrapper on Windows Switch User event?

[Jeroen V. <jvr...@gm...>]

Hey,

I think it should be possible. Use a combination of task scheduler ar
script that will stop the wrapper and the java-proces it is responsible for.
Don't know if there is a build-in function.

You can do this proces-wise by killing the wrapper.exe and the
corresponding java.exe proces in a script; or maybe you use aa certain dos
command to stop the wrapper in a more clean way(I don't know if there is
one that is used by the wrapper).

I know it is possible to do this way. i'm kinda doing the same thing on a
windows cluster. I use a combination of windows powershell and task
scheduler to check for remaining java-processes when a failover is detected
and kill them if there are. Task scheduler will however not work with
powershell(you'll need to use a .bat file or something like that to execute
the powershell script)

Hope this gives you a push in the right direction.

jeroen

On 6 August 2012 00:46, brian mcgann <br...@gi...> wrote:

> I'm wondering if it is possible to have the wrapper stop if it detects a
> Windows XP or Windows 7 Switch User event as opposed to a User Log Off
> event?
>
> Thanks,
>
> Brian McGann
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] How to stop the wrapper on Windows Switch User event?

[brian m. <br...@gi...>]

I'm wondering if it is possible to have the wrapper stop if it detects a
Windows XP or Windows 7 Switch User event as opposed to a User Log Off
event?

Thanks,

Brian McGann

Re: [Wrapper-user] Running console apps

[Leif M. <lei...@ta...>]

Alex,
Sorry, it is not currently possible to completely disable the Wrapper's
output.   You will at least always see the startup banner in the logs.That
output is logged at the STATUS log level which is as you found out, higher
than the INFO log level of the JVM output.

The Wrapper also has the ability to pass parameters directly through to the
JVM using the "--" value in the argument list.  Everything after that will
be sent directly to the JVM.

You can also customize the JVM to make all parameters go to the JVM:
http://wrapper.tanukisoftware.com/doc/english/customize.html

Cheers,
Leif

On Fri, Aug 3, 2012 at 9:29 PM, Alexandros Kritikos <al...@kr...>wrote:

> Hi Leif,
>
> We are experimenting with using wrapper to simply launch (and detach)
> various console java applications. These applications expect command line
> arguments so if they are run without anything they print out a usage
> message. Is it possible to disable ALL wrapper console output but still see
> any System.out messages from the java application? Currently if i set the
> console log level to anything less than INFO it not only suppresses wrapper
> console messages but the application ones. We are using the latest version
> of the wrapper.
>
> Many thanks in advance,
>
> Alex Kritikos
> my-Channels (A Software AG company)
>

[Wrapper-user] Running console apps

[Alexandros K. <al...@kr...>]

Hi Leif,

We are experimenting with using wrapper to simply launch (and detach) various console java applications. These applications expect command line arguments so if they are run without anything they print out a usage message. Is it possible to disable ALL wrapper console output but still see any System.out messages from the java application? Currently if i set the console log level to anything less than INFO it not only suppresses wrapper console messages but the application ones. We are using the latest version of the wrapper.

Many thanks in advance,

Alex Kritikos
my-Channels (A Software AG company)