[JBoss JIRA] (WFLY-6220) Duplicate WFLYUT0003 message in boot log
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-6220:
--------------------------------------
Summary: Duplicate WFLYUT0003 message in boot log
Key: WFLY-6220
URL: https://issues.jboss.org/browse/WFLY-6220
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: 11.0.0.Alpha1
Boot log noise:
18:06:49,739 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.16.Final starting
18:06:49,739 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.16.Final starting
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFCORE-1372) CompositeIndexProcessor::calculateModuleIndex does not respect import filters
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1372?page=com.atlassian.jira.plugi... ]
David Lloyd updated WFCORE-1372:
--------------------------------
Component/s: Server
(was: Modules)
> CompositeIndexProcessor::calculateModuleIndex does not respect import filters
> -----------------------------------------------------------------------------
>
> Key: WFCORE-1372
> URL: https://issues.jboss.org/browse/WFCORE-1372
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Alessio Soldano
> Assignee: David Lloyd
>
> I have a deployment whose manifest declares
> {noformat}Dependencies: org.foo annotations{noformat}
> What I'm trying to do with the org.foo module is basically filtering (and exposing) a subset of the org.apache.cxf.impl module. To achieve that, I have the following module.xml:
> {noformat}
> <module xmlns="urn:jboss:module:1.3" name="org.foo">
> <resources>
> </resources>
> <dependencies>
> <module name="org.apache.cxf.impl" services="import">
> <imports>
> <include path="META-INF/cxf"/>
> <include path="META-INF"/>
> <include path="org/apache/cxf/sts"/>
> <include path="org/apache/cxf/sts/**"/>
> <include path="org/apache/cxf/ws/security/sts/**"/>
> </imports>
> <exports>
> <include path="META-INF/cxf"/>
> <include path="META-INF"/>
> <include path="org/apache/cxf/sts"/>
> <include path="org/apache/cxf/sts/**"/>
> <include path="org/apache/cxf/ws/security/sts/**"/>
> </exports>
> </module>
> <module name="asm.asm" />
> <module name="javax.api" />
> <module name="javax.annotation.api" />
> <module name="javax.validation.api"/>
> <module name="javax.jms.api" />
> <module name="javax.jws.api" />
> <module name="javax.mail.api" />
> <module name="javax.resource.api" />
> <module name="javax.servlet.api" />
> <module name="javax.wsdl4j.api" />
> <module name="javax.xml.bind.api" services="import"/>
> <module name="com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider"/>
> <module name="com.sun.xml.bind" services="import"/>
> <module name="javax.xml.soap.api" />
> <module name="javax.xml.stream.api" />
> <module name="javax.xml.ws.api" />
> <module name="javax.ws.rs.api" />
> <module name="org.apache.commons.lang" />
> <module name="org.apache.httpcomponents"/>
> <module name="org.apache.neethi" />
> <module name="org.apache.velocity" />
> <module name="org.apache.xml-resolver" />
> <module name="org.apache.ws.xmlschema" />
> <module name="org.apache.ws.security" />
> <module name="org.apache.santuario.xmlsec" />
> <module name="org.codehaus.jettison" />
> <module name="org.codehaus.woodstox" />
> <module name="org.joda.time" />
> <module name="org.opensaml" />
> </dependencies>
> </module>
> {noformat}
> The problem I'm having is that the composite annotation index that's attached to my deployment includes annotations from org.apache.cxf.impl module classes that are not included in the imports/exports above.
> To me, this is due to the CompositeIndexProcessor::calculateModuleIndex(Module module) method that uses PathFilters.getDefaultImportFilter() (instead of my filters) for adding stuff to the index.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6210) Example ec2/gossip server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6210?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6210:
---------------------------------
Priority: Critical (was: Blocker)
> Example ec2/gossip server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6210
> URL: https://issues.jboss.org/browse/WFLY-6210
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 10.1.0.Final
>
>
> {noformat}
> [rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s standalone/configuration/standalone_xml_history/standalone-ha.initial.xml docs/examples/configs/standalone-ec2-ha.xml
> Files standalone/configuration/standalone_xml_history/standalone-ha.initial.xml and docs/examples/configs/standalone-ec2-ha.xml are identical
> {noformat}
> {noformat}
> [rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s standalone/configuration/standalone_xml_history/standalone-ha.initial.xml docs/examples/configs/standalone-gossip-ha.xml
> Files standalone/configuration/standalone_xml_history/standalone-ha.initial.xml and docs/examples/configs/standalone-gossip-ha.xml are identical
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6219) Example ec2/gossip server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-6219:
------------------------------------
Summary: Example ec2/gossip server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)
Key: WFLY-6219
URL: https://issues.jboss.org/browse/WFLY-6219
Project: WildFly
Issue Type: Bug
Components: Build System
Affects Versions: 10.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Blocker
Fix For: 10.1.0.Final
{noformat}
[rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s standalone/configuration/standalone_xml_history/standalone-ha.initial.xml docs/examples/configs/standalone-ec2-ha.xml
Files standalone/configuration/standalone_xml_history/standalone-ha.initial.xml and docs/examples/configs/standalone-ec2-ha.xml are identical
{noformat}
{noformat}
[rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s standalone/configuration/standalone_xml_history/standalone-ha.initial.xml docs/examples/configs/standalone-gossip-ha.xml
Files standalone/configuration/standalone_xml_history/standalone-ha.initial.xml and docs/examples/configs/standalone-gossip-ha.xml are identical
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5549) org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
by Karl Nicholas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5549?page=com.atlassian.jira.plugin.... ]
Karl Nicholas commented on WFLY-5549:
-------------------------------------
[~smarlow] Just to be clear, I did check the maven dependency tree. the dom4j was included as a dependency to the EntityManager jar. In my previous post, I listed all of the dependencies included as a result of adding EntityManager into the pom. Thanks.
> org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> ---------------------------------------------------------------------
>
> Key: WFLY-5549
> URL: https://issues.jboss.org/browse/WFLY-5549
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: carlos feria
> Assignee: Scott Marlow
>
> 10:06:35,545 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 61) MSC000001: Failed to start service jboss.persistenceunit."********": org.jboss.msc.service.StartException in service jboss.persistenceunit."*******": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:172)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:182)
> 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)
> Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97)
> at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:33)
> at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:27)
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.workWithClassLoader(ClassLoaderServiceImpl.java:342)
> at org.hibernate.internal.util.xml.XMLHelper.<init>(XMLHelper.java:26)
> at org.hibernate.envers.boot.internal.EnversServiceImpl.initialize(EnversServiceImpl.java:115)
> at org.hibernate.envers.boot.internal.AdditionalJaxbMappingProducerImpl.produceAdditionalMappings(AdditionalJaxbMappingProducerImpl.java:99)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:288)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:770)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:797)
> at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:154)
> ... 7 more
> 10:06:35,552 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "cooperativa-1.0.0.Final.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"cooperativa-1.0.0.Final.war#CooperativaPU\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"cooperativa-1.0.0.Final.war#CooperativaPU\": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory"}}
> 10:06:35,732 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "cooperativa-1.0.0.Final.war" (runtime-name : "cooperativa-1.0.0.Final.war")
> 10:06:35,733 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.persistenceunit."cooperativa-1.0.0.Final.war#CooperativaPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."cooperativa-1.0.0.Final.war#CooperativaPU": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFCORE-683) ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-683?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFCORE-683:
---------------------------------------
Assignee: Yeray Santana Borges
> ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly
> ------------------------------------------------------------------------------------------------
>
> Key: WFCORE-683
> URL: https://issues.jboss.org/browse/WFCORE-683
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.CR1
> Reporter: Brian Stansberry
> Assignee: Yeray Santana Borges
> Fix For: 3.0.0.Alpha1
>
>
> The two inner class OSHs in ModuleLoadingResourceDefinition don't deal with exceptions properly. They invoke AccessController.doPrivileged and then deal with any PrivilegedActionException by rethrowing as OperationFailedException.
> OperationFailedException represents a client mistake and is handled as such (e.g. isn't logged in the server log.) It shouldn't be thrown here unless the PrivilegedActionException.getCause() value is itself an OFE. Otherwise, the OSHs should throw a RuntimeException.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFCORE-683) ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-683?page=com.atlassian.jira.plugin... ]
Tomaz Cerar commented on WFCORE-683:
------------------------------------
instead of using reflection there is now proper api that is exposed via jmx.
example:
{code:java}
private static List<String> findResourcePaths(String moduleName) throws ModuleLoadException, ReflectiveOperationException {
ModuleLoaderMXBean loader = ModuleInfoHandler.getMxBean(Module.getCallerModuleLoader());
List<String> result = new LinkedList<>();
for (ResourceLoaderInfo rl : loader.getResourceLoaders(moduleName)){
if (rl.getLocation()!=null) {
result.add(new File(URI.create(rl.getLocation())).toString());
}
}
return result;
}
{code}
> ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly
> ------------------------------------------------------------------------------------------------
>
> Key: WFCORE-683
> URL: https://issues.jboss.org/browse/WFCORE-683
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.CR1
> Reporter: Brian Stansberry
> Fix For: 3.0.0.Alpha1
>
>
> The two inner class OSHs in ModuleLoadingResourceDefinition don't deal with exceptions properly. They invoke AccessController.doPrivileged and then deal with any PrivilegedActionException by rethrowing as OperationFailedException.
> OperationFailedException represents a client mistake and is handled as such (e.g. isn't logged in the server log.) It shouldn't be thrown here unless the PrivilegedActionException.getCause() value is itself an OFE. Otherwise, the OSHs should throw a RuntimeException.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5549) org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
by Karl Nicholas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5549?page=com.atlassian.jira.plugin.... ]
Karl Nicholas commented on WFLY-5549:
-------------------------------------
Like I said, I added entitymanager to my project myself. It's okay, I can leave it out now that I know it includes an incompatible dependency.
> org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> ---------------------------------------------------------------------
>
> Key: WFLY-5549
> URL: https://issues.jboss.org/browse/WFLY-5549
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: carlos feria
> Assignee: Scott Marlow
>
> 10:06:35,545 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 61) MSC000001: Failed to start service jboss.persistenceunit."********": org.jboss.msc.service.StartException in service jboss.persistenceunit."*******": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:172)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:182)
> 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)
> Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97)
> at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:33)
> at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:27)
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.workWithClassLoader(ClassLoaderServiceImpl.java:342)
> at org.hibernate.internal.util.xml.XMLHelper.<init>(XMLHelper.java:26)
> at org.hibernate.envers.boot.internal.EnversServiceImpl.initialize(EnversServiceImpl.java:115)
> at org.hibernate.envers.boot.internal.AdditionalJaxbMappingProducerImpl.produceAdditionalMappings(AdditionalJaxbMappingProducerImpl.java:99)
> at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:288)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:770)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:797)
> at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:154)
> ... 7 more
> 10:06:35,552 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "cooperativa-1.0.0.Final.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"cooperativa-1.0.0.Final.war#CooperativaPU\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"cooperativa-1.0.0.Final.war#CooperativaPU\": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory"}}
> 10:06:35,732 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "cooperativa-1.0.0.Final.war" (runtime-name : "cooperativa-1.0.0.Final.war")
> 10:06:35,733 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.persistenceunit."cooperativa-1.0.0.Final.war#CooperativaPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."cooperativa-1.0.0.Final.war#CooperativaPU": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months