[ 
https://issues.apache.org/jira/browse/QPID-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated QPID-7817:
-----------------------------
    Description: 
Currently the Java Broker's AMQP web socket implementation does not uphold all 
the following:

Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0 
Committee Specification 01 2.4 Exchanging AMQP Frames

bq. There is no mapping between an AMQP frame and a WebSocket message. 
Therefore, a single AMQP frame MAY be split over one or more consecutive 
WebSocket messages. Conversely, a single WebSocket message MAY contain one or 
more AMQP frames. There is also no mapping between an AMQP frame and a 
WebSocket frame. Therefore, a single AMQP frame MAY be split over one or more 
consecutive WebSocket frames. Conversely, a single WebSocket frame MAY contain 
one or more AMQP frames.

The current implementation will fail if a websocket frame arrives containing a 
partial AMQP frame.  Furthermore since, QPID-7763, internally WebSocketProvider 
chunks the incoming bytes into QBBs.  If this chunking results in a frame 
overlapping a chunk, processing will fail. 

  was:
Currently the Java Broker's AMQP web socket implementation does not uphold all 
the following:

Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0 
Committee Specification 01 2.4 Exchanging AMQP Frames

bq. There is no mapping between an AMQP frame and a WebSocket message. 
Therefore, a single AMQP frame MAY be split over one or more consecutive 
WebSocket messages. Conversely, a single WebSocket message MAY contain one or 
more AMQP frames. There is also no mapping between an AMQP frame and a 
WebSocket frame. Therefore, a single AMQP frame MAY be split over one or more 
consecutive WebSocket frames. Conversely, a single WebSocket frame MAY contain 
one or more AMQP frames.

The current implementation will fail if a websocket frame arrives containing a 
partial AMQP frame.   


> [Java Broker] [WebSocket] Websocket implementation must not assume that web 
> socket frame contains a whole AMQP frame
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7817
>                 URL: https://issues.apache.org/jira/browse/QPID-7817
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Keith Wall
>
> Currently the Java Broker's AMQP web socket implementation does not uphold 
> all the following:
> Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0 
> Committee Specification 01 2.4 Exchanging AMQP Frames
> bq. There is no mapping between an AMQP frame and a WebSocket message. 
> Therefore, a single AMQP frame MAY be split over one or more consecutive 
> WebSocket messages. Conversely, a single WebSocket message MAY contain one or 
> more AMQP frames. There is also no mapping between an AMQP frame and a 
> WebSocket frame. Therefore, a single AMQP frame MAY be split over one or more 
> consecutive WebSocket frames. Conversely, a single WebSocket frame MAY 
> contain one or more AMQP frames.
> The current implementation will fail if a websocket frame arrives containing 
> a partial AMQP frame.  Furthermore since, QPID-7763, internally 
> WebSocketProvider chunks the incoming bytes into QBBs.  If this chunking 
> results in a frame overlapping a chunk, processing will fail. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to