[JBoss JIRA] (WFCORE-4465) Ensure all transitive embedded are included by default
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4465?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-4465:
------------------------------------------
One thing I see is some of the typical client side API (OperationBuilder and OperationImpl) use wildfly-common solely for the org.wildfly.common.Assert stuff. So that may be the issue -- Galleon is creating Operation objects and that pulls in the dep.
If that's all it is, my instinct is to stop doing that vs requiring embedded users to add the dep.
There's other use like that in the org.jboss.as.controller.client.helpers packages, in stuff that's valid API for embedded use. All the old DeploymentPlan stuff. (I don't mean ContextualModelControllerClient here; it's in the package but is for a quite different use case and not, IMO, an embedded one.)
> Ensure all transitive embedded are included by default
> ------------------------------------------------------
>
> Key: WFCORE-4465
> URL: https://issues.jboss.org/browse/WFCORE-4465
> Project: WildFly Core
> Issue Type: Task
> Components: Embedded
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
>
> When using the {{wildfly-embedded}} dependency it requires some additional dependencies, for example {{org.wildfly.common:wildfly-common}}, to be included. These dependencies should be examined and explicitly added as dependencies so consumers do not need to know which dependencies need to be added.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12050) WildFly management console fails to load deployments if war fails to deploy
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12050?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-12050:
---------------------------------------
Assignee: Brian Stansberry (was: Flavia Rainone)
> WildFly management console fails to load deployments if war fails to deploy
> ---------------------------------------------------------------------------
>
> Key: WFLY-12050
> URL: https://issues.jboss.org/browse/WFLY-12050
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 16.0.0.Final
> Reporter: Philippe Julien
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 17.0.0.Beta1
>
> Attachments: Screen Shot 2019-05-06 at 10.37.03 AM.png
>
>
> When a .war that has servlets declared using @WebServlet fails to deploy, the console cannot list any deployments.
> Here is the exception that is logged by WildFly:
> {noformat}
> 09:52:08.629 [org.jboss.as.controller.management-operation] WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "test-war.war"),
> ("subsystem" => "undertow"),
> ("servlet" => "com.test.TestServlet")
> ]): java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:50)
> at org.wildfly.extension.undertow.DeploymentServletDefinition$AbstractMetricsHandler$1.execute(DeploymentServletDefinition.java:175)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
> at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212)
> at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72)
> at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93)
> at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61)
> at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> I have pushed a small reproducer .war application here: https://github.com/philippejulien/test-war
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12067) Organize plugin version properties in the root pom
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12067?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12067:
------------------------------------
Description: The root pom is structured to not group the pom properties related to plugins and their dependencies in with those related to the content of the software being built. This JIRA is just to tidy this up a bit and make the intended structure clearer.
> Organize plugin version properties in the root pom
> --------------------------------------------------
>
> Key: WFLY-12067
> URL: https://issues.jboss.org/browse/WFLY-12067
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> The root pom is structured to not group the pom properties related to plugins and their dependencies in with those related to the content of the software being built. This JIRA is just to tidy this up a bit and make the intended structure clearer.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11154) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11154?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11154:
----------------------------------
Affects Version/s: 16.0.0.Final
> mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11154
> URL: https://issues.jboss.org/browse/WFLY-11154
> Project: WildFly
> Issue Type: Enhancement
> Components: mod_cluster
> Affects Versions: 14.0.0.Final, 15.0.0.Beta1, 16.0.0.Final
> Reporter: Jan Kasik
> Assignee: Radoslav Husar
> Priority: Optional
>
> When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log:
> {code}
> INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds.
> {code}
> This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't.
> Suggestion: Replace this message with more accurate one.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months