Hi, Developer Community! 
The first EAP release of Jira Software 10.6 and Jira Service Management 10.6 is ready for testing.
You can download the EAP from this page. If you’re using maven.atlassian.com, the version is 10.6.0-m0003.
To find out more about this EAP release, check out Preparing for Jira 10.6.
If you have any comments, post them below.
Happy testing,
The Jira Data Center team
Hi, Developer Community!
The second EAP has been released. I’ve updated the main post with the EAP02 details.
Highlights:
Also, we’re deprecating the following databases:
Starting with the upcoming Jira 11 release, we’ll discontinue support for the following databases:
on both EAP versions the log shows a lot of the following entries (env generated by atlas-run)
2025-04-15 07:36:41,460+0200 Caesium-1-3 WARN ServiceRunner [o.o.c.entity.transaction.JNDIFactory] NamingException while finding UserTransaction named java:comp/env/UserTransaction in JNDI.
javax.naming.NameNotFoundException: Name [UserTransaction] is not bound in this Context. Unable to find [UserTransaction].
at org.apache.naming.NamingContext.lookup(NamingContext.java:520)
at org.apache.naming.NamingContext.lookup(NamingContext.java:148)
at org.apache.naming.NamingContext.lookup(NamingContext.java:530)
at org.apache.naming.NamingContext.lookup(NamingContext.java:148)
at org.apache.naming.NamingContext.lookup(NamingContext.java:530)
at org.apache.naming.NamingContext.lookup(NamingContext.java:155)
at org.apache.naming.SelectorContext.lookup(SelectorContext.java:144)
at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
at org.ofbiz.core.entity.transaction.JNDIFactory.getUserTransaction(JNDIFactory.java:126)
at com.atlassian.jira.ofbiz.sql.TransactionFactoryInterfaceWrapper.getUserTransaction(TransactionFactoryInterfaceWrapper.java:31)
at org.ofbiz.core.entity.TransactionFactory.getUserTransaction(TransactionFactory.java:106)
at org.ofbiz.core.entity.TransactionUtil.getStatus(TransactionUtil.java:91)
at org.ofbiz.core.entity.jdbc.SQLProcessor.getConnection(SQLProcessor.java:380)
at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:176)
at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:89)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:566)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:552)
at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:114)
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:296)
at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:172)
at com.atlassian.jira.entity.EntityEngineImpl.createValue(EntityEngineImpl.java:29)
at com.atlassian.jira.scheduler.OfBizRunDetailsDao.addRunDetails(OfBizRunDetailsDao.java:112)
at com.atlassian.scheduler.core.AbstractSchedulerService.addRunDetails(AbstractSchedulerService.java:136)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:91)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:500)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJobWithRetryOnFailure(CaesiumSchedulerService.java:463)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:413)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
at java.base/java.lang.Thread.run(Thread.java:840)
Cheers
Adam
Hi @adam.labus.
Can you please tell us, which version of Java did you use?
I was trying to reproduce the error you logged following this setup up instruction and I did not manage to see this error log in may case. I used Java 17, which the suggested Java version for the latest Jira Core (Server) and Jira Software instalations.
Also, can you, please, give us more information about the instalation/setup process you followed?
With regards,
Andriy.
I am using Java 17 - below is my configuration - the error occurs on the vanilla version (atlas-run)
atlas-version
ATLAS Version: 9.1.1
ATLAS Home: /Applications/Atlassian/atlassian-plugin-sdk
ATLAS Scripts: /Applications/Atlassian/atlassian-plugin-sdk/bin
ATLAS Maven Home: /Applications/Atlassian/atlassian-plugin-sdk/apache-maven-3.9.8
AMPS Version: 9.1.1
--------
Executing: /Applications/Atlassian/atlassian-plugin-sdk/apache-maven-3.9.8/bin/mvn --version -gs /Applications/Atlassian/atlassian-plugin-sdk/apache-maven-3.9.8/conf/settings.xml
Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
Maven home: /Applications/Atlassian/atlassian-plugin-sdk/apache-maven-3.9.8
Java version: 17.0.14, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.4", arch: "aarch64", family: "mac"
pom.xml
<jira.version>10.6.0-m0003</jira.version>
<platform.version>7.3.9</platform.version>
<amps.version>9.3.2</amps.version>
Cheers
Adam
Hi Adam,
Thank you for providing more information. Let me look at it carefully and try reproducing your problem once again.
We’ll get back once I have conducted my experiment.
With regards,
Andriy.
Hi @adam.labus ,
Thanks again for sharing the detailed information about your Java 17 setup, SDK version, and pom.xml.
Based on your previous message mentioning you used Java 17 (which is the recommended version), I did try to reproduce the NamingException following the standard setup procedures you referenced, but unfortunately, I wasn’t able to observe the same WARN logs in my test environment.
To help us figure out what might be different between our setups or the steps we’re taking, could you please clarify a few more things about how you encounter the issue?
atlas- commands you typically run, starting from when you open your terminal in the project directory until you observe the WARN messages in the log? (e.g., atlas-clean, atlas-package, atlas-run, etc.)pom.xml specifies <amps.version>9.3.2</amps.version>, while your SDK’s default seems to be 9.1.1 (from the atlas-version output). Is this AMPS version override intentional or required for your project? If it’s straightforward to test, could you quickly check if the error persists if you temporarily remove this property and let the SDK use its default AMPS version?WARN messages start appearing in the logs? Is it immediately after Jira finishes starting up via atlas-run, or do they only begin logging after you perform certain actions within the Jira UI or interact with your plugin?atlas-create-jira-plugin and then immediately run atlas-run in that new directory, without adding any custom code or significant dependencies?Your answers to these questions will be very helpful in tracking down the difference and resolving this potential issue in the EAP. Thanks again for your collaboration!
With regards,
Andriy.
I checked the change of AMPS version - on version 9.1.1 everything works correctly without errors in the logs, I double checked versions 9.3.1 and 9.3.2 - they have the same error in the logs
I do not verify further steps, because 9.1.1 works correctly 
Thank you!.
Hi @adam.labus ,
That’s great news that reverting to AMPS version 9.1.1 resolved the logging errors for you. I understand that this addresses the immediate issue, and you’re comfortable using this version for now.
If anything changes or if you encounter any other issues while working with the EAP, please don’t hesitate to reach out. We’re happy to help further if needed.
With regards,
Andriy.