[JBoss JIRA] (AS7-6252) mail subsystem cannot be created from scratch with the CLI
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6252?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on AS7-6252:
----------------------------------
Another workaround(IMO more appropriate) would be to do batch operation
something like:
{noformat}
batch
/subsystem=mail:remove
/subsystem=mail:add
/subsystem=mail:add/session=smtp:add(....)
/subsystem=mail:add/session=smtp/server=smtp:add(....)
batch-run
{noformat}
in any case it is bug and linked PR addresses it properly
> mail subsystem cannot be created from scratch with the CLI
> ----------------------------------------------------------
>
> Key: AS7-6252
> URL: https://issues.jboss.org/browse/AS7-6252
> Project: Application Server 7
> Issue Type: Bug
> Components: Mail
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Tom Fonteyne
> Assignee: Tom Fonteyne
> Priority: Minor
>
> /subsystem=mail:add
> fails with:
> JBAS014677: Failed to persist configuration change: JBAS014675: Failed to marshal configuration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JGRP-1559) FD: monitor task sometimes isn't running
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1559?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-1559 at 12/28/12 11:29 AM:
-----------------------------------------------------------
I changed the logic slightly:
- The monitor task is running when the membership is 2 or greater and it stops when the membership drops below
- There's 1 method (computePingDest()) which sets pingable_mbrs and ping_dest
- The monitor task doesn't do anything if ping_dest is null
This ensures that the monitor task is always running and a temporary null ping_dest doesn't cause it to stop.
was (Author: belaban):
I changed the logic slightly:
- The monitor task is running when the membership is 2 or greater and it stops when the membership drops below
- There's 1 method (computePingDest()) which sets pingable_mbrs and ping_dest
- The monitor task doesn't do anything if ping_dest is null
> FD: monitor task sometimes isn't running
> ----------------------------------------
>
> Key: JGRP-1559
> URL: https://issues.jboss.org/browse/JGRP-1559
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.2.6, 3.3
>
>
> FD.isMonitorRunning() is sometimes false even when the membership is > 1. Probable cause is restartMonitor() will stops the running monitor, but doesn't start a new one if ping_dest == null.
> Need to investigate concurrent updates to pingable_mbrs and ping_dest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (JGRP-1559) FD: monitor task sometimes isn't running
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1559?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1559:
--------------------------------
I changed the logic slightly:
- The monitor task is running when the membership is 2 or greater and it stops when the membership drops below
- There's 1 method (computePingDest()) which sets pingable_mbrs and ping_dest
- The monitor task doesn't do anything if ping_dest is null
> FD: monitor task sometimes isn't running
> ----------------------------------------
>
> Key: JGRP-1559
> URL: https://issues.jboss.org/browse/JGRP-1559
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.2.6, 3.3
>
>
> FD.isMonitorRunning() is sometimes false even when the membership is > 1. Probable cause is restartMonitor() will stops the running monitor, but doesn't start a new one if ping_dest == null.
> Need to investigate concurrent updates to pingable_mbrs and ping_dest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (AS7-6251) SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS defined incompatible ModelType and ParameterValidator
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/AS7-6251?page=com.atlassian.jira.plugin.s... ]
Chao Wang commented on AS7-6251:
--------------------------------
hi [~jalpedersen] why we use a different LONG type here?
I'm seeing this issue will fail the test ComplexDatasourceSubsystemTestCase when I tried to find a solution for AS7-6139 to strictly check the numeric value in ModelTypeValidator, and avoid the validation case like ModelNode(Long.MAX_LONG).asInt()
> SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS defined incompatible ModelType and ParameterValidator
> ----------------------------------------------------------------------------------------------------------
>
> Key: AS7-6251
> URL: https://issues.jboss.org/browse/AS7-6251
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> The SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS is defined :
> {code:title=org.jboss.as.connector.subsystems.common.pool.Constants.java|borderStyle=solid}
> public static final SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS = new SimpleAttributeDefinition(BACKGROUNDVALIDATIONMILLIS_NAME, Validation.Tag.BACKGROUND_VALIDATION_MILLIS.getLocalName(), new ModelNode(), ModelType.LONG, true, true, MeasurementUnit.MILLISECONDS, new IntRangeValidator(1, true, true));
> {code}
> The ModelType should be an integer value as defined in jboss-as-datasources_1_1.xsd:
> {code:xml}
> <xs:element name="background-validation-millis" type="xs:nonNegativeInteger" minOccurs="0">
> <xs:annotation>
> <xs:documentation>
> <![CDATA[[
> The background-validation-millis element specifies the amount of
> time, in millis, that background validation will run.
> ]]>
> </xs:documentation>
> </xs:annotation>
> </xs:element>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (AS7-6251) SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS defined incompatible ModelType and ParameterValidator
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/AS7-6251?page=com.atlassian.jira.plugin.s... ]
Jesper Pedersen closed AS7-6251.
--------------------------------
Resolution: Won't Fix
> SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS defined incompatible ModelType and ParameterValidator
> ----------------------------------------------------------------------------------------------------------
>
> Key: AS7-6251
> URL: https://issues.jboss.org/browse/AS7-6251
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> The SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS is defined :
> {code:title=org.jboss.as.connector.subsystems.common.pool.Constants.java|borderStyle=solid}
> public static final SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS = new SimpleAttributeDefinition(BACKGROUNDVALIDATIONMILLIS_NAME, Validation.Tag.BACKGROUND_VALIDATION_MILLIS.getLocalName(), new ModelNode(), ModelType.LONG, true, true, MeasurementUnit.MILLISECONDS, new IntRangeValidator(1, true, true));
> {code}
> The ModelType should be an integer value as defined in jboss-as-datasources_1_1.xsd:
> {code:xml}
> <xs:element name="background-validation-millis" type="xs:nonNegativeInteger" minOccurs="0">
> <xs:annotation>
> <xs:documentation>
> <![CDATA[[
> The background-validation-millis element specifies the amount of
> time, in millis, that background validation will run.
> ]]>
> </xs:documentation>
> </xs:annotation>
> </xs:element>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (AS7-5631) add-user script confusing error: Password must not have atleast one digit.
by boualem BOULARES (JIRA)
[ https://issues.jboss.org/browse/AS7-5631?page=com.atlassian.jira.plugin.s... ]
boualem BOULARES commented on AS7-5631:
---------------------------------------
yes jboss requires at least a numeric value in the password
> add-user script confusing error: Password must not have atleast one digit.
> --------------------------------------------------------------------------
>
> Key: AS7-5631
> URL: https://issues.jboss.org/browse/AS7-5631
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.2.0.Alpha1
> Reporter: Cheng Fang
> Assignee: Ondrej Zizka
> Fix For: 7.2.0.CR1
>
>
> when running add-user.sh to add an application user, and entering a weal password, got the following error:
> Password :
> Re-enter Password :
> What roles do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]:
> * Error *
> JBAS015266: Password must not have atleast one digit.
> I guess what it meant is password must have at least one digit.
> A search showed the following files referencing this message:
> ./domain-management/src/main/java/org/jboss/as/domain/management/DomainManagementMessages.java
> This file also contains some other typo like "atleast".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (AS7-6251) SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS defined incompatible ModelType and ParameterValidator
by Chao Wang (JIRA)
Chao Wang created AS7-6251:
------------------------------
Summary: SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS defined incompatible ModelType and ParameterValidator
Key: AS7-6251
URL: https://issues.jboss.org/browse/AS7-6251
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.3.Final (EAP)
Reporter: Chao Wang
Assignee: Chao Wang
Priority: Minor
The SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS is defined :
{code:title=org.jboss.as.connector.subsystems.common.pool.Constants.java|borderStyle=solid}
public static final SimpleAttributeDefinition BACKGROUNDVALIDATIONMILLIS = new SimpleAttributeDefinition(BACKGROUNDVALIDATIONMILLIS_NAME, Validation.Tag.BACKGROUND_VALIDATION_MILLIS.getLocalName(), new ModelNode(), ModelType.LONG, true, true, MeasurementUnit.MILLISECONDS, new IntRangeValidator(1, true, true));
{code}
The ModelType should be an integer value as defined in jboss-as-datasources_1_1.xsd:
{code:xml}
<xs:element name="background-validation-millis" type="xs:nonNegativeInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>
<![CDATA[[
The background-validation-millis element specifies the amount of
time, in millis, that background validation will run.
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months