[jbosstools-issues] [JBoss JIRA] (JBIDE-18373) Error when trying to publish seam project to EAP 6.3 in management profile
Rob Stryker (JIRA)
issues at jboss.org
Mon Oct 6 13:06:10 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008980#comment-13008980 ]
Rob Stryker commented on JBIDE-18373:
-------------------------------------
Unfortunatley I don't control the ordering.... It's possible I *could* by overriding some superclass methods, but, even if I did that, I don't feel I could intelligently discover what order various deployments should be deployed in. It seems something like this would require new UI and API for users or clients to add ordering information to deployments, so my publishers could draw from that.
I'll bring it up to max, but I'm extremely hesitant to put my plugin in charge of ordering deployments because the odds are pretty high I'd get the ordering wrong...
This is something that was never really a problem for local or filesystem publishing, because we simply wouldn't add the .dodeploy markers until all deployments were copied over, but in management deployment, it seems the server tries to complete a deployment immiedately and so ordering is now important.
Honestly, I would resolve this issue as partially completed and open a new issue for the ordering, from which we could discuss whether new API or UI is required. Again, I can't simply prioritize one module type over another. First, it'd be just as likely to be correct as incorrect. For example, if we prioritized single-file deployments over others, that still wouldn't solve the problem that the jar must be deployed before the xml. I'd need to further prioritize single-file jars over single-file xml, for THIS usecase. But there may be other usecases that require a single-file xml before a single-file jar, such as if a user has a pre-built jar or war archive that he's marked as deployable.
There's too many ways to go wrong here without adding additional API / UI for the users to customize it on their own.
> Error when trying to publish seam project to EAP 6.3 in management profile
> --------------------------------------------------------------------------
>
> Key: JBIDE-18373
> URL: https://issues.jboss.org/browse/JBIDE-18373
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
> Attachments: seam-publish.png, seam-remote.png
>
>
> When I try to deploy a seam web project to a remote EAP 6.3 server, it takes a few minutes (expected - big seam lib) and then fails (not expected) with this error:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298251 2014-09-17 15:47:40.273
> !MESSAGE Deployment of module seamproj has failed
> !SUBENTRY 1 org.jboss.ide.eclipse.as.management.as71 4 0 2014-09-17 15:47:40.273
> !MESSAGE The operation DEPLOY for unit seamproj.war was rolled back
> !ENTRY org.jboss.ide.eclipse.as.wtp.core 4 1644298249 2014-09-17 15:47:55.797
> !MESSAGE Error renaming /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/tmp/tmp7639865478274379783.jar to /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/deployments/seamproj.war/WEB-INF/lib/jboss-seam.jar.
> This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
> This is the server console on the remote host:
> {code}
> 15:47:37,811 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /home/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/data/content/ca/f4ac569df88605a785004d5f7683a20e809753/content
> 15:47:37,836 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "seamproj.war" (runtime-name: "seamproj.war")
> 15:47:39,474 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for seamproj
> 15:47:39,639 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.seamproj.war" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.
> 15:47:39,639 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.seamproj.war" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.
> 15:47:39,640 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.seamproj.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.
> 15:47:39,640 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.seamproj.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.
> 15:47:39,800 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named EjbSynchronizations in deployment unit deployment "seamproj.war" are as follows:
> java:global/seamproj/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
> java:app/seamproj/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
> java:module/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
> java:global/seamproj/EjbSynchronizations
> java:app/seamproj/EjbSynchronizations
> java:module/EjbSynchronizations
> 15:47:39,801 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named TimerServiceDispatcher in deployment unit deployment "seamproj.war" are as follows:
> java:global/seamproj/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
> java:app/seamproj/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
> java:module/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
> java:global/seamproj/TimerServiceDispatcher
> java:app/seamproj/TimerServiceDispatcher
> java:module/TimerServiceDispatcher
> 15:47:39,981 WARN [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016012: Deployment deployment "seamproj.war" contains CDI annotations but beans.xml was not found.
> 15:47:40,109 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "seamproj.war" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"seamproj.war#seamproj\" is missing [jboss.naming.context.java.seamprojDatasource]"]}
> 15:47:40,161 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment seamproj.war (runtime-name: seamproj.war) in 51ms
> 15:47:40,169 INFO [org.jboss.as.controller] (management-handler-thread - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START]
> service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START (missing) dependents: [service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformationStart, service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.VIEW."org.jboss.seam.transaction.LocalEjbSynchronizations".LOCAL (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START (missing) dependents: [service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformationStart, service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.VIEW."org.jboss.seam.async.LocalTimerServiceDispatcher".LOCAL (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.ejb3.timerService (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.deployment.unit."seamproj.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."com.sun.faces.config.ConfigureListener".START]
> service jboss.deployment.unit."seamproj.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".START]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacetTag".START]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.VersionBean".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.VersionBean".START]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.VersionBean".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.skin.SkinBean".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.skin.SkinBean".START]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.skin.SkinBean".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.apache.catalina.servlets.DefaultServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.catalina.servlets.DefaultServlet".START]
> service jboss.deployment.unit."seamproj.war".component."org.apache.catalina.servlets.DefaultServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START]
> service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamFilter".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamFilter".START]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamFilter".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamListener".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamListener".START]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamListener".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamResourceServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamResourceServlet".START]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamResourceServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START, service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".START, JBAS014799: ... and 12 more ]
> service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START, service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START]
> service jboss.naming.context.java.module.seamproj.seamproj.env."org.jboss.seam.async.TimerServiceDispatcher".timerService (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.naming.context.java.seamprojDatasource (missing) dependents: [service jboss.persistenceunit."seamproj.war#seamproj"]
> service jboss.persistenceunit."seamproj.war#seamproj" (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START, service jboss.naming.context.java.seamprojEntityManagerFactory, service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."seamproj.war".deploymentCompleteService, JBAS014799: ... and 14 more ]
> service jboss.web.deployment.default-host./seamproj (missing) dependents: [service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.web.deployment.default-host./seamproj.realm (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> {code}
> So clearly the deployment is incomplete on the server. In fact, the first line says that new content was added to /home/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/data/content/ca/f4ac569df88605a785004d5f7683a20e809753/content but this directory is empty.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbosstools-issues
mailing list