PSQLException value too long for type character varying

Sverre Moe November 23, 2015

After we upgraded to JIRA 7, all our BigPicture programs are gone. We did also update BigPicture to 3.1.0-jira7. Looking in the JIRA log file there is a lot of error, and warning messages.

2015-11-23 12:38:37,916 http-nio-8443-exec-4 WARN user1 758x30232x1 1j71xsk 10.11.4.74 /plugins/servlet/softwareplant-bigpicture/program [c.atlassian.ozymandias.SafePlugin
PointAccess] Unable to run plugin code because of 'java.lang.UnsupportedOperationException - null'.
2015-11-23 12:51:56,022 http-nio-8443-exec-8 ERROR user1 771x31113x1 13lx0d8 10.11.3.115 /rest/softwareplant-bigpicture/1.0/program [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: bundle [eu.softwareplant.bigpicture]
com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [eu.softwareplant.bigpicture]
        at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:95)
        at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:86)
        at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:42)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
        - name:PostgreSQL
        - version:9.1.12
        - minor version:1
        - major version:9
        - name:PostgreSQL Native Driver
        - version:PostgreSQL 9.1 JDBC4 (build 903)
org.postgresql.util.PSQLException: ERROR: value too long for type character varying(450)
        at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:47)
        at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:77)
        at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:72)
        at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)
        at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:34)
        ... 2 filtered
        at java.lang.reflect.Method.invoke(Method.java:497)
        at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:30)
        at com.sun.proxy.$Proxy122.doInTransaction(Unknown Source)
        ... 2 filtered
        at java.lang.reflect.Method.invoke(Method.java:497)
        at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:161)
        at com.sun.proxy.$Proxy122.doInTransaction(Unknown Source)
        at com.atlassian.sal.core.transaction.HostContextTransactionTemplate.execute(HostContextTransactionTemplate.java:21)
        ... 2 filtered
        at java.lang.reflect.Method.invoke(Method.java:497)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
        at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
        at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
        at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
        at com.sun.proxy.$Proxy872.execute(Unknown Source)
        at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory.create(AbstractActiveObjectsFactory.java:72)
        at com.atlassian.activeobjects.internal.DelegatingActiveObjectsFactory.create(DelegatingActiveObjectsFactory.java:32)
        at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:91)
        ... 6 more
Caused by: org.postgresql.util.PSQLException: ERROR: value too long for type character varying(450)
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2101)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1834)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:510)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:372)
        at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
        at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
        at net.java.ao.DatabaseProvider.executeUpdate(DatabaseProvider.java:2484)
        at net.java.ao.DatabaseProvider.executeUpdateForAction(DatabaseProvider.java:2554)
        at net.java.ao.DatabaseProvider.executeUpdatesForActions(DatabaseProvider.java:2517)
        at net.java.ao.schema.SchemaGenerator.migrate(SchemaGenerator.java:99)
        at net.java.ao.EntityManager.migrate(EntityManager.java:132)
        at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:45)

 

 

3 answers

1 accepted

2 votes
Answer accepted
Sverre Moe November 23, 2015

Thanks to excellent support from SoftwarePlant we where able to solve this issue. We modified the table which had a description entry above 450 characters.

SELECT a."ID", a."DESCRIPTION" FROM "AO_0456E7_GANTT" a WHERE LENGTH(a."DESCRIPTION") > 450;
UPDATE "AO_0456E7_GANTT" SET "DESCRIPTION" = 'Add Description' where "ID" = 17;

The problem was still present, so we thought there could be another entry in a different table, but it turns out we needed to restart JIRA after modifying the database.

0 votes
Matthew Jagiello
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 26, 2015

Just like mentioned, the issue was with descriptions longer than 450 characters. The next releases will have a limit set in the fields for typing specifically to prevent this.

0 votes
rrudnicki
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 23, 2015

Hi, 

Looks like you have an explicit 450 character limit. You might not have done this yourself explicitly, but the plugin has done it for you somewhere. 

 Are you getting this error only for those plugins? If so, I recommend you to raise a ticket to SoftwarePlant which is the vendor of those plugins.

 Regards, 

Renato Rudnicki

Sverre Moe November 23, 2015

I have raised an support to SoftwarePlant. Since this is urgent I wanted to increase my chances by voicing the issue here also. I was thinking of manually change the database 450 character limit, but I do not know which table the problem lies with.

Suggest an answer

Log in or Sign up to answer