Transaction (Process ID 67) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. The following is an example of one of the types of errors being observed in the server.log when this problem happened: After setting WF_INSTANCE_SAVE to ALWAYS instead of ERRORS_ONLY, workflows were hanging at the same time that SQL and/or Java thread deadlock errors were being written to the server.log. This was noticed when using TRIRIGA 3.3.2.2 with Microsoft SQL as a database, but this may happen with other versions of TRIRIGA, as well. It is possible to trigger a deadlock when saving workflow instances. The documentation will be updated so that it is clear that the exact report labels are used as the external table column names, so they must be valid SQL column names (no spaces, special characters, start with a letter, etc.). The integration developer needs to ensure the query report labels of the integration object outbound query has no spaces, punctuation, etc. The documentation does touch on this, but it was noticed the doc is missing the word “column”. The integration object was designed to use the exact report label as the external table column name, and is not designed to adjust for spaces, punctuation, etc. The query report labels are what controls external table column names. ID VARCHAR2(1000), COMPANY VARCHAR2(1000) ,Īs a temporary fix, change the script by adding an underscore (_) between First Name, Last Name, and Work Phone, and change the exclamation point (!) to the word Attention. Note the lack of spaces (underscores) between Last Name, First Name and Work Phone. After creating the IO project and testing the DB connection, identify the Table Name you want to use. We found that the script that is automatically created for outbound integration objects to create the table is improperly formed. Any help to resolve the error or any other inputs are greatly appreciated.Ĭaused by: .PersistenceException: Error executing sql: SqlĬaused by: : PreparedStatementCallback bad SQL grammar nested exception is 圎rrorException: ORA-00936: missing expression is passed as input instead of the Company Name). It looks like the selected value is not getting passed to the IN clause of the SELECT statement correctly. After selecting the value from Listbox, when I try to preview the report, I’m getting the script error. I am working on a TRIRIGA BIRT report using the Multi Value Listbox input parameter. Is input data sanitized and validated at the server to protect from OS commanding attacks?….Does the code manage input length at server to avoid buffer overflows?.When copying user input at the server, does the code manage buffer boundaries to avoid buffer overflows?.When buffer size calculations are dependent on user input, are buffer size ranges checked to be within expected values?. When accessing a user-controlled array index, is input validation performed at the server to ensure that the ranges are within the target array?.Is input validation performed at the server on any numeric input by ensuring that it is within the expected range?.Is input validation performed at the server to prevent URL redirection to an invalid site?.Are only input files with valid multipurpose internet mail extensions (MIME) types accepted?.Is sensitive personal information stored encrypted?.Have denial of service (DOS) scenarios been considered or tested?.If there are additional questions or concerns not outlined below, refer to the link above. The full book on the SEF can be found at this link. Here are answers to 20 specific questions. IBM TRIRIGA platform development follows the strict rules set within the IBM Secure Engineering Framework (SEF).
0 Comments
Leave a Reply. |