[JBoss JIRA] (DROOLS-5185) Investigate unused dependencies of scenariossimulation-kogito-runitme
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5185?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5185:
--------------------------------
Sprint: 2020 Week 13-15 (from Mar 23)
> Investigate unused dependencies of scenariossimulation-kogito-runitme
> ---------------------------------------------------------------------
>
> Key: DROOLS-5185
> URL: https://issues.redhat.com/browse/DROOLS-5185
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.35.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> There are [1] declared for 'drools-wb-scenario-simulation-editor-kogito-runtime' module.
> Investigate if they can not be removed.
> [1]
> {code}
> [WARNING] org.uberfire:uberfire-message-console-client:jar:7.35.0-SNAPSHOT:provided
> [WARNING] org.kie.workbench.widgets:kie-wb-config-resource-widget:jar:7.35.0-SNAPSHOT:provided
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-11717) Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
by Marc Anthony Puca (Jira)
[ https://issues.redhat.com/browse/WFLY-11717?page=com.atlassian.jira.plugi... ]
Marc Anthony Puca edited comment on WFLY-11717 at 3/24/20 8:39 AM:
-------------------------------------------------------------------
Hi everyone, is there any progress on this, I am getting the same issue when I deploy my app on wildfly 19.0.0 final and jdk-11.0.6+10.
The warning occurs just after WELD print
{panel:title=}
12:37:11,206 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.1.3 (Final)
12:37:11,273 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 88) WFLYCLINF0002: Started client-mappings cache from ejb container
WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/D:/wildfly-19.0.0.Final/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone()
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory$1.run(AbstractProxyFactory.java:121)
at java.base/java.security.AccessController.doPrivileged(Native Method)
{panel}
Thanks
was (Author: marcanthony):
Hi everyone, is there any progress on this, I am getting the same issue when I deploy my app on wildfly 19.0.0 final and jdk-11.0.6+10.
The warning occurs just after WELD print
{panel:title=My title}
12:37:11,206 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.1.3 (Final)
12:37:11,273 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 88) WFLYCLINF0002: Started client-mappings cache from ejb container
WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/D:/wildfly-19.0.0.Final/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone()
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory$1.run(AbstractProxyFactory.java:121)
at java.base/java.security.AccessController.doPrivileged(Native Method)
{panel}
Thanks
> Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
> ---------------------------------------------------------------------------
>
> Key: WFLY-11717
> URL: https://issues.redhat.com/browse/WFLY-11717
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 15.0.1.Final
> Reporter: Kris-Gerhard Aabrams
> Assignee: Brian Stansberry
> Priority: Major
> Labels: Java11
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/opt/jboss/wildfly/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.1.Final.jar!/) to method java.lang.Object.clone()
> WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-11717) Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
by Marc Anthony Puca (Jira)
[ https://issues.redhat.com/browse/WFLY-11717?page=com.atlassian.jira.plugi... ]
Marc Anthony Puca commented on WFLY-11717:
------------------------------------------
Hi everyone, is there any progress on this, I am getting the same issue when I deploy my app on wildfly 19.0.0 final and jdk-11.0.6+10.
The warning occurs just after WELD print
{panel:title=My title}
12:37:11,206 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.1.3 (Final)
12:37:11,273 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 88) WFLYCLINF0002: Started client-mappings cache from ejb container
WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/D:/wildfly-19.0.0.Final/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone()
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory$1.run(AbstractProxyFactory.java:121)
at java.base/java.security.AccessController.doPrivileged(Native Method)
{panel}
Thanks
> Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
> ---------------------------------------------------------------------------
>
> Key: WFLY-11717
> URL: https://issues.redhat.com/browse/WFLY-11717
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 15.0.1.Final
> Reporter: Kris-Gerhard Aabrams
> Assignee: Brian Stansberry
> Priority: Major
> Labels: Java11
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/opt/jboss/wildfly/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.1.Final.jar!/) to method java.lang.Object.clone()
> WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5056) [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5056?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-5056:
-----------------------------------
Priority: Minor (was: Major)
> [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned
> -------------------------------------------------------------------------------
>
> Key: DROOLS-5056
> URL: https://issues.redhat.com/browse/DROOLS-5056
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Daniel José dos Santos
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: issue.mp4, taxRate.dmn
>
>
> Sometimes the nodes inside the Decision Service are positioned outside from the Decision Service when the .DMN is saved an open again.
> I was unable to map exact when this happen, but I noticed that this happens depending on the changes you do in the position and size of the Decision Service and its inner nodes.
> I recorded a video with 2 minutes when the issue happens in the last seconds.
> As it can be notice it takes lots of trials to reproduce the issue.
> Also I was unable to reproduce the issue in the Business Central, so I'm not sure if it is related to DMN Editor in VS Code or DMN Editor itself.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-10137) EJB lookup over HTTP fails if object is used in the signiture
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-10137?page=com.atlassian.jira.plugi... ]
Parul Sharma commented on WFLY-10137:
-------------------------------------
[~crazycradd] I quickly saw but I won't get.
> EJB lookup over HTTP fails if object is used in the signiture
> -------------------------------------------------------------
>
> Key: WFLY-10137
> URL: https://issues.redhat.com/browse/WFLY-10137
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 11.0.0.Final
> Reporter: peter craddock
> Assignee: Parul Sharma
> Priority: Major
>
> I have a swing client that makes calls to the EJB tier via RMI the majority of the calls work fine using the workaround from WFLY-9636.
> The following calls was failing when connected over HTTP but was fine when using the original TCP connection
> public EntityList getAllWorkingSetsForCube( ModelRef modelRef, FinanceCubeRef financeCubeRef, int userId, Integer[] allowedStates )
> I worked round this and found that creating a method without the Integer[] as part of the signature works.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-4575:
--------------------------------
Steps to Reproduce:
- do an action that can be undone
- undo it
- try to close
> Test Scenario: unsaved changes warning appears even if file has not been changed
> --------------------------------------------------------------------------------
>
> Key: DROOLS-4575
> URL: https://issues.redhat.com/browse/DROOLS-4575
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: CustomerFocus, drools-tools
>
> If user opens a scesim file and then close it, no confirmation message should be opened
> h2. Manual Acceptance Test
> - Opening and closing without changes
> - Open, change data in cell, close
> - Open, add column, remove column, change column binding, close
> - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFCORE-4803) EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security
by Ingo Weiss (Jira)
[ https://issues.redhat.com/browse/WFCORE-4803?page=com.atlassian.jira.plug... ]
Ingo Weiss updated WFCORE-4803:
-------------------------------
Labels: downstream_dependency (was: )
> EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4803
> URL: https://issues.redhat.com/browse/WFCORE-4803
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Beta7
> Reporter: Ricardo Martin Camarero
> Assignee: Ricardo Martin Camarero
> Priority: Major
> Labels: downstream_dependency
> Fix For: 12.0.0.Beta1
>
>
> The application does not working when use the DIGEST-MD5 mechanism in the legacy security. This this the configuration on standalone.xml:
> {code:java}
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <http-connector name="http-remoting-connector" connector-ref="https" security-realm="ApplicationRealm">
> <sasl>
> <include-mechanisms value="DIGEST-MD5"/>
> <qop value="auth"/>
> <strength value="medium"/>
> <server-auth value="false"/>
> <reuse-session value="false"/>
> <policy>
> <forward-secrecy value="true"/>
> <no-active value="false"/>
> <no-anonymous value="false"/>
> <no-dictionary value="true"/>
> <no-plain-text value="false"/>
> <pass-credentials value="true"/>
> </policy>
> </sasl>
> </http-connector>
> </subsystem>
> {code}
> Using this configuration I have seen this exception in the application:
> {code:java}
> 019-12-16 09:08:44,132 TRACE [org.wildfly.security] (default task-1) Handling RealmCallback: selected = [RemotingRealm]
> 2019-12-16 09:08:44,132 TRACE [org.wildfly.security] (default task-1) Handling NameCallback: authenticationName = stubejbclient
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Principal assigning: [stubejbclient], pre-realm rewritten: [stubejbclient@RemotingRealm], realm name: [DIGEST-MD5], post-realm rewritten: [stubejbclient@RemotingRealm], realm rewritten: [stubejbclient@RemotingRealm]
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling CredentialCallback: failed to obtain credential
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling RealmCallback: selected = [RemotingRealm]
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling NameCallback: authenticationName = stubejbclient
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling CredentialCallback: failed to obtain credential
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling RealmCallback: selected = [RemotingRealm]
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling NameCallback: authenticationName = stubejbclient
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling PasswordCallback: PasswordCredential may not be supported
> 2019-12-16 09:08:44,133 TRACE [org.jboss.remoting.remote.server] (default task-1) Server sending authentication rejected: javax.security.sasl.SaslException: ELY05051: Callback handler does not support credential acquisition [Caused by org.wildfly.security.auth.callback.FastUnsupportedCallbackException: javax.security.auth.callback.PasswordCallback@1cf94092]
> at org.wildfly.security.mechanism.digest.PasswordDigestObtainer.getSaltedPasswordFromPasswordCallback(PasswordDigestObtainer.java:295)
> at org.wildfly.security.mechanism.digest.PasswordDigestObtainer.handleUserRealmPasswordCallbacks(PasswordDigestObtainer.java:112)
> at org.wildfly.security.sasl.digest.AbstractDigestMechanism.handleUserRealmPasswordCallbacks(AbstractDigestMechanism.java:195)
> at org.wildfly.security.sasl.digest.DigestSaslServer.validateDigestResponse(DigestSaslServer.java:264)
> at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateMessage(DigestSaslServer.java:363)
> at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:199)
> at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateResponse(DigestSaslServer.java:336)
> at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58)
> at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106)
> at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:59)
> at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245)
> at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217)
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:486)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.wildfly.security.auth.callback.FastUnsupportedCallbackException: javax.security.auth.callback.PasswordCallback@1cf94092
> 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling AuthenticationCompleteCallback: fail
> 2019-12-16 09:08:44,133 TRACE [org.jboss.remoting.remote.server] (default task-1) No more authentication attempts allowed, closing the connection
> {code}
> It works to EAP 7.0.x but is not working to EAP 7.2.x.
> The same configuration works on JBoss EAP 7.0.z. I'm attaching the EJB client, EJB service and standalone.xm.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFCORE-4764) Availability of web console during the startup of the Domain Controller
by Ingo Weiss (Jira)
[ https://issues.redhat.com/browse/WFCORE-4764?page=com.atlassian.jira.plug... ]
Ingo Weiss updated WFCORE-4764:
-------------------------------
Labels: downstream_dependency (was: )
> Availability of web console during the startup of the Domain Controller
> -----------------------------------------------------------------------
>
> Key: WFCORE-4764
> URL: https://issues.redhat.com/browse/WFCORE-4764
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Affects Versions: 11.0.0.Beta3
> Reporter: Yeray Borges Santana
> Assignee: Yeray Borges Santana
> Priority: Minor
> Labels: downstream_dependency
> Fix For: 12.0.0.Beta1
>
>
> The customer asking why the web console is only available after all servers are registered in the Domain.
> If the customer starts a domain controller using the host.xml file for example and enables all servers to auto-start="true" the web console is not available until all servers are registered and the browser prompts to add a new interface.
> In the log file, the HTTP management interface is enable in the end of the events:
> ~~~
> [Host Controller] 18:41:29,247 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
> [Host Controller] 18:41:30,208 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:30,210 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:30,284 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1
> [Host Controller] 18:41:30,342 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.4.Final-redhat-1
> [Host Controller] 18:41:30,356 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 18:41:30,383 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.4.Final-redhat-1
> [Host Controller] 18:41:30,478 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.5.Final-redhat-1
> [Host Controller] 18:41:30,603 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
> [Host Controller] 18:41:30,647 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /opt/jboss-eap-7.1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> [Host Controller] 18:41:30,705 INFO [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on 127.0.0.1:9999
> [Host Controller] 18:41:32,922 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:32,990 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,046 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,112 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [Host Controller] 18:41:33,612 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one
> 18:41:33,665 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
> [Host Controller] 18:41:35,496 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 348b688d (inbound) of Remoting connection 0f97728d to localhost/127.0.0.1:53171 of endpoint "master:MANAGEMENT" <46167ef2>]
> [Host Controller] 18:41:35,562 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two
> [Host Controller] 18:41:35,582 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one
> 18:41:35,606 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two'
> [Host Controller] 18:41:38,901 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 114e3864 (inbound) of Remoting connection 30f65708 to localhost/127.0.0.1:42083 of endpoint "master:MANAGEMENT" <46167ef2>]
> [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management
> [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1
> [Host Controller] 18:41:38,970 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) (Host Controller) started in 10487ms - Started 77 of 79 services (23 services are lazy, passive or on-demand)
> ~~~
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month