FileNet P8 4.5 中的工作流程错误

发布于 2024-10-20 01:41:16 字数 1088 浏览 1 评论 0原文

在 FileNet P8 4.5 中运行工作流程时,我间歇性地收到此错误。我收到此错误的步骤有两个 CE 操作 - “createFolder”和“applySecurityTemplate”。我无法追踪这个问题。任何帮助将不胜感激。

Work Performer Exception: <Server Name - name removed>com.filenet.api.exception.EngineRuntimeException;An error was returned from the server. A Web services request received a non-HTTP response.  Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close [Code=null] ... Object Reference [OBJECT_STORE:4] ID "{210A5F13-CA1A-44D6-808F-CA763C882BDA}" in ObjectStore "{210A5F13-CA1A-44D6-808F-CA763C882BDA}"; OMFC/Library/GetProperties//E_SERVER_ERROR

Root Cause:
An error was returned from the server. A Web services request received a non-HTTP response.  Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close

I am receiving this error intermittently when running a workflow in FileNet P8 4.5. The step where I get this error has two CE operations - "createFolder" and "applySecurityTemplate". I have not been able to trace the issue. Any help would be appreciated.

Work Performer Exception: <Server Name - name removed>com.filenet.api.exception.EngineRuntimeException;An error was returned from the server. A Web services request received a non-HTTP response.  Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close [Code=null] ... Object Reference [OBJECT_STORE:4] ID "{210A5F13-CA1A-44D6-808F-CA763C882BDA}" in ObjectStore "{210A5F13-CA1A-44D6-808F-CA763C882BDA}"; OMFC/Library/GetProperties//E_SERVER_ERROR

Root Cause:
An error was returned from the server. A Web services request received a non-HTTP response.  Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

对你的占有欲 2024-10-27 01:41:17

我首先有几个问题:

  1. 您使用的是 CE_Operations 组件适配器 (CA) 还是 WS_Request 适配器?
  2. 这些组件适配器是否曾经工作过,或者它们仅在此工作流程中失败?

解决 CA 问题可能很困难。基本上您可以执行以下操作:

  • 组件管理器的拨号日志记录并查看生成的日志。它们可能有点难以阅读(就像任何调试日志一样),但它们会为您提供更多信息。
  • 编写一个超级简单的工作流程来测试失败的用例。

另外,由于这些似乎是与 Web 服务相关的问题,您可能需要安装一个嗅探器(如 ethereal)来查看来回传递的内容。

哈!

汤姆普尔

I have a few questions first:

  1. Are you using the CE_Operations component adapter (CA) or the WS_Request adaptor?
  2. Do these component adapter EVER work, or do they only fail with this workflow?

Troubleshooting CA issues can be tough. Here's basically what you can do:

  • Dial-up logging of the Component Manager and look at the resulting logs. They can be a bit difficult to read (like any debug log), but they will give you more information.
  • Write a super-simple workflow that tests the use case that is failing.

Also, since these seems to be a web service-related issue, you may want to install a sniffer (like ethereal) to see what is being passed back and forth.

HTH!

Tom Purl

傾旎 2024-10-27 01:41:17

通过 PMR,IBM 要求我们从 /opt/FileNet/WebClient/Router/routercmd.sh 启动组件管理器,并将 CE URI 从现有的 FNCEWS40DIME 更改为 FNCEWS40MTOM,问题得到解决。

Through a PMR, IBM asked us to start component manager from /opt/FileNet/WebClient/Router/routercmd.sh and change the CE URI to FNCEWS40MTOM from the existing FNCEWS40DIME and the issue is resolved.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文