Re: Why so many port used when I use camel-netty4-http

2015-04-14 Thread Yuffie
Hi,Willem
Thanks for your help!
I think I need to read the document carefully first. 
Again, thank you!



--
View this message in context: 
http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433p5765810.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Why so many port used when I use camel-netty4-http

2015-04-14 Thread Yuffie
Hi,Yogesh.
Thanks for help!
Since I don't have a Linux environment, I don't if it work on Linux. But it
work in win7.
And I will try what you said.
Again thank you.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433p5765806.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Why so many port used when I use camel-netty4-http

2015-04-14 Thread Willem Jiang
EnterpriseInfoServiceRoute").isEqualTo("authdevices"))
> .process(new IfCanAuthProcessor())
> .choice()
> .when(header("CanAuth").isEqualTo("true"))
>  
> .to(routeMap.get("EnterpriseInfoService"))
> .endChoice()
>  
> .when(header("EnterpriseInfoServiceRoute").isEqualTo("other"))
> .to(routeMap.get("EnterpriseInfoService"))
> .endChoice()
> .when(header("serviceNickName").isEqualTo(PRODUCTNICK))
> .to(routeMap.get("i6p"))
> .when(header("serviceNickName").isEqualTo("properties"))
> .bean(new PropertyEndpoint())
> .endChoice()
> .end();
> }
> }
>  
> ---
>  
> And this is deployed in the Tomcat.
>  
> And we find that it maybe an issue of netty:
> http://blog.csdn.net/haoel/article/details/2224055
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433p5765797.html
>   
> Sent from the Camel - Users mailing list archive at Nabble.com.
>  



Re: Why so many port used when I use camel-netty4-http

2015-04-14 Thread yogu13
Hello,

Apart from the above can you provide us following info !!

1. How many ports are opened (delta) for the route which is getting
created?? You can do this by taking a note of all the ports opened when you
application is down and then take a note of the ports open once your
application is up and remove the common ports from the list

2. How does tomcat come into picture? is this deployed on tomcat ? what port
is your tomcat working on.

3. What version of OS and JDK and camel are you using.

Regards,
-Yogesh



--
View this message in context: 
http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433p5765799.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Why so many port used when I use camel-netty4-http

2015-04-14 Thread yogu13
Thanks!

Is this working properly in any of the environments ?

Also you try configuring the bootstrap options like keepAlive, Timeout's and
disconnect for netty endpoint ?

check "Reusing same server bootstrap configuration with multiple routes"
section in http://camel.apache.org/netty4-http.html

Regards,
-Yogesh



--
View this message in context: 
http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433p5765802.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Why so many port used when I use camel-netty4-http

2015-04-14 Thread Yuffie
   
.when(header("EnterpriseInfoServiceRoute").isEqualTo("other"))
.to(routeMap.get("EnterpriseInfoService"))
.endChoice()
.when(header("serviceNickName").isEqualTo(PRODUCTNICK))
    .to(routeMap.get("i6p"))
.when(header("serviceNickName").isEqualTo("properties"))
.bean(new PropertyEndpoint())
.endChoice()
.end();
}
}

---

And this is deployed in the Tomcat.

And we find that it maybe an issue of netty:
http://blog.csdn.net/haoel/article/details/2224055



--
View this message in context: 
http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433p5765797.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Why so many port used when I use camel-netty4-http

2015-04-09 Thread Willem Jiang
ABLISHED 7868
> TCP 192.168.6.111:17641 119.161.83.27:443 TIME_WAIT 0
> TCP 192.168.6.111:17646 164.46.204.84:443 SYN_SENT 1460
> TCP 192.168.6.111:17647 180.149.153.11:80 ESTABLISHED 7868
> TCP [::]:135 [::]:0 LISTENING 992
> TCP [::]:445 [::]:0 LISTENING 4
> TCP [::]:1025 [::]:0 LISTENING 560
> TCP [::]:1026 [::]:0 LISTENING 676
> TCP [::]:1027 [::]:0 LISTENING 480
> TCP [::]:1028 [::]:0 LISTENING 1036
> TCP [::]:1042 [::]:0 LISTENING 668
> TCP [::]:8009 [::]:0 LISTENING 10368
> TCP [::]:8080 [::]:0 LISTENING 10368
> TCP [::]:8082 [::]:0 LISTENING 10368
> TCP [::]:62332 [::]:0 LISTENING 1512
> TCP [::1]:12025 [::]:0 LISTENING 1460
> TCP [::1]:12110 [::]:0 LISTENING 1460
> TCP [::1]:12119 [::]:0 LISTENING 1460
> TCP [::1]:12143 [::]:0 LISTENING 1460
> TCP [::1]:12465 [::]:0 LISTENING 1460
> TCP [::1]:12563 [::]:0 LISTENING 1460
> TCP [::1]:12993 [::]:0 LISTENING 1460
> TCP [::1]:12995 [::]:0 LISTENING 1460
> TCP [::1]:27275 [::]:0 LISTENING 1460
> UDP 0.0.0.0:500 *:* 1036
> UDP 0.0.0.0:1900 *:* 1512
> UDP 0.0.0.0:4500 *:* 1036
> UDP 0.0.0.0:5355 *:* 1268
> UDP 0.0.0.0:49804 *:* 9104
> UDP 0.0.0.0:49826 *:* 9064
> UDP 0.0.0.0:54955 *:* 9064
> UDP 0.0.0.0:60507 *:* 9104
> UDP 0.0.0.0:62332 *:* 1512
> UDP 0.0.0.0:64551 *:* 9064
> UDP 127.0.0.1:4 *:* 2980
> UDP 127.0.0.1:56298 *:* 1460
> UDP 127.0.0.1:62715 *:* 1512
> UDP 192.168.6.111:137 *:* 4
> UDP 192.168.6.111:138 *:* 4
> UDP 192.168.6.111:62714 *:* 1512
> UDP [::]:500 *:* 1036
> UDP [::]:4500 *:* 1036
> UDP [::]:5355 *:* 1268
> UDP [::]:62332 *:* 1512
> UDP [fe80::35c6:35b2:c6db:ed40%10]:546 *:*
> 480
>  
> the PID 10368 is my tomcat.
> Can anyone help? Thanks a lot!
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433.html
>   
> Sent from the Camel - Users mailing list archive at Nabble.com.
>  



