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

[Wrapper-user] 質問：うるう秒について

[<Nob...@si...>]

タヌキソフトウェア　ご担当者様

いつもお世話になっております。
岩崎と申します。

Java Service Wrapper製品として、うるう秒を迎えた場合、どのような影響があるのかご教示頂けませんでしょうか？
また、影響がある場合には、その回避方法や対策をご教示下さい。

なお、Java Service Wrapperのバージョンは、3.5.26を使用しております。
※コミュニティ版です。

【備考】
OSのNTP同期設定は、slewモードです。

Re: [Wrapper-user] Clean shutdown of service when Windows shutsdown/restarts

[Maxime <ma...@ta...>]

Fredrick,

We have just released a new version (3.5.30) of the Java Service Wrapper.

In this new version, we added the ability for a service to handle the
SERVICE_CONTROL_SHUTDOWN control code sent before a system shutdown. This
can be simply configured by adding 'wrapper.ntservice.preshutdown=TRUE' in
your configuration file.

You may also use the 'wrapper.ntservice.preshutdown.timeout' property to
control how long the service manager should wait for your service to
shutdown cleanly until it timeouts.

You may read the descriptions of these properties in the following page:
https://wrapper.tanukisoftware.com/doc/english/prop-ntservice-preshutdown.html

As usual the new version can be downloaded on sourceforge or from our
website:
http://wrapper.tanukisoftware.com/doc/english/download.jsp

You may have a look at the release notes for a full list of changes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Please let me know if you have any questions or feedback.

Best Regards,

Maxime

On Wed, Mar 23, 2016 at 5:15 PM, Maxime <ma...@ta...> wrote:

> Fred,
>
> Thank you for reporting this issue.
>
> How long does your service need to shutdown cleanly?
>
> It seems that "WaitToKillServiceTimeout" has not effect on recent versions
> of Windows (or is limited to a value which is too low for your application
> to shutdown correctly).
>
> Currently the Wrapper does not handle the SERVICE_CONTROL_SHUTDOWN control
> code but we are studying the possibility to implement it in our next
> release.
>
> Best Regards,
>
> Maxime
>
> On Mon, Mar 21, 2016 at 8:06 PM, Fredrik <fre...@ho...> wrote:
>
>> Hi.
>> I have a problem that Windows doesn't wait for my service to shutdown
>> cleanly when shutting down/restarting Windows (tested on Windows Server
>> 2012 R2).
>> Windows only waits a short amount of time before simply killing the
>> service which results in an unclean shutdown.
>> I've done some research that Windows sends SERVICE_CONTROL_PRESHUTDOWN
>> control-code before  shutting down the OS.
>> Is it possible to get this control code via the wrapper or do you have
>> any other suggestions as how to handle this case.
>> I've also tried to set the "WaitToKillServiceTimeout" in the registry
>> without any luck.
>>
>> Regards
>> Fred
>>
>>
>> ------------------------------------------------------------------------------
>> Transform Data into Opportunity.
>> Accelerate data analysis in your applications with
>> Intel Data Analytics Acceleration Library.
>> Click to learn more.
>> http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>

[Wrapper-user] Maven release

[Guus d. K. <guu...@gm...>]

Hi,

In October 2015, Alexandre Klein wrote:

The current repository http://mvnrepository.com/artifact/tanukisoft/wrapper
> was not created by Tanuki Software Ltd. Feel free to use it, but we can't
> guarantee the authenticity of the files.
> However, it sounds like a good idea to have something on Maven, so we will
> have a look.
> We will let you know as soon as something is available.


(Archived link: https://sourceforge.net/p/wrapper/mailman/message/34557159/
 )

It would be good to have the community edition available in Maven, as that
will make it a lot easier to apply the wrapper to a lot of projects
(including my own). Has anything been decided on the matter?

Regards,

  Guus

[Wrapper-user] JMX Remote Configuration

[Mitchell S. <Mit...@cw...>]

Hello

I am attempting to configure the Tanuki wrapper for JMX monitoring but I am experiancing some issues

With other platforms I monitor not using the Tanuki wrapper (Tomcat), there are way to set both the rmiRegistryPort and the rmiServerPort which allows us to operate within the restrictions of our network.

However I cannot seem to replicate this behaviour.

Ideally what I would like is to set the initial connection (rmiRegisry) to port 11000 and the rmiServerPort to 11001

Without this it seems that the JVM selects a random port for the response which causes great difficulty with connectivity across distributed network

Can anyone help, offer some guidance

Thanks
Mitchell

Re: [Wrapper-user] Missing Tags

[Maxime <ma...@ta...>]

Jason,

Thank you for pointing out this issue. This was an omission in our
procedure. I just created 3 tags for v. 3.5.27, 3.5.28 and 3.5.29.
We will take care to create tags for our future releases.

Thank you again and sorry for the trouble it may have caused.

Best Regards,

Maxime

On Wed, May 18, 2016 at 10:27 AM, Jason Steenstra-Pickens <
jas...@or...> wrote:

