Hi Everyone,
I have the follow error when I tried to deploy an applicaton in xCP 2.2.
The content server is 7.0 and We was working on the xCP 2.0 version. The idea is use the compatibility between version
Does anybody have any idea?
If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.
Hi everyoneI
It is necessary to change the maximum upload size on the dispatcher-servlet.xml file if you have upload size error.
Should increment the bean multipartResolver on location_app_server\webapps\xms-server\WEB-INF\dispatcher-servlet.xml and location_app_server\webapps\xms-server\WEB-INF\clientDispatcher-servlet.xml
<bean id="multipartResolver" class="org.springframework.web.multipart.commons.CommonsMultipartResolver">
<property name="maxUploadSize">
<value>1073741824</value>
</property>
<property name="maxInMemorySize">
<value>4096</value>
</bean>
Are all your components like Content Server, xPlore, etc. on same patch level as xCP? Read xCP Release Notes / Patch Notes for details on which patch levels are compatible with that version of xCP.
is correct. You need to upgrade the Process Engine along with xMS Agent and other components (BAM, xPlore etc) to the matching version with the xCP 2.2 patch version you are using. Refer to release notes for the compatible versions.
Hi everyone
I want to comment that the null error was resolved. The problem was: We had not define the xcp developer environment. We only defined the D7 environment. the xms server was looking for bam service module, but it was not configured. Right now, we are trying to install a xcp 2.2 application at a server with xcp 2.0 as based. we want to use the compatibility between versions. Is this working fine? we are using xcp designer 2.2 upgrade 21
This is not advisable. When upgrading the xCP Application, you need to upgrade the whole stack. That is, xCP Designer, xMS Agent, Process Engine, BAM, xPlore, etc. For example, if you upgrade just the xCP Designer to 2.2 while xMS Agent stays at 2.0, then it may not deploy some of the new artifacts at all or deploy them incorrectly. Similarly, not upgrading PE and other components may have some unintended consequences which may even lead to data corruptions. Also, this being an unsupported configuration, the support may not be able to help recover, simply because it may just technically not be possible.
Are there any compelling reasons for not to upgrade?
Thanks Samir Vaidya for your response.
I have upgraded all xCP 2.2 components. But I had the follow error when I was trying to deploy one app.
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
Steps before this were OK - all objects are deployed ok in repository, everything is ok, app war file is copied in server app webapps folder.
Can anybody help me?
Damian
Are you using Tomcat 8? Please check if it is supported for the 2.2 Patch version you are using. Alternatively, switch to Tomcat 7. Do let us know if the problem persists.
Thanks you for your response.
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 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
Are you using the same target AppHost for both the applications? One created in xCP2.2 and the one migrated to xCP 2.2. Verify that the AppHost is actually reachable from the machine/VM where xms-agent is running.
Good morning!!! Im using the same environments and the same xms-agent. I used the xms-tools and I tried to install the app with xcp designer too.
I'll check again all configuration.
Do u have another idea?
One questions, Could be the time out configuration? Or some thing similar. Because the application migrated is bigger than the example application.
How big is the war? It may be worth a shot to increase the timeout. And while at time let's verify all the tomcat settings are in place. The xCP 2.2 Deployment Guide (Page 34) may be useful here http://greece.emc.com/collateral/TechnicalDocument/docu57227.pdf
Hi
I proved to migrate another application smaller than first. I could deploy this smaller application without problems.
I don have problem if the size of file .war to deploy is smaller than 150 MB.
The war file is 200 MB.
Let me check it out further. Meanwhile if its not too much trouble can you check what is the value in <tomcat-install-folder>\webapps\manager\WEB-INF\web.xml for max-file-size
max-file-size
The default entries are typically as follows
<multipart-config><!– 50MB max –><max-file-size>52428800</max-file-size><max-request-size>52428800</max-request-size><file-size-threshold>0</file-size-threshold></multipart-config>
Can you increase the max-file-size and max-request-size to 1073741824 (1GB) and see if that helps
Hi ... I have changed this to 500 MB at apphost sever and bam server. but it is not working. I will check all again!!
Can you enable the debug logging on in Designer and xms-agent and share the debug logs (xcpdesigner.log and xms-full.log). Also, open a support ticket if that is possible.
Hi ankur
I turn on the debugg at xms-server and I have the follow error:
2016/12/19 19:00:56,632 DEBUG [http-bio-7070-exec-5] - put object: 'User' with id: '396286a07c9d100087b8005056a32c4701'
2016/12/19 19:00:56,632 DEBUG [http-bio-7070-exec-5] - completed operation SaveOperation execution in 62 ms
2016/12/19 19:00:56,632 DEBUG [http-bio-7070-exec-5] - removing the cache
2016/12/19 19:01:25,883 DEBUG [http-bio-7070-exec-7] - created the cache
2016/12/19 19:01:25,883 DEBUG [http-bio-7070-exec-7] - going to execute operation FindAllOperation
2016/12/19 19:01:25,883 DEBUG [http-bio-7070-exec-7] -
Segment default: current size 10682368, free size 1163264
Segment temporary: current size 4096, free size 0
2016/12/19 19:01:25,883 DEBUG [http-bio-7070-exec-7] - for $alias in doc("/")//user where ((($alias/@role="ADMIN")) and ($alias/@deleted="false") and ($alias/object-type/@uid="com.emc.xms.resources.User")) return $alias
2016/12/19 19:01:25,899 DEBUG [http-bio-7070-exec-7] - query completed in 16 ms
2016/12/19 19:01:25,899 DEBUG [http-bio-7070-exec-7] - going to execute operation LoadRelationsOperation
2016/12/19 19:01:25,899 DEBUG [http-bio-7070-exec-7] -
2016/12/19 19:01:25,899 DEBUG [http-bio-7070-exec-7] - completed operation LoadRelationsOperation execution in 0 ms
2016/12/19 19:01:25,899 DEBUG [http-bio-7070-exec-7] - completed operation FindAllOperation execution in 16 ms
2016/12/19 19:01:25,899 DEBUG [http-bio-7070-exec-7] - removing the cache
2016/12/19 19:01:28,415 DEBUG [http-bio-7070-exec-7] - Resolving exception from handler [null]: org.springframework.web.multipart.MaxUploadSizeExceededException: Maximum upload size of 209715200 bytes exceeded; nested exception is org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because its size (209717523) exceeds the configured maximum (209715200)
But I incremented the max upload on all app (web.xml at manager site and the maxUpload at server.xml).
I'll try to change the value at the dispatcher-servlet.xml....