[logback-dev] [JIRA] Updates for LOGBACK-1752: SocketReceiver cannot deserialize events in OSGi
logback developers list
logback-dev at qos.ch
Fri Jun 23 12:59:00 CEST 2023
logback / LOGBACK-1752 [Open]
SocketReceiver cannot deserialize events in OSGi
==============================
Here's what changed in this issue in the last few minutes.
This issue has been created
This issue is now assigned to you.
View or comment on issue using this link
https://jira.qos.ch/browse/LOGBACK-1752
==============================
Issue created
------------------------------
Joe Shannon created this issue on 23/Jun/23 12:47
Summary: SocketReceiver cannot deserialize events in OSGi
Issue Type: Bug
Affects Versions: 1.3.8, 1.4.8
Assignee: Logback dev list
Components: logback-classic, logback-core
Created: 23/Jun/23 12:47
Environment: logback-core and logback-classic in OSGi
Priority: Major
Reporter: Joe Shannon
Description:
Using a SocketReceiver in an OSGi environment currently fails when running in OSGi.
The event class is ch.qos.logback.classic.spi.LoggingEventVO which is attempted to be deserialized by HardenedObjectInputStream (extends ObjectInputStream).
Since HardenedObjectInputStream is in logback-core, the class loader used for deserialization is the bundle loader for ch.qos.logback.core which is unable to load from package ch.qos.logback.classic.spi.
A couple of ideas for possible fix:
* Add optional Import-Package header for this package
* Allow a different class loader to be specified for deserialization
==============================
This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)
More information about the logback-dev
mailing list