部署准备提交阶段失败,无法准备事务

Ste*_*son 5 tridion

在从SDL Tridion 5.2迁移到2011 SP1之后尝试发布或取消发布某些页面和结构组时,我们遇到了问题.

发布事务在Committing Deployment阶段失败,并返回以下错误消息:

阶段:部署准备提交阶段失败,无法准备事务:tcm:0-682623-66560,null,null

cd_deployer.exe服务也几乎同时以100%的CPU使用率运行.

我们还在cd_deployer.log和cd_core.log文件中获取以下信息:

2012-05-02 07:32:09,346 ERROR DeployPipelineExecutor - Unable to start processing deployment package with transactionId: tcm:0-682520-66560
2012-05-02 07:36:36,071 ERROR DeployPipelineExecutor - Final attempt in Phase: Deployment Prepare Commit Phase failed for transaction: tcm:0-682526-66560
2012-05-02 07:36:36,071 ERROR DeployPipelineExecutor - Original stacktrace for transaction: tcm:0-682526-66560
com.tridion.deployer.ProcessingException: Unable to prepare transaction: tcm:0-682526-66560, null, null
    at com.tridion.deployer.phases.PreCommitPhase.handleFailure(PreCommitPhase.java:120) ~[cd_deployer.jar:na]
    at com.tridion.deployer.phases.PreCommitPhase.execute(PreCommitPhase.java:101) ~[cd_deployer.jar:na]
    at com.tridion.deployer.phases.DeployPipelineExecutor.runMainExecutePhase(DeployPipelineExecutor.java:186) [cd_deployer.jar:na]
    at com.tridion.deployer.phases.DeployPipelineExecutor.doExecute(DeployPipelineExecutor.java:97) [cd_deployer.jar:na]
    at com.tridion.deployer.phases.DeployPipelineExecutor.execute(DeployPipelineExecutor.java:61) [cd_deployer.jar:na]
    at com.tridion.deployer.TransactionManager.handleDeployPackage(TransactionManager.java:80) [cd_deployer.jar:na]
    at com.tridion.deployer.queue.QueueLocationHandler$1.run(QueueLocationHandler.java:176) [cd_deployer.jar:na]
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [na:1.6.0_30]
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [na:1.6.0_30]
    at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.6.0_30]
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [na:1.6.0_30]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.6.0_30]
    at java.lang.Thread.run(Unknown Source) [na:1.6.0_30]
Run Code Online (Sandbox Code Playgroud)

从页面中删除组件演示文稿并重新发布工作正常.使用不同的组件模板不起作用,因此问题似乎与组件在某处.

页面,二进制文件和DCP都发布到文件系统.我确实想知道问题是否与发布大型二进制文件有关,但是从组件中删除它们没有任何区别.

有没有人有任何想法如何解决这个问题?

亲切的问候

编辑:我现在已经跟踪了一些我无法发布或取消发布的组件.尝试发布或取消发布组件时,事务将保持在"提交部署"阶段大约5分钟,cd_deployer服务最大化CPU,最终失败并显示相同的错误消息.

如果我通过复制和粘贴创建相同的组件副本,这可以正常工作,并在几秒钟内直接发布,而不会影响服务器的CPU.很奇怪!

编辑2:这是我们目前在cd_storage_conf.xml文件中为每个发布提供的示例:

<Storage Type="filesystem" Class="com.tridion.storage.filesystem.FSDAOFactory" Id="21_content" defaultFilesystem="false">
    <Root Path="D:/WebSites/live/Website/wwwroot/" />
</Storage>
<Storage Type="filesystem" Class="com.tridion.storage.filesystem.FSDAOFactory" Id="21_data" defaultFilesystem="true" defaultStorage="true">
    <Root Path="D:/WebSites/live/Website/Data" />
</Storage>

<Publication Id="21" defaultStorageId="21_data" cached="false">
    <Item typeMapping="Page" cached="false" storageId="21_content"/>
    <Item typeMapping="Binary" storageId="21_content" cached="false"/>
    <Item typeMapping="ComponentPresentation" storageId="21_data"/>
</Publication>  
Run Code Online (Sandbox Code Playgroud)

元数据没有特定的类型映射.

Chr*_*ers 3

您是否尝试过取消发布然后重新发布有问题的页面?这通常可以为我解决问题。我有一个理论,有时旧的失败事务可能会锁定代理中的某些行。取消发布该页面似乎可以释放他们。这并不能真正解决问题的原因,但如果有效,应该有助于隔离原因。