Re: Connection pool
Hello Mohamed, On Thu, May 5, 2022 at 2:59 AM Mohamed Eliyas Abdul Kadar wrote: > > Hi All > I am trying to limit the db connections on the oracle side by limiting the > size of connection pool in the datasource config as below. I tried setting > the max size to 20 by maxTotal/ maxActive either of them didn't work. The db > side connection was always more than 30. Please advise. > > > initialSize="10" maxTotal="10" maxIdle="10" maxWaitMillis="1" > username="PORTAL" password="cde" > driverClassName="oracle.jdbc.driver.OracleDriver" > url="jdbc:oracle:thin:@cde" factory="SecureDataSource"/> > Can you please check the source IP of the connections just to make sure they all originated from the server where you are running your Tomcat? By any chance are you running multiple instances of Tomcats? Thanks & Regards, Suvendu > Regards > Mohamed > This communication and its attachments contain confidential information and > is intended only for the named addressee. If you are not the named addressee > you should not disseminate, distribute or copy this communication. Please > notify the sender immediately if you have received this communication by > mistake and delete or destroy this communication. Communications cannot be > guaranteed to be secured or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. > The sender therefore does not accept liability for any errors or omissions in > the contents of this communication which arise as a result of transmission. > If verification is required please request a hard-copy version. NeoGenomics > Laboratories, 9490 NeoGenomics Way, Fort Myers, FL 33912, > http://www.neogenomics.com (2022) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Connection pool
Hi All I am trying to limit the db connections on the oracle side by limiting the size of connection pool in the datasource config as below. I tried setting the max size to 20 by maxTotal/ maxActive either of them didn't work. The db side connection was always more than 30. Please advise. Regards Mohamed This communication and its attachments contain confidential information and is intended only for the named addressee. If you are not the named addressee you should not disseminate, distribute or copy this communication. Please notify the sender immediately if you have received this communication by mistake and delete or destroy this communication. Communications cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this communication which arise as a result of transmission. If verification is required please request a hard-copy version. NeoGenomics Laboratories, 9490 NeoGenomics Way, Fort Myers, FL 33912, http://www.neogenomics.com (2022)
Re: Tomcat + Safari WebSocket issue
On 03/05/2022 14:12, Hagenauer, Florian wrote: Does anyone have an idea or is able to clarify if this is an issue with Tomcat or with Safari/WebKit? Or if there is a workaround to this issue? I've just run Safari on a fully updated macOS Monterey against the Autobahn|Testsuite for the WebSocket protocol. Safari failed multiple tests, mostly in the compression sections. Safari also exhibited multiple "non-strict" results which indicate things like closing a connection with the wrong close code. Tomcat fully passes the Autobahn|Testsuite. Given the above, it seems reasonable to conclude that there are still a few bugs in Safari's WebSocket implementation that need fixing. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat + Safari WebSocket issue
Hi Pawel, > Try capturing the traffic (with Wireshark, etc) for the broken connection > against Tomcat, and then also to the "working" Python server, at least what > are the differences on the wire. > That would probably help identify the problem a lot faster. I attached screenshots from Wireshark capturing three scenarios: * tomcat-safari.png (triggers the issue) * tomcat-chrome.png (does not trigger the issue) * python-safari.png (does not trigger the issue) I am no expert in low-level WebSocket communication, but it looks like Safari has an issue with Tomcat splitting the message into frames. Beste regards, Florian -Original Message- From: Pawel Veselov Sent: Dienstag, 3. Mai 2022 18:20 To: Hagenauer, Florian Cc: Tomcat Users List Subject: Re: Tomcat + Safari WebSocket issue Florian, On Tue, May 3, 2022 at 3:12 PM Hagenauer, Florian wrote: > since Apple released Safari 15 (both iOS and macOS) I am running into a > strange issue related to Apache Tomcat, Safari/WebKit and certain sequences > of messages received via a WebSocket. When the browser receives messages in > this order, the connection gets closed. > > The following sequence triggers the issue: > 1. Connect from Safari to a Tomcat WebSocket server and use the > 'permessage-deflate' extension 2. Receive a text message from the > WebSocket server 3. Receive a large binary message from the server 4. > The WebSocket connection is closed with the close code PROTOCOL_ERROR. Try capturing the traffic (with Wireshark, etc) for the broken connection against Tomcat, and then also to the "working" Python server, at least what are the differences on the wire. That would probably help identify the problem a lot faster. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
