[JCS-229] LateralTCPListener class uses always StandardSerializer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: jcs-3.1
• Fix Version/s: jcs-3.2
• Component/s: TCP Lateral Cache

Language

Java

• Assignee: Thomas Vandahl
• Reporter: Dorota Oeknigk-Urbanska
• Created: 04/Apr/22 12:00
• Updated: 18/Sep/23 17:34
• Resolved: 09/Apr/22 10:18

Description

Version jcs-3.1 introduced an option to use EncryptingSerializer instead of StandardSerializer.

However when EncryptingSerializer  is configured for LTCP by :

jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer

synchronization does not work.

LateralTCPSender supports custom Serializer  (by constructor which allowed LateralTCPService to pass Serializer as parameter)- and it's properly sending encripted messages. LateralTCPListener does not support custom Serializer and uses always StandardSerializer - which in this case when received message is encripted fails.

 

 

Solution attached in patch.diff file.

 

Issue Links

• links to: GitHub Pull Request #89