User Unable to Loging to JIRA even though Directory is Active
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
Following an upgrade to JIRA 7.2.6, users are unable to upgrade anymore. This impacts both internal and users from LDAP.
Diagnosis
Diagnostic Steps
Checking the database confirms that the users do exist in the database and the directories are active.
Check if you have any value in your server.xml different from the default we recommend as seen below:
1 2 3 4 5 6 7 8 9 10 11<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true"/>You can see something similar to the below in your log:
1
2
3
4
5
6
7
8
9
10
11
2016-12-10 12:09:55,985 http-bio-7010-exec-28 ERROR anonymous 729x1198x1 rexser yy.yy.yy.yyy /login.jsp [c.a.jira.ofbiz.ChainedSQLInterceptor] Unexpected exception in com.atlassian.jira.ofbiz.InstrumentedSQLInterceptor@5fd227da
java.lang.IllegalStateException: The OpTimer has been re-used. end() can only be called once!
at
com.atlassian.instrumentation.operations.SimpleOpTimer.end(SimpleOpTimer.java:109)
at com.atlassian.instrumentation.operations.SimpleOpTimer.end(SimpleOpTimer.java:81)
at
2016-12-10 12:09:55,987 http-bio-7010-exec-28 ERROR anonymous 729x1198x1 r4dbw6 172.17.43.173 /login.jsp [o.o.c.entity.jdbc.SQLProcessor] !!! ABANDONED SQLProcessor DETECTED !!!
This probably means that somebody forgot to close an EntityListIterator.
Connection: DelegatingConnectionImpl[connectionPoolInfo=ConnectionPoolInfo{maxSize=30, minSize=20, initialSize=null, maxIdle=20, maxWait=30000, sleepTime=300000, lifeTime=600000, deadLockMaxWait=600000, deadLockRetryWait=10000, validationQuery='select 1 from dual', minEvictableTimeMillis=60000, timeBetweenEvictionRunsMillis=300000, poolPreparedStatements=null, testOnBorrow=false, testOnReturn=null, testWhileIdle=true, maxOpenPreparedStatements=null, numTestsPerEvictionRun=null, removeAbandonedOnBorrow=true, removeAbandonedOnMaintanance=null, removeAbandonedTimeout=300, validationQueryTimeout=null, defaultCatalog=null},sqlConnectionInterceptor=org.ofbiz.core.entity.jdbc.interceptors.connection.SafeDelegatingSqlConnectionInterceptor@3ea4145c]
SQL: nullCause
JIRA possibly has the parameter maxPostSize="0" specified in the server.xml and seems not to be able to process data of the size which is set to infinity.
Solution
Resolution
Remove the parameter maxPostSize="0" from your JIRA Installation > Conf > server.xml file.
Was this helpful?