Help with Server.Log Warnings

[Sherry Lake]

We are getting this error in our server.log:

[2025-03-07T13:59:43.727+0000] [Payara 6.2024.6] [WARNING] [] [edu.harvard.iq.dataverse.util.BundleUtil] [tid: _ThreadID=88 _ThreadName=http-thread-pool::jk-connector(2)] [timeMillis: 1741355983727] [levelValue: 900] [[
  Could not find key "externaltools.zipPreviewer.displayname" in bundle file: ]]

We do have zipPreviewer installed as an external previewer. I looked at the Bundle.properties file and see this line for Data Curation Tool:

externaltools.dct.displayname=Data Curation Tool

Do I need to add a similar one for zipPreviewer? To get rid of the warnings?

We are also getting LOTS of these warnings causing our server.log file to rollover many times a day - so we have about 10 or so server log files for a day. Here's that Warning:

[2025-03-07T14:21:47.495+0000] [Payara 6.2024.6] [WARNING] [] [] [tid: _ThreadID=88 _ThreadName=http-thread-pool::jk-connector(2)] [timeMillis: 1741357307495] [levelValue: 900] [[
  Response has already been committed, and further write operations are not permitted. This may result in an IllegalStateException being triggered by the underlying application. To avoid this situation, consider adding a Rule `.when(Direction.isInbound().and(Response.isCommitted())).perform(Lifecycle.abort())`, or figure out where the response is being incorrectly committed and correct the bug in the offending code.]]

Thanks,

Sherry Lake 

UVA Dataverse http://dataverse.lib.virginia.edu

[James Myers]

Yes, adding a line in Bundle.properties, or the _en/other language versions for international instances will get rid of that warning. Don has also posted a change to the logging settings that can quiet this type of warning.

 

For the second one, I’m not sure that anyone knows exactly where it is from. It’s likely that a similar change to the logging level could get rid of that, but it would be nice to fix it if anyone can find the root cause.

 

-- Jim

--
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 visit https://groups.google.com/d/msgid/dataverse-community/22fc2fd8-b18b-4812-9233-dcdceabef59en%40googlegroups.com.