In many instances, file configuration issues may result in an inability to login to the Semarchy platform. For the scenario outlined in the article examples, users attempting to login can successfully navigate to the Welcome page, but will see an error once credentials are entered and validation is attempted. Resolving this type of error is will require system admin access, since configuration changes are usually required in order to fix this problem. The purpose of this article is to provide troubleshooting steps that will aid users in resolving this category of errors.

Description of error

Users attempting to login/authenticate to Semarchy xDM using a browser and standard connection URL may encounter this error: 500 Internal Server Error. A user will encounter this error on screen after they have entered their credentials and are attempting to login.

Status 500 Internal Server Error


Step 1 - Review Error Logs

[Best Practice Recommendation] In order to minimize "noise" from your logs, clear all contents from the logs directory first, then regenerate the error. Using the method most familiar, a)stop Tomcat, b)clear the logs directory, then c)restart Tomcat and reattempt the connection.

Navigate to the Tomcat logs folder and open the catalina.xx.log file. In our excerpt below, we can see two statements that reference SEMARCHY_REPOSITORY. The first is a SEVERE ERROR, while the second message is a WARNING. This is a very strong indication the issue resides within the SEMARCHY_REPOSITORY section of the semarchy.xml file.

Locate and open the Catalina log file.
12-Nov-2020 09:20:21.197 SEVERE [Blueprint Extender: 1] org.apache.tomcat.jdbc.pool.ConnectionPool.init Unable to create initial connections of pool.
  java.sql.SQLException: Driver:org.postgresql.Driver@61393fd0 returned null for URL:jdbc:sqlserver://localhost:1433;databaseName=SEMARCHY_REPOSITORY

 12-Nov-2020 09:20:01.366 WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference Login failed for user 'SEMARCHY_REPOSITORY'.   

Step 2 - Make Appropriate Changes and Restart Tomcat

Locate and open the semarchy.xml file. Since the error above points to an issue with the SEMARCHY_REPOSITORY resource, we review the related section first. The most common parameter values to review are the url, username, and password. In the example below, the url value is simply incorrect and should be updated to reflect a valid Postgres database location.

Incorrect URL value

After identifying the misconfigured section, update the value (corrected value below), save the changes, and restart Tomcat.