Postgresql Pentaho 5.4-连接尝试失败（postgres）

我正在使用Pentaho BI服务器5.4。我用Spoon创建了一些水壶作业，将它们上传到服务器，并通过XAction文件安排它们。其中大多数都能正常工作，但有一个步骤会继续出现以下错误并停止作业执行：

2018-04-19 09:51:02,838 ERROR [org.pentaho.di] 2018/04/19 09:51:02 - Source.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : An error cause this step to stop: org.pentaho.di.core.exception.KettleDatabaseException:
2018/04/19 09:51:02 - Source.0 - Error occurred while trying to connect to the database
2018/04/19 09:51:02 - Source.0 -
2018/04/19 09:51:02 - Source.0 - Error connecting to database: (using class org.postgresql.Driver)
2018/04/19 09:51:02 - Source.0 - The connection attempt failed.
2018-04-19 09:51:02,839 ERROR [org.pentaho.di] 2018/04/19 09:51:02 - DimOrigen.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Error initializing step [Source]

连接是使用JNDI进行的。我知道这个JNDI工作得很好，因为我在其他转换中使用它，它们不会崩溃。此外，此问题仅在生产环境中出现，而不在我的机器中出现；并且仅在转换的某些步骤中（其他步骤使用相同的JNDI，并且不给出任何错误消息）

错误的完整堆栈跟踪如下所示：

2018-04-19 09:51:02,861 ERROR [org.pentaho.platform.plugin.action.kettle.KettleComponent] Error Start: Pentaho Pentaho Open Source BA Server 5.4.0.1-130
2018-04-19 09:51:02,861 ERROR [org.pentaho.platform.plugin.action.kettle.KettleComponent] 42ad3cc8-43ae-11e8-9bc0-0001a4a6a11b:COMPONENT:context-1888026901-1524127635683:0101-Transformation.xactionKettle.ERROR_0008 - [es_383] An unexpected error occurred running the transformation org.pentaho.platform.plugin.action.kettle.KettleComponentException: Kettle.ERROR_0014 - [es_249] Error occurred during transformation execution
org.pentaho.platform.plugin.action.kettle.KettleComponentException: Kettle.ERROR_0014 - [es_249] Error occurred during transformation execution
        at org.pentaho.platform.plugin.action.kettle.KettleComponent.executeJob(KettleComponent.java:1027)
        at org.pentaho.platform.plugin.action.kettle.KettleComponent.executeAction(KettleComponent.java:603)
        at org.pentaho.platform.engine.services.solution.ComponentBase.execute(ComponentBase.java:465)
        at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeComponent(RuntimeContext.java:1186)
        at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeAction(RuntimeContext.java:1151)
        at org.pentaho.platform.engine.services.runtime.RuntimeContext.performActions(RuntimeContext.java:1063)
        at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeLoop(RuntimeContext.java:1013)
        at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeSequence(RuntimeContext.java:895)
        at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeSequence(RuntimeContext.java:797)
        at org.pentaho.platform.engine.services.solution.SolutionEngine.executeInternal(SolutionEngine.java:352)
        at org.pentaho.platform.engine.services.solution.SolutionEngine.execute(SolutionEngine.java:282)
        at org.pentaho.platform.engine.services.solution.SolutionEngine.execute(SolutionEngine.java:179)
        at org.pentaho.platform.web.http.api.resources.XactionUtil.executeInternal(XactionUtil.java:311)
        at org.pentaho.platform.web.http.api.resources.XactionUtil.executeHtml(XactionUtil.java:201)
        at org.pentaho.platform.web.http.api.resources.XactionUtil.execute(XactionUtil.java:366)
        at org.pentaho.platform.web.http.ActionSequenceContentGenerator.createContent(ActionSequenceContentGenerator.java:82)
        at org.pentaho.platform.engine.services.solution.SimpleContentGenerator.createContent(SimpleContentGenerator.java:60)
        at org.pentaho.platform.web.http.api.resources.GeneratorStreamingOutput.generateContent(GeneratorStreamingOutput.java:236)
        at org.pentaho.platform.web.http.api.resources.GeneratorStreamingOutput.write(GeneratorStreamingOutput.java:163)
        at org.pentaho.platform.web.http.api.resources.GeneratorStreamingOutputProvider.writeTo(GeneratorStreamingOutputProvider.java:54)
        at org.pentaho.platform.web.http.api.resources.GeneratorStreamingOutputProvider.writeTo(GeneratorStreamingOutputProvider.java:33)
        at com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
        at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1479)
        at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1391)
        at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1381)
        at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
        at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)
        at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:716)

---

有人知道这里发生了什么吗？

错误消息的信息量不大。数据库有自己的日志文件。您可以尝试“跟踪”PostgreSQL日志文件，并在执行转换时观察它是否有错误。如果连接尝试到达服务器，您可能会在PostgreSQL日志中找到错误。谢谢您的回答。我无法访问数据库服务器日志。您的作业是否尝试访问同一个表进行读写操作？不，没有。我终于设法执行了转换。似乎还有其他转换在后台执行，处理相同的表并阻止它们。我已经重新安排了预定的xD。谢谢你的关注。