Back to bug 1024109
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brian Stansberry | 2013-10-29 03:27:26 UTC | Status | NEW | POST |
| Ladislav Thon | 2013-10-31 14:56:22 UTC | CC | lthon | |
| Ladislav Thon | 2013-10-31 14:57:32 UTC | Link ID | JBoss Issue Tracker WFLY-2370 | |
| Brian Stansberry | 2013-11-20 21:28:06 UTC | Doc Text | Cause: A host controller is able to receive management requests from users before its server management system is fully started. Consequence: Executing a request to check the status of a server immediately after starting a host controller can result in a failure response to the request and a NullPointerException in the host controller log. An example CLI request would be: /host=thehost/server-config=the-server:read-attribute(name=status) This problem can only happen within a very narrow window during boot, so typically some sort of automation would be involved; e.g. a script that starts the host controller and then immediately invokes the CLI. Workaround: Include error handling logic in any automated logic that attempts to read server information immediately after host controller launch. Some sort of polling logic would typically be needed in any case to account for the fact that the results of any request will be changing as the server starts. A slight delay (a second or two at most) before attempting to read servers will help avoid the NPE in the logs. Result: |
|
| Brian Stansberry | 2013-11-20 21:30:25 UTC | Doc Type | Bug Fix | Known Issue |
| Red Hat Bugzilla | 2013-11-20 21:30:25 UTC | Doc Type | Known Issue | Bug Fix |
| Brian Stansberry | 2013-11-20 21:30:53 UTC | Doc Type | Bug Fix | Known Issue |
| Red Hat Bugzilla | 2013-11-20 21:30:53 UTC | Doc Type | Known Issue | Bug Fix |
| Brian Stansberry | 2013-11-20 21:31:26 UTC | Doc Text | Cause: A host controller is able to receive management requests from users before its server management system is fully started. Consequence: Executing a request to check the status of a server immediately after starting a host controller can result in a failure response to the request and a NullPointerException in the host controller log. An example CLI request would be: /host=thehost/server-config=the-server:read-attribute(name=status) This problem can only happen within a very narrow window during boot, so typically some sort of automation would be involved; e.g. a script that starts the host controller and then immediately invokes the CLI. Workaround: Include error handling logic in any automated logic that attempts to read server information immediately after host controller launch. Some sort of polling logic would typically be needed in any case to account for the fact that the results of any request will be changing as the server starts. A slight delay (a second or two at most) before attempting to read servers will help avoid the NPE in the logs. Result: | Cause: A Host Controller is able to receive management requests from users before its server management system is fully started. Consequence: Executing a request to check the status of a server immediately after starting a host controller can result in a failure response to the request and a NullPointerException in the host controller log. An example CLI request would be: /host=thehost/server-config=the-server:read-attribute(name=status) This problem can only happen within a very narrow window during boot, so typically some sort of automation would be involved; e.g. a script that starts the host controller and then immediately invokes the CLI. Workaround: Include error handling logic in any automated logic that attempts to read server information immediately after host controller launch. Some sort of polling logic would typically be needed in any case to account for the fact that the results of any request will be changing as the server starts. A slight delay (a second or two at most) before attempting to read servers will help avoid the NPE in the logs. Result: |
| Doc Type | Bug Fix | Known Issue | ||
| Dana Mison | 2013-11-27 02:51:13 UTC | CC | dmison | |
| Doc Text | Cause: A Host Controller is able to receive management requests from users before its server management system is fully started. Consequence: Executing a request to check the status of a server immediately after starting a host controller can result in a failure response to the request and a NullPointerException in the host controller log. An example CLI request would be: /host=thehost/server-config=the-server:read-attribute(name=status) This problem can only happen within a very narrow window during boot, so typically some sort of automation would be involved; e.g. a script that starts the host controller and then immediately invokes the CLI. Workaround: Include error handling logic in any automated logic that attempts to read server information immediately after host controller launch. Some sort of polling logic would typically be needed in any case to account for the fact that the results of any request will be changing as the server starts. A slight delay (a second or two at most) before attempting to read servers will help avoid the NPE in the logs. Result: | Management requests sent to a Host Controller immediately after the Host Controller launches may fail with an exception of type NullPointerException. This is because there is a period of time between when the Host Controller becomes able to receive requests and when the server management system is fully started. This period of time is usually less than one to two seconds, but any requests received in that time will fail. This should only occur in automated environments, such as a script that starts the Host Controller and then immediately attempts to invoke a management operation. Currently, Red Hat recommends the following workaround for scripts or any other automation that attempts to perform management operations immediately after launching a Host Controller: 1. Include a slight delay (one or two seconds) to allow enough time for all of a Host Controller’s systems to start. 2. Include error handling logic. 3. Use polling logic to account for changing request results as a server launches. This will be fixed in a future release. |
||
| Dana Mison | 2013-11-27 02:52:31 UTC | Doc Text | Management requests sent to a Host Controller immediately after the Host Controller launches may fail with an exception of type NullPointerException. This is because there is a period of time between when the Host Controller becomes able to receive requests and when the server management system is fully started. This period of time is usually less than one to two seconds, but any requests received in that time will fail. This should only occur in automated environments, such as a script that starts the Host Controller and then immediately attempts to invoke a management operation. Currently, Red Hat recommends the following workaround for scripts or any other automation that attempts to perform management operations immediately after launching a Host Controller: 1. Include a slight delay (one or two seconds) to allow enough time for all of a Host Controller’s systems to start. 2. Include error handling logic. 3. Use polling logic to account for changing request results as a server launches. This will be fixed in a future release. | Management requests sent to a Host Controller immediately after the Host Controller launches may fail with an exception of type `NullPointerException`. This is because there is a period of time between when the Host Controller becomes able to receive requests and when the server management system is fully started. This period of time is usually less than one to two seconds, but any requests received in that time will fail. This should only occur in automated environments, such as a script that starts the Host Controller and then immediately attempts to invoke a management operation. Currently, Red Hat recommends the following workaround for scripts or any other automation that attempts to perform management operations immediately after launching a Host Controller: 1. Include a slight delay (one or two seconds) to allow enough time for all of a Host Controller’s systems to start. 2. Include error handling logic. 3. Use polling logic to account for changing request results as a server launches. This will be fixed in a future release. |
| Dana Mison | 2013-11-27 03:05:32 UTC | Doc Text | Management requests sent to a Host Controller immediately after the Host Controller launches may fail with an exception of type `NullPointerException`. This is because there is a period of time between when the Host Controller becomes able to receive requests and when the server management system is fully started. This period of time is usually less than one to two seconds, but any requests received in that time will fail. This should only occur in automated environments, such as a script that starts the Host Controller and then immediately attempts to invoke a management operation. Currently, Red Hat recommends the following workaround for scripts or any other automation that attempts to perform management operations immediately after launching a Host Controller: 1. Include a slight delay (one or two seconds) to allow enough time for all of a Host Controller’s systems to start. 2. Include error handling logic. 3. Use polling logic to account for changing request results as a server launches. This will be fixed in a future release. | Management requests sent to a Host Controller immediately after the Host Controller launches may fail with an exception of type `NullPointerException`. This is because there is a period of time between when the Host Controller becomes able to receive requests and when the server management system is fully started. This period of time is usually less than one second, but any requests received in that time will fail. This should only occur in automated environments, such as a script that starts the Host Controller and then immediately attempts to invoke a management operation on one of its servers. Currently, Red Hat recommends the following workaround for scripts or any other automation that attempts to perform management operations immediately after launching a Host Controller: 1. Include a slight delay (one or two seconds) to allow enough time for all of a Host Controller’s systems to start. 2. Include error handling logic. 3. Use polling logic to account for changing request results as a server launches. This will be fixed in a future release. |
| Josef Cacek | 2013-12-12 12:14:38 UTC | CC | jcacek | |
| Blocks | 953259 | |||
| Severity | unspecified | high | ||
| Brian Stansberry | 2013-12-12 14:46:04 UTC | Target Release | --- | EAP 6.3.0 |
| Josef Cacek | 2013-12-12 15:04:55 UTC | Blocks | 953259 | |
| mark yarborough | 2013-12-16 20:56:42 UTC | CC | myarboro | |
| Kabir Khan | 2013-12-18 16:59:18 UTC | CC | kkhan | |
| Target Milestone | --- | DR1 | ||
| Kabir Khan | 2013-12-19 14:30:12 UTC | Status | POST | MODIFIED |
| Kabir Khan | 2014-01-08 12:05:08 UTC | Target Milestone | DR1 | DR0 |
| mark yarborough | 2014-01-09 22:27:34 UTC | Blocks | 1041330 | |
| mark yarborough | 2014-01-09 22:28:24 UTC | Summary | NPE in DelegatingServerInventory | [CCC] (6.3) NPE in DelegatingServerInventory |
| Dana Mison | 2014-01-09 23:34:58 UTC | CC | dmison | |
| Paul Gier | 2014-02-11 23:53:57 UTC | Status | MODIFIED | ON_QA |
| Petr Kremensky | 2014-03-04 12:00:06 UTC | Status | ON_QA | VERIFIED |
| Lucas Costi | 2014-05-13 04:40:31 UTC | CC | lcosti | |
| Docs Contact | rdickens | lcosti | ||
| Doc Text | Management requests sent to a Host Controller immediately after the Host Controller launches may fail with an exception of type `NullPointerException`. This is because there is a period of time between when the Host Controller becomes able to receive requests and when the server management system is fully started. This period of time is usually less than one second, but any requests received in that time will fail. This should only occur in automated environments, such as a script that starts the Host Controller and then immediately attempts to invoke a management operation on one of its servers. Currently, Red Hat recommends the following workaround for scripts or any other automation that attempts to perform management operations immediately after launching a Host Controller: 1. Include a slight delay (one or two seconds) to allow enough time for all of a Host Controller’s systems to start. 2. Include error handling logic. 3. Use polling logic to account for changing request results as a server launches. This will be fixed in a future release. | Management requests sent to a Host Controller immediately after the Host Controller had launched may have failed with an exception of type `NullPointerException`. This was because there was a period of time between when the Host Controller was able to receive requests and when the server management system had fully started. This period of time was usually less than one second, but any requests received in that time would fail. This issue has been fixed in this release by making sure that a Host Controller will only receive requests once the server management system has fully started. As a result, there is no longer period of time where received requests will trigger a `NullPointerException` because the the server management system has not fully started. | ||
| Doc Type | Known Issue | Bug Fix | ||
| mark yarborough | 2014-06-28 15:25:26 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:25:26 UTC |
Back to bug 1024109