This page last changed on Oct 31, 2006 by david.soul@atlassian.com.
Identifying The Error
If Confluence will not start due to an error:
java.lang.NullPointerException
at com.atlassian.plugin.DefaultPluginManager.getEnabledModuleDescriptorsByClass(DefaultPluginManager.java:495)
...
Check your Confluence log files for a database listener error reporting that the SID is unknown. On standalone, the log file to check is atlassian-confluence.log in the logs directory of your Confluence install, for example C:\confluence-2.2.9-std\logs\atlassian-confluence.log. Scroll to the bottom of the file and search or browse for a "Listener refused" error such as:
Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
my.dbserver.com:1522:myschema
This example was thrown on an Oracle database, where my.dbserver.com was the database server, and myschema was the Oracle SID. Your error may be different.
Fixing The Error
You will need to modify your database connection URL specified in the Resource for your database. On standalone, this is in the server.xml file in the conf directory of your confluence install, for example C:\confluence-2.2.9-std\conf\server.xml. An example connection URL is:
jdbc:oracle:thin:@my.dbserver.com:1521:myschema
This example has a server hostname of my.dbserver.com and a schema ID of myschema.
If your connection URL is missing the @ symbol before the server hostname, add it and restart. If the @ symbol is present, check that the schema ID is correct. Oracle users can check the SID of their database in the Oracle tnsnames file.
|