7:22 a.m.
Dear devs,
a small proposal: would it be fine to expose transaction timeout defaults as
a property in the transactions subsystem ?
AFAIK you have to include it in the coordinator-environment element. ....
<subsystem xmlns="urn:jboss:domain:transactions:1.0">
<core-environment socket-binding="txn-socket-process-id"/>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<coordinator-environment enable-statistics="false"
default-timeout="300" />
</subsystem>
kind regards,
Francesco Marchioni
7:48 a.m.
Do you mean the default timeout? Because it can be set before starting a
new transaction.
Carlo
On 05/05/2011 02:22 PM, Francesco Marchioni wrote:
Dear devs,
a small proposal: would it be fine to expose transaction timeout
defaults as a property in the transactions subsystem ?
AFAIK you have to include it in the coordinator-environment element. ....
<subsystem xmlns="urn:jboss:domain:transactions:1.0">
<core-environment socket-binding="txn-socket-process-id"/>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<coordinator-environment enable-statistics="false"
default-timeout="300" />
</subsystem>
kind regards,
Francesco Marchioni
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
10:45 a.m.
It's already there:
<xs:complexType name="coordinator-environment">
<xs:annotation>
<xs:documentation>
<![CDATA[
The coordinator environment configuration.
]]>
</xs:documentation>
</xs:annotation>
<xs:attribute name="enable-statistics" type="xs:boolean"
default="false"/>
<xs:attribute name="default-timeout" type="xs:int"
default="300" />
</xs:complexType>
Apologies if it got added since this thread started.
On 5/5/11 7:22 AM, Francesco Marchioni wrote:
Dear devs,
a small proposal: would it be fine to expose transaction timeout
defaults as a property in the transactions subsystem ?
AFAIK you have to include it in the coordinator-environment element. ....
<subsystem xmlns="urn:jboss:domain:transactions:1.0">
<core-environment socket-binding="txn-socket-process-id"/>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<coordinator-environment enable-statistics="false"
default-timeout="300" />
</subsystem>
kind regards,
Francesco Marchioni
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
10:57 a.m.
Hello,
I beg your pardon I was meaning to expose the default transaction timeout in
standalone.xml (not in the .xsd stylesheet) . At the moment, it's a
"hidden"
default element of coordinator-environment.
<subsystem xmlns="urn:jboss:domain:transactions:1.0">
<core-environment socket-binding="txn-socket-process-id"/>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<coordinator-environment/>
<object-store/>
</subsystem>
Could it be useful for a common user to have this attribute handy ?
Regards
Francesco
2011/5/9 Brian Stansberry <brian.stansberry(a)redhat.com>
It's already there:
<xs:complexType name="coordinator-environment">
<xs:annotation>
<xs:documentation>
<![CDATA[
The coordinator environment configuration.
]]>
</xs:documentation>
</xs:annotation>
<xs:attribute name="enable-statistics" type="xs:boolean"
default="false"/>
<xs:attribute name="default-timeout" type="xs:int"
default="300" />
</xs:complexType>
Apologies if it got added since this thread started.
On 5/5/11 7:22 AM, Francesco Marchioni wrote:
> Dear devs,
> a small proposal: would it be fine to expose transaction timeout
> defaults as a property in the transactions subsystem ?
> AFAIK you have to include it in the coordinator-environment element. ....
>
> <subsystem xmlns="urn:jboss:domain:transactions:1.0">
> <core-environment socket-binding="txn-socket-process-id"/>
> <recovery-environment socket-binding="txn-recovery-environment"
> status-socket-binding="txn-status-manager"/>
>
> <coordinator-environment enable-statistics="false"
default-timeout="300"
/>
>
> </subsystem>
>
> kind regards,
> Francesco Marchioni
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
11:38 a.m.
I don't want to make a general pattern of doing that, but in this case I
can see the benefit; we have a bunch of socket binding stuff in that
subsystem config which is boilerplate that might discourage users from
looking for this one thing that they'd most likely want to tweak.
https://issues.jboss.org/browse/AS7-728
On 5/9/11 10:57 AM, Francesco Marchioni wrote:
Hello,
I beg your pardon I was meaning to expose the default transaction
timeout in standalone.xml (not in the .xsd stylesheet) . At the moment,
it's a "hidden" default element of coordinator-environment.
<subsystem xmlns="urn:jboss:domain:transactions:1.0">
<core-environment socket-binding="txn-socket-process-id"/>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<coordinator-environment/>
<object-store/>
</subsystem>
Could it be useful for a common user to have this attribute handy ?
Regards
Francesco
2011/5/9 Brian Stansberry <brian.stansberry(a)redhat.com
<mailto:brian.stansberry@redhat.com>>
It's already there:
<xs:complexType name="coordinator-environment">
<xs:annotation>
<xs:documentation>
<![CDATA[
The coordinator environment configuration.
]]>
</xs:documentation>
</xs:annotation>
<xs:attribute name="enable-statistics" type="xs:boolean"
default="false"/>
<xs:attribute name="default-timeout" type="xs:int"
default="300" />
</xs:complexType>
Apologies if it got added since this thread started.
On 5/5/11 7:22 AM, Francesco Marchioni wrote:
> Dear devs,
> a small proposal: would it be fine to expose transaction timeout
> defaults as a property in the transactions subsystem ?
> AFAIK you have to include it in the coordinator-environment
element. ....
>
> <subsystem xmlns="urn:jboss:domain:transactions:1.0">
> <core-environment socket-binding="txn-socket-process-id"/>
> <recovery-environment socket-binding="txn-recovery-environment"
> status-socket-binding="txn-status-manager"/>
>
> <coordinator-environment enable-statistics="false"
default-timeout="300" />
>
> </subsystem>
>
> kind regards,
> Francesco Marchioni
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
4948
days inactive
4952
days old
4 comments
3 participants
participants (3)
-
Brian Stansberry -
Carlo de Wolf -
Francesco Marchioni