Preparing for Jira Software 10.0 and Jira Service Management 6.0 - multiple EAPs coming your way

@MateuszWitkowski @AndrzejKotas

Can anyone from the Jira team give an updated estimate on when we can expect Jira 10 to be released for GA?
The initial release estimate on the post was Q2-Q3. Since we’re yet to see a Platform 7 migrated EAP, can we expect Q3 to be the time scope for GA?

1 Like

Hi,

Finally, I managed to get my plugin enabled. But, any page from the plugin is returning 404 error (after stalling for a second or two).

Nothing in the logs related to the plugin.

But, there is this exception:

[INFO] [talledLocalContainer] INFO: Initiating Jersey application, version 'Jersey: 1.19.5-atlassian-17 e82a5696e4ec99aa82f929706300af9a18da3870'
[INFO] [talledLocalContainer] ERROR StatusConsoleListener Could not register mbeans
[INFO] [talledLocalContainer]  javax.management.InstanceAlreadyExistsException: org.apache.logging.log4j2:type=10269ea2,component=Loggers,name=com.atlassian.jira.cluster.DefaultIndexFetcher
[INFO] [talledLocalContainer] 	at java.management/com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:436)
[INFO] [talledLocalContainer] 	at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1865)
[INFO] [talledLocalContainer] 	at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:960)
[INFO] [talledLocalContainer] 	at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:895)
[INFO] [talledLocalContainer] 	at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:320)
[INFO] [talledLocalContainer] 	at java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:523)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.jmx.Server.register(Server.java:400)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.jmx.Server.registerLoggerConfigs(Server.java:362)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:186)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:141)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:632)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:137)
[INFO] [talledLocalContainer] 	at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:61)
[INFO] [talledLocalContainer] 	at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:47)
[INFO] [talledLocalContainer] 	at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:33)
[INFO] [talledLocalContainer] 	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:363)
[INFO] [talledLocalContainer] 	at org.slf4j.bridge.SLF4JBridgeHandler.getSLF4JLogger(SLF4JBridgeHandler.java:202)
[INFO] [talledLocalContainer] 	at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:293)
[INFO] [talledLocalContainer] 	at java.logging/java.util.logging.Logger.log(Logger.java:980)
...

Any ideas why I get the 404 error and why nothing in the logs?
Thanks

Issue upgrading Docker Container from Jira Software 10.0.0-EAP03 to 10.0.0-EAP04
Hi everyone,
I’m encountering issues when upgrading my Docker container from atlassian/jira-software:10.0.0-EAP03 to atlassian/jira-software:10.0.0-EAP04. The previous version runs smoothly with my current setup, but the new container doesn’t work under the same configuration.
Has anyone else faced this problem? Are there specific configuration changes needed for version 10.0.0-EAP04?

Thanks in advance for your help!

