[JBoss JIRA] (JGRP-2305) Get rid of need for java.net.preferIPv4Stack
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2305?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2305.
----------------------------
Resolution: Done
> Get rid of need for java.net.preferIPv4Stack
> --------------------------------------------
>
> Key: JGRP-2305
> URL: https://issues.jboss.org/browse/JGRP-2305
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16
>
>
> New address picking scheme:
> * First we detect which addresses are available: IPv4 and/or IPv6 (dual-stack if both)
> * When we encounter an IPv4 address:
> ** If dual-stack or IPv4 stack: use it
> ** If IPv6-only stack: use it unless it is a class D (multicast) address: then convert it to an IPv6-mapped address
> * When we encounter an IPv6 address:
> ** If dual-stack or IPv6-only stack: use it
> ** Else: throw an exception (IPv6 address in an IPv4-only stack)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-134) Bad WARN messages: AMQ222211: Storage is back to stable now...
by Miroslav Novak (Jira)
Miroslav Novak created WFWIP-134:
------------------------------------
Summary: Bad WARN messages: AMQ222211: Storage is back to stable now...
Key: WFWIP-134
URL: https://issues.jboss.org/browse/WFWIP-134
Project: WildFly WIP
Issue Type: Bug
Components: Artemis
Reporter: Miroslav Novak
Assignee: Martyn Taylor
There are unwanted WARN messages:
{code}
13:47:48,158 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 15.0.0.Alpha1-SNAPSHOT (WildFly Core 7.0.0.Alpha4) started in 8017ms - Started 495 of 723 services (489 services are lazy, passive or on-demand)
13:47:50,235 WARN [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371)) AMQ222183: Blocking message production on address 'jms.queue.InQueue'; size is currently: 10,635,300 bytes; max-size-bytes on address: 10,485,760, global-max-size is 10,635,300
13:47:52,642 WARN [org.apache.activemq.artemis.core.server] (Thread-4 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371)) AMQ222211: Storage is back to stable now, under max-disk-usage.
13:47:57,642 WARN [org.apache.activemq.artemis.core.server] (Thread-15 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371)) AMQ222211: Storage is back to stable now, under max-disk-usage.
...
{code}
when server has configured {{global-max-memory-size}} and address-full-policy to BLOCK. Once {{global-max-memory-size}} then starts to log above warnings which with max-disk-usage. Which is not correct as no disk limitation was reached.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 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 updated WFLY-5966:
-----------------------------------
Description:
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
was:
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
> 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-11279) The org.jboss.as.jpa module includes some unnecessary dependencies
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11279:
---------------------------------------
Summary: The org.jboss.as.jpa module includes some unnecessary dependencies
Key: WFLY-11279
URL: https://issues.jboss.org/browse/WFLY-11279
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Prune some dependencies that analysis shows are not used by the dependent org.jboss.as.jpa:
org.jboss.jts
org.jboss.jts.integration
org.jboss.as.clustering.common
org.jboss.as.connector
org.jboss.as.web-common
org.wildfly.clustering.service
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4197) Add support for TLS 1.3
by Farah Juma (Jira)
Farah Juma created WFCORE-4197:
----------------------------------
Summary: Add support for TLS 1.3
Key: WFCORE-4197
URL: https://issues.jboss.org/browse/WFCORE-4197
Project: WildFly Core
Issue Type: Feature Request
Components: Security
Reporter: Farah Juma
Assignee: Farah Juma
It presently appears as though TLS 1.3 support could be available from Java 11.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11259) Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
by Adam Bialas (Jira)
[ https://issues.jboss.org/browse/WFLY-11259?page=com.atlassian.jira.plugin... ]
Adam Bialas commented on WFLY-11259:
------------------------------------
I just added to jboss-deployment-structure:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<sub-deployment name="bbb.war">
<dependencies>
<module name="org.dom4j" />
</dependencies>
</sub-deployment>
</jboss-deployment-structure>
Seems that problem is fixed - persistense.xml is parsed without exception and application when required uses dom4j from lib folder. However, why I had to add this explicitly? And is it a correct way to fix that problem?
> Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11259
> URL: https://issues.jboss.org/browse/WFLY-11259
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Reporter: Adam Bialas
> Assignee: Scott Marlow
> Priority: Major
>
> I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown:
> org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> and the application fails to deploy.
> I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used.
> I created jboss-deployment-structure:
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <deployment>
> <exclusions>
> <module name="org.dom4j"/>
> </exclusions>
> </deployment>
> </jboss-deployment-structure>
> Even though I get the same exception so I suppose both jars are loaded and cause problems.
> I checked how class loading works on Wildfly 11.0.0 in comparison to JBoss EAP 7.1. In both cases this class is first loaded from provided 1.6.1 jar. JBoss does not load the newer version. However, Wildfly does and here is the problem.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11259) Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
by Adam Bialas (Jira)
[ https://issues.jboss.org/browse/WFLY-11259?page=com.atlassian.jira.plugin... ]
Adam Bialas commented on WFLY-11259:
------------------------------------
Here is the ear structure I have (need) and which works on JBoss EAP 7.1:
aaa.ear
- lib
dom4j-2.1.0.jar
- sample.ejb (requires dom4j-2.1.0.jar)
- bbb.war (has persistence.xml so hibernate module is implicitly added, hibernate has as required dom4j module so it should load 1.6.1 version)
> Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11259
> URL: https://issues.jboss.org/browse/WFLY-11259
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Reporter: Adam Bialas
> Assignee: Scott Marlow
> Priority: Major
>
> I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown:
> org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> and the application fails to deploy.
> I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used.
> I created jboss-deployment-structure:
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <deployment>
> <exclusions>
> <module name="org.dom4j"/>
> </exclusions>
> </deployment>
> </jboss-deployment-structure>
> Even though I get the same exception so I suppose both jars are loaded and cause problems.
> I checked how class loading works on Wildfly 11.0.0 in comparison to JBoss EAP 7.1. In both cases this class is first loaded from provided 1.6.1 jar. JBoss does not load the newer version. However, Wildfly does and here is the problem.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months