[JBoss JIRA] (WFLY-4847) STOMP logging does not work
by Ville Skyttä (JIRA)
[ https://issues.jboss.org/browse/WFLY-4847?page=com.atlassian.jira.plugin.... ]
Ville Skyttä updated WFLY-4847:
-------------------------------
Description:
STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean connection close.
Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
was:
STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean shutdown.
Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
> STOMP logging does not work
> ---------------------------
>
> Key: WFLY-4847
> URL: https://issues.jboss.org/browse/WFLY-4847
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 9.0.0.CR2
> Reporter: Ville Skyttä
> Assignee: Jason Greene
>
> STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean connection close.
> Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4847) STOMP logging does not work
by Ville Skyttä (JIRA)
Ville Skyttä created WFLY-4847:
----------------------------------
Summary: STOMP logging does not work
Key: WFLY-4847
URL: https://issues.jboss.org/browse/WFLY-4847
Project: WildFly
Issue Type: Bug
Affects Versions: 9.0.0.CR2
Reporter: Ville Skyttä
Assignee: Jason Greene
STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean shutdown.
Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFCORE-785) Improve capability related error messages
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-785?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-785:
------------------------------------
Fix Version/s: 2.0.0.Beta1
(was: 2.0.0.CR1)
> Improve capability related error messages
> -----------------------------------------
>
> Key: WFCORE-785
> URL: https://issues.jboss.org/browse/WFCORE-785
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 2.0.0.Beta1
>
>
> When operation handlers request non-existent capabilities, the error messages aren't particularly helpful. For example:
> /"WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.data-source.invalid' is unknown."
> This is largely because it's the CapabilityRegistry that throws the exceptions, and it doesn't have much context about why the capability is needed to use in a better error message.
> Likely solutions are:
> 1) If CapabilityRegistryImpl has more context than is being used, look into using it.
> 2) Provide more context to CapabilityRegistry (I don't much like this one; providing parameters to a call only for use in a failure message is smelly to me.)
> 3) Use a custom exception type when the capability is missing, instead of ISE, and have OperationContextImpl catch that and add contextual information.
> I expect 3) is the likely solution.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFCORE-785) Improve capability related error messages
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-785:
---------------------------------------
Summary: Improve capability related error messages
Key: WFCORE-785
URL: https://issues.jboss.org/browse/WFCORE-785
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 2.0.0.CR1
When operation handlers request non-existent capabilities, the error messages aren't particularly helpful. For example:
/"WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.data-source.invalid' is unknown."
This is largely because it's the CapabilityRegistry that throws the exceptions, and it doesn't have much context about why the capability is needed to use in a better error message.
Likely solutions are:
1) If CapabilityRegistryImpl has more context than is being used, look into using it.
2) Provide more context to CapabilityRegistry (I don't much like this one; providing parameters to a call only for use in a failure message is smelly to me.)
3) Use a custom exception type when the capability is missing, instead of ISE, and have OperationContextImpl catch that and add contextual information.
I expect 3) is the likely solution.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-462) Eliminate the threads subsystem
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-462?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar resolved WFLY-462.
------------------------------
Fix Version/s: 10.0.0.Alpha4
9.0.0.CR2
(was: 10.0.0.Beta1)
Resolution: Done
Threads subsystem was changed to only run in domain controller to allow support for legacy host controllers management.
there ware additional steps done to make it easier for resources from threads subsystem to be easier reused in other parts of the server
> Eliminate the threads subsystem
> -------------------------------
>
> Key: WFLY-462
> URL: https://issues.jboss.org/browse/WFLY-462
> Project: WildFly
> Issue Type: Task
> Reporter: David Lloyd
> Assignee: Tomaz Cerar
> Fix For: 10.0.0.Alpha4, 9.0.0.CR2
>
>
> The threads subsystem should be eliminated, and instead the individual consuming subsystems should utilize common code from the jboss-as-threads module to define and manage thread pools within their own configuration models.
> Subtasks for affected subsystems.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4846) Unable to create vault
by Sören Dierkes (JIRA)
[ https://issues.jboss.org/browse/WFLY-4846?page=com.atlassian.jira.plugin.... ]
Sören Dierkes commented on WFLY-4846:
-------------------------------------
I found a "resolution". If the storepass is EQUAL to the keypass it works.
But I guess it ist he wrong place anyways and can be closed/moved.
> Unable to create vault
> ----------------------
>
> Key: WFLY-4846
> URL: https://issues.jboss.org/browse/WFLY-4846
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 9.0.0.CR2
> Reporter: Sören Dierkes
> Assignee: Darran Lofthouse
>
> I was unable to create a vault with the current release.
> The last version I've tried and which works was 8.2.0 with Java 8
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFCORE-784) [PATCH] fix 2 bugs in bin/standalone.sh
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-784?page=com.atlassian.jira.plugin... ]
Tomaz Cerar moved WFLY-4297 to WFCORE-784:
------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-784 (was: WFLY-4297)
Component/s: Scripts
(was: Scripts)
> [PATCH] fix 2 bugs in bin/standalone.sh
> ---------------------------------------
>
> Key: WFCORE-784
> URL: https://issues.jboss.org/browse/WFCORE-784
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Martin Petricek
> Assignee: Tomaz Cerar
> Attachments: bin-fix.patch
>
>
> bin/standalone.sh does not use "shift" correctly when parsing commandline option, failing with "bin/standalone.sh: 34: shift: can't shift that many" if "--debug" without a parameter is used on dash (default shell in debian)
> Second issue is that the script does not handle correctly situation when CDPATH environment variable is set, failing completely.
> Attaching patch that fixes both these issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (ELY-218) Logical RoleMapper Implementation(s)
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-218?page=com.atlassian.jira.plugin.sy... ]
David Lloyd resolved ELY-218.
-----------------------------
Resolution: Done
> Logical RoleMapper Implementation(s)
> ------------------------------------
>
> Key: ELY-218
> URL: https://issues.jboss.org/browse/ELY-218
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Utils
> Reporter: Darran Lofthouse
> Assignee: David Lloyd
> Fix For: 1.0.0.Alpha2
>
>
> In addition to the current role mapper implementation it would be useful to have implementation(s) that can handle logical operations i.e. and, or, xor.
> Not sure at this point if it makes sense for this to be single implementations or a single mapper that can be provided a set of operations to perform.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4846) Unable to create vault
by Sören Dierkes (JIRA)
[ https://issues.jboss.org/browse/WFLY-4846?page=com.atlassian.jira.plugin.... ]
Sören Dierkes updated WFLY-4846:
--------------------------------
Description:
I was unable to create a vault with the current release.
The last version I've tried and which works was 8.2.0 with Java 8
was:
I was unable to create a vault with the current release.
The last version I've tried and which works was 8.2.0.
> Unable to create vault
> ----------------------
>
> Key: WFLY-4846
> URL: https://issues.jboss.org/browse/WFLY-4846
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 9.0.0.CR2
> Reporter: Sören Dierkes
> Assignee: Darran Lofthouse
>
> I was unable to create a vault with the current release.
> The last version I've tried and which works was 8.2.0 with Java 8
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months