[JBoss JIRA] (WFLY-7456) Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-7456?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-7456.
-----------------------------
Resolution: Rejected
> Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7456
> URL: https://issues.jboss.org/browse/WFLY-7456
> Project: WildFly
> Issue Type: Bug
> Components: Mail
> Affects Versions: 10.1.0.Final
> Reporter: Radim Hatlapatka
> Assignee: Tomaz Cerar
> Priority: Optional
> Labels: user_experience
>
> There is inconsistent description for custom server when reading it as child description => {{/subsystem=mail/mail-session=default:read-resource-description}}, where it is {{Custom mail server configuration}} and when reading its description directly => {{/subsystem=mail/mail-session=default/custom=xxx:read-resource-description}}, where it is {{Mail session server}}
> This doesn't look nice from UX PoV, where I believe these values should be the same.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8478) Setting elytron ssl-context on undertow without reload
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8478?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-8478.
-----------------------------
Resolution: Rejected
You need to pass {allow-resource-service-restart=true} header to operation if you want to have runtime change without reload
> Setting elytron ssl-context on undertow without reload
> ------------------------------------------------------
>
> Key: WFLY-8478
> URL: https://issues.jboss.org/browse/WFLY-8478
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Reporter: Martin Choma
> Assignee: Tomaz Cerar
> Labels: user_experience
>
> Please, allow setting of elytron ssl-context on undertow without reload.
> {code}
> [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=server)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8478) Setting elytron ssl-context on undertow without reload
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8478?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar moved WFCORE-2448 to WFLY-8478:
-------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-8478 (was: WFCORE-2448)
Component/s: Security
Web (Undertow)
(was: Security)
Affects Version/s: (was: 3.0.0.Beta7)
> Setting elytron ssl-context on undertow without reload
> ------------------------------------------------------
>
> Key: WFLY-8478
> URL: https://issues.jboss.org/browse/WFLY-8478
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Reporter: Martin Choma
> Assignee: Tomaz Cerar
> Labels: user_experience
>
> Please, allow setting of elytron ssl-context on undertow without reload.
> {code}
> [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=server)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBJCA-1341) Account for additional DB2 FATAL connection errors
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1341?page=com.atlassian.jira.plugin... ]
Stefano Maestri commented on JBJCA-1341:
----------------------------------------
[~jolee] yup it's what I've written. Maybe is not so easy to read because I've written all option on the same line just separating them by a column. Editing to make it more readable
> Account for additional DB2 FATAL connection errors
> --------------------------------------------------
>
> Key: JBJCA-1341
> URL: https://issues.jboss.org/browse/JBJCA-1341
> Project: IronJacamar
> Issue Type: Enhancement
> Components: Validator
> Reporter: Ingo Weiss
> Assignee: Ingo Weiss
> Original Estimate: 2 days
> Time Spent: 2 days
> Remaining Estimate: 0 minutes
>
> Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException. Not all -99999 errors are fatal. For those variations that are known to be fatal, a check should be added to treat as such.
> One example would be the -99999 error that indicates "Connection is closed"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years