9:15 p.m.
This works fine for me. Adding that xml snippet to standalone.xml after the
<extensions> element I see the property being set during boot before any processing
of subsystem operations begins.
On Dec 12, 2016, at 1:55 PM, Brian Stansberry
<brian.stansberry(a)redhat.com> wrote:
I don’t see anything in the organization of boot ops that would have changed the
ordering, and the add op for that system property should be executing prior to the
subsystem ops. I’ll see if I can reproduce.
> On Dec 12, 2016, at 12:10 PM, Kabir Khan <kabir.khan(a)jboss.com> wrote:
>
> Where are you trying to use the system property from? They should only be attempted
resolved during the RUNTIME stage, not MODEL.
>> On 12 Dec 2016, at 18:00, Tom Jenkinson <tom.jenkinson(a)redhat.com> wrote:
>>
>> Hi,
>>
>> I have a subsystem that configures itself from system properties.
>>
>> For example:
>> <system-properties>
>> <property name="RecoveryEnvironmentBean.expiryScannerClassNames"
value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner
com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/>
>> </system-properties>
>>
>> In earlier revisions of WFLY this worked fine. However I am now seeing that the
system property is not set until after my subsystem has started. I can tell this as I have
breakpoints on where I process the property. I can see "MSC service thread 1-4"
attempting to process the property (which is not set). I do later see messages that
suggest the system property is set but at that the later point:
>>
>> 2016-12-12 17:57:48,042 TRACE [org.jboss.as.controller.management-operation]
(Controller Boot Thread) Final response for step handler
org.jboss.as.server.operations.SystemPropertyAddHandler@784c8c5f handling add in address
[("system-property" =>
"RecoveryEnvironmentBean.expiryScannerClassNames")] is {"outcome"
=> "success"}
>> 2016-12-12 17:57:48,093 TRACE [org.jboss.as.controller.management-operation]
(Controller Boot Thread) Final response for step handler
org.jboss.as.controller.ValidateModelStepHandler@87b4493 handling
internal-model-validation in address [("system-property" =>
"RecoveryEnvironmentBean.expiryScannerClassNames")] is {"outcome"
=> "success"}
>>
>> Does my subsystem need to depend on something to get the old behaviour of being
started after system properties are processed?
>>
>> My subsystem is the transaction one and the service is the recovery manager.
>>
>> Thanks!
>> Tom
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat