Jira - 9.4.21 - SQL Exception while executing the following:INSERT INTO public.clusternode

[Francisco Ferrara]

ERROR : Caused by: org.ofbiz.core.entity.GenericEntityException: while inserting: 

This error is because in the cluster.properties file the jira.node.id field is more than 60 characters long

[GenericEntity:ClusterNode][nodeState,ACTIVE][ip,jira-service-0000][cacheListenerPort,40001][nodeVersion,9.4.21][nodeId,jira-service-0000{'content': '1532262863357268066', 'redirected': False, 'url': 'http://metadata.google.internal/computeMetadata/v1/instance/id', 'status': 200, 'metadata_flavor': 'Google', 'content_type': 'application/text', 'etag': '67267932839549f3', 'date': 'Tue, 14 May 2024 14:04:18 GMT', 'server': 'Metadata Server for VM', 'connection': 'Close', 'content_length': '19', 'x_xss_protection': '0', 'x_frame_options': 'SAMEORIGIN', 'cookies_string': '', 'cookies': {}, 'msg': 'OK (19 bytes)', 'elapsed': 0, 'changed': False, 'failed': False}][nodeBuildNumber,940021][timestamp,1715696900700]

(SQL Exception while executing the following:INSERT INTO public.clusternode (NODE_ID, NODE_STATE, TIMESTAMP, IP, CACHE_LISTENER_PORT, NODE_BUILD_NUMBER, NODE_VERSION) VALUES (?, ?, ?, ?, ?, ?, ?) (ERROR: value too long for type character varying(60)))


Workround:

check the file cluster.properties  and verify that the node is no larger than 60 characters

example:

/var/atlassian/application-data/jira/cluster.properties =

jira.node.id =  jira-service-0000{'content': '1532262863357268066', 'redirected': False, 'url': 'http://metadata.google.internal/computeMetadata/v1/instance/id', 'status': 200, 'metadata_flavor': 'Google', 'content_type': 'application/text', 'etag': '67267932839549f3', 'date': 'Tue, 14 May 2024 14:04:18 GMT', 'server': 'Metadata Server for VM', 'connection': 'Close', 'content_length': '19', 'x_xss_protection': '0', 'x_frame_options': 'SAMEORIGIN', 'cookies_string': '', 'cookies': {}, 'msg': 'OK (19 bytes)', 'elapsed': 0, 'changed': False, 'failed': False}][nodeBuildNumber,940020][timestamp,1715696900700]

Workround

jira.node.id =  jira-service-0000