|
|
Luca Pasquali created an issue |
|
diskquota: impossible to configure JNDI on vanilla installation of geoserver |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.17.3 |
|
Assignee: |
Unassigned |
|
Attachments: |
Screenshot from 2020-10-23 22-55-08.png, image-2020-11-05-10-49-35-304.png |
|
Components: |
Configuration |
|
Created: |
05/Nov/20 10:59 AM |
|
Environment: |
Tested on Centos 6,7 SLES 15 SP1, Ubuntu Focal 20.04 |
|
Priority: |
|
|
Reporter: |
Medium|
In brief: Demonstration As in this image when I try to configure diskquota on a brand new clean install of geoserver 2.17.3 with and empty datadir, all looks like to work when hitting save but actually it does not. I get this misleading error in the logs: If I re-open the diskquota a strange, uncomplete connection pool menu (no jndi!) opens up:
I tested to change the correct database password with a wrong one in the jndi config of context.xml and I get the expected error if I try to save, demonstrating the jdbc error above is not trustable as jdbc does his job and connects with a wrong password; I used always the jdbc driver in the geoserver war (no jdbc driver was present anywhere but the said one while reproducing, as the one inside the war should suffice):
If I configure the database for diskquota as native geoserver’s connection pooling, everthing is ok. |
|
|
|
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149-sha1:4f621fb) |
|
|
|
