[jira] [Updated] (JCS-229) LateralTCPListener class uses always StandardSerializer
[ https://issues.apache.org/jira/browse/JCS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl updated JCS-229: --- Assignee: Thomas Vandahl > LateralTCPListener class uses always StandardSerializer > --- > > Key: JCS-229 > URL: https://issues.apache.org/jira/browse/JCS-229 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Assignee: Thomas Vandahl >Priority: Major > Attachments: patch.diff > > Original Estimate: 4h > Remaining Estimate: 4h > > 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. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCS-229) LateralTCPListener class uses always StandardSerializer
[ https://issues.apache.org/jira/browse/JCS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dorota Oeknigk-Urbanska updated JCS-229: 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. was: 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. > LateralTCPListener class uses always StandardSerializer > --- > > Key: JCS-229 > URL: https://issues.apache.org/jira/browse/JCS-229 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Priority: Major > Attachments: patch.diff > > Original Estimate: 4h > Remaining Estimate: 4h > > 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. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCS-229) LateralTCPListener class uses always StandardSerializer
[ https://issues.apache.org/jira/browse/JCS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dorota Oeknigk-Urbanska updated JCS-229: Attachment: patch.diff > LateralTCPListener class uses always StandardSerializer > --- > > Key: JCS-229 > URL: https://issues.apache.org/jira/browse/JCS-229 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Priority: Major > Attachments: patch.diff > > Original Estimate: 4h > Remaining Estimate: 4h > > 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. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
