Am using WebNMS 4.7 in one of the swing Application launched through java WebStart.
The status of the devices is not getting updated after rediscovery is finished.
Events are visible for the Rediscovery started and finished, but their corresponding alarms are not visible.
Found the following exception in logs:
ALERT: Exception thrown on Alert Addition in Fault Manager; Alert key is ==Disc-10.165.148.15 at:
java.lang.NumberFormatException: For input string: "NULL"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:449)
at java.lang.Integer.parseInt(Integer.java:499)
at com.adventnet.nms.store.relational.RelationalObject.setValue(RelationalObject.java:2080)
at com.adventnet.nms.store.relational.RelationalObject.setValuesForInsert(RelationalObject.java:1902)
at com.adventnet.nms.store.relational.RelationalObject.setValuesForInsert(RelationalObject.java:1876)
at com.adventnet.nms.store.relational.RelationalAlert.getStatementsForAdd(RelationalAlert.java:178)
at com.adventnet.nms.store.relational.RelationalObject$ForAdd.addObject(RelationalObject.java:960)
at com.adventnet.nms.store.relational.RelationalObject.addObject(RelationalObject.java:411)
at com.adventnet.nms.store.relational.CommonAlertToRelational.addObject(CommonAlertToRelational.java:508)
at com.adventnet.nms.store.CommonDBStore.addObject(CommonDBStore.java:460)
at com.adventnet.nms.alertdb.AlertLog.updateTheLog(AlertLog.java:343)
at com.adventnet.nms.alertdb.AlertLog.update(AlertLog.java:715)
at com.adventnet.nms.alertdb.FaultMgr.run(FaultMgr.java:729)
at com.adventnet.management.scheduler.WorkerThread.run(WorkerThread.java:70)
[26 Jun 2017 16:05:39:417] ALERT: UserTransactionException in Fault Manager run Method at:
com.adventnet.management.transaction.UserTransactionException: For input string: "NULL" ; nested exception is:
com.adventnet.management.transaction.UserTransactionException: [TransactionAPI] : Transaction Rolled back over a Connection with ID : [77] in Thread : Thread[main-3,5,main], Cause: com.adventnet.management.transaction.UserTransactionException: [TransactionAPI] : Transaction Rolled back over a Connection with ID : [77] in Thread : Thread[main-3,5,main]
com.adventnet.management.transaction.UserTransactionException: [TransactionAPI] : Transaction Rolled back over a Connection with ID : [77] in Thread : Thread[main-3,5,main]
at com.adventnet.management.transaction.TransactionAPI.rollback(TransactionAPI.java:563)
at com.adventnet.management.transaction.TransactionAPI.rollback(TransactionAPI.java:503)
at com.adventnet.nms.alertdb.AlertLog.rollback(AlertLog.java:107)
at com.adventnet.nms.alertdb.AlertLog.updateTheLog(AlertLog.java:369)
at com.adventnet.nms.alertdb.AlertLog.update(AlertLog.java:715)
at com.adventnet.nms.alertdb.FaultMgr.run(FaultMgr.java:729)
at com.adventnet.management.scheduler.WorkerThread.run(WorkerThread.java:70)
Can anybody please help me understand in which scenarios the WebNMS framework throws such exceptions or what can be the root causes?
Am using WebNMS 4.7 in one of the swing Application launched through java WebStart. After 3-4 client connections am getting the following error Dialog, while login:
"Fatal error has occurred on connecting to the server. The server might probably be busy to allow client connections. Please reconnect or try after some time."
The server gets free in about 20 mins, and after that am able to login.
Can anybody please help me understand in which scenarios the WebNMS framework throws this error or what can be the causes? Could not find any related exceptions in the log files.