Post reply

Viewing Processes

  • October 23, 2006 at 4:04 am

    #367666

    Hello all,

    We currently have 3 load balanced Tomcat Web Servers with 4 instances of Tomcat running on each server.  Each instance of Tomcat has its own IP. (All running on Windows 2003 Server R2, 64-bit plus W2K3 SP1).  The back-end is a 64-bit SQL Server 2005 (not yet service packed) active/passive cluster also running on Windows 2K3 R2 + SP1.

    At the moment we have a problem where a Tomcat instance will develop a problem, batter the SQL Server into submission and then everything goes downhill from there!  I was just wondering if there is a way - in SQL Server - if we can find out which instance in casuing the problem? When you view processes in SQL Server, it gives you the host name of the server making the connection.  We need to drill down further to get IP address of the instance making the connection request, if possible.

    I freely acknowledge that this is not a SQL problem, just looking for a way of identifying the root cause of a problem which (eventually) affects SQL.

    Thanks.

    Dave.

    PS - Please ask for any further info/clarification.

  • October 23, 2006 at 9:54 am

    #667403

    I have somewhat similar layout for one of my applications. I have 4 instances of WebLogic with different IPs on the same machine connecting to one SQL Server. The instances connect to SQL Server using SQL Server Standard login. I provide different login names and passwords for instances and they connect to different databases so I can see what connection has problems.

    You may tell us more about authentication that your web servers are using when connecting to SQL Server.

    And yes, this is a valid question for this forum. You are asking about connections to SQL Server.

     

    Regards,Yelena Varsha

  • October 23, 2006 at 10:11 am

    #667408

    Hi Yelena,

    Firstly, many thanks for your reply.

    Secondly, yes I am using Standard SQL authentication.  I simply have 1 login used by all instances to connect to the SQL box.  I do like your idea though - different logins for the instances would definately be a start. 

    We did try using Windows Authentication but setting up Tomcat to use this method proved very frustrating - all sorts of Tomcat's Java driver software had to be upgraded and as we control the back-end and not the front-end, we stuck with SQL authentication out of pure ease.

    Anyway, thanks again for your reply, it certainly give me a push in the right direction.

    Dave.

  • October 24, 2006 at 10:02 am

    #667633

    I'm not familiar with the connection options available with Tomcat, but we routinely use the "Application Name" property in our ADO/ADO.NET connection strings. Then we can identify SQLServer processes not just by the user login, but also by the application.

    -Matt

  • October 24, 2006 at 10:39 am

    #667643

    Matt,

    This is a good approach in general, but it may not work if:

    1. The application name is not provided in the connection string by the application

    2. If all instances are running the same application. For example, if you have 4 instances of the same application for different groups of people that require different customizations for thir instances.

    Dave,

    Windows authentication mostly does not provide for connection pooling. You need the same credentials for connection pooling. If you use different logins for different instances, this is OK, each instance will have its own connection pool.

    Regards,Yelena Varsha

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply