January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9391) Validation errors with "jboss-web_11_0.xsd

by Erik . (JIRA)

[ https://issues.jboss.org/browse/WFLY-9391?page=com.atlassian.jira.plugin.... ] Erik . commented on WFLY-9391: ------------------------------ The include for jboss-common_7_0.xsd {code:xml} <xsd:include schemaLocation="jboss-common_7_0.xsd"/> {code} to solve WFLY-5410 was added in jboss-web_10_1.xsd but not to jboss-web_10_0.xsd and jboss-web_11_0.xsd. > Validation errors with "jboss-web_11_0.xsd > ------------------------------------------ > > Key: WFLY-9391 > URL: https://issues.jboss.org/browse/WFLY-9391 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.CR1 > Reporter: Wolfgang Knauf > Assignee: Jason Greene > > Eclipse reports some errors when validating a "jboss-web.xml" file which defines the 11.0 xsd. > First problem: "web-app_3_1.xsd" is imported. The target namespace seems to be invalid, it should be "http://xmlns.jcp.org/xml/ns/javaee" instead of "http://java.sun.com/xml/ns/javaee" > <xsd:import namespace="http://xmlns.jcp.org/xml/ns/javaee" schemaLocation="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"/> > The validation error: *"The namespace attribute 'http://java.sun.com/xml/ns/javaee' of an import element information must be identical to the targetNamespace attribute 'http://xmlns.jcp.org/xml/ns/javaee' of the imported document".* > It would probably also make sense to include the full schemaLocation URL ;-). > After fixing the namespace, there are four more errors left: > *src-resolve: Cannot resolve the name 'jboss:jndiEnvironmentRefsGroup' to a( n ) group component > src-resolve: Cannot resolve the name 'javaee:generic-booleanType' to a( n ) 'simpleType definition' component > src-ct.2.1: Complex type definition Representation Error for type 'symbolic-link-allowedType' ... > src-resolve: Cannot resolve the name 'jboss:security-roleType' to a( n ) 'type definition' component* > The first two errors: previous versions of jboss-web.xsd imported "jboss-common_6_0.xsd" which defined a "jndiEnvironmentRefsGroup". This file also imported "javaee_6.xsd", which defines the "generic-booleanType". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-973) JMX - Non string attributes dont work well with expressions & min/max

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-973?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-973: ----------------------------------------- After many years I finally understand what the issue is here! I filed WFCORE-3493 which I now realize is the same thing that this is talking about. > JMX - Non string attributes dont work well with expressions & min/max > --------------------------------------------------------------------- > > Key: WFCORE-973 > URL: https://issues.jboss.org/browse/WFCORE-973 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, JMX > Reporter: Tomaz Cerar > Assignee: Enrique González Martínez > Priority: Minor > Attachments: stacktrace.log > > > See ModelControllerMBeanTestCase.java:255 > problem is in conversion of attributes and when we have expressions jmx attribute type becomes String even if AD is of type INT > And if attribute has min/max setting mbean fails validation upon creation > I am not actually sure how we can fix this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-973) JMX - Non string attributes dont work well with expressions & min/max

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-973?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-973: --------------------------------------- Assignee: Brian Stansberry (was: Enrique González Martínez) > JMX - Non string attributes dont work well with expressions & min/max > --------------------------------------------------------------------- > > Key: WFCORE-973 > URL: https://issues.jboss.org/browse/WFCORE-973 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, JMX > Reporter: Tomaz Cerar > Assignee: Brian Stansberry > Priority: Minor > Attachments: stacktrace.log > > > See ModelControllerMBeanTestCase.java:255 > problem is in conversion of attributes and when we have expressions jmx attribute type becomes String even if AD is of type INT > And if attribute has min/max setting mbean fails validation upon creation > I am not actually sure how we can fix this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3493) MBeanInfoFactory stores invalid minValue/maxValue data for jboss.as.expr domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3493?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3493: ------------------------------------- Issue Type: Bug (was: Task) > MBeanInfoFactory stores invalid minValue/maxValue data for jboss.as.expr domain > ------------------------------------------------------------------------------- > > Key: WFCORE-3493 > URL: https://issues.jboss.org/browse/WFCORE-3493 > Project: WildFly Core > Issue Type: Bug > Components: JMX > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > MBeanInfoFactory.getParameterInfos is trying to store a minValue and maxValue in the OpenMBeanParameterInfo it creates if the DMR description data includes a "min" or a "max". This is fine when numeric types are what is being stored, but with the jboss.as.expr domain what's being stored are Strings. And OpenMBeanParameterInfo is meant to do meaningful comparisons of values against any configured min and max. It does this via Comparable.compareTo calls on the provided objects. That doesn't work with String, e.g. "6".compareTo("2147483647") reports that 6 is bigger. > Constructing the OpenMBeanParameterInfo itself will fail if item has a default that doesn't lexically compare properly with any min or max or if the min and max don't happen to lexically compare properly. The only reason this doesn't blow up now is we don't happen to have any attributes with default values that are lexically greater than the string form of their max (e.g. 3 or higher would be more than Integer.MAX_VALUE). > I expect we'd also see failures if anyone used the OpenMBeanParameterInfo we provide and called isValue on it with something like 3. > I think the correct solution is to simply not provide this data for any non-numeric OpenMBeanParameterInfo. There would be a loss of information provided to human readers who happen to inspect the OpenMBeanParameterInfo but what we provide now is not correct for software consumers. An alternative is to only turn this off is the attribute has a default that doesn't fall lexically between the min and the max, or if we have min that is lexically greater than the max. This would mean we continue to present human readable data and just hope that there are no software consumers that expect it to function as per the OpenMBeanParameterInfo javadoc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3493) MBeanInfoFactory stores invalid minValue/maxValue data for jboss.as.expr domain

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3493: ---------------------------------------- Summary: MBeanInfoFactory stores invalid minValue/maxValue data for jboss.as.expr domain Key: WFCORE-3493 URL: https://issues.jboss.org/browse/WFCORE-3493 Project: WildFly Core Issue Type: Task Components: JMX Reporter: Brian Stansberry Assignee: Brian Stansberry MBeanInfoFactory.getParameterInfos is trying to store a minValue and maxValue in the OpenMBeanParameterInfo it creates if the DMR description data includes a "min" or a "max". This is fine when numeric types are what is being stored, but with the jboss.as.expr domain what's being stored are Strings. And OpenMBeanParameterInfo is meant to do meaningful comparisons of values against any configured min and max. It does this via Comparable.compareTo calls on the provided objects. That doesn't work with String, e.g. "6".compareTo("2147483647") reports that 6 is bigger. Constructing the OpenMBeanParameterInfo itself will fail if item has a default that doesn't lexically compare properly with any min or max or if the min and max don't happen to lexically compare properly. The only reason this doesn't blow up now is we don't happen to have any attributes with default values that are lexically greater than the string form of their max (e.g. 3 or higher would be more than Integer.MAX_VALUE). I expect we'd also see failures if anyone used the OpenMBeanParameterInfo we provide and called isValue on it with something like 3. I think the correct solution is to simply not provide this data for any non-numeric OpenMBeanParameterInfo. There would be a loss of information provided to human readers who happen to inspect the OpenMBeanParameterInfo but what we provide now is not correct for software consumers. An alternative is to only turn this off is the attribute has a default that doesn't fall lexically between the min and the max, or if we have min that is lexically greater than the max. This would mean we continue to present human readable data and just hope that there are no software consumers that expect it to function as per the OpenMBeanParameterInfo javadoc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-9610: ---------------------------------- Calling jobOperator.stop(executionId) to stop the job execution. It should work even though it's in STARTING status. If it doesn't, please file a JIRA issue and it should be fixed. > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Serg Pol (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Serg Pol commented on WFLY-9610: -------------------------------- do You mean call jobOperator.stop(executionId) or abandon(executionId) in this case? will it work in this case? because BatchJob wasn't yet started(status STARTING) in reality thanks > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-9610: ---------------------------------- A job execution in STARTING status can be stopped by the batch client. So your requirement (run it or drop it) can be achieved by a timed stop operation from the batch client. For a general time-to-live feature in job execution, we will need to evaluate it more. > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Serg Pol (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Serg Pol commented on WFLY-9610: -------------------------------- this delayed BatchJob is executed later if free thread appears, according my test. Is it possible to manage execution of delayed BatchJobs with status STARTING? To switch it off? For example if BatchJob wasn't started because of no available free threads than it will not be started any more later, for example in half hour. Starting of BatchJobs in wrong time because of no available free threads now can be bad for some tasks-use cases. > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1482) GSSAPI tests can be more clear as Parameterized

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1482?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1482: ---------------------------- Affects Version/s: 1.2.0.Beta11 > GSSAPI tests can be more clear as Parameterized > ----------------------------------------------- > > Key: ELY-1482 > URL: https://issues.jboss.org/browse/ELY-1482 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Testsuite > Affects Versions: 1.2.0.Beta11 > Reporter: Jan Kalina > Assignee: Jan Kalina > > This 4 tests in GssapiTestSuite can be replaced by one Parametrized JUnit test: > * JdkClientJdkServerSuiteChild > * JdkClientWildFlyServerSuiteChild > * WildFlyClientJdkServerSuiteChild > * WildFlyClientWildFlyServerSuiteChild -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 January 2018