Home Documentum

xCP 2.2 error deploy / deploying app war

edited December 14, 2016 in Documentum

Hi Everyone

I created a example application at xCP 2.2. But I had the follow error when I was trying to deploy.

apptest-xCP22AppTest-1.0.0.war deployment has failed

java.lang.LinkageError: org/apache/tools/ant/Project

    at org.apache.tools.ant.Task.log(Task.java:294)

    at org.apache.catalina.ant.BaseRedirectorHelperTask.handleErrorOutput(BaseRedirectorHelperTask.java:328)

    at org.apache.catalina.ant.AbstractCatalinaTask.execute(AbstractCatalinaTask.java:266)

    at org.apache.catalina.ant.DeployTask.execute(DeployTask.java:210)

    at internal.com.emc.xcp.deployment.wardeployer.tcserver.TCServerWarDeployer.deploy(TCServerWarDeployer.java:79)

    at internal.com.emc.xcp.deployment.deployer.factory.WarDeployerFactory.deploy(WarDeployerFactory.java:65)

    at com.emc.xcp.builder.deployment.AppDeployerNodeService$DEPLOY_PHASE$1.doPhase(AppDeployerNodeService.java:30)

    at com.emc.xcp.builder.deployment.AppDeployerNodeService$1.call(AppDeployerNodeService.java:99)

    at com.emc.xcp.builder.deployment.AppDeployerNodeService$1.call(AppDeployerNodeService.java:1)

    at java.util.concurrent.FutureTask.run(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

2016/12/13 06:52:42,379 ERROR [pool-37-thread-4] - Problem deploying: com.emc.executionenvironment.xcp.xcpserver

com.emc.xcp.builder.deployment.AppDeployException: apptest-xCP22AppTest-1.0.0.war deployment has failed

    at internal.com.emc.xcp.deployment.wardeployer.tcserver.TCServerWarDeployer.deploy(TCServerWarDeployer.java:86)

    at internal.com.emc.xcp.deployment.deployer.factory.WarDeployerFactory.deploy(WarDeployerFactory.java:65)

    at com.emc.xcp.builder.deployment.AppDeployerNodeService$DEPLOY_PHASE$1.doPhase(AppDeployerNodeService.java:30)

    at com.emc.xcp.builder.deployment.AppDeployerNodeService$1.call(AppDeployerNodeService.java:99)

    at com.emc.xcp.builder.deployment.AppDeployerNodeService$1.call(AppDeployerNodeService.java:1)

    at java.util.concurrent.FutureTask.run(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.LinkageError: org/apache/tools/ant/Project

    at org.apache.tools.ant.Task.log(Task.java:294)

    at org.apache.catalina.ant.BaseRedirectorHelperTask.handleErrorOutput(BaseRedirectorHelperTask.java:328)

    at org.apache.catalina.ant.AbstractCatalinaTask.execute(AbstractCatalinaTask.java:266)

    at org.apache.catalina.ant.DeployTask.execute(DeployTask.java:210)

    at internal.com.emc.xcp.deployment.wardeployer.tcserver.TCServerWarDeployer.deploy(TCServerWarDeployer.java:79)

    ... 8 more

2016/12/13 06:52:43,212  INFO [pool-71-thread-2] - No actions needed during xPlore upgradeData

2016/12/13 06:52:43,238  INFO [pool-72-thread-4] - Application URL: http://sdbuetmlab15:8080/xCP22AppTest

2016/12/13 06:52:43,238  INFO [pool-72-thread-2] - Started SearchDeployer 'PostDeploy'

2016/12/13 06:52:43,316  INFO [pool-72-thread-2] - No actions needed during xPlore PostDeploy

2016/12/13 06:52:43,342  INFO [pool-72-thread-2] - Finished executing SearchDeployer 'PostDeploy' (Execution time = 0 secs)

2016/12/13 06:52:43,367  INFO [executionCommandExecutor-1] - AppDeploymentManager deployedin....108secs

2016/12/13 06:52:43,522  INFO [executionCommandExecutor-1] - Registering deployed application into catalog: environment: xCP-2.2-Developer-Agent, name = xCP22AppTest, namespace = apptest, version = 1.0.0

2016/12/13 06:52:45,620  INFO [executionCommandExecutor-1] - Deploying application was successful

2016/12/13 06:52:45,652 DEBUG [executionCommandExecutor-1] - Cleaning up the files created during deployment

2016/12/13 06:52:45,652  INFO [executionCommandExecutor-1] - CommandRequest ID is [email protected]

2016/12/13 06:52:45,681 DEBUG [executionCommandExecutor-1] - Payload temp path - D:\Tomcat 8.0\temp\work\c36af014-c6fd-45db-a446-5d859f5f0619\payload_0759d036-345c-4ebc-a248-84564f1cc5a3.xml

2016/12/13 06:52:45,681 DEBUG [executionCommandExecutor-1] - Work temp folder to be cleaned - D:\Tomcat 8.0\temp\work\c36af014-c6fd-45db-a446-5d859f5f0619

2016/12/13 06:52:45,702 DEBUG [executionCommandExecutor-1] - Deleted temp folder within work path D:\Tomcat 8.0\temp\work\c36af014-c6fd-45db-a446-5d859f5f0619 successfully

2016/12/13 06:52:45,703 DEBUG [executionCommandExecutor-1] - commandFinished: Finish command [commandId->ad37ff40-a82e-4196-a670-ef991e31aabc]

Can anyboy help me?

Thank u!

Damian

Tagged:

Best Answer

  • ankur..ankur.. Ankur Sharma
    edited December 13, 2016 Accepted Answer

    Please make sure you are using the supported Tomcat version for 2.2 Patch version.

Answers

  • ankur..ankur.. Ankur Sharma
    edited December 13, 2016 Accepted Answer

    Please make sure you are using the supported Tomcat version for 2.2 Patch version.

  • edited December 14, 2016

    The issue was resolved after install the apache tomcat 7.0.56. Right now, I can deploy application from designer and xms-server at xCP 2.2. But I have a problem when I try deploy an upgraded application  from xCP 2.0 to xCP 2.2.  The error is:

    xMS server unavailable. Please check connection.

    com.documentum.xms.api.client.ClientExecutionException: xMS server unavailable. Please check connection.

        at com.documentum.xms.api.client.impl.XmsRestTemplate.doExecute(XmsRestTemplate.java:88)

        at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:401)

        at com.documentum.xms.api.client.impl.XmsRestTemplate.execute(XmsRestTemplate.java:62)

        at org.springframework.web.client.RestTemplate.postForObject(RestTemplate.java:279)

        at com.emc.xms.execution.impl.RestExecutionService.execute(RestExecutionService.java:67)

        at com.documentum.xms.api.client.impl.XmsClient$ExecutionServiceAwareCommandRequest.getResults(XmsClient.java:163)

        at com.emc.xms.client.XmsClientFacade.deployApplication(XmsClientFacade.java:228)

        at com.documentum.deployment.xms.XmsAppDeployer.deploy(XmsAppDeployer.java:122)

        at internal.com.emc.xcp.builder.deployment.xms.XMSDeploymentService.deploy(XMSDeploymentService.java:82)

        at com.emc.xcp.builder.deployment.service.AbstractDeploymentService.deploy(AbstractDeploymentService.java:32)

        at internal.com.emc.xcp.builder.deployment.xms.XMSDeploymentService.deploy(XMSDeploymentService.java:45)

        at internal.com.emc.xcp.builder.deployment.XcpDeployCommand.execute(XcpDeployCommand.java:35)

        at internal.com.emc.xcp.builder.build.maven.MavenHookManager.execute(MavenHookManager.java:29)

        at internal.com.emc.xcp.builder.build.maven.MavenHookServlet.doPost(MavenHookServlet.java:52)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

        at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)

        at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)

        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)

        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

        at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:386)

        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)

        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)

        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229)

        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)

        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)

        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)

        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)

        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)

        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)

        at org.eclipse.jetty.server.Server.handle(Server.java:366)

        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)

        at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:982)

        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1043)

        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)

        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)

        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)

        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)

        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)

        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)

        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)

        at java.lang.Thread.run(Thread.java:745)

    Caused by: org.springframework.web.client.ResourceAccessException: I/O error: Error writing request body to server; nested exception is java.io.IOException: Error writing request body to server

        at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:453)

        at com.documentum.xms.api.client.impl.XmsRestTemplate.doExecute(XmsRestTemplate.java:84)

        ... 42 more

    Caused by: java.io.IOException: Error writing request body to server

        at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3192)

        at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3160)

        at java.io.FilterOutputStream.write(FilterOutputStream.java:77)

        at java.io.FilterOutputStream.write(FilterOutputStream.java:125)

        at org.springframework.util.FileCopyUtils.copy(FileCopyUtils.java:113)

        at org.springframework.http.converter.ResourceHttpMessageConverter.writeInternal(ResourceHttpMessageConverter.java:87)

        at org.springframework.http.converter.ResourceHttpMessageConverter.writeInternal(ResourceHttpMessageConverter.java:1)

        at org.springframework.http.converter.AbstractHttpMessageConverter.write(AbstractHttpMessageConverter.java:179)

        at org.springframework.http.converter.FormHttpMessageConverter.writePart(FormHttpMessageConverter.java:306)

        at org.springframework.http.converter.FormHttpMessageConverter.writeParts(FormHttpMessageConverter.java:270)

        at org.springframework.http.converter.FormHttpMessageConverter.writeMultipart(FormHttpMessageConverter.java:260)

        at org.springframework.http.converter.FormHttpMessageConverter.write(FormHttpMessageConverter.java:200)

        at org.springframework.http.converter.FormHttpMessageConverter.write(FormHttpMessageConverter.java:1)

        at org.springframework.web.client.RestTemplate$HttpEntityRequestCallback.doWithRequest(RestTemplate.java:588)

        at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:436)

        ... 43 more

    I/O error: Error writing request body to server; nested exception is java.io.IOException: Error writing request body to server

    org.springframework.web.client.ResourceAccessException: I/O error: Error writing request body to server; nested exception is java.io.IOException: Error writing request body to server

    I dont have problems with the new applications created and deployed at xCP 2.2. I have this problem on the applications migrated from xCP 2.0 to xCP 2.2

Sign In or Register to comment.