Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-11-11 Thread duke
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-11-11 Thread Viktor Klang
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-11-04 Thread Viktor Klang
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-11-01 Thread Doug Lea
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-11-01 Thread Alan Bateman
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-11-01 Thread Viktor Klang
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-11-01 Thread Roger Riggs
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-10-30 Thread Viktor Klang
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

Re: RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-10-30 Thread David M . Lloyd
On Wed, 30 Oct 2024 08:54:55 GMT, kabutz wrote: > The ArrayBlockingQueue has had a readObject() method since Java 7, which > checks invariants of the deserialized object. However, it does not have a > writeObject() method. This means that the ArrayBlockingQueue could be > modified whilst it is

RFR: 8343250: ArrayBlockingQueue serialization not thread safe

2024-10-30 Thread kabutz
The ArrayBlockingQueue has had a readObject() method since Java 7, which checks invariants of the deserialized object. However, it does not have a writeObject() method. This means that the ArrayBlockingQueue could be modified whilst it is being written, resulting in broken invariants. The readOb