http and https connections are kept in 'CLOSE_WAIT' if using apache camel












0














I am using apache-camel as client for http and https requests.



After requests are processed the connections are going into CLOSE_WAIT.



My camel-context doesn't stop after the execution of requests.
If I stop it manually then connections are going into TIME_WAIT.



Now I am wondering if I can make connections to go into TIME_WAIT by some configuration in camel-context or code for http requests.



Edited:




  1. I have tried solutions mentioned for this issue like adding "Connection" header with value "close". But it didn't work.


  2. I have used HttpComponent like below to close connections in finally block



Code:



HttpComponent httpComponent = (HttpComponent) pContext.getComponent(ServerConstants.CAMEL_COMPONENT_HTTP);
httpComponent.getHttpConnectionManager().closeIdleConnections(0);


Second solution is working for http connections but not for https.



Solution:



Finally able to make it work by defining custom HeaderFilterStrategy which does not filter Connection:close header and setting this filter bean id in URL as query param.










share|improve this question
























  • You need to add more details but on a glance this seems related to stackoverflow.com/questions/5636316/…
    – Sheetal Mohan Sharma
    Nov 12 at 9:16










  • i have tried above two things.Out of which one is working for only "http".
    – sasidhar
    Nov 12 at 9:26










  • Glad half is done now. Please check how you have configured your SSL. With given information can't help further.
    – Sheetal Mohan Sharma
    Nov 12 at 10:54










  • It looks like few http headers(like connection) are getting filtered when we use exchange. If it is http url we are able to send those http headers to the service but when it is over https those headers are not reaching the service.
    – sasidhar
    Nov 13 at 5:31










  • Resolved it using custom HeaderFilterStrategy.
    – sasidhar
    Nov 13 at 6:05
















0














I am using apache-camel as client for http and https requests.



After requests are processed the connections are going into CLOSE_WAIT.



My camel-context doesn't stop after the execution of requests.
If I stop it manually then connections are going into TIME_WAIT.



Now I am wondering if I can make connections to go into TIME_WAIT by some configuration in camel-context or code for http requests.



Edited:




  1. I have tried solutions mentioned for this issue like adding "Connection" header with value "close". But it didn't work.


  2. I have used HttpComponent like below to close connections in finally block



Code:



HttpComponent httpComponent = (HttpComponent) pContext.getComponent(ServerConstants.CAMEL_COMPONENT_HTTP);
httpComponent.getHttpConnectionManager().closeIdleConnections(0);


Second solution is working for http connections but not for https.



Solution:



Finally able to make it work by defining custom HeaderFilterStrategy which does not filter Connection:close header and setting this filter bean id in URL as query param.










share|improve this question
























  • You need to add more details but on a glance this seems related to stackoverflow.com/questions/5636316/…
    – Sheetal Mohan Sharma
    Nov 12 at 9:16










  • i have tried above two things.Out of which one is working for only "http".
    – sasidhar
    Nov 12 at 9:26










  • Glad half is done now. Please check how you have configured your SSL. With given information can't help further.
    – Sheetal Mohan Sharma
    Nov 12 at 10:54










  • It looks like few http headers(like connection) are getting filtered when we use exchange. If it is http url we are able to send those http headers to the service but when it is over https those headers are not reaching the service.
    – sasidhar
    Nov 13 at 5:31










  • Resolved it using custom HeaderFilterStrategy.
    – sasidhar
    Nov 13 at 6:05














0












0








0







I am using apache-camel as client for http and https requests.



After requests are processed the connections are going into CLOSE_WAIT.



My camel-context doesn't stop after the execution of requests.
If I stop it manually then connections are going into TIME_WAIT.



Now I am wondering if I can make connections to go into TIME_WAIT by some configuration in camel-context or code for http requests.



Edited:




  1. I have tried solutions mentioned for this issue like adding "Connection" header with value "close". But it didn't work.


  2. I have used HttpComponent like below to close connections in finally block



Code:



HttpComponent httpComponent = (HttpComponent) pContext.getComponent(ServerConstants.CAMEL_COMPONENT_HTTP);
httpComponent.getHttpConnectionManager().closeIdleConnections(0);


Second solution is working for http connections but not for https.



Solution:



Finally able to make it work by defining custom HeaderFilterStrategy which does not filter Connection:close header and setting this filter bean id in URL as query param.