Why so many port used when I use camel-netty4-http

2015-04-07 Thread Yuffie
127.0.0.1:17602ESTABLISHED 10368
  TCP127.0.0.1:17604127.0.0.1:17605ESTABLISHED 10368
  TCP127.0.0.1:17605127.0.0.1:17604ESTABLISHED 10368
  TCP127.0.0.1:272750.0.0.0:0  LISTENING   1460
  TCP192.168.6.111:139  0.0.0.0:0  LISTENING   4
  TCP192.168.6.111:1173 180.153.160.237:80 CLOSE_WAIT  9064
  TCP192.168.6.111:1195 180.153.160.237:80 CLOSE_WAIT  9064
  TCP192.168.6.111:1197 180.153.160.237:80 CLOSE_WAIT  9064
  TCP192.168.6.111:1240 180.153.160.237:80 CLOSE_WAIT  9064
  TCP192.168.6.111:1642 180.153.160.237:80 CLOSE_WAIT  9064
  TCP192.168.6.111:2938 180.149.138.98:80  ESTABLISHED 7868
  TCP192.168.6.111:1336460.28.215.83:80ESTABLISHED 7868
  TCP192.168.6.111:17234119.161.83.27:443  ESTABLISHED 7868
  TCP192.168.6.111:17327180.153.160.237:80 CLOSE_WAIT  9064
  TCP192.168.6.111:17606119.161.83.27:443  ESTABLISHED 7868
  TCP192.168.6.111:17619119.161.83.27:443  ESTABLISHED 7868
  TCP192.168.6.111:17621119.161.83.27:443  ESTABLISHED 7868
  TCP192.168.6.111:17640119.161.83.27:443  ESTABLISHED 7868
  TCP192.168.6.111:17641119.161.83.27:443  TIME_WAIT   0
  TCP192.168.6.111:17646164.46.204.84:443  SYN_SENT1460
  TCP192.168.6.111:17647180.149.153.11:80  ESTABLISHED 7868
  TCP[::]:135   [::]:0 LISTENING   992
  TCP[::]:445   [::]:0 LISTENING   4
  TCP[::]:1025  [::]:0 LISTENING   560
  TCP[::]:1026  [::]:0 LISTENING   676
  TCP[::]:1027  [::]:0 LISTENING   480
  TCP[::]:1028  [::]:0 LISTENING   1036
  TCP[::]:1042  [::]:0 LISTENING   668
  TCP[::]:8009  [::]:0 LISTENING   10368
  TCP[::]:8080  [::]:0 LISTENING   10368
  TCP[::]:8082  [::]:0 LISTENING   10368
  TCP[::]:62332 [::]:0 LISTENING   1512
  TCP[::1]:12025[::]:0 LISTENING   1460
  TCP[::1]:12110[::]:0 LISTENING   1460
  TCP[::1]:12119[::]:0 LISTENING   1460
  TCP[::1]:12143[::]:0 LISTENING   1460
  TCP[::1]:12465[::]:0 LISTENING   1460
  TCP[::1]:12563[::]:0 LISTENING   1460
  TCP[::1]:12993[::]:0 LISTENING   1460
  TCP[::1]:12995[::]:0 LISTENING   1460
  TCP[::1]:27275[::]:0 LISTENING   1460
  UDP0.0.0.0:500*:*1036
  UDP0.0.0.0:1900   *:*1512
  UDP0.0.0.0:4500   *:*1036
  UDP0.0.0.0:5355   *:*1268
  UDP0.0.0.0:49804  *:*9104
  UDP0.0.0.0:49826  *:*9064
  UDP0.0.0.0:54955  *:*9064
  UDP0.0.0.0:60507  *:*9104
  UDP0.0.0.0:62332  *:*1512
  UDP0.0.0.0:64551  *:*9064
  UDP127.0.0.1:4*:*2980
  UDP127.0.0.1:56298*:*1460
  UDP127.0.0.1:62715*:*1512
  UDP192.168.6.111:137  *:*4
  UDP192.168.6.111:138  *:*4
  UDP192.168.6.111:62714*:*1512
  UDP[::]:500   *:*1036
  UDP[::]:4500  *:*1036
  UDP[::]:5355  *:*1268
  UDP[::]:62332 *:*1512
  UDP[fe80::35c6:35b2:c6db:ed40%10]:546  *:*
   
480

the PID 10368 is my tomcat.
Can anyone help? Thanks a lot!



--
View this message in context: 
http://camel.465427.n5.nabble.com/Why-so-many-port-used-when-I-use-camel-netty4-http-tp5765433.html
Sent from the Camel - Users mailing list archive at Nabble.com.