Description of problem: The same bundle being executed in 3.3 results in different behavior from 3.1.2. The 3.3 bundle deployment does not add the same HKLM registry additions/modifications when compared to the 3.1.2 bundle deployment. As a limiter to the behavior, this only occurs when the agent is running under the local system account. Setting the service to run as a specific admin user allows the bundle deployment to execute in a manner similar to 3.1.2 with the registry edits occurring successfully. Version-Release number of selected component (if applicable): JBoss ON 3.3 How reproducible: Always
I am still digging into this a bit. What we know is that if running a 3.3 agent as a service under the SYSTEM user the installer executed by the JBoss ON bundle recipe does not create some of its registry keys. The installer does print some error messages related to files not being found but this does not appear to be directly tied to the creation of the missing keys. If the agent is running as a service under an actual user account, the installer executes as expected and all keys are created correctly. Using the exact same bundle in 3.1.2, the installer executes as expected and all keys are created correctly regardless of running as a service as the SYSTEM account or normal user account. I am looking into the Java Service Wrapper as the cause as this is the most obvious change between 3.1.2 and 3.3. JBoss ON 3.1.2 is using an old binary provided directly by the Tanuki Software Java Service Wrapper community/developer project. 3.3 on the other hand is using a new version of the source built as part of the JBoss ON distribution. Additionally, not only is the version different but the fact that we provide a 64-bit version in 3.3 may be of importance.
commit bac3bb61dd5c71b495318af50a8347dc3b14d2b5 Merge: 1fe43cb a2b784c Author: Michael Burman <yak> Date: Mon Sep 4 21:16:48 2017 +0300 Merge pull request #320 from josejulio/bugs/1324217 Bug 1324217 - Checks %TMP% and %TEMP% paths on windows, and tries to … commit a2b784c65334db8b91a6206c534fc064f0be9de2 Author: Josejulio Martínez <jmartine> Date: Wed Aug 30 18:59:24 2017 -0500 Bug 1324217 - Checks %TMP% and %TEMP% paths on windows, and tries to create them if needed
Moving to ON_QA. JON 3.3.9 CR01 artifacts are available for test from here: http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/135/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of jon-server-3.3.0.GA-update-09.zip.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2846