04-02-2014 12:53 PM
We've been seeing random "Transaction not run. Task finished properly." error messages for two of our 9.23 BPM locations.
After some research, I found this in the bsm_tasks_execution.log:
27/03/2014 08:09:03 WARN [BpmTaskRunner-17] [GeneralScriptTaskExecutor] Failed to copy script output files from C:\ProgramData\HP\BPM\workspace\agent1\Site1\PMR_-
_Vision_3e04da35f0629be2de2cb7ee367a6a77_1\Comtrac Visio\572_1\res to the data folder C:\ProgramData\HP\BPM\workspace\agent1\Site1\data\ trans_t\1395922020030_590\1395922080034_1_572_Comt racVisio java.nio.file.FileSystemException: C:\ProgramData\HP\BPM\workspace\agent1\Site1\data\ trans_t\1395922020030_590\1395922080034_1_572_Comt racVisio\ComtracVision_1.json: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException (WindowsException.java:86) ~[?:1.7.0_45] at sun.nio.fs.WindowsException.rethrowAsIOException(W indowsException.java:97) ~[?:1.7.0_45] at sun.nio.fs.WindowsException.rethrowAsIOException(W indowsException.java:102) ~[?:1.7.0_45] at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.ja va:165) ~[?:1.7.0_45] at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsF ileSystemProvider.java:278) ~[?:1.7.0_45] at java.nio.file.Files.copy(Files.java:1225) ~[?:1.7.0_45] at com.hp.bsm.bpm.utils.FileUtils.copyFile(FileUtils. java:917) ~[bpm_common.jar:?] at com.hp.bsm.bpm.utils.FileUtils.copyFile(FileUtils. java:881) ~[bpm_common.jar:?] at com.hp.bsm.bpm.utils.FileUtils.copy(FileUtils.java :950) ~[bpm_common.jar:?] at com.hp.bsm.bpm.utils.FileUtils.copy(FileUtils.java :936) ~[bpm_common.jar:?] at com.hp.bsm.bpm.utils.SampleUtils.copySamplesFiles( SampleUtils.java:295) [bpm_server_common.jar:?] at com.hp.bsm.bpm.execution.GeneralScriptTaskExecutor .handleScriptOutputFiles(GeneralScriptTaskExecutor .java:348) [bpm_server.jar:?] at com.hp.bsm.bpm.execution.GeneralScriptTaskExecutor .executeAndWait(GeneralScriptTaskExecutor.java:161 ) [bpm_server.jar:?] at com.hp.bsm.bpm.execution.GeneralBtfExecutor.execut eScriptAndWait(GeneralBtfExecutor.java:93) [bpm_server.jar:?] at com.hp.bsm.bpm.execution.GeneralBtfExecutor.execut eSequentialScripts(GeneralBtfExecutor.java:154) [bpm_server.jar:?] at com.hp.bsm.bpm.execution.ClassicModeBtfExecutor.ex ecuteBtf(ClassicModeBtfExecutor.java:61) [bpm_server.jar:?] at com.hp.bsm.bpm.execution.ClassicModeBtfExecutor.ex ecuteBtf(ClassicModeBtfExecutor.java:54) [bpm_server.jar:?] at com.hp.bsm.bpm.execution.BtfTasksRunnable.run(BtfT asksRunnable.java:25) [bpm_server.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1145) [?:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:615) [?:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [?:1.7.0_45]
These warning messages in the log file are timing perfectly with the error messages in BSM. This particular vugen script runs from five locations, two of which are 9.23 BPMs. The attached picture show that these two 9.23 BPMs reporting the error message. We have not seen the same from any of our other locations.
We have other scripts (also recorded in VuGen 11.52) running from the two 9.23 BPM locations but none of those are receiving the same message.
I have tried removing the data collector from the BTF, allowing it to clear out of the BPM and then adding it back. I have tried restarting the BPM but it always comes back. Not sure what else to do to resolve this.
Any help is appreciated,
04-03-2014 07:18 AM
Click "Miscellaneous" and tick "Run Vuser as a thread"
Recompile the script and add it back to BSM with newer version. Deploy it to your BPM, see if it works better now.
04-03-2014 08:08 AM
In this script Multithreading/Run Vuser as a thread has already been ticked. My guess is that this is going to be a BPM related issue as the same version of script is running across multiple BPMs without this issue.
04-03-2014 08:16 AM
Hi, please try to run the script using command line, just copy the line form script directory\res\mdrv.cmd file
and open command line on BPM.
maybe oyu can learn more about the problem.
If it will nto help, I suggest to turn on the debug logs (as describe in Admin PDF), and send the logs to support