Problem installing Dataverse 5.6

[ofuuzo ofuuzo]

Hei,

Am getting the following error message when deploying Dataverse 5.6 from 5.5 with payara-5.2021.5.  I grabbed  a copy of PostgreSQL JDBC Driver from  https://jdbc.postgresql.org/download/postgresql-42.2.23.jar and put that jar in /usr/local/payara5/glassfish/lib/ . Am running Postgres9.6. Need help.

"remote failure: Error occurred during deployment: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.7.7.payara-p3): org.eclipse.persistence.exceptions.DatabaseException

Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Access denied to execute this method : setURL"

Cheers

Obi

[Philip Durbin]

Hi Obi,

Don and I are talking about this a bit on Slack but I'm not sure what to tell you. I'd suggest emailing sup...@dataverse.org to get a ticket started.

I think your approach of trying to drop a Postgres driver into place makes sense (though I also thought we had moved it into the war in a recent release).

I don't know if these are helpful or not, but I found them when searching for "Error in allocating a connection":

- https://github.com/IQSS/dataverse/issues/7495#issuecomment-879321531

- https://github.com/IQSS/dataverse/pull/7048#issuecomment-723353433

I'm a little concerned that they're no longer relevant. There have been numerous changes in the database setup lately. Again, I think the best path forward is to open a support ticket with the email address above.

Of course, if others in the community have ideas, please go ahead! :)

Thanks,

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/531218a9-a9d9-4dee-84d6-9ee008992978n%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[ofuuzo ofuuzo]

Thanks Phil. I will send it to the support group. I tried both copying and not copying Postgresql driver into /.../lib and it did not work.

Cheers

Obi

[ofuuzo ofuuzo]

I have sent a message to Support. I think there is something wrong with the dataverse-5.6.war, by reading error message from the server log:

----- Root Cause -----

javax.faces.view.facelets.FaceletException: Error Parsing /dataverse_header.xhtml: Error Traced[line: 277] The content of elements must consist of well-formed character data or markup.

        at com.sun.faces.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:445)

.......

Cheers 

Obi

mandag 16. august 2021 kl. 19:52:15 UTC+2 skrev Philip Durbin:

[Kevin Condon]

Hi Obi,

The setURL error is something I'd seen when upgrading and I'd found it was cause by not setting the db connection info correctly, namely the host and port settings from v5.3 release notes:

3. Update your database connection.

Please configure your connection details, replacing all the ${DB_...}.

• <payara install path>/bin/asadmin create-system-properties "dataverse.db.user=${DB_USER}"

• <payara install path>/bin/asadmin create-system-properties "dataverse.db.host=${DB_HOST}"

• <payara install path>/bin/asadmin create-system-properties "dataverse.db.port=${DB_PORT}"

• <payara install path>/bin/asadmin create-system-properties "dataverse.db.name=${DB_NAME}"

• echo "AS_ADMIN_ALIASPASSWORD=${DB_PASS}" > /tmp/password.txt

• <payara install path>/bin/asadmin create-password-alias --passwordfile /tmp/password.txt dataverse.db.password

• rm /tmp/password.txt

[ofuuzo ofuuzo]

Hi Kevin,

Thanks very much. It works and the problem is solved. But, it is strange that I have to reconfigure the db connection details while I see these values in v. 5.5 domain.xml before upgrading. Thanks once again for helping.

Cheers

Obi

[Kevin Condon]

Obi, 

That's great! I'm not sure why it wasn't working on 5.5 with the same settings, maybe there was a caching issue? I sometimes have trouble deploying while testing different builds so I manually undeploy the current war file, shut down payara, rm  the /usr/local/payara5/domains/domain1/generated and /usr/local/payara5/domains/domain1/osgi-cache directories, restart payara, then attempt to deploy. That usually corrects any caching weirdness.

Glad it's working!

Kevin