> Hi,
>
>
>
> I am in the process of upgrading our application to use the latest version
> of the wrapper, version 3.5.29. We keep these artifacts in an internal ivy
> repository and the ivy configuration contains a link to the code repository
> and tag for that specific version. However, I noticed that the latest tag
> in https://sourceforge.net/p/wrapper/code/HEAD/tree/tags/ is version
> 3.5.26. Was this intentional or was it just an oversight? If there is no
> intention of adding a tag are you able to tell be what the revision number
> was for that build?
>
>
>
>
>
> Cheers,
>
> Jason
>
>
>
> [image: http://cdn.orionhealth.com/email/signature/logo.png]
> <https://www.orionhealth.com/>
>
> [image: http://cdn.orionhealth.com/email/signature/spacer.gif]
>
> [image: http://cdn.orionhealth.com/email/signature/spacer.gif]
>
> *Jason Steenstra-Pickens*
> Intermediate Software Developer
>
> *d *+64211844533
>
>
>
> *m *+64211844533
>
>
>
> *e*
>
> jason.steenstra-pickens
>
> @
>
> orionhealth.
>
> com
>
>
>
> *s* jason.steenstra-pickens
>
>
> Orion House, 181 Grafton Road, Grafton, Auckland 1010, New Zealand
>
>
>
> [image: http://cdn.orionhealth.com/email/signature/icon_facebook.gif]
> <https://www.facebook.com/orionhealth>
>
> [image: http://cdn.orionhealth.com/email/signature/icon_twitter.gif]
> <https://www.twitter.com/orionhealth>
>
> [image: http://cdn.orionhealth.com/email/signature/icon_linkedin.gif]
> <https://www.linkedin.com/company/orion-health>
>
>
>
> *www.orionhealth.com* <https://www.orionhealth.com/>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
> untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Missing Tags

[Jason Steenstra-P. <jas...@or...>]

Hi,

I am in the process of upgrading our application to use the latest version of the wrapper, version 3.5.29. We keep these artifacts in an internal ivy repository and the ivy configuration contains a link to the code repository and tag for that specific version. However, I noticed that the latest tag in https://sourceforge.net/p/wrapper/code/HEAD/tree/tags/ is version 3.5.26. Was this intentional or was it just an oversight? If there is no intention of adding a tag are you able to tell be what the revision number was for that build?


Cheers,
Jason

[http://cdn.orionhealth.com/email/signature/logo.png]<https://www.orionhealth.com/>

[http://cdn.orionhealth.com/email/signature/spacer.gif]

[http://cdn.orionhealth.com/email/signature/spacer.gif]

Jason Steenstra-Pickens
Intermediate Software Developer
d +64211844533


m +64211844533


e

jason.steenstra-pickens

@

orionhealth.

com


s jason.steenstra-pickens


Orion House, 181 Grafton Road, Grafton, Auckland 1010, New Zealand


[http://cdn.orionhealth.com/email/signature/icon_facebook.gif]<https://www.facebook.com/orionhealth>

[http://cdn.orionhealth.com/email/signature/icon_twitter.gif]<https://www.twitter.com/orionhealth>

[http://cdn.orionhealth.com/email/signature/icon_linkedin.gif]<https://www.linkedin.com/company/orion-health>


www.orionhealth.com<https://www.orionhealth.com/>

[Wrapper-user] WrapperManager.exec() is using fork() on Red Hat Enterprise Linux with WrapperProcessConfig.POSIX_SPAWN set

[Isenberg, H. <ise...@e-...>]

Our Java based server application is bundled with Tanuki Wrapper since years and used on different Linux distributions at customer locations. Recently we observed Out Of Memory issues when launching external processes, a problem which was already solved years ago with WrapperManager.exec(). However, with Red Hat 6.5 and newer, fork() is used. I haven't analyzed it in detail yet, but assume Red Hat has removed posix_spawn() or just forwards it to fork().

As Java 8 is now offering posix_spawn(), too, I'll try that as workaround:
http://bugs.java.com/view_bug.do?bug_id=5049299 
JDK-5049299 : (process) Use posix_spawn, not fork, on S10 to avoid swap exhaustion
Resolved Date: 2013-08-13
Fixed Versions: 8 (b105)

For launching the external process, Java 8 is using a similar method as Tanuki as it first starts an external process (jdk/jre/lib/jspawnhelper). Maybe falling back to this might be an option for Tanuki, too?

This sample apparently uses fork() on Red Hat 6.5 and newer:

String[] cmd = {"/bin/ls", "/tmp"};
WrapperProcessConfig wpc = new WrapperProcessConfig().setDetached(false).setStartType(WrapperProcessConfig.POSIX_SPAWN); 
WrapperProcess p = org.tanukisoftware.wrapper.WrapperManager.exec(cmd, wpc);
int result = p.waitFor();

-- 
Holger Isenberg
Professional Services
e-Spirit AG

T: +49 231 477 77 331
M: +49 178 280 81 64
Fax: +49 231 477 77 499
ise...@e-...
http://e-spirit.com

+++
News für Content-Strategen: Jetzt abonnieren! http://www.e-spirit.com/newsletter
Digitales Marketing mit FirstSpirit http://www.e-spirit.com/digitalmarketing
+++

Sitz des Unternehmens: Stockholmer Allee 24 | 44269 Dortmund
Vorstand: Jörn Bodemann (Vors.) | Udo Sträßer | Christoph Junge
Vorsitzender des Aufsichtsrats: Michael Kenfenheuer
Amtsgericht Dortmund (HRB 20399)

Re: [Wrapper-user] (no subject)

[Maxime <ma...@ta...>]

Hello Stepan,

Thank you for your email.

Did you check that "wrapperdemo.jar" is present in the lib folder and has
the correct permissions for the current user?
Also, you sent wrapper.conf, but demoapp is using demoapp.conf.

Best Regards,

Maxime

On Wed, Apr 13, 2016 at 5:57 AM, Stepan Shelkovskiy <qst...@gm...>
wrote:

> Hello, I have some problem with wrapper on single server (on other
> machines all works perfect) I did not see any difference in configuration
>
> for test I just download wrapper, extract it in
> /opt/wrapper-linux-x86-32-3.5.27
> mark demoapp,testwrapper,wrapper AS executables and launch
> ./demoapp console
>
>
> 1.Java Service Wrapper Community Edition 32-bit 3.5.27
> 2.Linux SMP Debian 3.2.78-1 i686 GNU/Linux
> 3.wrapper.conf attached (it is default)
> 4.wrapper.log (debug=true attached)
>
>
> I see one error in all cases Error: Could not find or load main class
> org.tanukisoftware.wrapper.demo.DemoApp
> http://joxi.ru/752aQY4UWoX120
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] (no subject)

[Stepan S. <qst...@gm...>]

Hello, I have some problem with wrapper on single server (on other machines
all works perfect) I did not see any difference in configuration

for test I just download wrapper, extract it in
/opt/wrapper-linux-x86-32-3.5.27
mark demoapp,testwrapper,wrapper AS executables and launch
./demoapp console


1.Java Service Wrapper Community Edition 32-bit 3.5.27
2.Linux SMP Debian 3.2.78-1 i686 GNU/Linux
3.wrapper.conf attached (it is default)
4.wrapper.log (debug=true attached)


I see one error in all cases Error: Could not find or load main class
org.tanukisoftware.wrapper.demo.DemoApp
http://joxi.ru/752aQY4UWoX120

Re: [Wrapper-user] Java service wrapper cannot start application as a service

[Alexandre K. <ale...@ta...>]

Adrian,

When you download the Wrapper from our Website, it comes with a test
application. Maybe you can try our test application.
After extracting the files, you may need to edit conf\wrapper.conf.
Then you can run:
bin\InstallTestWrapper-NT.bat
bin\StartTestWrapper-NT.bat

And to remove it:
bin\UninstallTestWrapper-NT.bat

Is it possible to let us know what was the value for prompt? Maybe we would
be able to reproduce your problem. If it contains sensitive information,
you can send us an email at su...@ta...

Regards,
Alexandre Klein

Alexandre Klein
Tanuki Software, Ltd.
6-18-10-4F Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com

On Thu, Apr 7, 2016 at 8:19 PM, Adrian Ganea <gan...@gm...>
wrote:

> Alexandre,
>
> Thanks for you support.​ We've already checked both registry keys and they
> look good.
> The strange thing is that we have some systems on which we have no issues
> and others on which the application cannot be started as a service, even
> though they have the exact same settings(registry wise, adobe connect
> application wise, etc.).
>
> We also found out that removing the "prompt" environment variable from
> "HKEY_CURRENT_USER\.DEFAULT\Environment"(which is the registry entry for
> local system account's environment variables/ the service is configured to
> run under local system account identity) seems to fix the issue. In my
> opinion this workaround is not suitable since the environment variable
> could be again automatically added(we couldn't find information on how it
> gets added in the first place) to the registry or other applications/os
> components may rely on it.
> This is clearly a bug related to this variable, but it seems to occur only
> in certain OS configurations and it is very difficult to isolate
> and troubleshoot.
>
> Regarding your last suggestion, we will probably contact Adobe Connect
> support team and ask them to provide an installer based on the upgraded
> version of java service wrapper - we wouldn't try to put the farm into a
> potentially unsupported installation.
>
> We'll let you know if we manage to fix this eventually.
>
> Thanks,
> Adrian
>
>
>
> On Thu, Apr 7, 2016 at 1:11 PM, Alexandre Klein <
> ale...@ta...> wrote:
>
>> Adrian,
>>
>> Thank you for you tests.
>>
>> Can you check in both locations for a key that has a value with %prompt%:
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
>> Manager\Environment
>> HKEY_CURRENT_USER\Environment
>>
>> There was a bug in the Wrapper if a defined environment variable would
>> expand to a length larger than the 32k limit specified in the
>> ExpandEnvironmentStrings system function. But if it was working before, it
>> may not be the problem. It was fixed in version 3.5.7.
>>
>> There was also another problem that was fixed in 3.5.5:
>> https://sourceforge.net/p/wrapper/bugs/244/
>>
>> I think another good test would be to try a more recent version of the
>> Wrapper:
>> https://wrapper.tanukisoftware.com/doc/english/download.jsp
>>
>> How to upgrade the Wrapper:
>> https://wrapper.tanukisoftware.com/doc/english/howto-upgrade.html
>>
>> Please try with 3.5.29 and let me know the result.
>>
>> Regards,
>> Alexandre Klein
>>
>>
>> Alexandre Klein
>> Tanuki Software, Ltd.
>> 6-18-10-4F Nishi-Kasai, Edogawa-ku
>> Tokyo 134-0088 Japan
>> Tel: +81-3-3878-3211
>> Fax: +81-3-3878-0313
>> http://www.tanukisoftware.com
>>
>> On Wed, Apr 6, 2016 at 4:33 PM, Adrian Ganea <gan...@gm...>
>> wrote:
>>
>>> ​With regards to your suggestion about the %prompt% environment
>>> variable, we tried to do the call from powershell using
>>> [System.Environment]::ExpandEnvironmentVariables("%prompt%"). We added this
>>> in a powershell script and added a scheduled task that runs under local
>>> system account, just as the Adobe Connect Service is configured in
>>> services.msc. Unfortunately, this worked as expected - the name was
>>> expanded to the values that we can see in the registries.
>>> Is there any way to try the above piece of code with a java call, to
>>> simulate what the wrapper does and see if we get any error message?
>>>
>>> Kind regards,
>>> Adrian
>>>
>>>
>>> On Wed, Apr 6, 2016 at 9:24 AM, Adrian Ganea <gan...@gm...>
>>> wrote:
>>>
>>>> Hi Alexandre,
>>>>
>>>> Thank you for your feedback!
>>>>
>>>> Device manager was the first ​place I checked when I saw the error.
>>>> Couldn't find any issues there - moreover, we have 2 web front ends for
>>>> this application and both fail with the same error. As I said previously,
>>>> we have the same error when trying to install on any new machine created in
>>>> the same domain so this is why I believe this is not a hardware related
>>>> problem(device not functioning, etc.) but rather it has something to do
>>>> with OS configuration/change(group policies/a windows update that may cause
>>>> the issue). Does this make any sense?
>>>>
>>>> Event viewer captures only the 7000(the adobe connect service failed to
>>>> start...) and 7009(a timeout was reached(30000) while waiting for the
>>>> Adobe....) errors when trying to start the service. Still, the 7009 error
>>>> is not relevant, that 30 seconds timeout is not reached, the error message
>>>> pops up immediately.
>>>>
>>>> Kind regards,
>>>> Adrian
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Apr 6, 2016 at 6:15 AM, Alexandre Klein <
>>>> ale...@ta...> wrote:
>>>>
>>>>> Adrian,
>>>>>
>>>>> Thank you for your message.
>>>>>
>>>>> This error happens when the Wrapper tries to load the system
>>>>> environment variable from registry.
>>>>> In your case, it seems that the Wrapper can get the values from the
>>>>> registry but the problem occurs when it tries to expand variables (i.e.
>>>>> when it encounter a variable between '%'). In the log message we can see
>>>>> that it failed when resolving %prompt%.
>>>>> This piece of code is executed only when the Wrapper is running as a
>>>>> service. That's why you don't see this error when running in console mode.
>>>>>
>>>>> As you mentioned, this error happens before loading the JVM.
>>>>>
>>>>> Based on this message "a device attached to the system is not
>>>>> functioning" (which is from the OS), is there any problems with your
>>>>> devices in the Device Manager?
>>>>>
>>>>> Also, do you see any error messages in the Event Viewer?
>>>>>
>>>>> Regards,
>>>>> Alexandre Klein
>>>>>
>>>>> Alexandre Klein
>>>>> Tanuki Software, Ltd.
>>>>> 6-18-10-4F Nishi-Kasai, Edogawa-ku
>>>>> Tokyo 134-0088 Japan
>>>>> Tel: +81-3-3878-3211
>>>>> Fax: +81-3-3878-0313
>>>>> http://www.tanukisoftware.com
>>>>>
>>>>> On Tue, Apr 5, 2016 at 3:01 PM, Adrian Ganea <gan...@gm...>
>>>>> wrote:
>>>>>
>>>>>> Good morning,
>>>>>>
>>>>>> We have an Adobe Connect installation based on Java Service
>>>>>> Wrapper Standard Edition 64bit  3.3.9.
>>>>>> The operating system which the application runs on is Windows Server
>>>>>> 2008R2 Standard Edition. ​
>>>>>> After trying to install windows updates and restarting the machine,
>>>>>> we noticed that the Adobe Connect Service(ConnectProService) couldn't be
>>>>>> started using services.msc - it immediately threw the error message "The
>>>>>> service did not respond to the start or control request in a timely
>>>>>> fashion".
>>>>>> The only error that is thrown in *wrapper.log* is "wrapper | Error |
>>>>>> Unable to expand prompt - a device attached to the system is not
>>>>>> functioning". The problem is that we reverted(using a VM snapshot
>>>>>> from a day ago) the updates and we still have the issues. We also tried to
>>>>>> do the installation on other machines on the same domain and we have the
>>>>>> same issue, so I'm assuming that this can be caused by a GPO(we tried on an
>>>>>> isolated test domain and it's working) issue.
>>>>>> We even ran procmon.exe(sysinternals) and it indicated the same issue
>>>>>> - "Invalid device request".
>>>>>> For the moment we have a workaround - start ConnectProService in
>>>>>> console mode(using -c switch) and all looks good with the application.
>>>>>> Since the application is functioning properly using this switch, we believe
>>>>>> there is a problem with the java service wrapper. Moreover, starting the
>>>>>> application as a service doesn't even get to load the JVM, so playing with
>>>>>> the *wrapper.conf* file didn't help too much(setting
>>>>>> wrapper.debug=true, etc.).
>>>>>> Have you encountered this issue before? Any other ideas on what to
>>>>>> try next?
>>>>>>
>>>>>> Kind regards,
>>>>>> Adrian Ganea
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> Wrapper-user mailing list
>>>>>> Wra...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> Wrapper-user mailing list
>>>>> Wra...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Java service wrapper cannot start application as a service

[Adrian G. <gan...@gm...>]

Alexandre,

Thanks for you support.​ We've already checked both registry keys and they
look good.
The strange thing is that we have some systems on which we have no issues
and others on which the application cannot be started as a service, even
though they have the exact same settings(registry wise, adobe connect
application wise, etc.).

We also found out that removing the "prompt" environment variable from
"HKEY_CURRENT_USER\.DEFAULT\Environment"(which is the registry entry for
local system account's environment variables/ the service is configured to
run under local system account identity) seems to fix the issue. In my
opinion this workaround is not suitable since the environment variable
could be again automatically added(we couldn't find information on how it
gets added in the first place) to the registry or other applications/os
components may rely on it.
This is clearly a bug related to this variable, but it seems to occur only
in certain OS configurations and it is very difficult to isolate
and troubleshoot.

Regarding your last suggestion, we will probably contact Adobe Connect
support team and ask them to provide an installer based on the upgraded
version of java service wrapper - we wouldn't try to put the farm into a
potentially unsupported installation.

We'll let you know if we manage to fix this eventually.

Thanks,
Adrian



On Thu, Apr 7, 2016 at 1:11 PM, Alexandre Klein <
ale...@ta...> wrote:

> Adrian,
>
> Thank you for you tests.
>
> Can you check in both locations for a key that has a value with %prompt%:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
> Manager\Environment
> HKEY_CURRENT_USER\Environment
>
> There was a bug in the Wrapper if a defined environment variable would
> expand to a length larger than the 32k limit specified in the
> ExpandEnvironmentStrings system function. But if it was working before, it
> may not be the problem. It was fixed in version 3.5.7.
>
> There was also another problem that was fixed in 3.5.5:
> https://sourceforge.net/p/wrapper/bugs/244/
>
> I think another good test would be to try a more recent version of the
> Wrapper:
> https://wrapper.tanukisoftware.com/doc/english/download.jsp
>
> How to upgrade the Wrapper:
> https://wrapper.tanukisoftware.com/doc/english/howto-upgrade.html
>
> Please try with 3.5.29 and let me know the result.
>
> Regards,
> Alexandre Klein
>
>
> Alexandre Klein
> Tanuki Software, Ltd.
> 6-18-10-4F Nishi-Kasai, Edogawa-ku
> Tokyo 134-0088 Japan
> Tel: +81-3-3878-3211
> Fax: +81-3-3878-0313
> http://www.tanukisoftware.com
>
> On Wed, Apr 6, 2016 at 4:33 PM, Adrian Ganea <gan...@gm...>
> wrote:
>
>> ​With regards to your suggestion about the %prompt% environment variable,
>> we tried to do the call from powershell using
>> [System.Environment]::ExpandEnvironmentVariables("%prompt%"). We added this
>> in a powershell script and added a scheduled task that runs under local
>> system account, just as the Adobe Connect Service is configured in
>> services.msc. Unfortunately, this worked as expected - the name was
>> expanded to the values that we can see in the registries.
>> Is there any way to try the above piece of code with a java call, to
>> simulate what the wrapper does and see if we get any error message?
>>
>> Kind regards,
>> Adrian
>>
>>
>> On Wed, Apr 6, 2016 at 9:24 AM, Adrian Ganea <gan...@gm...>
>> wrote:
>>
>>> Hi Alexandre,
>>>
>>> Thank you for your feedback!
>>>
>>> Device manager was the first ​place I checked when I saw the error.
>>> Couldn't find any issues there - moreover, we have 2 web front ends for
>>> this application and both fail with the same error. As I said previously,
>>> we have the same error when trying to install on any new machine created in
>>> the same domain so this is why I believe this is not a hardware related
>>> problem(device not functioning, etc.) but rather it has something to do
>>> with OS configuration/change(group policies/a windows update that may cause
>>> the issue). Does this make any sense?
>>>
>>> Event viewer captures only the 7000(the adobe connect service failed to
>>> start...) and 7009(a timeout was reached(30000) while waiting for the
>>> Adobe....) errors when trying to start the service. Still, the 7009 error
>>> is not relevant, that 30 seconds timeout is not reached, the error message
>>> pops up immediately.
>>>
>>> Kind regards,
>>> Adrian
>>>
>>>
>>>
>>>
>>> On Wed, Apr 6, 2016 at 6:15 AM, Alexandre Klein <
>>> ale...@ta...> wrote:
>>>
>>>> Adrian,
>>>>
>>>> Thank you for your message.
>>>>
>>>> This error happens when the Wrapper tries to load the system
>>>> environment variable from registry.
>>>> In your case, it seems that the Wrapper can get the values from the
>>>> registry but the problem occurs when it tries to expand variables (i.e.
>>>> when it encounter a variable between '%'). In the log message we can see
>>>> that it failed when resolving %prompt%.
>>>> This piece of code is executed only when the Wrapper is running as a
>>>> service. That's why you don't see this error when running in console mode.
>>>>
>>>> As you mentioned, this error happens before loading the JVM.
>>>>
>>>> Based on this message "a device attached to the system is not
>>>> functioning" (which is from the OS), is there any problems with your
>>>> devices in the Device Manager?
>>>>
>>>> Also, do you see any error messages in the Event Viewer?
>>>>
>>>> Regards,
>>>> Alexandre Klein
>>>>
>>>> Alexandre Klein
>>>> Tanuki Software, Ltd.
>>>> 6-18-10-4F Nishi-Kasai, Edogawa-ku
>>>> Tokyo 134-0088 Japan
>>>> Tel: +81-3-3878-3211
>>>> Fax: +81-3-3878-0313
>>>> http://www.tanukisoftware.com
>>>>
>>>> On Tue, Apr 5, 2016 at 3:01 PM, Adrian Ganea <gan...@gm...>
>>>> wrote:
>>>>
>>>>> Good morning,
>>>>>
>>>>> We have an Adobe Connect installation based on Java Service
>>>>> Wrapper Standard Edition 64bit  3.3.9.
>>>>> The operating system which the application runs on is Windows Server
>>>>> 2008R2 Standard Edition. ​
>>>>> After trying to install windows updates and restarting the machine, we
>>>>> noticed that the Adobe Connect Service(ConnectProService) couldn't be
>>>>> started using services.msc - it immediately threw the error message "The
>>>>> service did not respond to the start or control request in a timely
>>>>> fashion".
>>>>> The only error that is thrown in *wrapper.log* is "wrapper | Error |
>>>>> Unable to expand prompt - a device attached to the system is not
>>>>> functioning". The problem is that we reverted(using a VM snapshot
>>>>> from a day ago) the updates and we still have the issues. We also tried to
>>>>> do the installation on other machines on the same domain and we have the
>>>>> same issue, so I'm assuming that this can be caused by a GPO(we tried on an
>>>>> isolated test domain and it's working) issue.
>>>>> We even ran procmon.exe(sysinternals) and it indicated the same issue
>>>>> - "Invalid device request".
>>>>> For the moment we have a workaround - start ConnectProService in
>>>>> console mode(using -c switch) and all looks good with the application.
>>>>> Since the application is functioning properly using this switch, we believe
>>>>> there is a problem with the java service wrapper. Moreover, starting the
>>>>> application as a service doesn't even get to load the JVM, so playing with
>>>>> the *wrapper.conf* file didn't help too much(setting
>>>>> wrapper.debug=true, etc.).
>>>>> Have you encountered this issue before? Any other ideas on what to try
>>>>> next?
>>>>>
>>>>> Kind regards,
>>>>> Adrian Ganea
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> Wrapper-user mailing list
>>>>> Wra...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Java service wrapper cannot start application as a service

[Alexandre K. <ale...@ta...>]

Adrian,

Thank you for you tests.

Can you check in both locations for a key that has a value with %prompt%:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment
HKEY_CURRENT_USER\Environment

There was a bug in the Wrapper if a defined environment variable would
expand to a length larger than the 32k limit specified in the
ExpandEnvironmentStrings system function. But if it was working before, it
may not be the problem. It was fixed in version 3.5.7.

There was also another problem that was fixed in 3.5.5:
https://sourceforge.net/p/wrapper/bugs/244/

I think another good test would be to try a more recent version of the
Wrapper:
https://wrapper.tanukisoftware.com/doc/english/download.jsp

How to upgrade the Wrapper:
https://wrapper.tanukisoftware.com/doc/english/howto-upgrade.html

Please try with 3.5.29 and let me know the result.

Regards,
Alexandre Klein


Alexandre Klein
Tanuki Software, Ltd.
6-18-10-4F Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com

On Wed, Apr 6, 2016 at 4:33 PM, Adrian Ganea <gan...@gm...>
wrote:

> ​With regards to your suggestion about the %prompt% environment variable,
> we tried to do the call from powershell using
> [System.Environment]::ExpandEnvironmentVariables("%prompt%"). We added this
> in a powershell script and added a scheduled task that runs under local
> system account, just as the Adobe Connect Service is configured in
> services.msc. Unfortunately, this worked as expected - the name was
> expanded to the values that we can see in the registries.
> Is there any way to try the above piece of code with a java call, to
> simulate what the wrapper does and see if we get any error message?
>
> Kind regards,
> Adrian
>
>
> On Wed, Apr 6, 2016 at 9:24 AM, Adrian Ganea <gan...@gm...>
> wrote:
>
>> Hi Alexandre,
>>
>> Thank you for your feedback!
>>
>> Device manager was the first ​place I checked when I saw the error.
>> Couldn't find any issues there - moreover, we have 2 web front ends for
>> this application and both fail with the same error. As I said previously,
>> we have the same error when trying to install on any new machine created in
>> the same domain so this is why I believe this is not a hardware related
>> problem(device not functioning, etc.) but rather it has something to do
>> with OS configuration/change(group policies/a windows update that may cause
>> the issue). Does this make any sense?
>>
>> Event viewer captures only the 7000(the adobe connect service failed to
>> start...) and 7009(a timeout was reached(30000) while waiting for the
>> Adobe....) errors when trying to start the service. Still, the 7009 error
>> is not relevant, that 30 seconds timeout is not reached, the error message
>> pops up immediately.
>>
>> Kind regards,
>> Adrian
>>
>>
>>
>>
>> On Wed, Apr 6, 2016 at 6:15 AM, Alexandre Klein <
>> ale...@ta...> wrote:
>>
>>> Adrian,
>>>
>>> Thank you for your message.
>>>
>>> This error happens when the Wrapper tries to load the system environment
>>> variable from registry.
>>> In your case, it seems that the Wrapper can get the values from the
>>> registry but the problem occurs when it tries to expand variables (i.e.
>>> when it encounter a variable between '%'). In the log message we can see
>>> that it failed when resolving %prompt%.
>>> This piece of code is executed only when the Wrapper is running as a
>>> service. That's why you don't see this error when running in console mode.
>>>
>>> As you mentioned, this error happens before loading the JVM.
>>>
>>> Based on this message "a device attached to the system is not
>>> functioning" (which is from the OS), is there any problems with your
>>> devices in the Device Manager?
>>>
>>> Also, do you see any error messages in the Event Viewer?
>>>
>>> Regards,
>>> Alexandre Klein
>>>
>>> Alexandre Klein
>>> Tanuki Software, Ltd.
>>> 6-18-10-4F Nishi-Kasai, Edogawa-ku
>>> Tokyo 134-0088 Japan
>>> Tel: +81-3-3878-3211
>>> Fax: +81-3-3878-0313
>>> http://www.tanukisoftware.com
>>>
>>> On Tue, Apr 5, 2016 at 3:01 PM, Adrian Ganea <gan...@gm...>
>>> wrote:
>>>
>>>> Good morning,
>>>>
>>>> We have an Adobe Connect installation based on Java Service
>>>> Wrapper Standard Edition 64bit  3.3.9.
>>>> The operating system which the application runs on is Windows Server
>>>> 2008R2 Standard Edition. ​
>>>> After trying to install windows updates and restarting the machine, we
>>>> noticed that the Adobe Connect Service(ConnectProService) couldn't be
>>>> started using services.msc - it immediately threw the error message "The
>>>> service did not respond to the start or control request in a timely
>>>> fashion".
>>>> The only error that is thrown in *wrapper.log* is "wrapper | Error |
>>>> Unable to expand prompt - a device attached to the system is not
>>>> functioning". The problem is that we reverted(using a VM snapshot
>>>> from a day ago) the updates and we still have the issues. We also tried to
>>>> do the installation on other machines on the same domain and we have the
>>>> same issue, so I'm assuming that this can be caused by a GPO(we tried on an
>>>> isolated test domain and it's working) issue.
>>>> We even ran procmon.exe(sysinternals) and it indicated the same issue - "Invalid
>>>> device request".
>>>> For the moment we have a workaround - start ConnectProService in
>>>> console mode(using -c switch) and all looks good with the application.
>>>> Since the application is functioning properly using this switch, we believe
>>>> there is a problem with the java service wrapper. Moreover, starting the
>>>> application as a service doesn't even get to load the JVM, so playing with
>>>> the *wrapper.conf* file didn't help too much(setting
>>>> wrapper.debug=true, etc.).
>>>> Have you encountered this issue before? Any other ideas on what to try
>>>> next?
>>>>
>>>> Kind regards,
>>>> Adrian Ganea
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Java service wrapper cannot start application as a service

[Adrian G. <gan...@gm...>]

​With regards to your suggestion about the %prompt% environment variable,
we tried to do the call from powershell using
[System.Environment]::ExpandEnvironmentVariables("%prompt%"). We added this
in a powershell script and added a scheduled task that runs under local
system account, just as the Adobe Connect Service is configured in
services.msc. Unfortunately, this worked as expected - the name was
expanded to the values that we can see in the registries.
Is there any way to try the above piece of code with a java call, to
simulate what the wrapper does and see if we get any error message?

Kind regards,
Adrian


On Wed, Apr 6, 2016 at 9:24 AM, Adrian Ganea <gan...@gm...>
wrote:

> Hi Alexandre,
>
> Thank you for your feedback!
>
> Device manager was the first ​place I checked when I saw the error.
> Couldn't find any issues there - moreover, we have 2 web front ends for
> this application and both fail with the same error. As I said previously,
> we have the same error when trying to install on any new machine created in
> the same domain so this is why I believe this is not a hardware related
> problem(device not functioning, etc.) but rather it has something to do
> with OS configuration/change(group policies/a windows update that may cause
> the issue). Does this make any sense?
>
> Event viewer captures only the 7000(the adobe connect service failed to
> start...) and 7009(a timeout was reached(30000) while waiting for the
> Adobe....) errors when trying to start the service. Still, the 7009 error
> is not relevant, that 30 seconds timeout is not reached, the error message
> pops up immediately.
>
> Kind regards,
> Adrian
>
>
>
>
> On Wed, Apr 6, 2016 at 6:15 AM, Alexandre Klein <
> ale...@ta...> wrote:
>
>> Adrian,
>>
>> Thank you for your message.
>>
>> This error happens when the Wrapper tries to load the system environment
>> variable from registry.
>> In your case, it seems that the Wrapper can get the values from the
>> registry but the problem occurs when it tries to expand variables (i.e.
>> when it encounter a variable between '%'). In the log message we can see
>> that it failed when resolving %prompt%.
>> This piece of code is executed only when the Wrapper is running as a
>> service. That's why you don't see this error when running in console mode.
>>
>> As you mentioned, this error happens before loading the JVM.
>>
>> Based on this message "a device attached to the system is not
>> functioning" (which is from the OS), is there any problems with your
>> devices in the Device Manager?
>>
>> Also, do you see any error messages in the Event Viewer?
>>
>> Regards,
>> Alexandre Klein
>>
>> Alexandre Klein
>> Tanuki Software, Ltd.
>> 6-18-10-4F Nishi-Kasai, Edogawa-ku
>> Tokyo 134-0088 Japan
>> Tel: +81-3-3878-3211
>> Fax: +81-3-3878-0313
>> http://www.tanukisoftware.com
>>
>> On Tue, Apr 5, 2016 at 3:01 PM, Adrian Ganea <gan...@gm...>
>> wrote:
>>
>>> Good morning,
>>>
>>> We have an Adobe Connect installation based on Java Service
>>> Wrapper Standard Edition 64bit  3.3.9.
>>> The operating system which the application runs on is Windows Server
>>> 2008R2 Standard Edition. ​
>>> After trying to install windows updates and restarting the machine, we
>>> noticed that the Adobe Connect Service(ConnectProService) couldn't be
>>> started using services.msc - it immediately threw the error message "The
>>> service did not respond to the start or control request in a timely
>>> fashion".
>>> The only error that is thrown in *wrapper.log* is "wrapper | Error |
>>> Unable to expand prompt - a device attached to the system is not
>>> functioning". The problem is that we reverted(using a VM snapshot
>>> from a day ago) the updates and we still have the issues. We also tried to
>>> do the installation on other machines on the same domain and we have the
>>> same issue, so I'm assuming that this can be caused by a GPO(we tried on an
>>> isolated test domain and it's working) issue.
>>> We even ran procmon.exe(sysinternals) and it indicated the same issue - "Invalid
>>> device request".
>>> For the moment we have a workaround - start ConnectProService in console
>>> mode(using -c switch) and all looks good with the application. Since the
>>> application is functioning properly using this switch, we believe there is
>>> a problem with the java service wrapper. Moreover, starting the
>>> application as a service doesn't even get to load the JVM, so playing with
>>> the *wrapper.conf* file didn't help too much(setting
>>> wrapper.debug=true, etc.).
>>> Have you encountered this issue before? Any other ideas on what to try
>>> next?
>>>
>>> Kind regards,
>>> Adrian Ganea
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>

Re: [Wrapper-user] Java service wrapper cannot start application as a service

[Adrian G. <gan...@gm...>]

Hi Alexandre,

Thank you for your feedback!

Device manager was the first ​place I checked when I saw the error.
Couldn't find any issues there - moreover, we have 2 web front ends for
this application and both fail with the same error. As I said previously,
we have the same error when trying to install on any new machine created in
the same domain so this is why I believe this is not a hardware related
problem(device not functioning, etc.) but rather it has something to do
with OS configuration/change(group policies/a windows update that may cause
the issue). Does this make any sense?

Event viewer captures only the 7000(the adobe connect service failed to
start...) and 7009(a timeout was reached(30000) while waiting for the
Adobe....) errors when trying to start the service. Still, the 7009 error
is not relevant, that 30 seconds timeout is not reached, the error message
pops up immediately.

Kind regards,
Adrian




On Wed, Apr 6, 2016 at 6:15 AM, Alexandre Klein <
ale...@ta...> wrote:

> Adrian,
>
> Thank you for your message.
>
> This error happens when the Wrapper tries to load the system environment
> variable from registry.
> In your case, it seems that the Wrapper can get the values from the
> registry but the problem occurs when it tries to expand variables (i.e.
> when it encounter a variable between '%'). In the log message we can see
> that it failed when resolving %prompt%.
> This piece of code is executed only when the Wrapper is running as a
> service. That's why you don't see this error when running in console mode.
>
> As you mentioned, this error happens before loading the JVM.
>
> Based on this message "a device attached to the system is not functioning"
> (which is from the OS), is there any problems with your devices in the
> Device Manager?
>
> Also, do you see any error messages in the Event Viewer?
>
> Regards,
> Alexandre Klein
>
> Alexandre Klein
> Tanuki Software, Ltd.
> 6-18-10-4F Nishi-Kasai, Edogawa-ku
> Tokyo 134-0088 Japan
> Tel: +81-3-3878-3211
> Fax: +81-3-3878-0313
> http://www.tanukisoftware.com
>
> On Tue, Apr 5, 2016 at 3:01 PM, Adrian Ganea <gan...@gm...>
> wrote:
>
>> Good morning,
>>
>> We have an Adobe Connect installation based on Java Service
>> Wrapper Standard Edition 64bit  3.3.9.
>> The operating system which the application runs on is Windows Server
>> 2008R2 Standard Edition. ​
>> After trying to install windows updates and restarting the machine, we
>> noticed that the Adobe Connect Service(ConnectProService) couldn't be
>> started using services.msc - it immediately threw the error message "The
>> service did not respond to the start or control request in a timely
>> fashion".
>> The only error that is thrown in *wrapper.log* is "wrapper | Error |
>> Unable to expand prompt - a device attached to the system is not
>> functioning". The problem is that we reverted(using a VM snapshot from a
>> day ago) the updates and we still have the issues. We also tried to do the
>> installation on other machines on the same domain and we have the same
>> issue, so I'm assuming that this can be caused by a GPO(we tried on an
>> isolated test domain and it's working) issue.
>> We even ran procmon.exe(sysinternals) and it indicated the same issue - "Invalid
>> device request".
>> For the moment we have a workaround - start ConnectProService in console
>> mode(using -c switch) and all looks good with the application. Since the
>> application is functioning properly using this switch, we believe there is
>> a problem with the java service wrapper. Moreover, starting the
>> application as a service doesn't even get to load the JVM, so playing with
>> the *wrapper.conf* file didn't help too much(setting wrapper.debug=true,
>> etc.).
>> Have you encountered this issue before? Any other ideas on what to try
>> next?
>>
>> Kind regards,
>> Adrian Ganea
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Java service wrapper cannot start application as a service

[Alexandre K. <ale...@ta...>]

Adrian,

Thank you for your message.

This error happens when the Wrapper tries to load the system environment
variable from registry.
In your case, it seems that the Wrapper can get the values from the
registry but the problem occurs when it tries to expand variables (i.e.
when it encounter a variable between '%'). In the log message we can see
that it failed when resolving %prompt%.
This piece of code is executed only when the Wrapper is running as a
service. That's why you don't see this error when running in console mode.

As you mentioned, this error happens before loading the JVM.

Based on this message "a device attached to the system is not functioning"
(which is from the OS), is there any problems with your devices in the
Device Manager?

Also, do you see any error messages in the Event Viewer?

Regards,
Alexandre Klein

Alexandre Klein
Tanuki Software, Ltd.
6-18-10-4F Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com

On Tue, Apr 5, 2016 at 3:01 PM, Adrian Ganea <gan...@gm...>
wrote:

> Good morning,
>
> We have an Adobe Connect installation based on Java Service
> Wrapper Standard Edition 64bit  3.3.9.
> The operating system which the application runs on is Windows Server
> 2008R2 Standard Edition. ​
> After trying to install windows updates and restarting the machine, we
> noticed that the Adobe Connect Service(ConnectProService) couldn't be
> started using services.msc - it immediately threw the error message "The
> service did not respond to the start or control request in a timely
> fashion".
> The only error that is thrown in *wrapper.log* is "wrapper | Error |
> Unable to expand prompt - a device attached to the system is not
> functioning". The problem is that we reverted(using a VM snapshot from a
> day ago) the updates and we still have the issues. We also tried to do the
> installation on other machines on the same domain and we have the same
> issue, so I'm assuming that this can be caused by a GPO(we tried on an
> isolated test domain and it's working) issue.
> We even ran procmon.exe(sysinternals) and it indicated the same issue - "Invalid
> device request".
> For the moment we have a workaround - start ConnectProService in console
> mode(using -c switch) and all looks good with the application. Since the
> application is functioning properly using this switch, we believe there is
> a problem with the java service wrapper. Moreover, starting the
> application as a service doesn't even get to load the JVM, so playing with
> the *wrapper.conf* file didn't help too much(setting wrapper.debug=true,
> etc.).
> Have you encountered this issue before? Any other ideas on what to try
> next?
>
> Kind regards,
> Adrian Ganea
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Java service wrapper cannot start application as a service

