Can anyone tell me why I receive the error message: SQLException while posting alert: java.sql.SQLException: ERROR: More than one tuple returned by a subselect used as an expression in my eventEngine.log. The only alerts I receive is software and firmware changes and not box down or anything else.
Okt 18 08:45:53 2005 eventEngine BOX_STATE_EVENTHANDLER-6-CALLBACK Alert processing done, processed 1, queue size 34 Okt 18 08:45:53 2005 eventEngine BOX_STATE_EVENTHANDLER-6-CALLBACK Box down: 158.38.xx.xx Okt 18 08:45:53 2005 eventEngine BOX_STATE_EVENTHANDLER-6-CALLBACK Added alert: e=7731 d=222 n=117 t=boxState s=x [status=down] Okt 18 08:45:53 2005 eventEngine DEV_DB-6-POSTALERT Posting alert: e=7731 d=222 n=117 t=boxState s=x [status=down] Okt 18 08:45:53 2005 eventEngine DEV_DB-6-POSTALERT SQLException while posting alert: java.sql.SQLException: ERROR: More than one tuple returned by a subselect used as an expression.
Okt 18 08:45:53 2005 eventEngine BOX_STATE_EVENTHANDLER-4-CALLBACK While posting netel down alert, PostAlertException: Got SQLException: ERROR: More than one tuple returned by a subselect used as an expression.
Okt 18 08:45:53 2005 eventEngine BOX_STATE_EVENTHANDLER-6-HANDLE Scheduling callback in 883 ms (0 s) Okt 18 08:45:53 2005 eventEngine BOX_STATE_EVENTHANDLER-6-CALLBACK Alert processing done, processed 1, queue size 34
From kreide at gmail.com Tue Oct 18 01:16:43 2005
From: kreide at gmail.com (Kristian Eide) Date: Tue Oct 18 09:16:48 2005 Subject: [Nav-users] java.sql.SQLException: ERROR In-Reply-To: 8A65B72C71E7484FBE1862045AAC5A8FB73BC2@embla.ansatt.hint.no References: 8A65B72C71E7484FBE1862045AAC5A8FB73BC2@embla.ansatt.hint.no Message-ID: b4c110fd0510180016ud40dff9l3c8fbb736c7d2662@mail.gmail.com
Can anyone tell me why I receive the error message: SQLException while posting alert: java.sql.SQLException: ERROR: More than one tuple returned by a subselect used as an expression in my eventEngine.log. The
Yes, this is most likely caused by too many entries in the alerttype table. My suggestion would be to delete all entries from that table and re-run the INSERT statements from manage.sql.
-- Kristian