[JBoss JIRA] (WFLY-12642) Error when maintaining Datasources & Drivers via Console
by Harald Pehl (Jira)
[ https://issues.jboss.org/browse/WFLY-12642?page=com.atlassian.jira.plugin... ]
Harald Pehl resolved WFLY-12642.
--------------------------------
Resolution: Done
Fixed by https://github.com/hal/console/commit/3816a13bc8e71071a54fe9a873896d37d48...
> Error when maintaining Datasources & Drivers via Console
> --------------------------------------------------------
>
> Key: WFLY-12642
> URL: https://issues.jboss.org/browse/WFLY-12642
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 18.0.0.Final
> Environment: Apache Maven 3.6.0
> Maven home: /usr/share/maven
> Java version: 13, vendor: Ubuntu, runtime: /usr/lib/jvm/java-13-openjdk-amd64
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "5.0.0-31-generic", arch: "amd64", family: "unix"
> Reporter: Wolfgang Mayer
> Assignee: Harald Pehl
> Priority: Major
> Attachments: Console_version.png, ErrorMessage.png
>
>
> When opening 'Datasources & Drivers -> JDBC Drivers' an message is popping up saying that an internal error occured with Details "newValue is null"
> After clicking the "+" to add a JDBC Driver I can add the JDBC driver indeed but the drivers are not showing up in the console.
> When opening 'Datasources & Drivers -> Datasources' the datasources are listed correctly. But when trying to add another Datasource the same internal message is popping up and it ist not possible to add the Datasouce via Console
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning
by Tomas Terem (Jira)
[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ]
Tomas Terem updated WFWIP-269:
------------------------------
Priority: Blocker (was: Major)
> Colon in a header name doesn't show a warning
> ---------------------------------------------
>
> Key: WFWIP-269
> URL: https://issues.jboss.org/browse/WFWIP-269
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Execute:
> {code:java}
> /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
> {code}
> Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Of course, colon can't be part of the header name, but I think that users should at least see a warning describing this behaviour.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning
by Tomas Terem (Jira)
Tomas Terem created WFWIP-269:
---------------------------------
Summary: Colon in a header name doesn't show a warning
Key: WFWIP-269
URL: https://issues.jboss.org/browse/WFWIP-269
Project: WildFly WIP
Issue Type: Bug
Reporter: Tomas Terem
Assignee: Darran Lofthouse
Execute:
{code:java}
/core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
{code}
Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Of course, colon can't be part of the header name, but I think that users should at least see a warning describing this behaviour.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning
by Tomas Terem (Jira)
[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ]
Tomas Terem updated WFWIP-269:
------------------------------
Labels: management (was: )
> Colon in a header name doesn't show a warning
> ---------------------------------------------
>
> Key: WFWIP-269
> URL: https://issues.jboss.org/browse/WFWIP-269
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Major
> Labels: management
>
> Execute:
> {code:java}
> /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}])
> {code}
> Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Of course, colon can't be part of the header name, but I think that users should at least see a warning describing this behaviour.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-268) Specifying empty list of constant-headers causes fatal error
by Tomas Terem (Jira)
Tomas Terem created WFWIP-268:
---------------------------------
Summary: Specifying empty list of constant-headers causes fatal error
Key: WFWIP-268
URL: https://issues.jboss.org/browse/WFWIP-268
Project: WildFly WIP
Issue Type: Bug
Reporter: Tomas Terem
Assignee: Darran Lofthouse
Specifying empty list of constant-headers causes fatal error.
{code:java}
17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: "WFLYCTL0155: 'headers' may not be null"
17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months