[Adrian G. <gan...@gm...>]

Good morning,

We have an Adobe Connect installation based on Java Service
Wrapper Standard Edition 64bit  3.3.9.
The operating system which the application runs on is Windows Server 2008R2
Standard Edition. ​
After trying to install windows updates and restarting the machine, we
noticed that the Adobe Connect Service(ConnectProService) couldn't be
started using services.msc - it immediately threw the error message "The
service did not respond to the start or control request in a timely
fashion".
The only error that is thrown in *wrapper.log* is "wrapper | Error | Unable
to expand prompt - a device attached to the system is not functioning". The
problem is that we reverted(using a VM snapshot from a day ago) the updates
and we still have the issues. We also tried to do the installation on other
machines on the same domain and we have the same issue, so I'm assuming
that this can be caused by a GPO(we tried on an isolated test domain and
it's working) issue.
We even ran procmon.exe(sysinternals) and it indicated the same issue
- "Invalid
device request".
For the moment we have a workaround - start ConnectProService in console
mode(using -c switch) and all looks good with the application. Since the
application is functioning properly using this switch, we believe there is
a problem with the java service wrapper. Moreover, starting the
application as a service doesn't even get to load the JVM, so playing with
the *wrapper.conf* file didn't help too much(setting wrapper.debug=true,
etc.).
Have you encountered this issue before? Any other ideas on what to try next?

