[QFJ-518] Incomplete addressing on BusinessMessageReject when using a FIX routing network Created: 04/May/10 Updated: 02/Apr/15 Resolved: 08/Oct/14 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | Engine |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | 1.6.0 |
| Type: | Bug | Priority: | Default |
| Reporter: | Cliff Evans | Assignee: | Christoph John |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
JDK 1.6_20 |
||
| Description |
|
If an exception is thrown in fromApp, e.g. FieldNotFound, and we're using FIX4.2 or greater when using a Routing Network, e.g. Autex, a BusinessMessageReject message is thrown. The message does not currently contain all of the addressing information required to successfully deliver the BMR message if the message isn't going directly to a recipient. If the message which causes the BMR contains routing information in: OnBehalfOfCompID (115) and OnBehalfOfSubID (116) This information should be included in the BMR reply in: DeliverToCompID (128) and DeliverToSubID (129) This will allow the Routing network to correctly deliver the message to the Application of the final recipient. Not including these fields results in the message being delivered directly to the Routing Network itself which doesn't know what to do with it. |
| Comments |
| Comment by Cliff Evans [ 12/May/10 ] |
|
It looks to me like there's just a missing call to: reject.reverseRoute(header); In the generateBusinessReject method. I can't think of any reason why you wouldn't route a BMR to the individual broker rather than the FIX routing network. |