[JBoss JIRA] (WFLY-10861) MP Health - security enabled, no user yed added, user get info about adding user to access web console, HTTP code is 200, should be 500
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-10861?page=com.atlassian.jira.plugin... ]
Kabir Khan reassigned WFLY-10861:
---------------------------------
Assignee: Kabir Khan (was: Jeff Mesnil)
> MP Health - security enabled, no user yed added, user get info about adding user to access web console, HTTP code is 200, should be 500
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10861
> URL: https://issues.jboss.org/browse/WFLY-10861
> Project: WildFly
> Issue Type: Bug
> Components: Management, MP Health
> Reporter: Rostislav Svoboda
> Assignee: Kabir Khan
> Priority: Blocker
>
> I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server
> Note: I didn't add user via {{bin/add-user.sh}}
> ----
> Kabir edit: the full command is:
> /subsystem=microprofile-health-smallrye:write-attribute(name=security-enabled,value=true)
> ----
> When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console:
> {code}
> <h3>Your WildFly Application Server is running.</h3>
> <p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able
> to access the admin console.</p>
> <p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of
> your WildFly installation and enter the requested information.</p>
> {code}
> Can /health endpoint get customized response in case no mgmt user is defined on server side ?
> Current response can be little confusing if user is not yet so familiar with WildFly.
> I marked this as minor bug.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2888:
-------------------------------------
Thanks so much [~stetson.robinson]!! [~karreiro] this expand collapse view will be in the next rev of the click-thru so you'll have a live example of the interaction. :)
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Stetson Robinson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-2888 at 8/20/18 1:40 PM:
-------------------------------------------------------------------
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be *Simple* or *Structured* data types:
• *Simple* data types have only a name and a type assignment. Example: "Age (Number)"
• *Structured* data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
I should add also that we always want to specify "DMN decision tables", which are distinct (in supported features) from the guided or uploaded decision tables used elsewhere in the workbench. I know we know, but just a reminder for any communication to the user, to avoid confusion.
was (Author: stetson.robinson):
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be Simple or Structured data types:
• Simple data types have only a name and a type assignment. Example: "Age (Number)"
• Structured data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Stetson Robinson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-2888:
------------------------------------------
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be Simple or Structured data types:
• Simple data types have only a name and a type assignment. Example: "Age (Number)"
• Structured data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1624) BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-1624?page=com.atlassian.jira.plugin.s... ]
Farah Juma closed ELY-1624.
---------------------------
> BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1624
> URL: https://issues.jboss.org/browse/ELY-1624
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
> Attachments: eap_server.log, jboss-cli.log, keystore.bcfks, standalone.xml
>
>
> I am trying to connect from jboss-cli.sh to EAP server. Server and client run with BC FIPS.
> {code:java|title=jboss-cli.log}
> 11:48:08,992 TRACE [org.jboss.remoting.remote] Attempting to connect to "remote+https://127.0.0.1:9993" with options {org.xnio.Options.SSL_STARTTLS=>false,org.xnio.Options.SSL_ENABLED=>true}
> 11:48:14,005 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:304)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 127.0.0.1:9993
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1447)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1226)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1394)
> ... 9 more
> Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:192)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:126)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> {code}
> It works when I use
> - non-FIPS java for CLI and FIPS java for server when connecting to secured 9993 port
> - FIPS java for CLI and non-FIPS java for server when connecting to unsecured port 9990
> Here I get getting over ELY-1621 and ELY-1622
> I would appreciate any hint for way of investigation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10835) Connection factory with discovery-group doesn't work
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10835?page=com.atlassian.jira.plugin... ]
Paul Ferraro edited comment on WFLY-10835 at 8/20/18 1:36 PM:
--------------------------------------------------------------
This doesn't look like a new issue. Since at least EAP6, the BroadcastEndpointFactory implementation used by the servers has not been an instance of JGroupsFileBroadcastEndpointFactory nor JGroupsPropertiesBroadcastEndpointFactory. Consequently, this would always have thrown a NotSerializableException.
>From a design perspective, I would question the sensibility of using JGroups for remote client discovery, as it would be very unorthodox for remote clients to become members of a JGroups cluster intended to be composed of EAP servers.
was (Author: pferraro):
This doesn't look like a new issue. Since at least EAP6, the BroadcastEndpointFactory implementation used by the servers has never been JGroupsFileBroadcastEndpointFactory nor JGroupsPropertiesBroadcastEndpointFactory. Consequently, this would always have thrown a NotSerializableException.
>From a design perspective, I would question the sensibility of using JGroups for remote client discovery, as it would be very unorthodox for remote clients to become members of a JGroups cluster intended to be composed of EAP servers.
> Connection factory with discovery-group doesn't work
> ----------------------------------------------------
>
> Key: WFLY-10835
> URL: https://issues.jboss.org/browse/WFLY-10835
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Final
> Reporter: Martin Styk
> Assignee: ehsavoie Hugonnet
> Priority: Critical
> Attachments: firefox.desktop, server-trace.log, standalone-full-ha.xml
>
>
> Jms client can not use remote connection factory defined as follows
> {noformat}
> <discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" discovery-group="dg-group1" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
> {noformat}
> Following exception is thrown on client
> {noformat}
> Exception in thread "main" java.lang.RuntimeException: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at client.ProducerJms11.sendMessages(ProducerJms11.java:67)
> at client.Producer.run(Producer.java:34)
> at client.Producer.sendAllSync(Producer.java:25)
> at client.ProducerJms11.main(ProducerJms11.java:14)
> Caused by: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:261)
> at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
> at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
> at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
> at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
> at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at client.ProducerJms11.sendMessages(ProducerJms11.java:43)
> ... 3 more
> Caused by: java.io.EOFException: Read past end of file
> at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUnsignedByte(BlockUnmarshaller.java:258)
> at org.jboss.marshalling.river.BlockUnmarshaller.readInt(BlockUnmarshaller.java:296)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUTF(BlockUnmarshaller.java:326)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.readExternal(ActiveMQConnectionFactory.java:186)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1414)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
> ... 15 more
> Caused by: an exception which occurred:
> in object of type org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory
> {noformat}
> It fails on attempt to look up RemoteCF
> {noformat}
> ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup(ClientDefaults.CONNECTION_FACTORY);
> {noformat}
> Same scenario with connector works well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1624) BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-1624?page=com.atlassian.jira.plugin.s... ]
Farah Juma commented on ELY-1624:
---------------------------------
[~dlofthouse] We can close this one as a duplicate of XNIO-327.
> BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1624
> URL: https://issues.jboss.org/browse/ELY-1624
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
> Attachments: eap_server.log, jboss-cli.log, keystore.bcfks, standalone.xml
>
>
> I am trying to connect from jboss-cli.sh to EAP server. Server and client run with BC FIPS.
> {code:java|title=jboss-cli.log}
> 11:48:08,992 TRACE [org.jboss.remoting.remote] Attempting to connect to "remote+https://127.0.0.1:9993" with options {org.xnio.Options.SSL_STARTTLS=>false,org.xnio.Options.SSL_ENABLED=>true}
> 11:48:14,005 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:304)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 127.0.0.1:9993
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1447)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1226)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1394)
> ... 9 more
> Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:192)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:126)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> {code}
> It works when I use
> - non-FIPS java for CLI and FIPS java for server when connecting to secured 9993 port
> - FIPS java for CLI and non-FIPS java for server when connecting to unsecured port 9990
> Here I get getting over ELY-1621 and ELY-1622
> I would appreciate any hint for way of investigation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1624) BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-1624?page=com.atlassian.jira.plugin.s... ]
Farah Juma resolved ELY-1624.
-----------------------------
Resolution: Duplicate Issue
> BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1624
> URL: https://issues.jboss.org/browse/ELY-1624
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
> Attachments: eap_server.log, jboss-cli.log, keystore.bcfks, standalone.xml
>
>
> I am trying to connect from jboss-cli.sh to EAP server. Server and client run with BC FIPS.
> {code:java|title=jboss-cli.log}
> 11:48:08,992 TRACE [org.jboss.remoting.remote] Attempting to connect to "remote+https://127.0.0.1:9993" with options {org.xnio.Options.SSL_STARTTLS=>false,org.xnio.Options.SSL_ENABLED=>true}
> 11:48:14,005 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:304)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 127.0.0.1:9993
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1447)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1226)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1394)
> ... 9 more
> Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:192)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:126)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> {code}
> It works when I use
> - non-FIPS java for CLI and FIPS java for server when connecting to secured 9993 port
> - FIPS java for CLI and non-FIPS java for server when connecting to unsecured port 9990
> Here I get getting over ELY-1621 and ELY-1622
> I would appreciate any hint for way of investigation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1624) BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1624?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on ELY-1624:
---------------------------------------
Hi [~fjuma] as the fix for this was applied to XNIO do we still need an ELY issue?
> BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1624
> URL: https://issues.jboss.org/browse/ELY-1624
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
> Attachments: eap_server.log, jboss-cli.log, keystore.bcfks, standalone.xml
>
>
> I am trying to connect from jboss-cli.sh to EAP server. Server and client run with BC FIPS.
> {code:java|title=jboss-cli.log}
> 11:48:08,992 TRACE [org.jboss.remoting.remote] Attempting to connect to "remote+https://127.0.0.1:9993" with options {org.xnio.Options.SSL_STARTTLS=>false,org.xnio.Options.SSL_ENABLED=>true}
> 11:48:14,005 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:304)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 127.0.0.1:9993
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1447)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1226)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1394)
> ... 9 more
> Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:192)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:126)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> {code}
> It works when I use
> - non-FIPS java for CLI and FIPS java for server when connecting to secured 9993 port
> - FIPS java for CLI and non-FIPS java for server when connecting to unsecured port 9990
> Here I get getting over ELY-1621 and ELY-1622
> I would appreciate any hint for way of investigation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months