[JBoss JIRA] (AS7-3446) If you remove a thread factory when the factory is assigned to a pool, you get strange errors.
7:05 a.m.
Stan Silvert created AS7-3446:
---------------------------------
Summary: If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.1.Final
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:57 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3446:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.2.Final
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
4:05 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-3446:
----------------------------------
stan, any update on this?
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
7:24 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3446:
-----------------------------------
I should get to it next week. I just tried it out and the message no longer appears,
which probably is a bug on the server side. At that point the thread pool still has a
non-existent factory assigned to it.
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
4:03 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-3446:
-----------------------------
Fix Version/s: 7.2.0.Alpha1
(was: 7.1.2.Final-redhat1)
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.2.0.Alpha1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
4:05 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-3446:
-----------------------------
Fix Version/s: 7.1.2.Final-redhat1
(was: 7.2.0.Alpha1)
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:28 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Stan Silvert resolved AS7-3446.
-------------------------------
Resolution: Done
This was apparently fixed on the server side with the latest AS update.
Now when you delete a thread factory it automatically removes it from any thread pools it
was assigned to. I'm going to give Brian a heads up just to confirm this.
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:56 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Stan Silvert reopened AS7-3446:
-------------------------------
Reopening.
This is still broken. What I was seeing in console was not
the true story. It just looked like the factory was removed from the thread pool. But
that was just a weird GWT/console behavior resulting from the fact that the drop-down is
now empty.
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:06 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Stan Silvert reassigned AS7-3446:
---------------------------------
Assignee: Brian Stansberry (was: Stan Silvert)
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:15 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-3446:
----------------------------------
and the operation does respond with:
{noformat}
[INFO] {
[INFO] "outcome" => "failed",
[INFO] "rolled-back" => true
[INFO] }
{noformat}
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:15 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-3446:
----------------------------------
This is what you get on the server side:
{noformat}
13:13:03,525 ERROR [org.jboss.as.controller.management-operation]
(HttpManagementService-threads - 15) JBAS014612: Operation ("read-attribute")
failed - address: ([
("subsystem" => "threads"),
("bounded-queue-thread-pool" => "bounded_queue")
]): java.lang.IllegalStateException: JBAS012459: The executor service hasn't been
initialized.
at
org.jboss.as.threads.BoundedQueueThreadPoolService.getValue(BoundedQueueThreadPoolService.java:88)
at
org.jboss.as.threads.BoundedQueueThreadPoolService.getRejectedCount(BoundedQueueThreadPoolService.java:148)
at
org.jboss.as.threads.BoundedQueueThreadPoolMetricsHandler.setResult(BoundedQueueThreadPoolMetricsHandler.java:58)
at
org.jboss.as.threads.ThreadPoolMetricsHandler.executeRuntimeStep(ThreadPoolMetricsHandler.java:68)
at
org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:319)
at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:225)
at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:232)
at
org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
at
org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
at
org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[classes.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[classes.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.0.0.GA.jar:2.0.0.GA]
{noformat}
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:26 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-3446:
-----------------------------
Comment: was deleted
(was: and the operation does respond with:
{noformat}
[INFO] {
[INFO] "outcome" => "failed",
[INFO] "rolled-back" => true
[INFO] }
{noformat}
)
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:28 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3446:
-----------------------------------
That's odd. I still get no error at all.
{noformat}
/subsystem=threads/queueless-thread-pool=myqueless/:add(max-threads=1)
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
/subsystem=threads/thread-factory=myfactory/:add
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
/subsystem=threads/queueless-thread-pool=myqueless/:write-attribute(name=thread-factory,value=myfactory)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
/subsystem=threads/thread-factory=myfactory/:remove
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
{noformat}
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:28 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun edited comment on AS7-3446 at 4/26/12 7:28 AM:
-----------------------------------------------------------
It's actually a sequence of errors.
First (upon removal of the factory you'll get on the client:
{noformat}
JBAS014762: Removing services has lead to unsatisfied dependencies: Service
jboss.thread.factory.custom_factory was depended upon by service
jboss.thread.executor.bounded_queue
{noformat}
This seems to be fine. However upon subsequent requests to the thread subsystem,
you'll get the following on the server side:
This is what you get on the server side:
{noformat}
13:13:03,525 ERROR [org.jboss.as.controller.management-operation]
(HttpManagementService-threads - 15) JBAS014612: Operation ("read-attribute")
failed - address: ([
("subsystem" => "threads"),
("bounded-queue-thread-pool" => "bounded_queue")
]): java.lang.IllegalStateException: JBAS012459: The executor service hasn't been
initialized.
at
org.jboss.as.threads.BoundedQueueThreadPoolService.getValue(BoundedQueueThreadPoolService.java:88)
at
org.jboss.as.threads.BoundedQueueThreadPoolService.getRejectedCount(BoundedQueueThreadPoolService.java:148)
at
org.jboss.as.threads.BoundedQueueThreadPoolMetricsHandler.setResult(BoundedQueueThreadPoolMetricsHandler.java:58)
at
org.jboss.as.threads.ThreadPoolMetricsHandler.executeRuntimeStep(ThreadPoolMetricsHandler.java:68)
at
org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:319)
at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:225)
at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:232)
at
org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
at
org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
at
org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[classes.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[classes.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.0.0.GA.jar:2.0.0.GA]
{noformat}
was (Author: heiko.braun):
This is what you get on the server side:
{noformat}
13:13:03,525 ERROR [org.jboss.as.controller.management-operation]
(HttpManagementService-threads - 15) JBAS014612: Operation ("read-attribute")
failed - address: ([
("subsystem" => "threads"),
("bounded-queue-thread-pool" => "bounded_queue")
]): java.lang.IllegalStateException: JBAS012459: The executor service hasn't been
initialized.
at
org.jboss.as.threads.BoundedQueueThreadPoolService.getValue(BoundedQueueThreadPoolService.java:88)
at
org.jboss.as.threads.BoundedQueueThreadPoolService.getRejectedCount(BoundedQueueThreadPoolService.java:148)
at
org.jboss.as.threads.BoundedQueueThreadPoolMetricsHandler.setResult(BoundedQueueThreadPoolMetricsHandler.java:58)
at
org.jboss.as.threads.ThreadPoolMetricsHandler.executeRuntimeStep(ThreadPoolMetricsHandler.java:68)
at
org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299)
[jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at
org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:319)
at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:225)
at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:232)
at
org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
at
org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
at
org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54)
at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[classes.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[classes.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.0.0.GA.jar:2.0.0.GA]
{noformat}
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:30 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-3446:
----------------------------------
maybe you did not reload the server config ("process-state" =>
"reload-required")?
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
6:34 a.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3446:
-----------------------------------
Ah, now I see what you're talking about Heiko. That's the error you get later
because the management model is now corrupted. But we should instead get an error when
you first try to remove the factory. That way the management model will never get into
that broken state.
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:49 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-3446:
-----------------------------
Comment: was deleted
(was: That's odd. I still get no error at all.
{noformat}
/subsystem=threads/queueless-thread-pool=myqueless/:add(max-threads=1)
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
/subsystem=threads/thread-factory=myfactory/:add
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
/subsystem=threads/queueless-thread-pool=myqueless/:write-attribute(name=thread-factory,value=myfactory)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
/subsystem=threads/thread-factory=myfactory/:remove
{
"outcome" => "success",
"response-headers" => {"process-state" =>
"reload-required"}
}
{noformat})
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:49 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-3446:
----------------------------------
Here's the updated list of commands that produce the error:
{noformat}
/subsystem=threads/queueless-thread-pool=myqueless:add(max-threads=1)
/subsystem=threads/thread-factory=myfactory:add
/subsystem=threads/queueless-thread-pool=myqueless:write-attribute(name=thread-factory,value=myfactory)
:reload
/subsystem=threads/thread-factory=myfactory:remove
{noformat}
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:51 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-3446:
-----------------------------
Comment: was deleted
(was: maybe you did not reload the server config ("process-state" =>
"reload-required")?)
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:03 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3446:
---------------------------------------
Thanks. More simply (avoiding the reload) this shows it:
[standalone@localhost:9999 /] /subsystem=threads/thread-factory=myfactory:add
{"outcome" => "success"}
[standalone@localhost:9999 /]
/subsystem=threads/queueless-thread-pool=myqueless:add(max-threads=1,thread-factory=myfactory)
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=threads/thread-factory=myfactory:remove
{
"outcome" => "failed",
"failure-description" => "JBAS014762: Removing services has lead to
unsatisfied dependencies:
Service jboss.thread.factory.myfactory was depended upon by service
jboss.thread.executor.myqueless",
"rolled-back" => true
}
The problem is an NPE during the execution of the rollback.
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:09 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry edited comment on AS7-3446 at 4/26/12 3:08 PM:
----------------------------------------------------------------
Thanks. More simply (avoiding the reload) this shows it:
{noformat}
[standalone@localhost:9999 /] /subsystem=threads/thread-factory=myfactory:add
{"outcome" => "success"}
[standalone@localhost:9999 /]
/subsystem=threads/queueless-thread-pool=myqueless:add(max-threads=1,thread-factory=myfactory)
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=threads/thread-factory=myfactory:remove
{
"outcome" => "failed",
"failure-description" => "JBAS014762: Removing services has lead to
unsatisfied dependencies:
Service jboss.thread.factory.myfactory was depended upon by service
jboss.thread.executor.myqueless",
"rolled-back" => true
}
{noformat}
The problem is an NPE during the execution of the rollback.
was (Author: brian.stansberry):
Thanks. More simply (avoiding the reload) this shows it:
[standalone@localhost:9999 /] /subsystem=threads/thread-factory=myfactory:add
{"outcome" => "success"}
[standalone@localhost:9999 /]
/subsystem=threads/queueless-thread-pool=myqueless:add(max-threads=1,thread-factory=myfactory)
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=threads/thread-factory=myfactory:remove
{
"outcome" => "failed",
"failure-description" => "JBAS014762: Removing services has lead to
unsatisfied dependencies:
Service jboss.thread.factory.myfactory was depended upon by service
jboss.thread.executor.myqueless",
"rolled-back" => true
}
The problem is an NPE during the execution of the rollback.
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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:06 p.m.
[
https://issues.jboss.org/browse/AS7-3446?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-3446.
-----------------------------------
Resolution: Done
If you remove a thread factory when the factory is assigned to a
pool, you get strange errors.
----------------------------------------------------------------------------------------------
Key: AS7-3446
URL: https://issues.jboss.org/browse/AS7-3446
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Delete a thread factory that is still assigned to a thread pool. You get a message that
just says, "undefined".
--
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
5192
days inactive
5284
days old
21 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Heiko Braun (JIRA)
-
Jason Greene (JIRA)
-
Stan Silvert (JIRA)