Skip to:
When a notification is larger than 4000 chars, it's inserted in the database (table "notifications", column "textmsg") truncated to 4000 chars.
If a notification is HTML-based, when presented in the WebApp, the layout of the list of notifications is going to be bogus.
In my installation of version 1.8.17, I've patch:
"OnmsNotifcation.java" to remove the "@Column(size=4000)" annotation to method "getTextMsg()
NotificationManager.java to remove the hardcoded limitation to 4000 chars in method "insertNotice(..)"
After some tests, the problem was resolved.
Thanks to Alejandro Galue, who pinpointed the exact location of the problem. He's email is attached, to document the issue.
Fixed on revision fa9e0fab900fab36987ebb8525f2c68fc322e678 for 1.12 and merged into master on revision 2bacc95df15be80bd8bb039f8463777ae2832007
When a notification is larger than 4000 chars, it's inserted in the database (table "notifications", column "textmsg") truncated to 4000 chars.
If a notification is HTML-based, when presented in the WebApp, the layout of the list of notifications is going to be bogus.
In my installation of version 1.8.17, I've patch:
"OnmsNotifcation.java" to remove the "@Column(size=4000)" annotation to method "getTextMsg()
NotificationManager.java to remove the hardcoded limitation to 4000 chars in method "insertNotice(..)"
After some tests, the problem was resolved.
Thanks to Alejandro Galue, who pinpointed the exact location of the problem. He's email is attached, to document the issue.