You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by robert lazarski <ro...@gmail.com> on 2007/04/13 19:13:44 UTC
Stuck in SYN_RECV when binding to ip
Hi all,
I'm using the tomcat that is embedded into jboss 4.0.5 , 5.5.17 I believe.
I'm running opensuse 10.1 with kernel 2.6.16.13 . I'm trying to test our app
which is now behind a load balancer. I've tried with and without apr to the
same effect. My ifconfig shows:
eth0 Link encap:Ethernet HWaddr 00:0C:29:5D:68:E7
inet addr:xxx.xxx.166.53 Bcast:xxx.xxx.166.63 Mask:
255.255.255.240
inet6 addr: fe80::20c:29ff:fe5d:68e7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1955979 errors:0 dropped:0 overruns:0 frame:0
TX packets:906962 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:519352897 (495.2 Mb) TX bytes:201866177 (192.5 Mb)
Interrupt:177 Base address:0x1400
eth0:eth1 Link encap:Ethernet HWaddr 00:0C:29:5D:68:E7
inet addr:192.168.2.53 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:177 Base address:0x1400
eth0:eth2 Link encap:Ethernet HWaddr 00:0C:29:5D:68:E7
inet addr:192.168.3.53 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:177 Base address:0x1400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:142486 errors:0 dropped:0 overruns:0 frame:0
TX packets:142486 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8030550 (7.6 Mb) TX bytes:8030550 (7.6 Mb)
I need to bind to 192.168.3.53 for the load balancer to route the request
tomcat. I'm passing '-b192.168.3.53' to JBoss to change the ${
jboss.bind.address} to that address in the server.xml . There are a couple
vars as localhost in the server.xml, which I tried changing to also to
192.168.3.53 to the same affect, which is via netstat repeating this, and
never going to TIME_WAIT etc:
tcp 0 0 192.168.3.53:8080 xxx.xxx.118.243:8368
SYN_RECV -
I have org.apache classes in debug, and I see no activity in the logs for
this request. Here's the tcpdump output, any ideas?
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0:eth2, link-type EN10MB (Ethernet), capture size 96 bytes
13:06:09.356665 IP 192.168.3.83.44251 > 192.168.3.53.8080: S
1368024561:1368024561(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:09.357250 IP 192.168.3.53.8080 > 192.168.3.83.44251: S
1810740491:1810740491(0) ack 1368024562 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:09.356773 IP 192.168.3.83.44251 > 192.168.3.53.8080: . ack 1 win 5840
13:06:09.356782 IP 192.168.3.83.44251 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:09.358098 IP 192.168.3.53.8080 > 192.168.3.83.44251: F 1:1(0) ack 2
win 1460
13:06:09.358288 IP 192.168.3.83.44251 > 192.168.3.53.8080: . ack 2 win 5840
13:06:12.279592 IP xxx.xxx.118.243.23993 > 192.168.3.53.8080: S
3134476487:3134476487(0) win 5840 <mss 1460,sackOK,timestamp 3942011
0,nop,wscale 7>
13:06:12.279653 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55622954 3942011,nop,wscale 2>
13:06:15.324432 IP xxx.xxx.118.243.23993 > 192.168.3.53.8080: S
3134476487:3134476487(0) win 5840 <mss 1460,sackOK,timestamp 3942761
0,nop,wscale 7>
13:06:15.324467 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55623715 3942011,nop,wscale 2>
13:06:16.277964 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55623954 3942011,nop,wscale 2>
13:06:16.356277 IP 192.168.3.83.44261 > 192.168.3.53.8080: S
1375853566:1375853566(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:16.356357 IP 192.168.3.53.8080 > 192.168.3.83.44261: S
1808607667:1808607667(0) ack 1375853567 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:16.357181 IP 192.168.3.83.44261 > 192.168.3.53.8080: . ack 1 win 5840
13:06:16.357186 IP 192.168.3.83.44261 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:16.357337 IP 192.168.3.53.8080 > 192.168.3.83.44261: . ack 2 win 1460
13:06:16.359300 IP 192.168.3.53.8080 > 192.168.3.83.44261: F 1:1(0) ack 2
win 1460
13:06:16.359469 IP 192.168.3.83.44261 > 192.168.3.53.8080: . ack 2 win 5840
13:06:21.328864 IP xxx.xxx.118.243.23993 > 192.168.3.53.8080: S
3134476487:3134476487(0) win 5840 <mss 1460,sackOK,timestamp 3944261
0,nop,wscale 7>
13:06:21.328903 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55625217 3942011,nop,wscale 2>
13:06:22.275878 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55625454 3942011,nop,wscale 2>
13:06:23.378968 IP 192.168.3.83.44272 > 192.168.3.53.8080: S
1382979341:1382979341(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:23.379345 IP 192.168.3.53.8080 > 192.168.3.83.44272: S
1812121272:1812121272(0) ack 1382979342 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:23.379942 IP 192.168.3.83.44272 > 192.168.3.53.8080: . ack 1 win 5840
13:06:23.379953 IP 192.168.3.83.44272 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:23.382991 IP 192.168.3.53.8080 > 192.168.3.83.44272: . ack 2 win 1460
13:06:23.383239 IP 192.168.3.53.8080 > 192.168.3.83.44272: F 1:1(0) ack 2
win 1460
13:06:23.384123 IP 192.168.3.83.44272 > 192.168.3.53.8080: . ack 2 win 5840
13:06:30.343169 IP 192.168.3.83.44282 > 192.168.3.53.8080: S
1389547057:1389547057(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:30.343211 IP 192.168.3.53.8080 > 192.168.3.83.44282: S
1820921563:1820921563(0) ack 1389547058 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:30.343444 IP 192.168.3.83.44282 > 192.168.3.53.8080: . ack 1 win 5840
13:06:30.343450 IP 192.168.3.83.44282 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:30.344694 IP 192.168.3.53.8080 > 192.168.3.83.44282: . ack 2 win 1460
13:06:30.345930 IP 192.168.3.53.8080 > 192.168.3.83.44282: F 1:1(0) ack 2
win 1460
13:06:30.346111 IP 192.168.3.83.44282 > 192.168.3.53.8080: . ack 2 win 5840
13:06:33.298387 IP xxx.xxx.118.243.23993 > 192.168.3.53.8080: S
3134476487:3134476487(0) win 5840 <mss 1460,sackOK,timestamp 3947261
0,nop,wscale 7>
13:06:33.298422 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55628210 3942011,nop,wscale 2>
13:06:34.271593 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55628454 3942011,nop,wscale 2>
13:06:37.375401 IP 192.168.3.83.44292 > 192.168.3.53.8080: S
1409293558:1409293558(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:37.375441 IP 192.168.3.53.8080 > 192.168.3.83.44292: S
1838529707:1838529707(0) ack 1409293559 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:37.375685 IP 192.168.3.83.44292 > 192.168.3.53.8080: . ack 1 win 5840
13:06:37.375691 IP 192.168.3.83.44292 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:37.376502 IP 192.168.3.53.8080 > 192.168.3.83.44292: F 1:1(0) ack 2
win 1460
13:06:37.376704 IP 192.168.3.83.44292 > 192.168.3.53.8080: . ack 2 win 5840
13:06:44.339871 IP 192.168.3.83.44303 > 192.168.3.53.8080: S
1421942527:1421942527(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:44.339923 IP 192.168.3.53.8080 > 192.168.3.83.44303: S
1835251824:1835251824(0) ack 1421942528 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:44.340182 IP 192.168.3.83.44303 > 192.168.3.53.8080: . ack 1 win 5840
13:06:44.340193 IP 192.168.3.83.44303 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:44.341136 IP 192.168.3.53.8080 > 192.168.3.83.44303: F 1:1(0) ack 2
win 1460
13:06:44.341341 IP 192.168.3.83.44303 > 192.168.3.53.8080: . ack 2 win 5840
13:06:51.338598 IP 192.168.3.83.44313 > 192.168.3.53.8080: S
1421677845:1421677845(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:51.338844 IP 192.168.3.53.8080 > 192.168.3.83.44313: S
1852649202:1852649202(0) ack 1421677846 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:51.339044 IP 192.168.3.83.44313 > 192.168.3.53.8080: . ack 1 win 5840
13:06:51.339081 IP 192.168.3.83.44313 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:51.339850 IP 192.168.3.53.8080 > 192.168.3.83.44313: F 1:1(0) ack 2
win 1460
13:06:51.342341 IP 192.168.3.83.44313 > 192.168.3.53.8080: . ack 2 win 5840
13:06:57.330987 IP xxx.xxx.118.243.23993 > 192.168.3.53.8080: S
3134476487:3134476487(0) win 5840 <mss 1460,sackOK,timestamp 3953261
0,nop,wscale 7>
13:06:57.331022 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55634219 3942011,nop,wscale 2>
13:06:58.372822 IP 192.168.3.83.44323 > 192.168.3.53.8080: S
1433941232:1433941232(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:06:58.372874 IP 192.168.3.53.8080 > 192.168.3.83.44323: S
1853630397:1853630397(0) ack 1433941233 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:06:58.373111 IP 192.168.3.83.44323 > 192.168.3.53.8080: . ack 1 win 5840
13:06:58.373117 IP 192.168.3.83.44323 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:06:58.376019 IP 192.168.3.53.8080 > 192.168.3.83.44323: F 1:1(0) ack 2
win 1460
13:06:58.376215 IP 192.168.3.83.44323 > 192.168.3.53.8080: . ack 2 win 5840
13:06:58.468163 IP 192.168.3.53.8080 > xxx.xxx.118.243.23993: S
1800088503:1800088503(0) ack 3134476488 win 5792 <mss 1460,sackOK,timestamp
55634504 3942011,nop,wscale 2>
13:07:05.335069 IP 192.168.3.83.44333 > 192.168.3.53.8080: S
1439531854:1439531854(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:07:05.335114 IP 192.168.3.53.8080 > 192.168.3.83.44333: S
1858300551:1858300551(0) ack 1439531855 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:07:05.336001 IP 192.168.3.83.44333 > 192.168.3.53.8080: . ack 1 win 5840
13:07:05.336006 IP 192.168.3.83.44333 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:07:05.337217 IP 192.168.3.53.8080 > 192.168.3.83.44333: . ack 2 win 1460
13:07:05.337715 IP 192.168.3.53.8080 > 192.168.3.83.44333: F 1:1(0) ack 2
win 1460
13:07:05.337890 IP 192.168.3.83.44333 > 192.168.3.53.8080: . ack 2 win 5840
13:07:12.377214 IP 192.168.3.83.44343 > 192.168.3.53.8080: S
1447801003:1447801003(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:07:12.377263 IP 192.168.3.53.8080 > 192.168.3.83.44343: S
1862097448:1862097448(0) ack 1447801004 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:07:12.377492 IP 192.168.3.83.44343 > 192.168.3.53.8080: . ack 1 win 5840
13:07:12.377498 IP 192.168.3.83.44343 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:07:12.378136 IP 192.168.3.53.8080 > 192.168.3.83.44343: F 1:1(0) ack 2
win 1460
13:07:12.378456 IP 192.168.3.83.44343 > 192.168.3.53.8080: . ack 2 win 5840
13:07:19.346968 IP 192.168.3.83.44354 > 192.168.3.53.8080: S
1454799175:1454799175(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:07:19.347008 IP 192.168.3.53.8080 > 192.168.3.83.44354: S
1872954921:1872954921(0) ack 1454799176 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:07:19.347208 IP 192.168.3.83.44354 > 192.168.3.53.8080: . ack 1 win 5840
13:07:19.347245 IP 192.168.3.83.44354 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:07:19.347619 IP 192.168.3.53.8080 > 192.168.3.83.44354: . ack 2 win 1460
13:07:19.348186 IP 192.168.3.53.8080 > 192.168.3.83.44354: F 1:1(0) ack 2
win 1460
13:07:19.348368 IP 192.168.3.83.44354 > 192.168.3.53.8080: . ack 2 win 5840
13:07:26.384963 IP 192.168.3.83.44364 > 192.168.3.53.8080: S
1458774421:1458774421(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:07:26.385017 IP 192.168.3.53.8080 > 192.168.3.83.44364: S
1889194219:1889194219(0) ack 1458774422 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:07:26.385256 IP 192.168.3.83.44364 > 192.168.3.53.8080: . ack 1 win 5840
13:07:26.385267 IP 192.168.3.83.44364 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:07:26.386251 IP 192.168.3.53.8080 > 192.168.3.83.44364: F 1:1(0) ack 2
win 1460
13:07:26.386461 IP 192.168.3.83.44364 > 192.168.3.53.8080: . ack 2 win 5840
13:07:33.338703 IP 192.168.3.83.44374 > 192.168.3.53.8080: S
1462961310:1462961310(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0>
13:07:33.338758 IP 192.168.3.53.8080 > 192.168.3.83.44374: S
1885358461:1885358461(0) ack 1462961311 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
13:07:33.338987 IP 192.168.3.83.44374 > 192.168.3.53.8080: . ack 1 win 5840
13:07:33.338993 IP 192.168.3.83.44374 > 192.168.3.53.8080: F 1:1(0) ack 1
win 5840
13:07:33.339756 IP 192.168.3.53.8080 > 192.168.3.83.44374: F 1:1(0) ack 2
win 1460
13:07:33.339948 IP 192.168.3.83.44374 > 192.168.3.53.8080: . ack 2 win 5840
Thanks!
Robert
Re: Stuck in SYN_RECV when binding to ip
Posted by robert lazarski <ro...@gmail.com>.
On 4/13/07, robert lazarski <ro...@gmail.com> wrote:
>
> <snip>
> eth0 Link encap:Ethernet HWaddr 00:0C:29:5D:68:E7
> inet addr:xxx.xxx.166.53 Bcast:xxx.xxx.166.63 Mask:
> 255.255.255.240
> inet6 addr: fe80::20c:29ff:fe5d:68e7/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1955979 errors:0 dropped:0 overruns:0 frame:0
> TX packets:906962 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:519352897 (495.2 Mb) TX bytes:201866177 (192.5 Mb)
> Interrupt:177 Base address:0x1400
>
> eth0:eth1 Link encap:Ethernet HWaddr 00:0C:29:5D:68:E7
> inet addr: 192.168.2.53 Bcast:192.168.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:177 Base address:0x1400
>
> eth0:eth2 Link encap:Ethernet HWaddr 00:0C:29:5D:68:E7
> inet addr:192.168.3.53 Bcast:192.168.3.255 Mask: 255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:177 Base address:0x1400
>
> lo Link encap:Local Loopback
> inet addr: 127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:142486 errors:0 dropped:0 overruns:0 frame:0
> TX packets:142486 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:8030550 (7.6 Mb) TX bytes:8030550 (7.6 Mb)
>
> I need to bind to 192.168.3.53 for the load balancer to route the request
> tomcat. I'm passing '-b192.168.3.53' to JBoss to change the ${
> jboss.bind.address} to that address in the server.xml . There are a couple
> vars as localhost in the server.xml, which I tried changing to also to
> 192.168.3.53 to the same affect, which is via netstat repeating this, and
> never going to TIME_WAIT etc:
>
> tcp 0 0 192.168.3.53:8080 xxx.xxx.118.243:8368
> SYN_RECV -
Simplifying the problem, I installed tomcat 5.5.20 and I see the same
problem. All I did was change the server.xml to have:
Host name="192.168.3.53"
Please help,
Robert
Re: Stuck in SYN_RECV when binding to ip
Posted by robert lazarski <ro...@gmail.com>.
On 4/13/07, robert lazarski <ro...@gmail.com> wrote:
>
>
> tcp 0 0 192.168.3.53:8080 xxx.xxx.118.243:8368
> SYN_RECV -
This turned out to be a routing issue. I had to add a second default
gw , which created other problems but at least the mystery is solved.
Robert
Re: Error message
Posted by df...@email.arizona.edu.
Thanks for responding; I am using 1.4.2 with TOMCAT 5.0.28
Dwight
Quoting Martin Gainty <mg...@hotmail.com>:
> Dwight-
>
> Must be too much heat because I havent seen this since IBM J2RE 1.4.2
> Which JDK are you using?
> Which version Tomcat?
>
> M--
> This email message and any files transmitted with it contain confidential
> information intended only for the person(s) to whom this email message is
> addressed. If you have received this email message in error, please notify
> the sender immediately by telephone or email and destroy the original
> message without making a copy. Thank you.
>
> ----- Original Message -----
> From: "Dwight Farris" <df...@email.arizona.edu>
> To: "'Tomcat Users List'" <us...@tomcat.apache.org>
> Sent: Friday, April 13, 2007 7:45 PM
> Subject: Error message
>
>
>> Has anyone seen an error message similar to the following?
>>
>> java.lang.ClassFormatError: Illegal exception table range in class
>> file org/apache/tomcat/util/buf/ByteChunk
>>
>> Dwight (520) 626-9913
>> (520) 626-6345 (fax)
>> (952) 237-0606 (cell)
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Error message
Posted by Martin Gainty <mg...@hotmail.com>.
Dwight-
Must be too much heat because I havent seen this since IBM J2RE 1.4.2
Which JDK are you using?
Which version Tomcat?
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message -----
From: "Dwight Farris" <df...@email.arizona.edu>
To: "'Tomcat Users List'" <us...@tomcat.apache.org>
Sent: Friday, April 13, 2007 7:45 PM
Subject: Error message
> Has anyone seen an error message similar to the following?
>
> java.lang.ClassFormatError: Illegal exception table range in class
> file org/apache/tomcat/util/buf/ByteChunk
>
> Dwight
> (520) 626-9913
> (520) 626-6345 (fax)
> (952) 237-0606 (cell)
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Error message
Posted by Rashmi Rubdi <ra...@gmail.com>.
According to the docs:
http://java.sun.com/javase/6/docs/api/java/lang/ClassFormatError.html
Thrown when the Java Virtual Machine attempts to read a class file and
determines that the file is malformed or otherwise cannot be
interpreted as a class file.
ByteChunk is in tomcat-coyote.jar , replace your JAR with the one from
the distro for your version of TC and see if you still get the error.
-Rashmi
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Error message
Posted by Dwight Farris <df...@email.arizona.edu>.
Has anyone seen an error message similar to the following?
java.lang.ClassFormatError: Illegal exception table range in class
file org/apache/tomcat/util/buf/ByteChunk
Dwight
(520) 626-9913
(520) 626-6345 (fax)
(952) 237-0606 (cell)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Stuck in SYN_RECV when binding to ip
Posted by robert lazarski <ro...@gmail.com>.
On 4/13/07, Rashmi Rubdi <ra...@gmail.com> wrote:
>
> On 4/13/07, robert lazarski <ro...@gmail.com> wrote:
> > I'm using the tomcat that is embedded into jboss 4.0.5 , 5.5.17 I
> believe.
>
> Did you check with JBoss's support/forum ?
>
> -Rashmi
I'm using just tomcat 5.5.20 now for testing - same problem though. Added
address="myip" to the connectors in server.xml but no help.
Thanks,
Robert
Re: Stuck in SYN_RECV when binding to ip
Posted by Rashmi Rubdi <ra...@gmail.com>.
On 4/13/07, robert lazarski <ro...@gmail.com> wrote:
> I'm using the tomcat that is embedded into jboss 4.0.5 , 5.5.17 I believe.
Did you check with JBoss's support/forum ?
-Rashmi
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org