Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WS-Addressing - failed to retrieve Message Addressing Properties from context #93

Closed
senikk opened this issue Feb 18, 2020 · 5 comments
Closed

WS-Addressing - failed to retrieve Message Addressing Properties from context #93

senikk opened this issue Feb 18, 2020 · 5 comments
Assignees
@aaron-kumar
Labels
Inactive Please respond, or issue will be closed issue Issue which are under review, can be bug
Milestone
5.x.x

Comments

@senikk
Copy link

senikk commented Feb 18, 2020

I've seen several of these with failed to retrieve Message Addressing Properties from context against several accesspoints.

07:25:35.933 [main] DEBUG org.apache.cxf.ws.addressing.ContextUtils - WS-Addressing - failed to retrieve Message Addressing Properties from context 07:25:35.934 [main] INFO org.apache.cxf.services.DummyImpl.REQ_OUT - REQ_OUT Address: https://xxxxxxxx HttpMethod: POST Content-Type: multipart/related; type="application/soap+xml"; boundary="uuid:14438554-fce0-451e-ac7c-03dc3b416c10"; start="<root.message@cxf.apache.org>"; start-info="application/soap+xml" ExchangeId: 5f6cf420-1940-4184-a828-1b8c48906f41 ServiceName: outbound-service PortName: port PortTypeName: DummyImpl Headers: {Accept=*/*} Payload: --uuid:14438554-fce0-451e-ac7c-03dc3b416c10
@FrodeBjerkholt
Copy link
Contributor

Noted - I am back at the office at Thursday.

@senikk
Copy link
Author

senikk commented Feb 24, 2020

Any news on this?

@FrodeBjerkholt
Copy link
Contributor

FrodeBjerkholt commented Feb 24, 2020 •
edited
Loading

No, not yet. I have focused on issue #88 which I will complete tomorrow.

@FrodeBjerkholt
Copy link
Contributor

I think this is something you can safely ignore.

@SuperJuell SuperJuell added the Inactive Please respond, or issue will be closed label Feb 2, 2021
@aaron-kumar aaron-kumar added the issue Issue which are under review, can be bug label Dec 6, 2021
@aaron-kumar aaron-kumar added this to the 5.x.x milestone Dec 6, 2021
@aaron-kumar
Copy link
Member

No further comment after Frode comment in 2020, so closing issue.
Feel free to reopen, if you still facing this issue.

@aaron-kumar aaron-kumar self-assigned this Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aaron-kumar aaron-kumar

Labels
Inactive Please respond, or issue will be closed issue Issue which are under review, can be bug
Projects
Oxalis Public Roadmap
Status: Completed
Milestone
5.x.x
Development

No branches or pull requests
4 participants
@senikk @aaron-kumar @FrodeBjerkholt @SuperJuell