Kind regards,
Adrian Ganea

[Wrapper-user] Clean shutdown of service when Windows shutsdown/restarts

[Fredrik <fre...@ho...>]

The shutdown time varies between 30 seconds to 3 - 4 minutes depending on
what external resources are connected to the application at the time of
shutdown.

Regards
Fredrik

Re: [Wrapper-user] Clean shutdown of service when Windows shutsdown/restarts

[Maxime <ma...@ta...>]

Fred,

Thank you for reporting this issue.

How long does your service need to shutdown cleanly?

It seems that "WaitToKillServiceTimeout" has not effect on recent versions
of Windows (or is limited to a value which is too low for your application
to shutdown correctly).

Currently the Wrapper does not handle the SERVICE_CONTROL_SHUTDOWN control
code but we are studying the possibility to implement it in our next
release.

Best Regards,

Maxime

On Mon, Mar 21, 2016 at 8:06 PM, Fredrik <fre...@ho...> wrote:

> Hi.
> I have a problem that Windows doesn't wait for my service to shutdown
> cleanly when shutting down/restarting Windows (tested on Windows Server
> 2012 R2).
> Windows only waits a short amount of time before simply killing the
> service which results in an unclean shutdown.
> I've done some research that Windows sends SERVICE_CONTROL_PRESHUTDOWN
> control-code before  shutting down the OS.
> Is it possible to get this control code via the wrapper or do you have any
> other suggestions as how to handle this case.
> I've also tried to set the "WaitToKillServiceTimeout" in the registry
> without any luck.
>
> Regards
> Fred
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

