JIRA fails to start after migration from JSM 5.12.26 to JSM 10.3.12

Alexandra Mihaela Apostol

Hello,

We are trying to upgrade from JIRA JSM 5.12.26 to JSM 10.3.12 on DC non clusterd.
Since for JIRA LTS versions we have used the installer as for previous instalations. 

We have configured the new configuration files with our data, and have successfully installed JAVA 17.

I have used ojdbc8.jar and we are connecting to an oracle database version 19c. 

Even so, JIRA fails to start and gives the errors below in the logs:

atlassian-jira.log:

---

2025-10-20 14:23:45,302+0200 http-nio-8080-exec-4 WARN anonymous 863x3x1 1rz8t02 172.28.249.112 /secure/johnson/data [c.a.j.config.properties.ApplicationPropertiesStore] Exception getting property 'jira.security.csp.sandbox.excluded.content.type' from database. Using default

com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Could not find a field-type definition with name "oracle19g"

at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2085)

at com.google.common.cache.LocalCache.get(LocalCache.java:4017)

at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4040)

at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4989)

at com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4996)

[...]

com.atlassian.jira.config.properties.ApplicationPropertiesStore.getStringFromDb(ApplicationPropertiesStore.java:251)

at com.atlassian.jira.config.properties.ApplicationPropertiesStore.getString(ApplicationPropertiesStore.java:314)

at com.atlassian.jira.config.properties.ApplicationPropertiesImpl.getDefaultBackedString(ApplicationPropertiesImpl.java:70)

... 1 filtered

at java.base/java.util.Optional.flatMap(Optional.java:289)

... 24 filtered

at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1189)

at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:658)

at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)

at java.base/java.lang.Thread.run(Thread.java:840)

---

catalina.out:

---

2025-10-20 14:29:32,194+0200 JIRA-Bootstrap ERROR      [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.

java.lang.UnsatisfiedLinkError: /opt/atlassian/jira/temp/bc-lts-jnihr2rsbltmt-libs/libbc-lts-avx.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /opt/atlassian/jira/temp/bc-lts-jnihr2rsbltmt-libs/libbc-lts-avx.so)

at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)

at java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)

at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)

at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)

at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2394)

at java.base/java.lang.Runtime.load0(Runtime.java:755)

at java.base/java.lang.System.load(System.java:1970)

at org.bouncycastle.crypto.NativeLoader$3.run(Unknown Source)

at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)

at org.bouncycastle.crypto.NativeLoader.loadDriver(Unknown Source)

at org.bouncycastle.crypto.NativeLoader.<clinit>(Unknown Source)

at org.bouncycastle.crypto.CryptoServicesRegistrar.<clinit>(Unknown Source)

at org.bouncycastle.jce.provider.BouncyCastleProvider.<clinit>(Unknown Source)

at com.atlassian.secrets.service.aes.SecurityProvider.get(SecurityProvider.java:18)

at com.atlassian.secrets.service.aes.AESKeyGenerator.generateSecretKey(AESKeyGenerator.java:86)

at com.atlassian.secrets.service.aes.AESKeyGenerator.generateDefaultKey(AESKeyGenerator.java:56)

at com.atlassian.secrets.service.SecretConfigManager.maybeGenerateDefaultConfigFile(SecretConfigManager.java:98)

at com.atlassian.secrets.service.SecretServiceFactory.lambda$getOrCreateConfig$0(SecretServiceFactory.java:111)

[...]

at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)

at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:107)

at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:162)

at java.base/java.lang.Thread.run(Thread.java:840)

2025-10-20 14:29:32,199+0200 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.

Exception in thread "JIRA-Bootstrap" java.lang.UnsatisfiedLinkError: /opt/atlassian/jira/temp/bc-lts-jnihr2rsbltmt-libs/libbc-lts-avx.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /opt/atlassian/jira/temp/bc-lts-jnihr2rsbltmt-libs/libbc-lts-avx.so)

at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)

at java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)

at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)

at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)

at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2394)

at java.base/java.lang.Runtime.load0(Runtime.java:755)

at java.base/java.lang.System.load(System.java:1970)

at org.bouncycastle.crypto.NativeLoader$3.run(Unknown Source)

at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)

at org.bouncycastle.crypto.NativeLoader.loadDriver(Unknown Source)

at org.bouncycastle.crypto.NativeLoader.<clinit>(Unknown Source)

at org.bouncycastle.crypto.CryptoServicesRegistrar.<clinit>(Unknown Source)

at org.bouncycastle.jce.provider.BouncyCastleProvider.<clinit>(Unknown Source)

at com.atlassian.secrets.service.aes.SecurityProvider.get(SecurityProvider.java:18)

at com.atlassian.secrets.service.aes.AESKeyGenerator.generateSecretKey(AESKeyGenerator.java:86)

at com.atlassian.secrets.service.aes.AESKeyGenerator.generateDefaultKey(AESK

I have tried using ojdbc11.jar or ojdbc17.jar, but it failed. 
Initially, before the upgrade we were pointing to the same database, and it worked as expected. 
Since this is a DEV env, for the moment I don't have an DNS in FQDN configured by the network team, but even so, this jira used to start without any issues using http://ip:port/jira.

Any insight would be helpful.

Thank you!
Best regards,
Alexandra-Mihaela Apostol

Tuncay Senturk _Snapbytes_

Hi @Alexandra Mihaela Apostol 

First, I'd say, from Jira 10 onward Atlassian removed the Linux installers, they recommend tar.gz method. 

Anyway, checking the logs, I see;

UnsatisfiedLinkError ... libbc-lts-avx.so: /lib64/libc.so.6: version `GLIBC_2.14' not found

Jira 10 bundles a BouncyCastle native library; on older Linux it fails when glibc < 2.14

I am not sure if this is the root cause but I'd suggest upgrading the OS to a supported with newer glibc (e.g Ubuntu 20.04)

The other error is 'Could not find a field-type definition with name "oracle19g" '

this usually means the database-type in your dbconfig.xml doesn't match a known field type. It should be something like

<database-type>oracle10g</database-type>

Don't use oracle19g there, try oracle10g.

Regarding the JDBC driver, Atlassian recommends 19.3 ojdbc8 driver. It supports JDK 17, I believe.

Long story short, it's hard for me to say what is causing the problem but there may be several and I tried to list them above.