[JBoss JIRA] (AS7-6636) CNFE when using org.apache.xerces.util.XMLCatalogResolver
by Magesh Bojan (JIRA)
[ https://issues.jboss.org/browse/AS7-6636?page=com.atlassian.jira.plugin.s... ]
Magesh Bojan updated AS7-6636:
------------------------------
Description:
CNFE is thrown when using org.apache.xerces.util.XMLCatalogResolver. The xml-resolver used by xerces seem to have not been added as a dependency in that module. Example exception:
{noformat}
aused by: java.lang.NoClassDefFoundError: org/apache/xml/resolver/readers/CatalogReader
at org.switchyard.validate.xml.XmlValidator.setupValidatingParser(XmlValidator.java:135)
at org.switchyard.validate.xml.XmlValidator.<init>(XmlValidator.java:112)
at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:39)
at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:29)
at org.switchyard.validate.ValidatorUtil.newValidators(ValidatorUtil.java:102)
at org.switchyard.validate.ValidatorRegistryLoader.registerValidators(ValidatorRegistryLoader.java:85)
at org.switchyard.deploy.internal.Deployment.registerValidators(Deployment.java:257)
at org.switchyard.deploy.internal.Deployment.doInit(Deployment.java:114)
at org.switchyard.deploy.internal.AbstractDeployment.init(AbstractDeployment.java:142)
at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:103)
at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:78)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
aused by: java.lang.ClassNotFoundException: org.apache.xml.resolver.readers.CatalogReader from [Module "org.apache.xerces:main" from local module loader @2cb49d (roots: C:\ESB\git\swyd\release\jboss-as7\standalone\dist\target\switchyard-as7-0.8\modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
... 16 more
{noformat}
The trace source can be found here https://github.com/igarashitm/core/blob/SWITCHYARD-1314/validate/src/main...
was:
CNFE is thrown when using org.apache.xerces.util.XMLCatalogResolver. The xml-resolver used by xerces seem to have not been added as a dependency in that module. Example exception:
{noformat}
Caused by: java.lang.NoClassDefFoundError: org/apache/xerces/util/XMLCatalogResolver
at org.switchyard.validate.xml.XmlValidator.setupValidatingParser(XmlValidator.java:135)
at org.switchyard.validate.xml.XmlValidator.<init>(XmlValidator.java:112)
at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:39)
at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:29)
at org.switchyard.validate.ValidatorUtil.newValidators(ValidatorUtil.java:102)
at org.switchyard.validate.ValidatorRegistryLoader.registerValidators(ValidatorRegistryLoader.java:85)
at org.switchyard.deploy.internal.Deployment.registerValidators(Deployment.java:257)
at org.switchyard.deploy.internal.Deployment.doInit(Deployment.java:114)
at org.switchyard.deploy.internal.AbstractDeployment.init(AbstractDeployment.java:142)
at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:103)
at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:78)
{noformat}
The trace source can be found here https://github.com/igarashitm/core/blob/SWITCHYARD-1314/validate/src/main...
> CNFE when using org.apache.xerces.util.XMLCatalogResolver
> ---------------------------------------------------------
>
> Key: AS7-6636
> URL: https://issues.jboss.org/browse/AS7-6636
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.1.Final
> Reporter: Magesh Bojan
>
> CNFE is thrown when using org.apache.xerces.util.XMLCatalogResolver. The xml-resolver used by xerces seem to have not been added as a dependency in that module. Example exception:
> {noformat}
> aused by: java.lang.NoClassDefFoundError: org/apache/xml/resolver/readers/CatalogReader
> at org.switchyard.validate.xml.XmlValidator.setupValidatingParser(XmlValidator.java:135)
> at org.switchyard.validate.xml.XmlValidator.<init>(XmlValidator.java:112)
> at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:39)
> at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:29)
> at org.switchyard.validate.ValidatorUtil.newValidators(ValidatorUtil.java:102)
> at org.switchyard.validate.ValidatorRegistryLoader.registerValidators(ValidatorRegistryLoader.java:85)
> at org.switchyard.deploy.internal.Deployment.registerValidators(Deployment.java:257)
> at org.switchyard.deploy.internal.Deployment.doInit(Deployment.java:114)
> at org.switchyard.deploy.internal.AbstractDeployment.init(AbstractDeployment.java:142)
> at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:103)
> at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:78)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> aused by: java.lang.ClassNotFoundException: org.apache.xml.resolver.readers.CatalogReader from [Module "org.apache.xerces:main" from local module loader @2cb49d (roots: C:\ESB\git\swyd\release\jboss-as7\standalone\dist\target\switchyard-as7-0.8\modules)]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> ... 16 more
> {noformat}
> The trace source can be found here https://github.com/igarashitm/core/blob/SWITCHYARD-1314/validate/src/main...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6619) Management API for Datasources subsystem is missing some properties
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/AS7-6619?page=com.atlassian.jira.plugin.s... ]
Stefano Maestri commented on AS7-6619:
--------------------------------------
In fact the opertion was not working at all from cli because input parameter's metadata was missing too
> Management API for Datasources subsystem is missing some properties
> -------------------------------------------------------------------
>
> Key: AS7-6619
> URL: https://issues.jboss.org/browse/AS7-6619
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.2.0.Alpha1
> Reporter: Zbyněk Roubalík
> Assignee: Stefano Maestri
>
> Some properties which were present in previous versions of AS7 are missing in current release:
> Parameter driver-name for operation 'get-installed-driver' is no longer available.
> These value-type for 'reply-properties' for operation 'get-installed-driver' are no longer available: [jdbc-compliant, module-slot, driver-class-name, driver-module-name]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6636) CNFE when using org.apache.xerces.util.XMLCatalogResolver
by Magesh Bojan (JIRA)
Magesh Bojan created AS7-6636:
---------------------------------
Summary: CNFE when using org.apache.xerces.util.XMLCatalogResolver
Key: AS7-6636
URL: https://issues.jboss.org/browse/AS7-6636
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Magesh Bojan
CNFE is thrown when using org.apache.xerces.util.XMLCatalogResolver. The xml-resolver used by xerces seem to have not been added as a dependency in that module. Example exception:
{noformat}
Caused by: java.lang.NoClassDefFoundError: org/apache/xerces/util/XMLCatalogResolver
at org.switchyard.validate.xml.XmlValidator.setupValidatingParser(XmlValidator.java:135)
at org.switchyard.validate.xml.XmlValidator.<init>(XmlValidator.java:112)
at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:39)
at org.switchyard.validate.xml.XmlValidatorFactory.newValidator(XmlValidatorFactory.java:29)
at org.switchyard.validate.ValidatorUtil.newValidators(ValidatorUtil.java:102)
at org.switchyard.validate.ValidatorRegistryLoader.registerValidators(ValidatorRegistryLoader.java:85)
at org.switchyard.deploy.internal.Deployment.registerValidators(Deployment.java:257)
at org.switchyard.deploy.internal.Deployment.doInit(Deployment.java:114)
at org.switchyard.deploy.internal.AbstractDeployment.init(AbstractDeployment.java:142)
at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:103)
at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:78)
{noformat}
The trace source can be found here https://github.com/igarashitm/core/blob/SWITCHYARD-1314/validate/src/main...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6565) single jdbc driver deployed inside ear takes name of ear
by Tom Eicher (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
Tom Eicher commented on AS7-6565:
---------------------------------
Considerung that trunk is now AS8, is it really so important to keep the backwards compatible behaviour of having a (single) JDBC driver being named {{myApplicationName.ear}} ?
To me, this just feels wrong and unnecessary obscure.
Less obvious wrong things have been changed between major versions...
> single jdbc driver deployed inside ear takes name of ear
> --------------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JCA
> Affects Versions: 7.1.1.Final, 8.0.0.Alpha1
> Reporter: Tom Eicher
> Assignee: Stefano Maestri
>
> We need to always give service name for jdbdriver as
> {code}
> deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion
> {code}
> even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names.
> Original description was:
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6565) single jdbc driver deployed inside ear takes name of ear
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
Stefano Maestri commented on AS7-6565:
--------------------------------------
Keeping backward compatibility as main goal I think the best thing is to revert these changes and reject the bug. In fact the issue Tom has outlined for multiple driver inside same ear wasn't a problem also in old code. Let me sum up how old code worked:
1) deployed driver take the name of jar containing them if deployed as jar
2) driver take the ear name if and only if the ear contain just one driver.
3) driver take a name composed of ear name and driver name if ear contain more than one driver
And note that what you are asking to log in server.log is in fact covered by a the dedicated DMR operation :installed-drivers-list.
Any comments are welcome.
> single jdbc driver deployed inside ear takes name of ear
> --------------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JCA
> Affects Versions: 7.1.1.Final, 8.0.0.Alpha1
> Reporter: Tom Eicher
> Assignee: Stefano Maestri
>
> We need to always give service name for jdbdriver as
> {code}
> deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion
> {code}
> even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names.
> Original description was:
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6511) Investigate OSGi test failures after MSC upgrade to 1.1.1.Final
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6511?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on AS7-6511:
-------------------------------------
Please disable the failing tests. I can look at this in approx three weeks time (i.e. when R5 is done)
> Investigate OSGi test failures after MSC upgrade to 1.1.1.Final
> ---------------------------------------------------------------
>
> Key: AS7-6511
> URL: https://issues.jboss.org/browse/AS7-6511
> Project: Application Server 7
> Issue Type: Task
> Components: OSGi
> Environment: Tested on (not able to reproduce)
> ---
> [blackhole][/home/opalka/git/jboss-as/trunk]>java -version
> java version "1.6.0_38"
> Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)
> ---
> [blackhole][/home/opalka/git/jboss-as/trunk]>mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /home/opalka/java/maven/3.0.4
> Java version: 1.6.0_38, vendor: Sun Microsystems Inc.
> Java home: /home/opalka/java/jdk/orcl/jdk1.6.0_38/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.7.6-201.fc18.x86_64", arch: "amd64", family: "unix"
> ---
> [blackhole][/home/opalka/git/jboss-as/trunk]>uname -a
> Linux blackhole 3.7.6-201.fc18.x86_64 #1 SMP Mon Feb 4 15:54:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Richard Opalka
> Assignee: Thomas Diesler
> Priority: Blocker
> Fix For: 7.3.0.Alpha1
>
>
> I did my best to reproduce this issue but I'm not able to reproduce it locally:( It doesn't matter if I run whole test suite or just this test, the
> test is always passing for me. Since OSGi is not my domain, I'm assigning
> this issue to OSGi team. This bug is related to this PR:
> https://github.com/jbossas/jboss-as/pull/4052
> I'm temporarily disabling the failing test (the purpose of this JIRA).
> Failing test is:
> [INFO] Surefire report directory: /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/osgi/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> ...
> Results :
> Failed tests: testFailStartLevel(org.jboss.as.test.integration.osgi.deployment.DeferredResolveTestCase): Bundle ACTIVE expected:<32> but was:<4>
> Tests run: 120, Failures: 1, Errors: 0, Skipped: 6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6629) Deployment classloader leak in Infinispan integration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6629?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6629:
----------------------------------
Fix Version/s: (was: 7.2.0.Alpha1)
Work on 7.2.0.Alpha1 is done.
> Deployment classloader leak in Infinispan integration
> -----------------------------------------------------
>
> Key: AS7-6629
> URL: https://issues.jboss.org/browse/AS7-6629
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Fedora 17, Oracle JDK's 7u9 & 7u15, Bundled hibernate 3 JPA deployment
> Reporter: Brent Douglas
> Assignee: Paul Ferraro
> Labels: classloader, infinispan, leak
> Fix For: 8.0.0.Alpha1
>
> Attachments: infinispan-leak.png
>
>
> The AS7 infinispan integration module leaks references to an undeployed deployment's classloader through the DefaultCacheManager provided from EmbeddedCacheManagerService.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months