[
https://issues.apache.org/jira/browse/AIRAVATA-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568956#comment-15568956
]
Marcus Christie commented on AIRAVATA-2159:
-------------------------------------------
Supun found the problem. The NOTIFICATION_MESSAGE doesn't allow messages longer
than 256 characters. From the airavata.log on gw77
{noformat}
Caused by: <openjpa-2.2.0-r422266:1244990 fatal general error>
org.apache.openjpa.persistence.Persisten
ceException: Data truncation: Data too long for column 'NOTIFICATION_MESSAGE'
at row 1 {prepstmnt 13516
55151
INSERT INTO NOTIFICATION (NOTIFICATION_ID, CREATION_DATE,
EXPIRATION_DATE, GATEWAY_ID, NOTIFICATION_MESSAGE, PRIORITY,
PUBLISHED_DATE, TITLE)
VALUES (?, ?, ?, ?, ?, ?, ?, ?)
[params=(String) 33ffca17-d998-4deb-9fb4-8e725c40b799, (Timestamp) 2016-10-12
10:41:00.457, (Timestamp)
2016-10-26 10:40:00.0, (String) seagrid, (String) We will be performing
maintenance on the SDSC Datace
nter power infra..., (String) NORMAL, (Timestamp) 2016-10-19 10:40:00.0,
(String) SDSC Comet, Gordon Ma
intenance]} [code=1406, state=22001]
FailedObject:
org.apache.airavata.registry.core.experiment.catalog.model.Notification@74657c26
at
org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4918)
at
org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4878)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatement
ManagerImpl.java:143)
at
org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingP
reparedStatementManagerImpl.java:79)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementM
anagerImpl.java:99)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerIm
pl.java:87)
at
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:55
0)
at
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:10
6)
at
org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdat
eManager.java:59)
at
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:103)
at
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:713)
at
org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
... 28 more
Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Data truncation:
Data too long for column
'NOTIFICATION_MESSAGE' at row 1 {prepstmnt 1351655151
INSERT INTO NOTIFICATION (NOTIFICATION_ID, CREATION_DATE,
EXPIRATION_DATE, GATEWAY_ID, NOTIFICATION_MESSAGE, PRIORITY,
PUBLISHED_DATE, TITLE)
VALUES (?, ?, ?, ?, ?, ?, ?, ?)
[params=(String) 33ffca17-d998-4deb-9fb4-8e725c40b799, (Timestamp) 2016-10-12
10:41:00.457, (Timestamp) 2016-10-26 10:40:00.0, (String) seagrid, (String) We
will be performing maintenance on the SDSC Datacenter power infra..., (String)
NORMAL, (Timestamp) 2016-10-19 10:40:00.0, (String) SDSC Comet, Gordon
Maintenance]} [code=1406, state=22001]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:247)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:223)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:72)
...
{noformat}
> SEAGrid Notice creation error.
> -------------------------------
>
> Key: AIRAVATA-2159
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2159
> Project: Airavata
> Issue Type: Bug
> Reporter: Sudhakar Pamidighantam
> Assignee: Marcus Christie
>
> When I tried to create a new notice out of the recent XSEDE new from Mahidhar
> (copied below) I get an error as follows
> An error has occurred. Please try again later.
> Which repreats if I click on create button again.
> Not sure if I am doing something.
> Begin forwarded message:
> From: XSEDE User News <n...@xsede.org>
> Subject: SDSC Comet, Gordon Maintenance: 6AM-6PM (PT), Oct 25, 2016
> Date: October 11, 2016 at 1:14:44 PM EDT
> To: <pamid...@iu.edu>
> Reply-To: No Reply <n...@xsede.org>
> A new message has been posted to XSEDE User News.
> Categories: Comet (SDSC), Gordon (SDSC)
> Start time: 25 Oct, 2016 06:00 PDT
> End time: 25 Oct, 2016 18:00 PDT
> Posted on 11 Oct, 2016 16:49 UTC by Mahidhar Tatineni
> We will be performing maintenance on the SDSC Datacenter power infrastructure
> on Oct 25, 2016. Both Comet and Gordon will be unavailable 6AM-6PM (PT) on
> Tuesday, Oct 25, 2016. We have reservations in place on both machines so jobs
> that do not fit in the window before the maintenance will be queued and run
> after the maintenance is completed. Jobs will not run during the maintenance.
> Please email h...@xsede.org if you have any questions.
> ----------------------------------------
> This message was generated by XSEDE User News v3.0. You can view this
> message in the XSEDE User Portal at
> https://portal.xsede.org/web/xup/user-news/-/news/item/7715.
> You can manage your XSEDE User News subscriptions at
> https://portal.xsede.org/group/xup/user-news/-/news/manage-subscription.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
