re: mysql JDBC tomcat

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yeah we are using CentOS and I don't know if jetty is running anyway.
The customer played around with routing and it seems to work OK now.
Must have been some random thing?

On a completely other note, you can see below the original message.
WHy is the formatting all screwed up?  User to work fine.

-----Original Message-----
From: fedora-list-request@xxxxxxxxxx [mailto:fedora-list-request@xxxxxxxxxx]
Sent: Friday, February 15, 2008 09:06 AM
To: fedora-list@xxxxxxxxxx
Subject: fedora-list Digest, Vol 48, Issue 122

 ------------------------------ Message: 8 Date: Fri, 15 Feb 2008 09:56:04 -0500 From: Robert L Cochran Subject: Re: mysql JDBC tomcat To: For users of Fedora Message-ID: <47B5A804.5070708@xxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 The Fedora 8 implementation of tomcat5 and jetty has a major bug: both tomcat5 and jetty, as packaged by the providers, use the same port by default. Usually jetty is started up before tomcat5, and this guarantees that tomcat5, by default, will break because jetty is listening on that same port. To fix the problem, you need to edit /etc/tomcat5/server.xml and change the default connector port number. Why does Fedora 8 include jetty? Because Fedora Eclipse needs it. The default implementations of tomcat5 and jetty need to change to so that they use different port numbers of both these packages are being installed. I don't know if this has any bearing on your problem -- on the surface of it, doesn't seem so -- but I wanted to mention this. Bob Cochran Greenbelt, Maryland, USA tony.chamberlain@xxxxxxxxx wrote: > > Perhaps there is a mysql group I could ask? But I will ask here anyway. > > Someone is using java and tomcat and mysql. Accessing mysql on 10.0.0.66 > from 10.10.0.2. They are pingable from each other but go through gateway > 10.10.0.30. > > And mysql -h 10.0.0.66 > from 10.10.0.2 returns a prompt after a while. > > However using jdbc times out even with a timeout of 70000. Here is > the command: > > > jdbc:mysql://10.0.0.66/dma_oam?useUnicode=true&characterEncoding=Big5&socketTimeout=700000&connectTimeout=700000 > id > (id omitted from this message for security reasons) > > This is being executed from Java. > > And to repeat, when it was used before there were 1 hop from server > machine to host machine (like here): > > traceroute to 10.0.0.50 (10.0.0.50), 30 hops max, 38 byte packets > 1 10.0.0.50 (10.0.0.50) 1.158 ms 0.198 ms 0.186 ms > > but in this case there are two > > traceroute to 10.0.0.66 (10.0.0.66), 30 hops max, 38 byte packets > 1 10.10.0.30 (10.10.0.30) 20.068 ms 19.775 ms 19.806 ms > 2 10.0.0.66 (10.0.0.66) 24.404 ms 23.240 ms 23.249 ms > > > > Could this be the reason for the timeout? Can jdbc not hop? > > > if you are interested, here is a stack backtrace > > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) > at java.io.BufferedInputStream.read(BufferedInputStream.java:317) > at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1316) > at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:1463) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1854) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1109) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1203) > at com.mysql.jdbc.MysqlIO.sqlQuery(MysqlIO.java:1164) > at com.mysql.jdbc.Connection.execSQL(Connection.java:2087) > at com.mysql.jdbc.Connection.execSQL(Connection.java:2037) > at com.mysql.jdbc.Statement.executeQuery(Statement.java:1156) > at > com.mysql.jdbc.Connection.initializePropsFromServer(Connection.java:2753) > at com.mysql.jdbc.Connection.createNewIO(Connection.java:1671) > at com.mysql.jdbc.Connection.(Connection.java:432) > > 
-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux