-
Bug
-
Resolution: Fixed
-
Low
-
5.0, 5.2.11
-
- JIRA 5
- Windows 7 64 bits
- JDK SE 1.6.0_29-b11 (32 bits)
- SQL server 2008 Express edition | Mysql 5.5 | Postgres 9.1.9 | Oracle 10 and 11G
-
5
-
Even after a successful test connection using config.bat file, JIRA is unable to connect database using password with special character. That error was confirmed using SQL 2008 and Mysql 5.5
As an example, use fz2/Gf%uX!FK;99= as password
Step by Step to reproduce:
- Create new database
- Grant access to a new user using fz2/Gf%uX!FK;99= as user password
- Configure JIRA and test connection using config.bat file
- Try so startup JIRA with startup.bat
I tried to use parent encoding and quotes, didn’t work too.
The following error appear in the atlassian-jira.log
2013-06-03 14:50:17,043 main ERROR [NoModule] Error getting datasource via DBCP: JdbcDatasourceInfo{uri='jdbc:jtds:sqlserver://nywcl1150db01:7001/JIRAPREVIEW1;autoCommit=false', driverClassName='net.sourceforge.jtds.jdbc.Driver', username='jirapreview1', password='********', isolationLevel='null', connectionProperties=null, connectionPoolInfo=ConnectionPoolInfo{maxSize=20, minSize=20, initialSize=null, maxIdle=20, maxWait=30000, sleepTime=300000, lifeTime=600000, deadLockMaxWait=600000, deadLockRetryWait=10000, validationQuery=null, minEvictableTimeMillis=null, timeBetweenEvictionRunsMillis=null, poolPreparedStatements=null, testOnBorrow=null, testOnReturn=null, testWhileIdle=null, maxOpenPreparedStatements=null, numTestsPerEvictionRun=null, removeAbandonedTimeout=300, validationQueryTimeout=null, defaultCatalog=null}}
java.lang.RuntimeException: javax.management.InstanceAlreadyExistsException: com.atlassian.jira:name=BasicDataSource
at org.weakref.jmx.MBeanExporter.export(MBeanExporter.java:45)
at org.apache.commons.dbcp.ManagedBasicDataSource.exportMBean(ManagedBasicDataSource.java:70)
at org.apache.commons.dbcp.ManagedBasicDataSource.<init>(ManagedBasicDataSource.java:61)
at org.apache.commons.dbcp.ManagedBasicDataSourceFactory.createDataSource(ManagedBasicDataSourceFactory.java:278)
at org.ofbiz.core.entity.transaction.DBCPConnectionFactory.createDataSource(DBCPConnectionFactory.java:190)
at org.ofbiz.core.entity.transaction.DBCPConnectionFactory.getConnection(DBCPConnectionFactory.java:91)
at org.ofbiz.core.entity.ConnectionFactory.tryGenericConnectionSources(ConnectionFactory.java:69)
....
Caused by: javax.management.InstanceAlreadyExistsException: com.atlassian.jira:name=BasicDataSource
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at org.weakref.jmx.MBeanExporter.export(MBeanExporter.java:39)
... 140 more
Workaround
Use a password without special characters (limit the password to using _ or . with alphanumeric characters only).
- has a regression in
-
JRASERVER-66755 Regression: Cannot use special characters in the database password
- Gathering Impact