share|improve this question















I am using apache-camel as client for http and https requests.



After requests are processed the connections are going into CLOSE_WAIT.



My camel-context doesn't stop after the execution of requests.
If I stop it manually then connections are going into TIME_WAIT.



Now I am wondering if I can make connections to go into TIME_WAIT by some configuration in camel-context or code for http requests.



Edited:




  1. I have tried solutions mentioned for this issue like adding "Connection" header with value "close". But it didn't work.


  2. I have used HttpComponent like below to close connections in finally block



Code:



HttpComponent httpComponent = (HttpComponent) pContext.getComponent(ServerConstants.CAMEL_COMPONENT_HTTP);
httpComponent.getHttpConnectionManager().closeIdleConnections(0);


Second solution is working for http connections but not for https.



Solution:



Finally able to make it work by defining custom HeaderFilterStrategy which does not filter Connection:close header and setting this filter bean id in URL as query param.







http https http-headers apache-camel






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 at 6:04

























asked Nov 12 at 9:07









sasidhar

64




64












  • You need to add more details but on a glance this seems related to stackoverflow.com/questions/5636316/…
    – Sheetal Mohan Sharma
    Nov 12 at 9:16










  • i have tried above two things.Out of which one is working for only "http".
    – sasidhar
    Nov 12 at 9:26










  • Glad half is done now. Please check how you have configured your SSL. With given information can't help further.
    – Sheetal Mohan Sharma
    Nov 12 at 10:54










  • It looks like few http headers(like connection) are getting filtered when we use exchange. If it is http url we are able to send those http headers to the service but when it is over https those headers are not reaching the service.
    – sasidhar
    Nov 13 at 5:31










  • Resolved it using custom HeaderFilterStrategy.
    – sasidhar
    Nov 13 at 6:05


















  • You need to add more details but on a glance this seems related to stackoverflow.com/questions/5636316/…
    – Sheetal Mohan Sharma
    Nov 12 at 9:16










  • i have tried above two things.Out of which one is working for only "http".
    – sasidhar
    Nov 12 at 9:26










  • Glad half is done now. Please check how you have configured your SSL. With given information can't help further.
    – Sheetal Mohan Sharma
    Nov 12 at 10:54










  • It looks like few http headers(like connection) are getting filtered when we use exchange. If it is http url we are able to send those http headers to the service but when it is over https those headers are not reaching the service.
    – sasidhar
    Nov 13 at 5:31










  • Resolved it using custom HeaderFilterStrategy.
    – sasidhar
    Nov 13 at 6:05
















You need to add more details but on a glance this seems related to stackoverflow.com/questions/5636316/…
– Sheetal Mohan Sharma
Nov 12 at 9:16




You need to add more details but on a glance this seems related to stackoverflow.com/questions/5636316/…
– Sheetal Mohan Sharma
Nov 12 at 9:16












i have tried above two things.Out of which one is working for only "http".
– sasidhar
Nov 12 at 9:26




i have tried above two things.Out of which one is working for only "http".
– sasidhar
Nov 12 at 9:26












Glad half is done now. Please check how you have configured your SSL. With given information can't help further.
– Sheetal Mohan Sharma
Nov 12 at 10:54




Glad half is done now. Please check how you have configured your SSL. With given information can't help further.
– Sheetal Mohan Sharma
Nov 12 at 10:54












It looks like few http headers(like connection) are getting filtered when we use exchange. If it is http url we are able to send those http headers to the service but when it is over https those headers are not reaching the service.
– sasidhar
Nov 13 at 5:31




It looks like few http headers(like connection) are getting filtered when we use exchange. If it is http url we are able to send those http headers to the service but when it is over https those headers are not reaching the service.
– sasidhar
Nov 13 at 5:31












Resolved it using custom HeaderFilterStrategy.
– sasidhar
Nov 13 at 6:05




Resolved it using custom HeaderFilterStrategy.
– sasidhar
Nov 13 at 6:05

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53258874%2fhttp-and-https-connections-are-kept-in-close-wait-if-using-apache-camel%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53258874%2fhttp-and-https-connections-are-kept-in-close-wait-if-using-apache-camel%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Florida Star v. B. J. F.

Danny Elfman

Lugert, Oklahoma