December 2012 - jboss-jira - Jboss List Archives

[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

13 years, 4 months

1
0
0 / 0

[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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6253) mail subsystem cannot be created from scratch with the CLI

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-6253: --------------------------------- Summary: mail subsystem cannot be created from scratch with the CLI Key: AS7-6253 URL: https://issues.jboss.org/browse/AS7-6253 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6252) mail subsystem cannot be created from scratch with the CLI

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-6252: --------------------------------- Summary: 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

13 years, 4 months

1
0
0 / 0

[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

13 years, 4 months

1
0
0 / 0

[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

13 years, 4 months

1
0
0 / 0

[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/27/12 12:06 PM: ----------------------------------------------------------- This method is called every 2 seconds: {code} private void startFdMonitorIfNeeded(FD fd, JChannel channel) { boolean moreThanTwoMembersInCluster = channel.isConnected() && channel.getView().getMembers().size() > 1; if( moreThanTwoMembersInCluster ) { if( !fd.isMonitorRunning() ) { fd.startFailureDetection(); LOG.error("FD forcefully started for nodeId = " + channel.getName() + ", cluster = " + channel.getClusterName()); } } } {code} After 65 min it reported that task was not running. was (Author: belaban): This method is called every 2 seconds: private void startFdMonitorIfNeeded(FD fd, JChannel channel) { boolean moreThanTwoMembersInCluster = channel.isConnected() && channel.getView().getMembers().size() > 1; if( moreThanTwoMembersInCluster ) { if( !fd.isMonitorRunning() ) { fd.startFailureDetection(); LOG.error("FD forcefully started for nodeId = " + channel.getName() + ", cluster = " + channel.getClusterName()); } } } After 65 min it reported that task was not running. > 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

13 years, 4 months

1
0
0 / 0

[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: -------------------------------- This method is called every 2 seconds: private void startFdMonitorIfNeeded(FD fd, JChannel channel) { boolean moreThanTwoMembersInCluster = channel.isConnected() && channel.getView().getMembers().size() > 1; if( moreThanTwoMembersInCluster ) { if( !fd.isMonitorRunning() ) { fd.startFailureDetection(); LOG.error("FD forcefully started for nodeId = " + channel.getName() + ", cluster = " + channel.getClusterName()); } } } After 65 min it reported that task was not running. > 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1559) FD: monitor task sometimes isn't running

by Bela Ban (JIRA)

Bela Ban created JGRP-1559: ------------------------------ Summary: 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6104) jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove()

by Raymond Naseef (JIRA)

[ https://issues.jboss.org/browse/AS7-6104?page=com.atlassian.jira.plugin.s... ] Raymond Naseef edited comment on AS7-6104 at 12/27/12 10:59 AM: ---------------------------------------------------------------- This comment on 2012-12-07 made no sense. Keeping as this was referenced later in the timeline was (Author: raymond.naseef): Reinstalled JBoss 7.1.1 and repeated steps on the same computer. :remove succeeded, so there were no errors. I will look into this more, but expect it will be closed unless something comes up. > jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove() > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-6104 > URL: https://issues.jboss.org/browse/AS7-6104 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 7.1.1.Final > Environment: Windows 7 Professional SP1 > Reporter: Raymond Naseef > Assignee: Brian Stansberry > Labels: jboss-as7, modules, postgresql > Fix For: 7.2.0.Alpha1 > > > NullPointerException during jboss-cli remove with command: > jboss-cli --connect command="/subsystem=datasources/jdbc-driver=bop:remove" > Console and log below. > This happens when standalone.xml has XML entry for driver that does not exist (see "Steps to Reproduce"). I have also seen this happen in a case where the driver does exist; not sure how the latter happened, or how important that is. > MS-DOS Console: > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: null", > "rolled-back" => true > } > Server Log: > 23:17:42,627 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 19) JBAS014612: Operation ("remove") failed - address: ([ > ("subsystem" => "datasources"), > ("jdbc-driver" => "postgresql-driver") > ]): java.lang.NullPointerException > at org.jboss.as.controller.OperationContextImpl.doRemove(OperationContextImpl.java:298) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.OperationContextImpl.removeService(OperationContextImpl.java:293) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.connector.subsystems.datasources.JdbcDriverRemove.performRuntime(JdbcDriverRemove.java:66) > at org.jboss.as.controller.AbstractRemoveStepHandler$1.execute(AbstractRemoveStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] -- 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

13 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012