[
https://issues.apache.org/jira/browse/SOLR-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950544#comment-17950544
]
Jason Gerlowski commented on SOLR-17032:
----------------------------------------
I've spent bits of time poking at this on and off, and haven't managed to
figure it out. I'm sure it's fixable - it's just never been high enough
priority for me personally to devote quite as much time as it needs.
A workaround in the interim would be a log4j config change to set the log level
for the involved logger to "ERROR".
> Jersey MessagingBinders class logs "A class javax.activation.DataSource for a
> default provider MessageBodyWriter<javax.activation.DataSource> was not
> found" warning on startup
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-17032
> URL: https://issues.apache.org/jira/browse/SOLR-17032
> Project: Solr
> Issue Type: Bug
> Affects Versions: 9.4
> Reporter: Shawn Heisey
> Priority: Minor
> Labels: startup
>
> Solr 9.4.0 on both Linux and Windows log the following:
> {code:java}
> 2023-10-16 13:07:54.191 WARN (main) [] o.g.j.m.i.MessagingBinders A class
> javax.activation.DataSource for a default provider
> MessageBodyWriter<javax.activation.DataSource> was not found. The provider is
> not available.
> {code}
> Research turns up that getting rid of this warning requires addingÂ
> {{jakarta.activation/jakarta.activation-api}} to dependencies.
> Have not been able to determine whether this is actually a problem or just a
> harmless log entry.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