jira_1        | 05-Jun-2024 16:53:22.802 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: [/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib]
jira_1        | 05-Jun-2024 16:53:23.913 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
jira_1        | 05-Jun-2024 16:53:23.969 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [1934] milliseconds
jira_1        | 05-Jun-2024 16:53:24.079 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
jira_1        | 05-Jun-2024 16:53:24.080 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.89]
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "root"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.scheduler.JiraSchedulerLauncher"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.web.action.util.LDAPConfigurer"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.DefaultIndexFetcher"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.distribution.localq.rmi.auth.ClusterAuthStatsManager"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.applinks"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "net.java.ao.sql"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "httpaccesslog" for logger config "com.atlassian.jira.web.filters.accesslog.AccessLogFilter"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.index.LuceneCorruptionChecker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin.classloader"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "slowsqlquerylog" for logger config "com.atlassian.jira.issue.search.providers.DbSearchProvider_SLOW"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "org.ofbiz"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.web.exception.WebExceptionChecker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "slowquerylog" for logger config "com.atlassian.jira.issue.search.providers.LuceneSearchProvider_SLOW"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.secrets"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin.osgi.factory"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.config.database"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "net.java.ao"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.user"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.util.system.JiraSystemRestarterImpl"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.jql.resolver"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.bc.dataimport"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "webwork.multipart.MultiPartRequestWrapper"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "app" for logger config "app-monitoring-data-logger"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.plugin.userformat.DefaultUserFormats"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "httpaccesslog" for logger config "com.atlassian.jira.web.filters.accesslog.AccessLogFilterIncludeImages"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.index.AccumulatingResultBuilder"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.DefaultClusterManager"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "net.java.ao.schema.SchemaGenerator"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.activeobjects.osgi"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.index.DefaultIndexEngine"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.util.profiling.filters"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.security"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.bc.user"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.startup"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.index.ha.DefaultNodeReindexService"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.imports"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin.manager.PluginEnabler"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "remoteappssecurity" for logger config "com.atlassian.plugin.remotable.plugin.service.LocalSignedRequestHandler"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "org.ofbiz.core.entity.jdbc.DatabaseUtil"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "profilerlog" for logger config "com.atlassian.util.profiling"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.cache.ehcache.BlockingParallelCacheReplicator"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "net.sf.ehcache.config.CacheConfiguration"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.index.WriterWrapper"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.issue.index.DefaultIndexManager"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "webwork.util.ServletValueStack"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "atlassian-performance"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.ratelimiting"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.distribution.localq.LocalQCacheManager"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.plugin.ext.perforce"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "sqllog" for logger config "com.atlassian.jira.ofbiz.LoggingSQLInterceptor"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.distribution.localq.LocalQCacheReplicator"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "xsrflog" for logger config "com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "ipd" for logger config "ipd-monitoring-data-logger"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.workflow.migration"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.upgrade"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin.spring.scanner.extension.DevModeBeanInitialisationLoggerBeanPostProcessor"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.appconsistency.integrity.IntegrityChecker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "remoteappssecurity" for logger config "com.atlassian.plugin.remotable.plugin.module.permission.ApiScopingFilter"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.soy.impl.GetTextFunction"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.upgrade"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "diagnostics" for logger config "atlassian-diagnostics-data-logger"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.util.index"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.issue.views"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.action.admin"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.service.services.DebugService"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.mail.settings.MailSetting"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.studio.jira.homepage.CloudHomepageFilter"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "securitylog" for logger config "com.atlassian.seraph.filter.LoginFilter"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "performance" for logger config "atlassian-performance-data-logger"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "webwork"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.plugin"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.workflow"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "httpdumplog" for logger config "com.atlassian.jira.web.filters.accesslog.AccessLogFilterDump"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.web.bean.BackingI18n"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "incomingmaillog" for logger config "com.atlassian.mail.incoming"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "org.twdata.pkgscanner"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.issue.index"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.project.version"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.sal.jira.scheduling"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.gadgets"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "remoteappssecurity" for logger config "com.atlassian.plugin.remotable.plugin.module.oauth.OAuth2LOAuthenticator"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.plugins.monitor"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "net.sf.ehcache.distribution"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "ipd-monitoring"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.imports.project"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.propertyset.ComponentCachingOfBizPropertyEntryStore"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin.servlet"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.jql"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.cache.stacktrace"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.project"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "httpaccesslog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "httpdumplog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "sqllog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "querydsllog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "slowquerylog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "slowsqlquerylog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "xsrflog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "securitylog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "outgoingmaillog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "incomingmaillog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "remoteappssecurity" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "apdexlog" for logger config "com.atlassian.jira.util.log.LogMarker"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "securitylog" for logger config "com.atlassian.jira.web.session.currentusers"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.issue.search.providers"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "securitylog" for logger config "com.atlassian.jira.login.security"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "sqllog" for logger config "net.java.ao.DelegateConnectionHandler"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "logMessage.jsp"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "apdexlog" for logger config "com.atlassian.jira.apdex.impl.SendAnalyticsJobRunner"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.distribution.localq"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "app-monitoring"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.cluster.dbr"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.upgrade.tasks.role"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "atlassian-diagnostics"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.web.action.admin.index.IndexAdminImpl"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.service"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "securitylog" for logger config "com.atlassian.seraph"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "remoteappssecurity" for logger config "com.atlassian.plugin.remotable.plugin.OAuthLinkManager"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.gadgets.directory"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.opensymphony"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.upgrade.tasks.UpgradeTask_Build663"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "securitylog" for logger config "com.atlassian.jira.login"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugin.osgi.container"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "startupjdbc" for logger config "jdbc.startup.log"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.jira.web.filters.ThreadLocalQueryProfiler"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "httpclient.wire"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "atlassian.plugin"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "remoteappssecurity" for logger config "com.atlassian.plugin.remotable.plugin.util.http.CachingHttpContentRetriever"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.cache.event"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "org.apache.shindig"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "outgoingmaillog" for logger config "com.atlassian.mail"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.plugins.rest.doclet"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.atlassian.crowd.directory"
jira_1        | ERROR StatusConsoleListener Unable to locate appender "filelog" for logger config "com.sun.jersey.spi.container.servlet.WebComponent"
jira_1        | 05-Jun-2024 16:53:32.944 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
jira_1        | 05-Jun-2024 16:53:32.953 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors
jira_1        | 05-Jun-2024 16:53:33.159 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
jira_1        | 05-Jun-2024 16:53:33.227 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [9257] milliseconds
postgresql_1  | 
postgresql_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
![here|690x138](upload://aMdlJgB3k1SrFX2AxhGliXuna39.png)

3 Likes

I could also not get the EAP04 docker images to startup. And I thought EAP04 is JDK17 only and they published the JDK11 images only (which should not work anymore).
I am still missing the UBI JDK17 images my build process depends on:

atlassian/jira-software:10.0.0-EAP04-ubi9-jdk17
2 Likes

I had the same issue when running Jira EAP 04 (from tar.gz) on Java 11.
Switching Java 11 to 17 resolved the issue for me.

4 Likes

I appreciate the information. I can now test with that tar file for a period. Thanks

Hi all

After Upgrading plugin into rest v2, I am able to start my plugin but I am getting all bean object null in my all controllers (resource class) in Jira 10EAP. can anybody help me?

1 Like

in my case I had to add to my beans the annotations:
@JsonIgnoreProperties(ignoreUnknown = true)
@JsonAutoDetect(fieldVisibility = JsonAutoDetect.Visibility.ANY)
and started to work…

so let me get It, you are using the EAP-04 and modifying it to install java 17 because the image itself it does not work correclty as it is?

Hello @victormartinez

       Thanks for answer
       I am using @Inject and @Autowired to get object of service class but I am getting null object in my controller class in Jira 10EAP. like when I try to call any method of service class from my controller getting null object of that service and I am using annotations @Inject or @Autowired to get object of service class.

Hi Victor,

Not really. Usually Atlassian published the Docker image UBI JDK17.
I now built it myself and pushed it to my private docker hub repo to use it in my builds.

For GitHub Actions you can do so by:

name: push vanilla jira linux-amd64 jdk17 images
on: push
jobs:
  build:
    runs-on: ubuntu-latest
    name: Push linux-adm64 vanilla images to Docker Hub
    steps:
      - name: Check out the repo
        uses: actions/checkout@v3
      - name: Log in to Docker Hub
        uses: docker/login-action@v2
        with:
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_PASSWORD }}
      - run: git clone --recurse-submodule https://bitbucket.org/atlassian-docker/docker-atlassian-jira.git
      - name: Build and push Docker image
        uses: docker/build-push-action@v3
        with:
          push: true
          build-args: |
            JIRA_VERSION=10.0.0-EAP04
          context: docker-atlassian-jira
          # ubi Dockerfile with JDK17
          file: docker-atlassian-jira/Dockerfile.ubi
          tags: mycompany/myrepo:jira10.0.0-EAP04-jdk17-linux-amd64

