[JBoss JIRA] (WFLY-762) Add schema references to standalone.xml, domain.xml, host.xml
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-762?page=com.atlassian.jira.plugin.s... ]
jaikiran pai commented on WFLY-762:
-----------------------------------
Each subsystem has its own set of parsers for each version of the schema. Those parsers have the knowledge of what's supported and what's not supported as elements and attributes. Note that this _isn't_ the kind of validation that I think you have in mind. These parsers *do not* read a xsd and then compare the xml. These parsers just have the knowledge of what's supposed to be there for that specific schema version. Take a look at the EJB3 subsystem 2.0 schema version parser for example https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo...
> Add schema references to standalone.xml, domain.xml, host.xml
> -------------------------------------------------------------
>
> Key: WFLY-762
> URL: https://issues.jboss.org/browse/WFLY-762
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Reporter: Gerry Matte
> Labels: domain, host, standalone, xml, xmlns
> Fix For: Awaiting Volunteers
>
>
> It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features.
> It seems quite surprising to me that these files do not have the schema references identified in the file header. Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues.
> I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users. A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on.
> Personally I favor having a switch that turns off validation - to be used on production servers only.
> If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attempted to use an out-of-date version when upgrading to a new version of JBoss AS 7.
> http://www.jboss.org/schema/jbossas/
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (WFLY-762) Add schema references to standalone.xml, domain.xml, host.xml
by Prashant Srivastava (JIRA)
[ https://issues.jboss.org/browse/WFLY-762?page=com.atlassian.jira.plugin.s... ]
Prashant Srivastava commented on WFLY-762:
------------------------------------------
Hi Jason,
I read your comment that your parsing code takes care of the schema validation on boot.Can you please tell me what modules etc. from jboss souce do I have to use if I want to do some thing similar on the fly.I am generating the server standalone.xml dynamically through code and the requirement is to validate it against the whole bunch of xsds.
> Add schema references to standalone.xml, domain.xml, host.xml
> -------------------------------------------------------------
>
> Key: WFLY-762
> URL: https://issues.jboss.org/browse/WFLY-762
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Reporter: Gerry Matte
> Labels: domain, host, standalone, xml, xmlns
> Fix For: Awaiting Volunteers
>
>
> It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features.
> It seems quite surprising to me that these files do not have the schema references identified in the file header. Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues.
> I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users. A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on.
> Personally I favor having a switch that turns off validation - to be used on production servers only.
> If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attempted to use an out-of-date version when upgrading to a new version of JBoss AS 7.
> http://www.jboss.org/schema/jbossas/
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (WFLY-1420) Upgrade Narayana to 5.0.0.M3
by Paul Robinson (JIRA)
Paul Robinson created WFLY-1420:
-----------------------------------
Summary: Upgrade Narayana to 5.0.0.M3
Key: WFLY-1420
URL: https://issues.jboss.org/browse/WFLY-1420
Project: WildFly
Issue Type: Component Upgrade
Components: Transactions
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 8.0.0.Alpha2
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (WFLY-1367) 4 version numbers exist for Narayana in pom.xml, despite only needing 1
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-1367?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated WFLY-1367:
--------------------------------
Description:
There are 4 different version properties for Narayana in WildFly, despite each component that uses the variable being released together (i.e. it's not possible to get a situation where the values of these versions differ).
{code} <version.org.jboss.jbossts.jbossjts>5.0.0.M2/version.org.jboss.jbossts.jbossjts>
<version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration>
<version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts>
<version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana>
{code}
As well as being messy, error-prone and more effort to change; it's also caused us a merge conflict (JBTM-1691) that didn't auto-merge correctly.
One version called "version.org.jboss.narayana" would make most sense.
was:
There are 5 different version properties for Narayana in WildFly, despite each component that uses the variable being released together (i.e. it's not possible to get a situation where the values of these versions differ).
{code} <version.org.jboss.jbossts.jbossjts>5.0.0.M2/version.org.jboss.jbossts.jbossjts>
<version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration>
<version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts>
<version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana>
{code}
As well as being messy, error-prone and more effort to change; it's also caused us a merge conflict (JBTM-1691) that didn't auto-merge correctly.
One version called "version.org.jboss.narayana" would make most sense.
> 4 version numbers exist for Narayana in pom.xml, despite only needing 1
> -----------------------------------------------------------------------
>
> Key: WFLY-1367
> URL: https://issues.jboss.org/browse/WFLY-1367
> Project: WildFly
> Issue Type: Bug
> Components: Build System, Transactions
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 8.0.0.Alpha2
>
>
> There are 4 different version properties for Narayana in WildFly, despite each component that uses the variable being released together (i.e. it's not possible to get a situation where the values of these versions differ).
> {code} <version.org.jboss.jbossts.jbossjts>5.0.0.M2/version.org.jboss.jbossts.jbossjts>
> <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration>
> <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts>
> <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana>
> {code}
> As well as being messy, error-prone and more effort to change; it's also caused us a merge conflict (JBTM-1691) that didn't auto-merge correctly.
> One version called "version.org.jboss.narayana" would make most sense.
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (WFLY-1367) 4 version numbers exist for Narayana in pom.xml, despite only needing 1
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-1367?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated WFLY-1367:
--------------------------------
Summary: 4 version numbers exist for Narayana in pom.xml, despite only needing 1 (was: 5 version numbers exist for Narayana in pom.xml, despite only needing 1)
> 4 version numbers exist for Narayana in pom.xml, despite only needing 1
> -----------------------------------------------------------------------
>
> Key: WFLY-1367
> URL: https://issues.jboss.org/browse/WFLY-1367
> Project: WildFly
> Issue Type: Bug
> Components: Build System, Transactions
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 8.0.0.Alpha2
>
>
> There are 5 different version properties for Narayana in WildFly, despite each component that uses the variable being released together (i.e. it's not possible to get a situation where the values of these versions differ).
> {code} <version.org.jboss.jbossts.jbossjts>5.0.0.M2/version.org.jboss.jbossts.jbossjts>
> <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration>
> <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts>
> <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana>
> {code}
> As well as being messy, error-prone and more effort to change; it's also caused us a merge conflict (JBTM-1691) that didn't auto-merge correctly.
> One version called "version.org.jboss.narayana" would make most sense.
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (WFLY-788) Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
by Vincent Massol (JIRA)
[ https://issues.jboss.org/browse/WFLY-788?page=com.atlassian.jira.plugin.s... ]
Vincent Massol commented on WFLY-788:
-------------------------------------
Is there a way to tell wildfly to not stop the deployment on error like this one and just to ignore invalid paths?
> Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
> -------------------------------------------------------------------
>
> Key: WFLY-788
> URL: https://issues.jboss.org/browse/WFLY-788
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Environment: Software
> Linux debian 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)
> Eclipse Java EE IDE for Web Developers.
> Version: Indigo Service Release 1
> Build id: 20110916-0149
> JBoss Tools 3.3 (Indigo)
> Hardware
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
> stepping : 11
> cpu MHz : 2660.399
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> apicid : 0
> initial apicid : 0
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3
> cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5320.79
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
> stepping : 11
> cpu MHz : 2660.399
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 1
> cpu cores : 2
> apicid : 1
> initial apicid : 1
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> Reporter: Roberto Requena
> Assignee: David Lloyd
> Labels: jboss
>
> When I try to deploy a .EAR project on the server with the following files "juh-3.2.1.jar" and "jurt-3.2.1.jar" contained in the web project lib folder, the server displays the following error:
> {noformat}
> WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
> 09:31:13,183 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
> 09:31:13,424 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
> 09:31:13,498 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
> 09:31:14,836 INFO [org.xnio] XNIO Version 3.0.3.GA
> 09:31:14,849 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
> 09:31:14,860 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
> 09:31:14,879 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
> 09:31:14,950 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
> 09:31:14,970 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
> 09:31:15,010 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 09:31:15,062 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
> 09:31:15,082 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 09:31:15,106 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
> 09:31:15,156 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
> 09:31:15,178 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
> 09:31:15,190 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
> 09:31:15,217 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
> 09:31:15,231 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 09:31:15,259 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 09:31:15,531 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
> 09:31:15,582 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Arrancando Coyote HTTP/1.1 en puerto http--127.0.0.1-8080
> 09:31:16,144 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 09:31:16,306 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
> 09:31:16,308 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
> 09:31:16,325 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment TestDeploy.ear
> 09:31:16,329 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments
> 09:31:16,342 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015002: Deployment of 'Download.war' requested, but the deployment is not present
> 09:31:16,343 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found Prueba-ear.ear in deployment directory. To trigger deployment create a file called Prueba-ear.ear.dodeploy
> 09:31:16,344 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TestDeploy.ear in deployment directory. To trigger deployment create a file called TestDeploy.ear.dodeploy
> 09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "Prueba-ear.ear"
> 09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "TestDeploy.ear"
> 09:31:16,690 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "TestDeployWeb.war"
> 09:31:16,722 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-ejb-0.0.1-SNAPSHOT.jar"
> 09:31:16,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-web-0.0.1-SNAPSHOT.war"
> 09:31:16,857 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry ridl.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
> 09:31:16,858 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jurt.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
> 09:31:16,871 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> 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]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.createAdditionalModule(ManifestClassPathProcessor.java:193) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.handlingExistingClassPathEntry(ManifestClassPathProcessor.java:185) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:162) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> 09:31:17,113 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for primary
> 09:31:17,188 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment Prueba-ear.ear
> 09:31:17,272 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment Prueba-ejb-0.0.1-SNAPSHOT.jar
> 09:31:17,274 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment Prueba-web-0.0.1-SNAPSHOT.war
> 09:31:17,287 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named MemberRegistration in deployment unit subdeployment "Prueba-ejb-0.0.1-SNAPSHOT.jar" of deployment "Prueba-ear.ear" are as follows:
> java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
> java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
> java:module/MemberRegistration!org.prueba.controller.MemberRegistration
> java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
> java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
> java:module/MemberRegistration
> 09:31:17,310 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting Services for CDI deployment: Prueba-ear.ear
> 09:31:17,343 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900 1.1.5 (AS71)
> 09:31:17,631 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011402: Starting Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
> 09:31:17,766 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-2) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 09:31:17,777 INFO [org.hibernate.Version] (MSC service thread 1-2) HHH000412: Hibernate Core {4.0.1.Final}
> 09:31:17,779 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000206: hibernate.properties not found
> 09:31:17,792 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000021: Bytecode provider name : javassist
> 09:31:17,809 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 09:31:17,963 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-2) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 09:31:18,282 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-2) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 09:31:18,287 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-2) HHH000431: Unable to determine H2 database version, certain features may not work
> 09:31:18,290 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-2) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
> 09:31:18,300 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-2) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 09:31:18,304 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-2) HHH000397: Using ASTQueryTranslatorFactory
> 09:31:18,377 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final
> 09:31:18,689 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000227: Running hbm2ddl schema export
> 09:31:18,703 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000389: Unsuccessful: drop sequence hibernate_sequence
> 09:31:18,704 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) Sequence "HIBERNATE_SEQUENCE" no encontrado
> Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
> drop sequence hibernate_sequence [90036-161]
> 09:31:18,708 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000230: Schema export complete
> 09:31:18,732 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment Prueba-ear.ear
> 09:31:19,130 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Inicializando Mojarra 2.1.7-jbossorg-1 (20120227-1401) para el contexto '/Prueba-web'
> 09:31:20,124 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /Prueba-web
> 09:31:20,133 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 09:31:20,133 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7241ms - Started 243 of 326 services (2 services failed or missing dependencies, 80 services are passive or on-demand)
> 09:31:20,334 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "Prueba-ear.ear" was rolled back with no failure message
> 09:31:20,335 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestDeploy.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}
> 09:31:20,355 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment TestDeployWeb.war in 19ms
> 09:31:20,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment TestDeploy.ear in 29ms
> 09:31:20,372 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment Prueba-ear.ear
> 09:31:20,381 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
> 09:31:20,382 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export
> 09:31:20,386 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete
> 09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment Prueba-ejb-0.0.1-SNAPSHOT.jar in 63ms
> 09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment Prueba-web-0.0.1-SNAPSHOT.war in 64ms
> 09:31:20,402 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment Prueba-ear.ear in 67ms
> 09:31:20,403 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
> 09:31:20,406 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}}}
> 09:31:20,407 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
> {noformat}
> I could see that causing the error are claspath declared in MANIFEST.MF files of these .jar files because they contain relative paths.
> {noformat}
> juh-3.2.1.jar
> Manifest-Version: 1.0
> Class-Path: ridl.jar jurt.jar ../../lib/ ../bin/
> {noformat}
> {noformat}
> jurt-3.2.1.jar
> Manifest-Version: 1.0
> Class-Path: ridl.jar unoloader.jar ../../lib/ ../bin/
> {noformat}
> Also I could see two things:
> # When I deploy only the Web project on the server containing these .jar files the error does not occur.
> # And If I remove the contents of the MANIFEST.MF file and deploying the .ear project the error does not occur.
> I have a .EAR project for test that demonstrates the error, but did not see any option to attach files. If you wish, tell me how to send them.
> Any other thing that I can help to order. I want to use to thank Stephen Coy and Tomaz Cerar for help.
> Thanks and sorry for my English
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (WFLY-788) Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
by Vincent Massol (JIRA)
[ https://issues.jboss.org/browse/WFLY-788?page=com.atlassian.jira.plugin.s... ]
Vincent Massol commented on WFLY-788:
-------------------------------------
Also note that this issue impacts us at XWiki: http://jira.xwiki.org/browse/XE-1302
> Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
> -------------------------------------------------------------------
>
> Key: WFLY-788
> URL: https://issues.jboss.org/browse/WFLY-788
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Environment: Software
> Linux debian 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)
> Eclipse Java EE IDE for Web Developers.
> Version: Indigo Service Release 1
> Build id: 20110916-0149
> JBoss Tools 3.3 (Indigo)
> Hardware
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
> stepping : 11
> cpu MHz : 2660.399
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> apicid : 0
> initial apicid : 0
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3
> cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5320.79
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
> stepping : 11
> cpu MHz : 2660.399
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 1
> cpu cores : 2
> apicid : 1
> initial apicid : 1
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> Reporter: Roberto Requena
> Assignee: David Lloyd
> Labels: jboss
>
> When I try to deploy a .EAR project on the server with the following files "juh-3.2.1.jar" and "jurt-3.2.1.jar" contained in the web project lib folder, the server displays the following error:
> {noformat}
> WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
> 09:31:13,183 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
> 09:31:13,424 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
> 09:31:13,498 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
> 09:31:14,836 INFO [org.xnio] XNIO Version 3.0.3.GA
> 09:31:14,849 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
> 09:31:14,860 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
> 09:31:14,879 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
> 09:31:14,950 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
> 09:31:14,970 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
> 09:31:15,010 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 09:31:15,062 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
> 09:31:15,082 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 09:31:15,106 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
> 09:31:15,156 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
> 09:31:15,178 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
> 09:31:15,190 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
> 09:31:15,217 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
> 09:31:15,231 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 09:31:15,259 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 09:31:15,531 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
> 09:31:15,582 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Arrancando Coyote HTTP/1.1 en puerto http--127.0.0.1-8080
> 09:31:16,144 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 09:31:16,306 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
> 09:31:16,308 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
> 09:31:16,325 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment TestDeploy.ear
> 09:31:16,329 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments
> 09:31:16,342 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015002: Deployment of 'Download.war' requested, but the deployment is not present
> 09:31:16,343 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found Prueba-ear.ear in deployment directory. To trigger deployment create a file called Prueba-ear.ear.dodeploy
> 09:31:16,344 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TestDeploy.ear in deployment directory. To trigger deployment create a file called TestDeploy.ear.dodeploy
> 09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "Prueba-ear.ear"
> 09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "TestDeploy.ear"
> 09:31:16,690 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "TestDeployWeb.war"
> 09:31:16,722 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-ejb-0.0.1-SNAPSHOT.jar"
> 09:31:16,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-web-0.0.1-SNAPSHOT.war"
> 09:31:16,857 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry ridl.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
> 09:31:16,858 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jurt.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
> 09:31:16,871 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> 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]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.createAdditionalModule(ManifestClassPathProcessor.java:193) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.handlingExistingClassPathEntry(ManifestClassPathProcessor.java:185) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:162) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> 09:31:17,113 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for primary
> 09:31:17,188 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment Prueba-ear.ear
> 09:31:17,272 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment Prueba-ejb-0.0.1-SNAPSHOT.jar
> 09:31:17,274 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment Prueba-web-0.0.1-SNAPSHOT.war
> 09:31:17,287 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named MemberRegistration in deployment unit subdeployment "Prueba-ejb-0.0.1-SNAPSHOT.jar" of deployment "Prueba-ear.ear" are as follows:
> java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
> java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
> java:module/MemberRegistration!org.prueba.controller.MemberRegistration
> java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
> java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
> java:module/MemberRegistration
> 09:31:17,310 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting Services for CDI deployment: Prueba-ear.ear
> 09:31:17,343 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900 1.1.5 (AS71)
> 09:31:17,631 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011402: Starting Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
> 09:31:17,766 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-2) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 09:31:17,777 INFO [org.hibernate.Version] (MSC service thread 1-2) HHH000412: Hibernate Core {4.0.1.Final}
> 09:31:17,779 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000206: hibernate.properties not found
> 09:31:17,792 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000021: Bytecode provider name : javassist
> 09:31:17,809 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 09:31:17,963 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-2) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 09:31:18,282 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-2) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 09:31:18,287 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-2) HHH000431: Unable to determine H2 database version, certain features may not work
> 09:31:18,290 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-2) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
> 09:31:18,300 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-2) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 09:31:18,304 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-2) HHH000397: Using ASTQueryTranslatorFactory
> 09:31:18,377 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final
> 09:31:18,689 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000227: Running hbm2ddl schema export
> 09:31:18,703 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000389: Unsuccessful: drop sequence hibernate_sequence
> 09:31:18,704 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) Sequence "HIBERNATE_SEQUENCE" no encontrado
> Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
> drop sequence hibernate_sequence [90036-161]
> 09:31:18,708 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000230: Schema export complete
> 09:31:18,732 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment Prueba-ear.ear
> 09:31:19,130 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Inicializando Mojarra 2.1.7-jbossorg-1 (20120227-1401) para el contexto '/Prueba-web'
> 09:31:20,124 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /Prueba-web
> 09:31:20,133 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 09:31:20,133 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7241ms - Started 243 of 326 services (2 services failed or missing dependencies, 80 services are passive or on-demand)
> 09:31:20,334 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "Prueba-ear.ear" was rolled back with no failure message
> 09:31:20,335 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestDeploy.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}
> 09:31:20,355 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment TestDeployWeb.war in 19ms
> 09:31:20,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment TestDeploy.ear in 29ms
> 09:31:20,372 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment Prueba-ear.ear
> 09:31:20,381 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
> 09:31:20,382 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export
> 09:31:20,386 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete
> 09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment Prueba-ejb-0.0.1-SNAPSHOT.jar in 63ms
> 09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment Prueba-web-0.0.1-SNAPSHOT.war in 64ms
> 09:31:20,402 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment Prueba-ear.ear in 67ms
> 09:31:20,403 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
> 09:31:20,406 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}}}
> 09:31:20,407 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
> {noformat}
> I could see that causing the error are claspath declared in MANIFEST.MF files of these .jar files because they contain relative paths.
> {noformat}
> juh-3.2.1.jar
> Manifest-Version: 1.0
> Class-Path: ridl.jar jurt.jar ../../lib/ ../bin/
> {noformat}
> {noformat}
> jurt-3.2.1.jar
> Manifest-Version: 1.0
> Class-Path: ridl.jar unoloader.jar ../../lib/ ../bin/
> {noformat}
> Also I could see two things:
> # When I deploy only the Web project on the server containing these .jar files the error does not occur.
> # And If I remove the contents of the MANIFEST.MF file and deploying the .ear project the error does not occur.
> I have a .EAR project for test that demonstrates the error, but did not see any option to attach files. If you wish, tell me how to send them.
> Any other thing that I can help to order. I want to use to thank Stephen Coy and Tomaz Cerar for help.
> Thanks and sorry for my English
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (WFLY-788) Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
by Vincent Massol (JIRA)
[ https://issues.jboss.org/browse/WFLY-788?page=com.atlassian.jira.plugin.s... ]
Vincent Massol commented on WFLY-788:
-------------------------------------
FTR I've raised https://issues.apache.org/ooo/show_bug.cgi?id=122424 (not sure I entered it in the right place though...)
> Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
> -------------------------------------------------------------------
>
> Key: WFLY-788
> URL: https://issues.jboss.org/browse/WFLY-788
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Environment: Software
> Linux debian 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)
> Eclipse Java EE IDE for Web Developers.
> Version: Indigo Service Release 1
> Build id: 20110916-0149
> JBoss Tools 3.3 (Indigo)
> Hardware
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
> stepping : 11
> cpu MHz : 2660.399
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> apicid : 0
> initial apicid : 0
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3
> cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5320.79
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
> stepping : 11
> cpu MHz : 2660.399
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 1
> cpu cores : 2
> apicid : 1
> initial apicid : 1
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> Reporter: Roberto Requena
> Assignee: David Lloyd
> Labels: jboss
>
> When I try to deploy a .EAR project on the server with the following files "juh-3.2.1.jar" and "jurt-3.2.1.jar" contained in the web project lib folder, the server displays the following error:
> {noformat}
> WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
> 09:31:13,183 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
> 09:31:13,424 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
> 09:31:13,498 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
> 09:31:14,836 INFO [org.xnio] XNIO Version 3.0.3.GA
> 09:31:14,849 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
> 09:31:14,860 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
> 09:31:14,879 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
> 09:31:14,950 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
> 09:31:14,970 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
> 09:31:15,010 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> 09:31:15,062 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
> 09:31:15,082 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 09:31:15,106 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
> 09:31:15,156 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
> 09:31:15,178 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
> 09:31:15,190 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
> 09:31:15,217 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
> 09:31:15,231 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 09:31:15,259 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
> 09:31:15,531 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
> 09:31:15,582 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Arrancando Coyote HTTP/1.1 en puerto http--127.0.0.1-8080
> 09:31:16,144 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 09:31:16,306 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
> 09:31:16,308 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
> 09:31:16,325 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment TestDeploy.ear
> 09:31:16,329 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments
> 09:31:16,342 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015002: Deployment of 'Download.war' requested, but the deployment is not present
> 09:31:16,343 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found Prueba-ear.ear in deployment directory. To trigger deployment create a file called Prueba-ear.ear.dodeploy
> 09:31:16,344 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TestDeploy.ear in deployment directory. To trigger deployment create a file called TestDeploy.ear.dodeploy
> 09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "Prueba-ear.ear"
> 09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "TestDeploy.ear"
> 09:31:16,690 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "TestDeployWeb.war"
> 09:31:16,722 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-ejb-0.0.1-SNAPSHOT.jar"
> 09:31:16,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-web-0.0.1-SNAPSHOT.war"
> 09:31:16,857 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry ridl.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
> 09:31:16,858 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jurt.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
> 09:31:16,871 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> 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]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.createAdditionalModule(ManifestClassPathProcessor.java:193) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.handlingExistingClassPathEntry(ManifestClassPathProcessor.java:185) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:162) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> 09:31:17,113 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for primary
> 09:31:17,188 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment Prueba-ear.ear
> 09:31:17,272 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment Prueba-ejb-0.0.1-SNAPSHOT.jar
> 09:31:17,274 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment Prueba-web-0.0.1-SNAPSHOT.war
> 09:31:17,287 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named MemberRegistration in deployment unit subdeployment "Prueba-ejb-0.0.1-SNAPSHOT.jar" of deployment "Prueba-ear.ear" are as follows:
> java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
> java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
> java:module/MemberRegistration!org.prueba.controller.MemberRegistration
> java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
> java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
> java:module/MemberRegistration
> 09:31:17,310 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting Services for CDI deployment: Prueba-ear.ear
> 09:31:17,343 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900 1.1.5 (AS71)
> 09:31:17,631 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011402: Starting Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
> 09:31:17,766 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-2) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 09:31:17,777 INFO [org.hibernate.Version] (MSC service thread 1-2) HHH000412: Hibernate Core {4.0.1.Final}
> 09:31:17,779 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000206: hibernate.properties not found
> 09:31:17,792 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000021: Bytecode provider name : javassist
> 09:31:17,809 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 09:31:17,963 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-2) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 09:31:18,282 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-2) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 09:31:18,287 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-2) HHH000431: Unable to determine H2 database version, certain features may not work
> 09:31:18,290 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-2) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
> 09:31:18,300 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-2) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 09:31:18,304 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-2) HHH000397: Using ASTQueryTranslatorFactory
> 09:31:18,377 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final
> 09:31:18,689 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000227: Running hbm2ddl schema export
> 09:31:18,703 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000389: Unsuccessful: drop sequence hibernate_sequence
> 09:31:18,704 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) Sequence "HIBERNATE_SEQUENCE" no encontrado
> Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
> drop sequence hibernate_sequence [90036-161]
> 09:31:18,708 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000230: Schema export complete
> 09:31:18,732 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment Prueba-ear.ear
> 09:31:19,130 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Inicializando Mojarra 2.1.7-jbossorg-1 (20120227-1401) para el contexto '/Prueba-web'
> 09:31:20,124 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /Prueba-web
> 09:31:20,133 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 09:31:20,133 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7241ms - Started 243 of 326 services (2 services failed or missing dependencies, 80 services are passive or on-demand)
> 09:31:20,334 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "Prueba-ear.ear" was rolled back with no failure message
> 09:31:20,335 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestDeploy.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}
> 09:31:20,355 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment TestDeployWeb.war in 19ms
> 09:31:20,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment TestDeploy.ear in 29ms
> 09:31:20,372 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment Prueba-ear.ear
> 09:31:20,381 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
> 09:31:20,382 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export
> 09:31:20,386 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete
> 09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment Prueba-ejb-0.0.1-SNAPSHOT.jar in 63ms
> 09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment Prueba-web-0.0.1-SNAPSHOT.war in 64ms
> 09:31:20,402 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment Prueba-ear.ear in 67ms
> 09:31:20,403 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
> 09:31:20,406 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}}}
> 09:31:20,407 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
> {noformat}
> I could see that causing the error are claspath declared in MANIFEST.MF files of these .jar files because they contain relative paths.
> {noformat}
> juh-3.2.1.jar
> Manifest-Version: 1.0
> Class-Path: ridl.jar jurt.jar ../../lib/ ../bin/
> {noformat}
> {noformat}
> jurt-3.2.1.jar
> Manifest-Version: 1.0
> Class-Path: ridl.jar unoloader.jar ../../lib/ ../bin/
> {noformat}
> Also I could see two things:
> # When I deploy only the Web project on the server containing these .jar files the error does not occur.
> # And If I remove the contents of the MANIFEST.MF file and deploying the .ear project the error does not occur.
> I have a .EAR project for test that demonstrates the error, but did not see any option to attach files. If you wish, tell me how to send them.
> Any other thing that I can help to order. I want to use to thank Stephen Coy and Tomaz Cerar for help.
> Thanks and sorry for my English
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (AS7-887) Support legacy ServiceMBeans in SAR deployments
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy... ]
jaikiran pai commented on AS7-887:
----------------------------------
>> Sorry I am bothing you as I dont have support and I have to stick to EAP 6.0.1.
EAP 6.0.1 binary is a paid product and you are entitled to support. Where did you get it from? You might want to check with your team to see who has access to the customer service portal.
>> We are migrating app from Websphere to Jboss 6.0.1 EAP. We have websphere's workmanager feature which needs to be migrate using commonj. I tried to foo-commonj.sar to make use of workmanager features from ejb in Jboss 6.0.1 EAP. I used previous versions support jars to register commonj jndi in Jboss 6.0.1 EAP.
You already created 2 other JIRAs to ask that question. Please do use the JIRAs for such questions. The user forums are the place where this should be discussed.
> Support legacy ServiceMBeans in SAR deployments
> -----------------------------------------------
>
> Key: AS7-887
> URL: https://issues.jboss.org/browse/AS7-887
> Project: Application Server 7
> Issue Type: Enhancement
> Components: JMX
> Reporter: Matt Drees
> Assignee: Eduardo Martins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
>
> It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore.
> Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore.
--
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
10 years, 11 months
- 1
- 0
[JBoss JIRA] (JASSIST-188) CtClass detach does not completely clean class from pool.
by Shigeru Chiba (JIRA)
[ https://issues.jboss.org/browse/JASSIST-188?page=com.atlassian.jira.plugi... ]
Shigeru Chiba resolved JASSIST-188.
-----------------------------------
Fix Version/s: 3.18.0-GA
Resolution: Done
> CtClass detach does not completely clean class from pool.
> ---------------------------------------------------------
>
> Key: JASSIST-188
> URL: https://issues.jboss.org/browse/JASSIST-188
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.17.0-GA
> Environment: Ubuntu, Windows, JDK 1.6/1.7
> Reporter: J D
> Assignee: Shigeru Chiba
> Priority: Critical
> Fix For: 3.18.0-GA
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Description:
> Class with same qualified name cannot be recreated even if previous class was detached successfully from pool.
> Creation#1: Consider class eg.foo.MyClass is created using default pool and private int myArg1 private member along with some getter/setter methods. After its creation, the CtClass.detach is invoked successfully.
> Creation#2: Subsequently, create eg.foo.MyClass using same default pool succeeds but any attempt to add members e.g. private int myArg1 fails with error:
> Field myArg1 in eg.foo.MyClass is private.
> Bug Analysis:
> MemberCodeGen.isAccessibleField has f.getDeclaringClass from Creation#1 but thisClass is from Creation#2. This was traced to MemberResolver.invalidNamesMap. When Creation#1 detached the CtClass, it got removed from pool but not from the invalidNamesMap for default pool. Subsequently when MemberResolver.lookupClass looks for "eg.foo.MyClass", the Creation#1's CtClass gets returned. This is a bug because that class was detached earlier and must not be reused for any processing - we are creating another instance because a new definition is needed for that class.
> The bug is critical as erroneous unintended cached class definitions could be used even when not intended leading to potentially very severe runtime problems. Remember that cache is a good only if it accurately provided cached results. In this case, stale/incorrect results will be returned.
> Proposed Fix:
> Add a static method detachInvalidNames in MemberResolver that removes a qualified class-name from invalidNamesMap for that class's pool. CtClass.detach must invoke this detachInvalidNames.
--
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
10 years, 11 months
- 1
- 0