If you have a problem getting a BRM pipeline to start up and get an error, here is a fix to try. Everywhere you see “XXX” is a replacement for the name of the client’s directory structure.
If you get the following message on startup of the pipeline:
bin/XXX: An error occurred during creation.
Originator : XXX.Pipelines.ExceptionPipeline.TransactionManager
Destination :
Message : ERR_TAM_INIT_FAILED
Arguments : XXX.Pipelines.ExceptionPipeline.TransactionManager
State : false
Severity : CRITICAL
Thread : 1
Go look in the $XXX_HOME/log/process/processXXXXX.log file for messages like:
01.12.2009 16:18:16 hostname XXX XXX MAJOR [T:1] 00081 – (XXX.Pipelines.ExceptionPipeline.Output.OutputCollection.EdrOutput.Module.OutputStream.Module) ‘No such file or directory’: Cannot move temporary file ‘./your/path/tmpExceptionPipelineToReplayEdrSerialize_YYYY.edr’ to output file ‘./your /path/ToReplayEdrSerialize_YYYY.edr’.
01.12.2009 16:18:18 hostname XXX XXX CRITICAL [T:1] 00441 – (XXX.Pipelines.ExceptionPipeline.TransactionManager) Failed to init transaction manager ‘XXX.Pipelines.ExceptionPipeline.TransactionManager’.
The tmpExceptionPipelineToReplayEdrSerialize_YYYY.edr file doesn’t exist for some reason, or is un-processable, and you have to remove references to it from the TAM startup files. There are two files that you need to delete:
$XXX_HOME/tam/ TamTransXXXXX.dat
$XXX_HOME/tam/ ExceptionBinaryLogFile.dat
Once you delete these two files, the pipeline should start up again. If it doesn’t, the file referenced may actually exist in the pipeline path. If it does, delete it.
Send questions to jdavis@ssglimited.com