[JBoss JIRA] (WFLY-11137) Make undertow extension module's dependency on org.jboss.as.security module optional
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11137?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-11137:
---------------------------------------
Assignee: Yeray Borges
> Make undertow extension module's dependency on org.jboss.as.security module optional
> ------------------------------------------------------------------------------------
>
> Key: WFLY-11137
> URL: https://issues.jboss.org/browse/WFLY-11137
> Project: WildFly
> Issue Type: Task
> Components: Security, Web (Undertow)
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
>
> Don't require the legacy security subsystem module if it's not actually used.
> Usage looks like this:
> {code}
> wildfly bstansberry$ cd undertow/
> undertow bstansberry$ git grep org.jboss.as.security
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentInfoService.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.deployment.AbstractSecurityDeployer;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.deployment.SecurityAttachments;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.service.JaccService;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.service.SecurityDomainService;
> src/main/java/org/wildfly/extension/undertow/security/DigestCredentialImpl.java:import org.jboss.as.security.DigestCredential;
> src/main/java/org/wildfly/extension/undertow/security/JAASIdentityManagerImpl.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/security/SecurityContextThreadSetupAction.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCDeployer.java:import org.jboss.as.security.deployment.AbstractSecurityDeployer;
> src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCDeployer.java:import org.jboss.as.security.service.JaccService;
> src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCService.java:import org.jboss.as.security.service.JaccService;
> {code}
> Dropping the use of SecurityAttachments from UndertowDeploymentProcessor and instead having it check for the presence of the org.wildfly.legacy-security capability will go a long way here. After that, most if not all of the other uses only get called either as a result of that check being true, or some config attribute that directly or indirectly references a security domain. IOW the other uses are only needed if the security subsystem is known to be configured.
> Per Intellij, DigestCredentialImpl is unused.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-5966:
--------------------------------------
Assignee: Yeray Borges (was: Jason Greene)
> Validate requirement for modules previously exported by javax.ejb.api
> ---------------------------------------------------------------------
>
> Key: WFLY-5966
> URL: https://issues.jboss.org/browse/WFLY-5966
> Project: WildFly
> Issue Type: Task
> Components: Server
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
>
> The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this:
> {code}
> <!-- TODO validate the need for these and remove if not needed.
> Prior to WFLY-5922 they were exported by javax.ejb.api. -->
> <module name="javax.api"/>
> <module name="javax.transaction.api"/>
> <module name="javax.xml.rpc.api"/>
> <module name="javax.rmi.api"/>
> <module name="org.omg.api"/>
> {code}
> If a module already had a dep on one of those, it's not in the block.
> This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed.
> Affected modules:
> feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml
> The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api:
> feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml
> jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml
> jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml
> The following modules were fixed or verified as correct (moved from the first list):
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11
by Kabir Khan (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
Kabir Khan commented on WFLY-11128:
-----------------------------------
[~jamezp] [~rsvoboda] [~asoldano] I cloned it to JBEAP-15630
> wsconsume failure on wildfly14 + JDK 11
> ---------------------------------------
>
> Key: WFLY-11128
> URL: https://issues.jboss.org/browse/WFLY-11128
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 13.0.0.Final, 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
> Attachments: HelloWorldService-imported.xml, HelloWorldService.xml, demo-service-code.zip, log.txt, logs.zip
>
>
> running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
> the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11150) wsconsume failure on wildfly14 + JDK 11
by Kabir Khan (Jira)
Kabir Khan created WFLY-11150:
---------------------------------
Summary: wsconsume failure on wildfly14 + JDK 11
Key: WFLY-11150
URL: https://issues.jboss.org/browse/WFLY-11150
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 13.0.0.Final, 14.0.0.Final
Environment: Windows 7 64bits
JDK 11
Wildfly 14
Reporter: mazen mahmoud
Assignee: R Searls
Fix For: 15.0.0.Alpha1
running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11
by Alessio Soldano (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
Alessio Soldano updated WFLY-11128:
-----------------------------------
Priority: Critical (was: Major)
> wsconsume failure on wildfly14 + JDK 11
> ---------------------------------------
>
> Key: WFLY-11128
> URL: https://issues.jboss.org/browse/WFLY-11128
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 13.0.0.Final, 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
> Attachments: HelloWorldService-imported.xml, HelloWorldService.xml, demo-service-code.zip, log.txt, logs.zip
>
>
> running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
> the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11
by Alessio Soldano (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
Alessio Soldano updated WFLY-11128:
-----------------------------------
Fix Version/s: 15.0.0.Alpha1
> wsconsume failure on wildfly14 + JDK 11
> ---------------------------------------
>
> Key: WFLY-11128
> URL: https://issues.jboss.org/browse/WFLY-11128
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 13.0.0.Final, 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
> Attachments: HelloWorldService-imported.xml, HelloWorldService.xml, demo-service-code.zip, log.txt, logs.zip
>
>
> running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
> the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet commented on WFLY-11112:
------------------------------------------
[~istraka] could you 'test' https://github.com/ehsavoie/wildfly/commit/5b93203b0080df00c5a7c1b0e50a07... ?
> WildFly intermittently fails to add pooled-connection-factory but it still got registered after
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-11112
> URL: https://issues.jboss.org/browse/WFLY-11112
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 15.0.0.Alpha1
> Reporter: Ivan Straka
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: server.log, standalone-full.xml
>
>
> We see following error in log of WildFly (master):
> {code}
> 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("pooled-connection-factory" => "activemq-ra")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"]
> }
> {code}
> Factory is defined:
> {code:java}
> <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
> {code}
> However factory is registered after and deployment is able to use it. Error is logged intermittently.
> Log file and xml configuration file are enclosed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11149) Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy
by Radoslav Husar (Jira)
Radoslav Husar created WFLY-11149:
-------------------------------------
Summary: Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy
Key: WFLY-11149
URL: https://issues.jboss.org/browse/WFLY-11149
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 14.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Running legacy operation ends up with an error:
{code}
[standalone@localhost:9990 /] /subsystem=modcluster/:disable
{
"outcome" => "failed",
"failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address.",
"rolled-back" => true
}
{code}
mod_cluster configuration:
{code}
[standalone@localhost:9990 /] /subsystem=modcluster/:read-resource
{
"outcome" => "success",
"result" => {
"mod-cluster-config" => {"configuration" => undefined},
"proxy" => {"default" => undefined}
}
}
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11
by R Searls (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
R Searls updated WFLY-11128:
----------------------------
Affects Version/s: 13.0.0.Final
> wsconsume failure on wildfly14 + JDK 11
> ---------------------------------------
>
> Key: WFLY-11128
> URL: https://issues.jboss.org/browse/WFLY-11128
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 13.0.0.Final, 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Major
> Attachments: HelloWorldService-imported.xml, HelloWorldService.xml, demo-service-code.zip, log.txt, logs.zip
>
>
> running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
> the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
by Ziad Saade (Jira)
[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ]
Ziad Saade commented on WFLY-11116:
-----------------------------------
Dear Paul
kindly note that the issue is reproduced in a Single Node Environment and Not Cluster, Note that I can't share the Code because it's confidential.
Is it possible to reproduce the issue and provide you a specific System Log for your Analysis and Feedback?
Best Regards
> Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11116
> URL: https://issues.jboss.org/browse/WFLY-11116
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Ziad Saade
> Assignee: Paul Ferraro
> Priority: Critical
>
> I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow:
>
> Book.java
> TestBean testBean=null;
> if(session.getAttribute("testBean")!=null)
> testBean = (TestBean)session.getAttribute("testBean");
> else{
> testBean=new TestBean();
> session.setAttribute("testBean",testBean);
> }
> testBean.setAmount("10");
>
> response.sendRedirect("BookPreview");
>
>
> The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated.
>
> BookPreview.java
>
> TestBean testBean = (TestBean)session.getAttribute("testBean");
> String amount = testBean.getAmount; //Null pointer exception when submitting the form
>
> <form method="Post" action="BookPreview">
>
> </form>
>
> TestBean.java
>
> public class TestBean implements java.io.Serializable {
>
> private static final long serialVersionUID = 1L;
> private String amount;
>
> public String getAmount() {
> return amount;
> }
>
> public void setAmount(String amount) {
> this.amount = amount;
> }
> }
>
> Kindly advice how to fix the problem at the level of the server configuration.
> PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....)
>
> Thanks and Best Regards
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months