And you can see I am building the Dockerfile.ubi file which if JDK17 already.

Hello @AndrzejKotas,
can you give us an update on the velocity allowlist. For Confluence 9 we are using the Velocity Allowlist plugin module and it works without problems. It seems like this is not yet available in the jira 10.0.0-m0005 snapshot. Is this observation true and when can we expect it to work? At least your documentation mentions that it is supported in Jira 10.

1 Like

@AndrzejKotas could we please get an update/timeline on when we can expect an EAP with platform 7 integrated?

We have had to pause all work on Jira, as we have a cross-product app that is already migrated to platform 7, at present we cannot start the app up on Jira 10.

3 Likes

Hi @ashraf.teleb85

I am also getting same error did you find any solution.
1 Like

Hi, I have a question about the opensymphony:propertyset dependency.

The opensymphony:propertyset dependency is listed as one of the dependencies that will be removed in Atlassian Data Center Platform 7.0 (link). Because of this, will we need to make any changes to the implementations of our post-functions in our plugins, since the PropertySet classes are used there?

After adding the opensymphony:propertyset dependency with the compile scope, I get an exception when installing the plugin:

Caused by: java.lang.LinkageError: loader constraint violation: loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @236d3aa3 wants to load interface com.opensymphony.module.propertyset.PropertySet. A different interface with the same name was previously loaded by org.apache.catalina.loader.ParallelWebappClassLoader @38d5b107. (com.opensymphony.module.propertyset.PropertySet is in unnamed module of loader org.apache.catalina.loader.ParallelWebappClassLoader @38d5b107, parent loader java.net.URLClassLoader @4fe3c938)
	at java.base/java.lang.ClassLoader.defineClass1(Native Method)
	at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017)

