Products | Versions |
---|---|
TIBCO BusinessEvents Enterprise Edition | - |
Not Applicable | - |
When trying to build an EAR
file using the command line interface TIBCO BusinessEvents functions, the execution
appears to complete successfully. But the
EAR file is not generated and the following is reported when a check is
performed on the process exit code.
$ echo $?
13
This can be reproduced on Linux using the 64-bit BE Standard executable. This issue is not seen under Windows.
/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-fareast-language:EN-US;}A number of checks could be performed:
- Increase the open file limit size.
- Ensure that the correct" Add On’s" have been installed.
- Run a sample project such as Fraud Detection to see if the results are the same.
- If the project contains some references to external libraries, add the parameter “-cp” when running studio-tools on the command line.
- Also, verify that the studio-tools command is run from the BE_HOME/studio/bin location.
OS exit code 13 is related to file permissions. You can set all permissions (777) to $TIBCO_HOME recursively to see if the behavior changes.
Some useful links follow:
http://www.lansa.com/support/tips/e0012.htm
http://nixcraft.com/showthread.php/14390-Possible-Exceptions-in-unix