[Wrapper-user] Clean shutdown of service when Windows shutsdown/restarts

[Fredrik <fre...@ho...>]

Hi.
I have a problem that Windows doesn't wait for my service to shutdown
cleanly when shutting down/restarting Windows (tested on Windows Server
2012 R2).
Windows only waits a short amount of time before simply killing the service
which results in an unclean shutdown.
I've done some research that Windows sends SERVICE_CONTROL_PRESHUTDOWN
control-code before  shutting down the OS.
Is it possible to get this control code via the wrapper or do you have any
other suggestions as how to handle this case.
I've also tried to set the "WaitToKillServiceTimeout" in the registry
without any luck.

Regards
Fred

Re: [Wrapper-user] Is Windows x64 support also GPL2

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

Adam,
The 64-bit Windows version was never released under the Community Edition
License.
The Standard or Professional Edition native libraries (DLLs) will only work
when run with a Standard or Professional Edition copy of the Wrapper.

Cheers,
Leif

On Thu, Mar 10, 2016 at 2:39 AM, Adam Retter <ad...@ex...> wrote:

> Hi there,
>
> I noticed that in the community edition you don't include the native
> library for Windows x64 support but you do in the standard and
> professional editions.
>
> Is the Windows x64 support also available under the GPL2 license? And
> if so, are we allowed to distribute the Windows 64 native binary from
> the standard edition alongside the others as GPL 2 licensed?
>
>
> Thanks Adam.
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb

