[JBoss JIRA] (WFLY-3639) default-web-module doesn't work for non default hosts & servers
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3639?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-3639:
----------------------------------
The fix in https://github.com/wildfly/wildfly/pull/9236 causes regressions
https://ci.wildfly.org/viewLog.html?buildId=28148&tab=buildResultsDiv&bui...
{code}
org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation failed: "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: WFLYUT0087: Duplicate default web module 'ROOT.war' configured on server 'default-server', host 'test'"
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
at org.jboss.as.test.integration.management.base.AbstractMgmtTestBase.executeOperation(AbstractMgmtTestBase.java:73)
at org.jboss.as.test.integration.management.base.AbstractMgmtTestBase.executeOperation(AbstractMgmtTestBase.java:85)
at org.jboss.as.test.integration.management.api.web.VirtualServerTestCase.addVirtualServer(VirtualServerTestCase.java:139)
at org.jboss.as.test.integration.management.api.web.VirtualServerTestCase.addRemoveVirtualServer(VirtualServerTestCase.java:100)
------- Stdout: -------
[0m02:01:58,958 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment dummy.jar (runtime-name: dummy.jar) in 3ms
[0m[0m02:01:58,966 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /opt/buildAgent/work/eef9fee5d4ca1630/testsuite/integration/basic/target/jbossas/standalone/data/content/2e/68ed26f1b74748fddd2839595a2c349cadbea7/content
[0m[0m02:01:58,966 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "dummy.jar" (runtime-name: "dummy.jar")
[0m02:01:58,971 INFO [org.jboss.as.test.integration.security.common.AbstractBaseSecurityRealmsServerSetupTask] (main) Removing security realm ssl-realm
02:01:58,992 INFO [org.jboss.as.test.integration.security.common.CoreUtils] (main) Client update: {
"operation" => "remove",
"address" => [
("core-service" => "management"),
("security-realm" => "ssl-realm")
],
"operation-headers" => {
"rollback-on-runtime-failure" => false,
"allow-resource-service-restart" => true
}
}
02:01:58,992 INFO [org.jboss.as.test.integration.security.common.CoreUtils] (main) Client update result: {
"outcome" => "success",
"response-headers" => {"process-state" => "reload-required"}
}
[0m02:01:59,029 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/eef9fee5d4ca1630/testsuite/integration/basic/target/jbossas/standalone/data/content/98/aa708e24ea1eb7be904d2ac263ce54c84bc9e8/content
[0m[0m02:01:59,032 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "dummy.jar" (runtime-name: "dummy.jar")
[0m[33m02:01:59,039 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.dummy.jar" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
[0m[0m02:01:59,042 INFO [org.jboss.as.arquillian] (MSC service thread 1-4) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."dummy.jar",unit=dummy.jar,tests=[org.jboss.as.test.integration.management.api.web.VirtualServerTestCase]]
[0m[0m02:01:59,050 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "dummy.jar" (runtime-name : "dummy.jar")
[0m[31m02:01:59,063 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("host" => "test")
]): java.lang.IllegalArgumentException: WFLYUT0087: Duplicate default web module 'ROOT.war' configured on server 'default-server', host 'test'
at org.wildfly.extension.undertow.deployment.DefaultDeploymentMappingProvider.addMapping(DefaultDeploymentMappingProvider.java:59)
at org.wildfly.extension.undertow.HostAdd.performRuntime(HostAdd.java:73)
at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
[0m
{code}
> default-web-module doesn't work for non default hosts & servers
> ---------------------------------------------------------------
>
> Key: WFLY-3639
> URL: https://issues.jboss.org/browse/WFLY-3639
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 11.0.0.Alpha1
>
>
> If you use config like this:
> {code:xml}
> <host name="default-host" default-web-module="myapp1.war" alias="webapp.domain1.com"/>
> <host name="other-host" default-web-module="myapp2.war" alias="test.domain2.net"/>
> {code}
> and have apps myapp1.war & myapp2.war deployed myappwar2.war won't be bind to other-host.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1833) Fix ServiceLoader iterator issue
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1833?page=com.atlassian.jira.plugi... ]
Richard Opalka updated WFCORE-1833:
-----------------------------------
Description:
ServiceLoader regression in latest Jigsaw JDK9 builds
is caused by fact ServiceLoader's iterator call to hasNext() method
is not covered with ServiceConfigurationError try-catch statement.
was:
There's ServiceLoader regression in recent Jigsaw JDK9 builds.
We will implement temporary workaround for this Jigsaw issue.
This issue can be closed / resolved once this workaround
will be eliminated from our code base.
> Fix ServiceLoader iterator issue
> --------------------------------
>
> Key: WFCORE-1833
> URL: https://issues.jboss.org/browse/WFCORE-1833
> Project: WildFly Core
> Issue Type: Sub-task
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> ServiceLoader regression in latest Jigsaw JDK9 builds
> is caused by fact ServiceLoader's iterator call to hasNext() method
> is not covered with ServiceConfigurationError try-catch statement.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1841) Subsystem parsers should be created lazily when needed
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1841?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-1841:
------------------------------------------
Something we did not mention when we talked about this but will also be benefit, there are scenarios where the version of the parser for the first load is different for all subsequent loads.
> Subsystem parsers should be created lazily when needed
> ------------------------------------------------------
>
> Key: WFCORE-1841
> URL: https://issues.jboss.org/browse/WFCORE-1841
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
>
> Currently when we register parsers for different versions of subsystem schema we always pass over instance of whole parser which is usually statically initialized.
> In practice legacy (non current) parsers are only used rarely and there is no point in having them loaded in memory when not needed.
> Impl should be based on provider pattern and as such also allow us to on demand create new instance of parser when needed, as well as enable us for parsers to be GCed, when they are not in use.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1841) Subsystem parsers should be created lazily when needed
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1841?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFCORE-1841:
-----------------------------------
Summary: Subsystem parsers should be created lazily when needed (was: Subsystem parsers should be created lazly when need)
> Subsystem parsers should be created lazily when needed
> ------------------------------------------------------
>
> Key: WFCORE-1841
> URL: https://issues.jboss.org/browse/WFCORE-1841
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
>
> Currently when we register parsers for different versions of subsystem schema we always pass over instance of whole parser which is usually statically initialized.
> In practice legacy (non current) parsers are only used rarely and there is no point in having them loaded in memory when not needed.
> Impl should be based on provider pattern and as such also allow us to on demand create new instance of parser when needed, as well as enable us for parsers to be GCed, when they are not in use.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7209) Operation to list installed Resource Adapters
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-7209?page=com.atlassian.jira.plugin.... ]
Stefano Maestri commented on WFLY-7209:
---------------------------------------
You are confusing rar deployed (through deployment or modules) w/ activation (through subsystem or ironjacamar.xml)
You could have more than one activation for each rar, and from a runtime POV activations are the only ones important.
Frankly, I don't see an operation mixing both concepts as useful.
> Operation to list installed Resource Adapters
> ---------------------------------------------
>
> Key: WFLY-7209
> URL: https://issues.jboss.org/browse/WFLY-7209
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Reporter: Guillermo González de Agüero
> Assignee: Stefano Maestri
> Fix For: 10.1.0.Final
>
>
> Currently there's no way to list all the installed Resource Adapters. Only configured resource adapters can be queried. However, they are automatically enabled at deployment time.
> I propose to add a new operation to list installed RAs and their configuration, similar to the one available for JDBC drivers. This would allow HAL to provide a wizard of available options when configuring them.
> The command would be something like: /subsystem=resource-adapters:installed-resource-adapters-list()
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1841) Subsystem parsers should be created lazly when need
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFCORE-1841:
-----------------------------------
Summary: Subsystem parsers should be created lazly when need
Key: WFCORE-1841
URL: https://issues.jboss.org/browse/WFCORE-1841
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Currently when we register parsers for different versions of subsystem schema we always pass over instance of whole parser which is usually statically initialized.
In practice legacy (non current) parsers are only used rarely and there is no point in having them loaded in memory when not needed.
Impl should be based on provider pattern and as such also allow us to on demand create new instance of parser when needed, as well as enable us for parsers to be GCed, when they are not in use.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7244) Web sockets are always enabled
by Kabir Khan (JIRA)
Kabir Khan created WFLY-7244:
--------------------------------
Summary: Web sockets are always enabled
Key: WFLY-7244
URL: https://issues.jboss.org/browse/WFLY-7244
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.1.0.Final
Reporter: Kabir Khan
Assignee: Stuart Douglas
Fix For: 11.0.0.Alpha1
TCK testing for WFLY-6784 unearthed that websockets were always turned on in the undertow subsystem, while they should be explicitly turned on with the websocket element.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7243) Web sockets are always enabled
by Kabir Khan (JIRA)
Kabir Khan created WFLY-7243:
--------------------------------
Summary: Web sockets are always enabled
Key: WFLY-7243
URL: https://issues.jboss.org/browse/WFLY-7243
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.1.0.Final
Reporter: Kabir Khan
Assignee: Stuart Douglas
Fix For: 11.0.0.Alpha1
TCK testing for WFLY-6784 unearthed that websockets were always turned on in the undertow subsystem, while they should be explicitly turned on with the websocket element.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (DROOLS-1310) Expired fact with activationCount > 0 are not evicted from objectstore
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1310?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-1310:
-----------------------------------
Attachment: RuleTest.java
Standalone JUnit reproducer for the case.
> Expired fact with activationCount > 0 are not evicted from objectstore
> ----------------------------------------------------------------------
>
> Key: DROOLS-1310
> URL: https://issues.jboss.org/browse/DROOLS-1310
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.CR2
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: RuleTest.java
>
>
> Expired fact with activationCount > 0 are not evicted from objectstore: intended behavior for serialization purposes, but for instance side-effects when used in an activation-group scenario where the rules are not 100% dual.
> Sized-down reproducer will be submitted at a later time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months