Guest

Preview Tool

Cisco Bug: CSCum01540 - Transporter exception when job has dependency in different group

Last Modified

Oct 27, 2014

Products (18)

  • Cisco Tidal Enterprise Transporter
  • Cisco Tidal Enterprise Adapter for Web Services
  • Cisco Tidal Enterprise Adapter for Oracle E-Business Suite
  • Cisco Tidal Enterprise Adapter for VMware
  • Cisco Tidal Enterprise Adapter for SAS
  • Cisco Tidal Enterprise Adapter for Oracle Database
  • Cisco Tidal Enterprise Adapter for SAP
  • Cisco Tidal Enterprise Adapter for Cognos
  • Cisco Tidal Enterprise Adapter for Informatica
  • Cisco Tidal Agent for OVMS
View all products in Bug Search Tool Login Required

Known Affected Releases

6.1.0

Description (partial)

Symptom:
Transporter exception when transporting jobs with dependencies in different job groups

[FTPJob has been updated.(ID:73070)EventJobJoin has been created.(ID:201997)EventJobJoin
has been created.(ID:201998)exception:java.lang.Exception
reason:
description:TES_020041:JobDependency refers to the group instance but does not have the
same parent with job[73070].

Conditions:
Transporter will successfully transport job without their dependencies if Job's Predecessors are in a different job group.

Steps to reproduce
1. Create job group "A" with two jobs (A and B)
2. Make job B dependent on job A completing
3. Move job A to a different job group "B"
4. Note job "B" is still dependent on job "A" in job group "B"
5. Use Transporter to move job group "A" and then job group "B" and note pop-up message Details below.
6. Check Destination DB and note job "B" was successfully transported but without Predecessor job "A"

[FTPJob has been updated.(ID:73070)EventJobJoin has been created.(ID:201997)EventJobJoin
has been created.(ID:201998)exception:java.lang.Exception
reason:
description:TES_020041:JobDependency refers to the group instance but does not have the
same parent with job[73070].
=> sun.reflect.GeneratedMethodAccessor339.invoke [null -1]
=> sun.reflect.DelegatingMethodAccessorImpl.invoke [null -1]
=> java.lang.reflect.Method.invoke [null -1]
=> com.tidalsoft.framework.execute.CallMethod.execute [CallMethod.java 228]
=> com.tidalsoft.scheduler.api.methods.impl.CreateObject.execute [CreateObject.java 34]
=> com.tidalsoft.framework.execute.Transaction.execute [Transaction.java 108]
=> com.tidalsoft.framework.execute.Executor.execute [Executor.java 65]
=> com.tidalsoft.framework.execute.Executor.executeAsync [Executor.java 52]
=> com.tidalsoft.framework.execute.Execution.execute [Execution.java 24]
=> com.tidalsoft.framework.rpc.RpcServer$1.onMessage [RpcServer.java 155]
=> org.apache.activemq.ActiveMQSession.run [ActiveMQSession.java 833]
=> org.apache.activemq.ActiveMQQueueSession.run [ActiveMQQueueSession.java 355]
=> com.tidalsoft.framework.jms.ServerSessionPool$ServerSession.run
[ServerSessionPool.java 240]
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.