In addition, the dependency itself is included with the jira-core and jira-api dependencies.

[INFO] +- com.atlassian.jira:jira-core:jar:10.0.0-m0005:provided
[INFO] |  \- com.atlassian.crowd:embedded-crowd-core:jar:5.3.0-QR20240130120105:provided
[INFO] |     \- (opensymphony:propertyset:jar:1.3-21Nov03:provided - omitted for conflict with 1.5)
[INFO] \- com.atlassian.jira:jira-api:jar:10.0.0-m0005:provided
[INFO]    +- com.atlassian.core:atlassian-core:jar:9.0.0:provided (version managed from 8.1.0)
[INFO]    |  \- (opensymphony:propertyset:jar:1.5:provided - omitted for duplicate)
[INFO]    +- com.atlassian.core:atlassian-core-user:jar:8.1.0:provided
[INFO]    |  \- (opensymphony:propertyset:jar:1.3-21Nov03:provided - omitted for conflict with 1.5)
[INFO]    \- opensymphony:propertyset:jar:1.5:provided

Hi @EliasBrattliSorensen, as Platform 7 is still in progress yes GA is planned for Q3.

2 Likes

Hello !
Thank you for the feedback. There was indeed a problem with publishing the UBI & JDK17 docker images. They have now been re-published and are available.
Also, JDK 11 images have been pulled has it is not supported.

3 Likes

I know it’s been a while, but we are working hard to implement these changes for you. We’re very close, and I hope we will be able to share an EAP build with Platform 7 integrated soon, most likely next week.

1 Like

Thank you for the update @AndrzejKotas! Happy to hear that you’re getting closer. The other DC teams have provided a very concrete timeline from the publication of an EAP until GA. Is the Jira team able to provide something similar? Are you plannning the EAP period to be for example one month, so early August? Or is it more likely to be early September, or late Sepember for GA? All the aforementioned are within Q3, but the difference matters and now that we’re very soon in Q3, a vague Q3 estimate doesn’t help much. Managing expectations for this will be of great help for our planning compatibility testing in the time to come.

Thanks, @EliasBrattliSorensen. Regarding the EAP period, the way we understand it, we’ve been in it since March, when we published the first EAP build and the majority of breaking changes you have already seen or experienced. This EAP will be focused on exposing Platform 7 integration, which is the last piece of the puzzle.

If all goes well(the happy path) you can expect

  • one more EAP build ~ first half of July - focused on polishing the Platform integration
  • RC towards the end of July

Obviously we will be looking into your feedback following the Platform integration EAP and adjust the plan accordingly.

Our goal currently is to have Jira code ready with a given scope so that we can better support you in closing on compatibility.

1 Like