Back to bug 1017816
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ondrej Chaloupka | 2013-12-02 15:05:24 UTC | Assignee | tom.jenkinson | zfeng |
| Depends On | 1036739 | |||
| Ondrej Chaloupka | 2013-12-02 15:11:21 UTC | Doc Text | Cause: Configuration problem to generate UUID from socket id. Consequence: The configuration option is not usable under EAP 6.2.0. Fix: Result: The user needs to use default config option for UUID generation which is process identifier implementation. |
|
| Russell Dickenson | 2013-12-03 21:41:47 UTC | Doc Text | Cause: Configuration problem to generate UUID from socket id. Consequence: The configuration option is not usable under EAP 6.2.0. Fix: Result: The user needs to use default config option for UUID generation which is process identifier implementation. | When the process ID generation method is changed to process-id-socket-binding instead of process-id-uuid, an error message starting with the following text results: change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction subsystem ---- ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 44) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "JBAS014746: process-id-uuid may not be null" ---- The cause of this issue is that the handling of the configuration parameter is incorrect. This will be resolved in a future release. No workaround is possible, so the default method of process ID generation must be used. |
| Ondrej Chaloupka | 2013-12-06 13:35:04 UTC | CC | tom.jenkinson | |
| Status | NEW | CLOSED | ||
| Resolution | --- | DUPLICATE | ||
| Last Closed | 2013-12-06 08:35:04 UTC | |||
| Russell Dickenson | 2017-10-10 00:10:25 UTC | Docs Contact | rdickens |
Back to bug 1017816