[Wrapper-user] Is Windows x64 support also GPL2

[Adam R. <ad...@ex...>]

Hi there,

I noticed that in the community edition you don't include the native
library for Windows x64 support but you do in the standard and
professional editions.

Is the Windows x64 support also available under the GPL2 license? And
if so, are we allowed to distribute the Windows 64 native binary from
the standard edition alongside the others as GPL 2 licensed?


Thanks Adam.

-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Wrapper-user] Automatic adaption of detailed JVM parameters like -Xmn to system memory

[Isenberg, H. <ise...@e-...>]

Thank you, that would be a well usable solution for my use-cases!
I'll include it in our default setting as soon as the release is available.

> Am 29.02.2016 um 10:34 schrieb Maxime <ma...@ta...>:
> 
> Holger,
> 
> Thank you for your message.
> 
> We discussed about the issue you raised and we plan to solve it by introducing a new virtual variable in the next release of the Java Service Wrapper.
> The variable will be something like WRAPPER_SYSMEM_<P> where <P> is a percentage of the physical memory available on the system.
> You will be able to use it in the wrapper.java.additional parameters for any JVM options that deal with memory.
> 
> wrapper.java.additional.x=-Xmx%WRAPPER_SYSMEM_60.0%
> 
> Your feedback is highly appreciated. Thank you.
> 
> Sincerely,
> 
> The Java Service Wrapper team.
> 
> On Tue, Feb 23, 2016 at 1:54 AM, Isenberg, Holger <ise...@e-...> wrote:
> With wrapper.java.maxmemory.percent a fraction of the system memory can be automatically assigned to the JVM to be used as overall heap limit. That is working fine, but for our server software, more specific JVM parameters are required as wrapper.java.additional like -Xmn or -XX:MaxMetaspaceSize or -XX:ReservedCodeCacheSize. For now, the values for these parameters are set to absolute numbers by our post-install script.
> 
> For automatic app deployment, a setting as fraction like maxmemory.percent is preferable so the process would automatically resize on the next start after the machine memory is increased.
> 
> Is someone using a workaround with using wrapper.java.additional_file to set environment variables to be read afterwards or something else to achieve setting percent values in wrapper.java.additional?
> 
> --
> Holger Isenberg
> e-Spirit AG
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140_______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Automatic adaption of detailed JVM parameters like -Xmn to system memory

