11:21 a.m.
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:20 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2094:
----------------------------------------
Those are the Java types, of course, from the API. So, where do we fix this?
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:56 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-2094:
-----------------------------------
I guess we fix the API? We don't really need thread count to be BigDecimal, right?
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:55 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2094:
----------------------------------------
Ok, for thread count properties (in all the pools) I switched to INT
https://github.com/aloubyansky/jboss-as/commit/2f5175bcbd54ce5dc17fa4b77e...
But for keepalive time, we should probably change the XSD.
The hierarchy of types is like this:
xsd:long is derived from xsd:integer by limiting min and max inclusive boundaries. Then
xsd:int is derived from xsd:long in the same way.
So, actually, the xsd allows bigger value then Java long.
I haven't sent the pull request yet. I want us to agree on all the issues here.
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:08 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-2094:
-----------------------------------
Sounds OK to me, but I'm only looking at it from a console perspective. Any primitive
type works for me as long as :read-resource-description agrees with the XSD.
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:27 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2094:
----------------------------------
Component/s: Domain Management
Server
(was: CLI)
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Server
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2094:
----------------------------------
Fix Version/s: 7.1.0.CR1
Scheduling for 7.1.0.CR1, but I think this may already be fixed?
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Server
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
Fix For: 7.1.0.CR1
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:36 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2094:
----------------------------------------
I left it open because because it was related to schema changes which I didn't do.
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Server
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
Fix For: 7.1.0.CR1
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:27 a.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2094:
------------------------------
Fix Version/s: 7.1.0.Final
(was: 7.1.0.CR1)
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Server
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
Fix For: 7.1.0.Final
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-2094:
-------------------------------------
Assignee: Brian Stansberry (was: Alexey Loubyansky)
Assigning threads-related management stuff to myself.
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Server
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Brian Stansberry
Priority: Minor
Fix For: 7.1.0.Final
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
[
https://issues.jboss.org/browse/AS7-2094?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-2094.
-----------------------------------
Assignee: Alexey Loubyansky (was: Brian Stansberry)
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Final)
Resolution: Done
Stuart had fixed the xsd issue in commit 1de35c8, and Alexey had fixed the
read-resource-description.
read-resource-description shows incorrect data types in Thread Pools
--------------------------------------------------------------------
Key: AS7-2094
URL: https://issues.jboss.org/browse/AS7-2094
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Server
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
Priority: Minor
Fix For: 7.1.0.CR1
If you do :read-resource-description on a bounded-queue-thread-pool you will get several
attributes with type of BigDecimal. From the xsd it looks none of them actually are of
that type. I'm glad for this because the console can't handle BigDecimal right
now.
Also, keepalive timeout is shown as a Long when it is really an Integer.
There are probably more of these as I have not checked throughout the subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4681
days inactive
4776
days old
10 comments
7 participants
participants (7)
-
Alexey Loubyansky (Commented) (JIRA) -
Brian Stansberry (Assigned) (JIRA)
-
Brian Stansberry (JIRA)
-
Brian Stansberry (Updated) (JIRA)
-
Jason Greene (Updated) (JIRA)
-
Stan Silvert (Commented) (JIRA)
-
Stan Silvert (Created) (JIRA)