Subject | Re: [firebird-support] Maximum Concurrent Connections that Firebird would allow |
---|---|
Author | Steve Wiser |
Post date | 2010-02-12T21:31:52Z |
What operating system? If you are using linux make sure you have setup
xinetd to not limit connections to a port. We have over 600 concurrent
connections to one of our servers on a daily basis.
-steve
xinetd to not limit connections to a port. We have over 600 concurrent
connections to one of our servers on a daily basis.
-steve
On 2/12/2010 3:57 PM, D K wrote:
>
> Hi,
> I would like to know the Firebird database limit for the maximum
> concurrent connections.
> When i try to make more that 100 connections, i get the following
> exception.
>
> org.hibernate.exception.GenericJDBCException: Cannot open connection
> at
> org.hibernate.exception.SQLStateConverter.handledNonSpecificException
> Caused by: org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544721.
> Unable to complete network request to host "localhost".
> Reason: Unable to
> complete network request to host "localhost"
>
> Is it possible to set the max number of concurrent connections for
> Firebird database .
> Thanks
> DK
>
> [Non-text portions of this message have been removed]
>
>
--
Steve Wiser
President
Specialized Business Software
6325 Cochran Road, Unit 1
Solon, OH 44139
www.specializedbusinesssoftware.com
(440) 542-9145 - fax (440) 542-9143
Toll Free: (866) 328-4936
This message and any files transmitted with it may contain information that is privileged, confidential, and exempt from disclosure under applicable law. They are intended solely for the use of the intended recipient. If you are not the intended recipient, distributing, copying, disclosing, or reliance on the contents of this communication is strictly prohibited. If this has reached you in error, kindly destroy this message and notify the sender immediately. Thank you for your assistance.
We attempt to sweep harmful content (e.g. viruses) from e-mail and attachments, however we cannot guarantee their safety and can accept no liability for any resulting damage. The recipient is responsible to verify the safety of this message and any attachments before accepting them.