[Maxime <ma...@ta...>]

Holger,

Thank you for your message.

We discussed about the issue you raised and we plan to solve it by
introducing a new virtual variable in the next release of the Java Service
Wrapper.
The variable will be something like WRAPPER_SYSMEM_<P> where <P> is a
percentage of the physical memory available on the system.
You will be able to use it in the wrapper.java.additional parameters for
any JVM options that deal with memory.



*wrapper.java.additional.x=-Xmx%WRAPPER_SYSMEM_60.0%*
Your feedback is highly appreciated. Thank you.

Sincerely,

The Java Service Wrapper team.

On Tue, Feb 23, 2016 at 1:54 AM, Isenberg, Holger <ise...@e-...>
wrote:

> With wrapper.java.maxmemory.percent a fraction of the system memory can be
> automatically assigned to the JVM to be used as overall heap limit. That is
> working fine, but for our server software, more specific JVM parameters are
> required as wrapper.java.additional like -Xmn or -XX:MaxMetaspaceSize or
> -XX:ReservedCodeCacheSize. For now, the values for these parameters are set
> to absolute numbers by our post-install script.
>
> For automatic app deployment, a setting as fraction like maxmemory.percent
> is preferable so the process would automatically resize on the next start
> after the machine memory is increased.
>
> Is someone using a workaround with using wrapper.java.additional_file to
> set environment variables to be read afterwards or something else to
> achieve setting percent values in wrapper.java.additional?
>
> --
> Holger Isenberg
> e-Spirit AG
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] Automatic adaption of detailed JVM parameters like -Xmn to system memory

