[JBoss JIRA] (WFLY-5746) Dropdown button of admin console is not working properly on Chrome( work ok on Firefox)
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-5746?page=com.atlassian.jira.plugin.... ]
Claudio Miranda closed WFLY-5746.
---------------------------------
Assignee: Claudio Miranda (was: Heiko Braun)
Resolution: Cannot Reproduce Bug
Cannot reproduce the problem, if you feel this is wrong reopen please.
> Dropdown button of admin console is not working properly on Chrome( work ok on Firefox)
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-5746
> URL: https://issues.jboss.org/browse/WFLY-5746
> Project: WildFly
> Issue Type: Enhancement
> Components: Web Console
> Affects Versions: 10.0.0.CR4
> Reporter: Sun Chanras
> Assignee: Claudio Miranda
> Priority: Minor
>
> dropdown button of wildfly admin console is not working properly, though it work good on FireFox.
> I found it very difficult to click on dropdown button to upload , remove ,deploy etc.
> But the problem does not exist on Firefox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-6024) The management console cannot display more than 5 runtime datasources
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-6024?page=com.atlassian.jira.plugin.... ]
Claudio Miranda closed WFLY-6024.
---------------------------------
Assignee: Claudio Miranda (was: Heiko Braun)
Resolution: Cannot Reproduce Bug
As the reporter said in the comment, it is working.
> The management console cannot display more than 5 runtime datasources
> ---------------------------------------------------------------------
>
> Key: WFLY-6024
> URL: https://issues.jboss.org/browse/WFLY-6024
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 9.0.2.Final
> Reporter: Laurent Pereira
> Assignee: Claudio Miranda
> Priority: Minor
> Attachments: wildfly-console-runtime-datasource.PNG
>
>
> From the runtime tab of the management console : I cannot display more than 5 datasources although more than 6 have been defined.
> As a consequence, it is not possible to manage the missing datasources.
> Sample screenshot :
> !wildfly-console-runtime-datasource.PNG|thumbnail!
> 5 datasources of 7 are displayed. 2 datasources are always hidden. No scroll available.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-6607) Broadcast/Discovery group is possible to create with just a name
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-6607?page=com.atlassian.jira.plugin.... ]
Claudio Miranda commented on WFLY-6607:
---------------------------------------
I removed the Web Console from component list, as I fixed them in HAL, however CLI accepts to create the resource with just a name.
> Broadcast/Discovery group is possible to create with just a name
> ----------------------------------------------------------------
>
> Key: WFLY-6607
> URL: https://issues.jboss.org/browse/WFLY-6607
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: Chao Wang
>
> When defining new broadcast-group in Configuration: Subsystems Subsystem: Messaging - ActiveMQ Messaging Provider: default
> user must define name, at least one connector and then either socket-binding or jgroups-channel-name (not both of them, just one)
> At this moment it's possible to create broadcast group with just a name which is wrong.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-6607) Broadcast/Discovery group is possible to create with just a name
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-6607?page=com.atlassian.jira.plugin.... ]
Claudio Miranda updated WFLY-6607:
----------------------------------
Component/s: (was: Web Console)
> Broadcast/Discovery group is possible to create with just a name
> ----------------------------------------------------------------
>
> Key: WFLY-6607
> URL: https://issues.jboss.org/browse/WFLY-6607
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: Chao Wang
>
> When defining new broadcast-group in Configuration: Subsystems Subsystem: Messaging - ActiveMQ Messaging Provider: default
> user must define name, at least one connector and then either socket-binding or jgroups-channel-name (not both of them, just one)
> At this moment it's possible to create broadcast group with just a name which is wrong.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8389) Settings modcluster/ssl-context conflict issue
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/WFLY-8389?page=com.atlassian.jira.plugin.... ]
Michal Petrov moved JBEAP-9619 to WFLY-8389:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8389 (was: JBEAP-9619)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: mod_cluster
(was: mod_cluster)
(was: User Experience)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR12)
(was: 7.1.0.DR13)
> Settings modcluster/ssl-context conflict issue
> ----------------------------------------------
>
> Key: WFLY-8389
> URL: https://issues.jboss.org/browse/WFLY-8389
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 11.0.0.Alpha1
> Reporter: Michal Petrov
> Assignee: Radoslav Husar
>
> Setting ssl-context in modcluster subsystem
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=ssl-context,value=clientSSLContext)
> {noformat}
> when ssl is configured
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration/ssl=configuration
> {noformat}
> shouldn't end as success
> {noformat}
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> {noformat}
> as {noformat}reload{noformat}
> triggers exception in server log
> {noformat}
> 2017-03-13 10:13:45,394 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.IllegalStateException: WFLYMODCLS0020: Only one of 'ssl-context' attribute or 'ssl' resource can be defined!
> at org.wildfly.extension.mod_cluster.ModClusterConfigurationServiceBuilder.configure(ModClusterConfigurationServiceBuilder.java:225)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemAdd.performBoottime(ModClusterSubsystemAdd.java:80)
> at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performBoottime(AbstractBoottimeAddStepHandler.java:157)
> at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performRuntime(AbstractBoottimeAddStepHandler.java:116)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:979)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:722)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:441)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:381)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> User shouldn't be allowed to set ssl-context in this scenario or be warned.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8389) Settings modcluster/ssl-context conflict issue
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/WFLY-8389?page=com.atlassian.jira.plugin.... ]
Michal Petrov reassigned WFLY-8389:
-----------------------------------
Assignee: Michal Petrov (was: Radoslav Husar)
> Settings modcluster/ssl-context conflict issue
> ----------------------------------------------
>
> Key: WFLY-8389
> URL: https://issues.jboss.org/browse/WFLY-8389
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 11.0.0.Alpha1
> Reporter: Michal Petrov
> Assignee: Michal Petrov
>
> Setting ssl-context in modcluster subsystem
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=ssl-context,value=clientSSLContext)
> {noformat}
> when ssl is configured
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration/ssl=configuration
> {noformat}
> shouldn't end as success
> {noformat}
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> {noformat}
> as {noformat}reload{noformat}
> triggers exception in server log
> {noformat}
> 2017-03-13 10:13:45,394 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.IllegalStateException: WFLYMODCLS0020: Only one of 'ssl-context' attribute or 'ssl' resource can be defined!
> at org.wildfly.extension.mod_cluster.ModClusterConfigurationServiceBuilder.configure(ModClusterConfigurationServiceBuilder.java:225)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemAdd.performBoottime(ModClusterSubsystemAdd.java:80)
> at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performBoottime(AbstractBoottimeAddStepHandler.java:157)
> at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performRuntime(AbstractBoottimeAddStepHandler.java:116)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:979)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:722)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:441)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:381)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> User shouldn't be allowed to set ssl-context in this scenario or be warned.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (HAWKULARQE-71) Test Hawkular Java Agent
by Hayk Hovsepyan (JIRA)
Hayk Hovsepyan created HAWKULARQE-71:
----------------------------------------
Summary: Test Hawkular Java Agent
Key: HAWKULARQE-71
URL: https://issues.jboss.org/browse/HAWKULARQE-71
Project: Hawkular QE
Issue Type: Task
Reporter: Hayk Hovsepyan
Assignee: mfoley user
Priority: Minor
There is a new Java Agent (HJA) that you can run in any JVM (including
but not limited to EAP-based projects). You do so by passing in a
"-javaagent" command line option to your JVM (e.g. java
-javaagent=hawkular-javaagent.jar=config=config.yaml -jar my-app.jar
...yadda...). There are two additional properties you must set in
standalone.conf if you want to run it inside an EAP JVM. The README will
have the details.
This new HJA is configured with a yaml file that largely mimics all the
standalone.xml data that HWFA has. There is no ${x} support in the YAML
file right now.
This new HJA can talk to any EAP or WildFly server over the DMR management
API. It can do deployments to your EAP/WildFly servers and monitoring of
EAP/WildFly subsystems just like HWFA can.
This new HJA can talk to any JMX server just like HWFA can (it will talk to
the local MBeanServer or, if remotely monitoring a JMX server, it will talk
to it over Jolokia/REST API).
This new HJA can NOT run directly inside of a Host Controller due to
https://issues.jboss.org/browse/WFCORE-2526 - however, you can run HJA
externally in its own JVM (e.g. java -jar hawkular-javaagent.jar
config=config.yaml) and have its config.yaml point to a remote Host
Controller and you'll get the same functionality.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-945) User names in Elytron FileSystemRealm are not case sensitive on Windows
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/ELY-945?page=com.atlassian.jira.plugin.sy... ]
Bartosz Baranowski commented on ELY-945:
----------------------------------------
Given that implementation relies on Path(Path p = p.resolve(next)), this is JDK bug. Not much can be done aside of lower casing everything.
> User names in Elytron FileSystemRealm are not case sensitive on Windows
> -----------------------------------------------------------------------
>
> Key: ELY-945
> URL: https://issues.jboss.org/browse/ELY-945
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Josef Cacek
> Assignee: Bartosz Baranowski
> Priority: Blocker
>
> User names are case sensitive on Linux but not on Windows when using the Elytron {{FileSystemSecurityRealm}}
> This is IMO a security issue. And it also affects platform certifications.
> If this is by any chance an expected behavior, then it has to be emphasized in documentation and in the domain model too (description of file-system-realm)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month