JBA errors with InComm's LaunchIT

Topics related to the integration of LSPS with external systems.
Forum rules
Make sure every topic contains information about your LSPS version and if relevant also your server OS, client OS, database name and version, and application server name and version.
nbe
 
Posts: 5
Joined: Mon Jul 11, 2016 6:48 pm

JBA errors with InComm's LaunchIT

Thu Sep 01, 2016 4:28 pm

InComm is noticing JBA errors in production. Can anyone offer feedback to what is causing these errors? I've attached the stack traces. Thanks in advance.
Attachments
JBA error stack trace 2.rtf
(49.7 KiB) Downloaded 224 times
JBA error stack track 1.rtf
(34.97 KiB) Downloaded 210 times

Roman Kubascik
 
Posts: 57
Joined: Thu Apr 16, 2015 9:05 am

Re: JBA errors with InComm's LaunchIT

Mon Sep 05, 2016 12:21 pm

Hi Nick,

from the log I only can say that key problem is:
SQLServerException: String or binary data would be truncated.

Someone is trying to save value which is bigger than the size of the column in the database table (shared record).
Problem could also be in stored procedures/triggers (if there are any) in the db which could try to store some long data.

1. You can enable SQL logging to track the problem
2. If it ok for you, you can set in LSPS_SETTINGS parameter CUT_LONG_STRINGS to true and long values will be truncated before saving into DB (and in the log you will see truncated values).

CUT_LONG_STRINGS:
Initialized on startup from database. Change of database value is not reflected in runtime. Can be changed in runtime via JMX. It does not change database value.

Regards,
Roman

nbe
 
Posts: 5
Joined: Mon Jul 11, 2016 6:48 pm

Re: JBA errors with InComm's LaunchIT

Fri Sep 16, 2016 3:33 pm

More JBA errors have been seen as well. Any insight is greatly appreciated.

19:31:08,610 ERROR [org.hibernate.engine.jdbc.batch.internal.BatchingBatch] (EJB default - 1) HHH000315: Exception executing batch [Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1]
19:31:08,622 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014120: Error invoking timeout for timer: [id=5ee3ab03-1069-4aa6-b911-1390ee967f8d timedObjectId=launchit-ear-5.0.2.lsps-engine-exec.Living Systems Process Suite.ProcessAgentImpl auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@77a49bb initialExpiration=Tue Sep 06 19:31:00 EDT 2016 intervalDuration(in milli sec)=0 nextExpiration=null timerState=CANCELED info=110403624]: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleEndTransactionException(CMTTxInterceptor.java:137) [jboss-as-ejb3-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:117) [jboss-as-ejb3-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
at org.jboss.as.ejb3.tx.TimerCMTTxInterceptor.endTransaction(TimerCMTTxInterceptor.java:67) [jboss-as-ejb3-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]

Roman Kubascik
 
Posts: 57
Joined: Thu Apr 16, 2015 9:05 am

Re: JBA errors with InComm's LaunchIT

Tue Sep 20, 2016 10:27 am

The Error "Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1" comes when:
1. Someone tried to update row which doesn't exist in the DB. It doesn't exist because of previous error (e.g. SQLServerException...).
2. Someone set generated ID with the setter method.
To locate the problem I recommend to enable SQL logging to see which query was executed before this error appeared.
I would first fix the problem "SQLServerException: String or binary data would be truncated." then you will see if there are any other problems.

Return to Integration

Who is online

Users browsing this forum: No registered users and 1 guest