[Isenberg, H. <ise...@e-...>]

With wrapper.java.maxmemory.percent a fraction of the system memory can be automatically assigned to the JVM to be used as overall heap limit. That is working fine, but for our server software, more specific JVM parameters are required as wrapper.java.additional like -Xmn or -XX:MaxMetaspaceSize or -XX:ReservedCodeCacheSize. For now, the values for these parameters are set to absolute numbers by our post-install script.

For automatic app deployment, a setting as fraction like maxmemory.percent is preferable so the process would automatically resize on the next start after the machine memory is increased.

Is someone using a workaround with using wrapper.java.additional_file to set environment variables to be read afterwards or something else to achieve setting percent values in wrapper.java.additional?

--
Holger Isenberg
e-Spirit AG

Re: [Wrapper-user] wrapper process is hung

[Cade T. <ca...@ca...>]

Hello Leif,
First off thank you so much for the response.

I updated the SO question with some additional details.  We are running a
very old version at 3.3.6 (not sure how to exactly verify this, but that is
my best guess).  It has been running years without issue, so unfortunately
out of site, out of mind.

I looked at the /var/log/messages at the time of the SIGKILL, but didn't
see anything in there logged from the C code.

I'm open to any ideas on how to isolate both the SIGKILL and the hung
wrapper.

Thanks in advance.

--cade

On Tue, Feb 9, 2016 at 10:05 PM, Leif Mortenson <
lei...@ta...> wrote:

> Cade,
> I am sorry for the trouble.
> I replied to you on Stack Overflow.
> Please let me know the version of the Wrapper, OS, and content of your
> syslog when the JVM was killed.
>
> http://stackoverflow.com/questions/35283549/java-service-wrapper-parent-process-is-hung/35306109
>
> Thanks,
> Leif
>
>
> On Tue, Feb 9, 2016 at 1:41 PM, Cade Thacker <ca...@ca...> wrote:
>
>> Hello All,
>> I'm not sure how to figure this out so figured I would turn to the
>> experts.
>>
>> I documented everything here:
>>
>>
>> http://stackoverflow.com/questions/35283549/java-service-wrapper-parent-process-is-hung
>>
>> But the simple summary is that when I issue a kill $pid (SIGTERM/15) on
>> the wrapper process (the JVM is long dead via something else killing it
>> with SIGKILL/9) nothing happens. (this is the same call from stopit() in
>> the wrapper.sh distributed by you all.
>>
>> As documented in the other question, that causes other issues downstream
>> because without the wrapper dying correctling, I can't restart them both.
>>
>> Any ideas on how to best trouble shoot this?  I'm not sure what would be
>> "stuck" in the wrapper C code so that a SIGTERM would not be properly
>> processed? SIGKILL/9 works as expected.
>>
>> If this was a Java process, I'd get a thread dump and a heap dump, but
>> not sure how to attack this C code.  Maybe dig through something in
>> /proc/$pid?
>>
>> Any help is incredibly appreciated!
>>
>>
>> --
>>
>> --cade
>>
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>


-- 

--cade