[JBoss JIRA] (DROOLS-1432) Improve error messages when compiling models with errors
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1432?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-1432:
----------------------------------
Release Notes Text: (was: Major infrastructure changes to properly support error validation are now implemented. Type definition and resolution is now correlated between DMN layer and FEEL layer. Additional work will be done through other tickets.)
> Improve error messages when compiling models with errors
> --------------------------------------------------------
>
> Key: DROOLS-1432
> URL: https://issues.jboss.org/browse/DROOLS-1432
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.0.0.Beta6
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Fix For: 7.0.0.Final
>
> Attachments: car_damage_responsibility2.dmn
>
>
> When a model contains errors that prevent compilation, the engine should provide a better error message pointing to the specific error.
> At the moment, the attached model fails with a NPE and a message:
> {quote}Message [id=1, kieBase=defaultKieBase, level=ERROR, path=car_damage_responsibility2.dmn, line=-1, column=0 text=Unable to compile DMN model for the resource]{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-8243) Clustered Singleton MDB does not activate
by Flavia Rainone (JIRA)
[ https://issues.jboss.org/browse/WFLY-8243?page=com.atlassian.jira.plugin.... ]
Flavia Rainone moved JBEAP-9130 to WFLY-8243:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8243 (was: JBEAP-9130)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
EJB
JMS
(was: Clustering)
(was: EJB)
(was: JMS)
Affects Version/s: (was: 7.1.0.DR8)
(was: 7.1.0.DR10)
(was: 7.1.0.DR11)
(was: 7.1.0.DR12)
Affects Testing: (was: Regression)
> Clustered Singleton MDB does not activate
> -----------------------------------------
>
> Key: WFLY-8243
> URL: https://issues.jboss.org/browse/WFLY-8243
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB, JMS
> Reporter: Flavia Rainone
> Assignee: Flavia Rainone
> Priority: Blocker
>
> Clustered Singleton MDB does not activate. It's regression in EAP 7.1.0.DR8 (against DR7).
> Customer impact: No Clustered Singleton MDB will activate in cluster and service will not operate. No warning or error will show in server logs. There is no workaround for this issue.
> Test scenario:
> - Start two EAP 7.1.0.DR8 servers in cluster with active delivery-group named "group"
> - Deploy queues InQueue and OutQueue to both of the servers. There is also Artemis cluster configured between servers so all messages will be load-balanced between the nodes.
> - Deploy MDB configured as clustered singletons to both of the server. MDBs belong to delivery-group "group"
> -- MDB consumes messages from InQueue and resends to OutQueue
> - Start sending messages to InQueue and consume from OutQueue.
> - Check that MDB on node 1 is active as it's sigleton master
> - Check that MDB on node 2 is NOT active
> - Kill node-1 (by kill -9 ...)
> - Check that MDB on node 2 is active as it's sigleton master
> Expected result:
> Consumer will receive all messages from OutQueue. All checks passes.
> Actual result:
> MDB on node 1 is not delivery active at the beginning of the test. Consumer timed out as there are no processed messages in OutQueue
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-8242) EjbSuspendHandler.endSuspension throws NPE
by Flavia Rainone (JIRA)
Flavia Rainone created WFLY-8242:
------------------------------------
Summary: EjbSuspendHandler.endSuspension throws NPE
Key: WFLY-8242
URL: https://issues.jboss.org/browse/WFLY-8242
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Flavia Rainone
Assignee: Flavia Rainone
This exception occurs sometimes:
java.lang.NullPointerException
at org.jboss.as.ejb3.suspend.EJBSuspendHandlerService.doneSuspended(EJBSuspendHandlerService.java:303) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
at org.jboss.as.ejb3.suspend.EJBSuspendHandlerService.decrementTransactionCount(EJBSuspendHandlerService.java:315) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
at org.jboss.as.ejb3.suspend.EJBSuspendHandlerService.afterCompletion(EJBSuspendHandlerService.java:285) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:101)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1216)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89)
at org.wildfly.transaction.client.LocalTransaction.commitAndDissociate(LocalTransaction.java:69) [wildfly-transaction-client-1.0.0.Beta17.jar:1.0.0.Beta17]
at org.wildfly.transaction.client.ContextTransactionManager.commit(ContextTransactionManager.java:61) [wildfly-transaction-client-1.0.0.Beta17.jar:1.0.0.Beta17]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:279) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-7.1.0.Alpha1-redhat-SNAPSHOT.jar:7.1.0.Alpha1-redhat-SNAPSHOT]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFCORE-1958) Clean up testsuite Elytron registration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1958?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1958:
------------------------------------------
[~dlofthouse] I'm not sure what needs to be done here, but for my work on WFCORE-2320 I reenabled a large number of tests in testsuite/domain that were @Ignored with a ref to this JIRA. I left the @Ignore, just commented out, so it's still possible to find those items by grepping for "WFCORE-1958".
I enabled them because they pass now and we need the test coverage.
In testsuite/manualmode org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase is still ignored, since it doesn't pass.
> Clean up testsuite Elytron registration
> ---------------------------------------
>
> Key: WFCORE-1958
> URL: https://issues.jboss.org/browse/WFCORE-1958
> Project: WildFly Core
> Issue Type: Task
> Components: Test Suite
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta6
>
>
> In a couple of places we have artificially registered the WildFly Elytron Security provider, we need to address this so tests can automatically have it available to them..
> Also re-enable the following test case: -
> * org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFCORE-2320) Unable to start Slave host after Master was restarted with enabled RBAC
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2320?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2320:
-------------------------------------
Fix Version/s: 3.0.0.Beta6
> Unable to start Slave host after Master was restarted with enabled RBAC
> -----------------------------------------------------------------------
>
> Key: WFCORE-2320
> URL: https://issues.jboss.org/browse/WFCORE-2320
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Tymel
> Assignee: Brian Stansberry
> Priority: Blocker
> Fix For: 3.0.0.Beta6
>
>
> It is not possible to connect to previously shutdown domain controller that uses RBAC. If steps to reproduce are followed then the following output is given on slave:
> {code}
> [Host Controller] 10:47:57,754 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:48:01,756 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:48:10,918 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:48:26,026 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:48:41,047 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:48:56,059 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:49:11,106 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:49:26,133 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:49:41,148 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:49:56,180 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:50:11,202 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:50:26,215 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:50:41,230 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:50:56,264 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:50:56,273 WARN [org.jboss.as.protocol.connection] (management task-1) WFLYPRT0018: No such request (15) associated with channel Channel ID ce1200c8 (outbound) of Remoting connection 6cf4e35b to /127.0.0.1:9999 of endpoint "my-local-domain:MANAGEMENT" <988a70d>
> [Host Controller] 10:51:11,275 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:51:11,304 WARN [org.jboss.as.protocol.connection] (management task-7) WFLYPRT0018: No such request (16) associated with channel Channel ID cabd84e6 (outbound) of Remoting connection 3083f850 to /127.0.0.1:9999 of endpoint "my-local-domain:MANAGEMENT" <988a70d>
> (...)
> Host Controller] 10:52:26,401 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 8) WFLYHC0150: Trying to reconnect to master host controller.
> [Host Controller] 10:52:40,194 ERROR [org.jboss.as.server] (Host Controller Service Threads - 7) WFLYSRV0216: Error cleaning obsolete content WFLYCTL0313: Unauthorized to execute operation 'read-attribute' for resource '[]' -- "WFLYCTL0332: Permission denied"
> [Host Controller] 10:52:40,196 ERROR [org.jboss.as.server] (Host Controller Service Threads - 7) WFLYSRV0216: Error cleaning obsolete content WFLYCTL0031: No operation named 'clean-obsolete-content' exists at address []
> {code}
> On master instance is given following output after a while:
> {code}
> [Host Controller] 10:52:59,560 ERROR [org.jboss.as.server] (Host Controller Service Threads - 31) WFLYSRV0216: Error cleaning obsolete content WFLYCTL0313: Unauthorized to execute operation 'read-attribute' for resource '[]' -- "WFLYCTL0332: Permission denied"
> [Host Controller] 10:52:59,564 ERROR [org.jboss.as.server] (Host Controller Service Threads - 31) WFLYSRV0216: Error cleaning obsolete content WFLYCTL0031: No operation named 'clean-obsolete-content' exists at address []
> {code}
> Once the slave instance has been shut down, it is not possible to start it again. See following output:
> {code}
> [Host Controller] 10:55:34,409 INFO [org.jboss.as.remoting] (MSC service thread 1-2) WFLYRMT0001: Listening on 127.0.0.1:19999
> [Host Controller] 10:55:34,701 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://127.0.0.1:9999: 1-$-WFLYCTL0216: Management resource '[]' not found
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$HostControllerConnectRequest.handleRequest(RemoteDomainConnection.java:390)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:321)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:286)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:234)
> [Host Controller] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:85)
> [Host Controller] at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:434)
> [Host Controller] at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:817)
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Host Controller] at java.lang.Thread.run(Thread.java:745)
> [Host Controller]
> [Host Controller] 10:55:34,702 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
> [Host Controller] 10:55:34,702 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect
> [Host Controller] 10:55:34,707 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99
> [Host Controller] 10:55:34,734 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta2-redhat-1) stopped in 16ms
> {code}
> Setting priority to blocker since this is a regression against 7.0.0.GA
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFCORE-2329) ServerAutoStartTestCase and ServerStartFailureTestCase are never run
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-2329:
----------------------------------------
Summary: ServerAutoStartTestCase and ServerStartFailureTestCase are never run
Key: WFCORE-2329
URL: https://issues.jboss.org/browse/WFCORE-2329
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Test Suite
Reporter: Brian Stansberry
Tests in testsuite/domain do not all automatically run just by being called XXXTestCase. They need to be located in one of the packages listed in the surefire config in testsuite/domain/pom.xml or by listed in the @Suite.SuiteClasses annotation of one of the suites that is in one of those packages. ServerAutoStartTestCase and ServerStartFailureTestCase are tests where neither of these are true so they are not running.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFCORE-2327) embed-server froze during start when RBAC used
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2327?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2327:
------------------------------------------
[~dlofthouse] I fixed this by cleaning up how in-VM ModelControllerClients are accessed, exposing a ModelControllerClientFactory as a capability. The factory has two methods for creating a client -- one that provides a client that always runs as superuser (using InVmAccess under the covers) and the other that does not. The existing internal client uses (Deployment scanner and offline CLI) use the SuperUser variant.
I don't want subsystem authors dealing with InVmAccess. That's internal. Hence the need for a factory that provides a suitable client for purely in-vm activity that should have SuperUser perms.
However, this "super user client" does not internally wrap its calls with AccessController.doPrivileged. So, in a security manager enabled VM, the code using the client will need to have ControllerPermission.PERFORM_IN_VM_CALL. This forces the code author to consider whether they are using the client appropriately.
For the deployment scanner, I wrapped its calls to "super user client" in a doPrivileged. (As you already had in your earlier work on this.)
For the offline CLI, I did not. This means that in a security manager environment offline CLI users will need permissions configured.
> embed-server froze during start when RBAC used
> ----------------------------------------------
>
> Key: WFCORE-2327
> URL: https://issues.jboss.org/browse/WFCORE-2327
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha17
> Reporter: Jan Kalina
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 3.0.0.Beta6
>
> Attachments: standalone.xml
>
>
> When RBAC enabled, embed-server froze during start - CLI prompt of started server does not show and need to be interrupted by Ctrl+C.
> {code}
> bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-server --std-out=echo
> 15:55:41,588 INFO [org.jboss.modules] (AeshProcess: 1) JBoss Modules version 1.6.0.Beta3
> 15:55:41,650 INFO [org.jboss.msc] (AeshProcess: 1) JBoss MSC version 1.2.7.Final
> 15:55:41,773 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Core 3.0.0.Alpha18-SNAPSHOT "Kenny" starting
> 15:55:41,966 INFO [org.jboss.as.domain.management] (MSC service thread 1-4) WFLYDM0136: Registered OpenSSL provider
> 15:55:42,302 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/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.
> 15:55:42,367 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> 15:55:42,386 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-4) WFLYDM0111: Keystore /home/jkalina/wildfly/wildfly-core/build/target/wildfly-core-3.0.0.Alpha18-SNAPSHOT/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 15:55:42,466 INFO [org.jboss.as.server] (ServerService Thread Pool -- 5) WFLYSRV0212: Resuming server
> 15:55:42,469 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha18-SNAPSHOT "Kenny" started in 875ms - Started 37 of 46 services (17 services are lazy, passive or on-demand)
> {code}
> In this stage it froze and need to be interrupted by Ctrl+C.
> {code}
> Interrupted while waiting for embedded server to start
> [disconnected /]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFCORE-2327) embed-server froze during start when RBAC used
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2327?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2327:
-------------------------------------
Fix Version/s: 3.0.0.Beta6
> embed-server froze during start when RBAC used
> ----------------------------------------------
>
> Key: WFCORE-2327
> URL: https://issues.jboss.org/browse/WFCORE-2327
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha17
> Reporter: Jan Kalina
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 3.0.0.Beta6
>
> Attachments: standalone.xml
>
>
> When RBAC enabled, embed-server froze during start - CLI prompt of started server does not show and need to be interrupted by Ctrl+C.
> {code}
> bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-server --std-out=echo
> 15:55:41,588 INFO [org.jboss.modules] (AeshProcess: 1) JBoss Modules version 1.6.0.Beta3
> 15:55:41,650 INFO [org.jboss.msc] (AeshProcess: 1) JBoss MSC version 1.2.7.Final
> 15:55:41,773 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Core 3.0.0.Alpha18-SNAPSHOT "Kenny" starting
> 15:55:41,966 INFO [org.jboss.as.domain.management] (MSC service thread 1-4) WFLYDM0136: Registered OpenSSL provider
> 15:55:42,302 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/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.
> 15:55:42,367 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
> 15:55:42,386 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-4) WFLYDM0111: Keystore /home/jkalina/wildfly/wildfly-core/build/target/wildfly-core-3.0.0.Alpha18-SNAPSHOT/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 15:55:42,466 INFO [org.jboss.as.server] (ServerService Thread Pool -- 5) WFLYSRV0212: Resuming server
> 15:55:42,469 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha18-SNAPSHOT "Kenny" started in 875ms - Started 37 of 46 services (17 services are lazy, passive or on-demand)
> {code}
> In this stage it froze and need to be interrupted by Ctrl+C.
> {code}
> Interrupted while waiting for embedded server to start
> [disconnected /]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months