This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
With the basic concept of Static binding and run-time binding,
you can profile you application Jprofiler to understand it more.
Joined: Dec 11, 2009
Thanks for your reply.
I am trying to understand how does JVM/CLR behave during compliation and deployment. Many times we observe that the first request from the client takes a little longer to be serviced by the App Server than the subsequent requests. This is mainly due to numerous reasons like Caching, DB getting indexed or etc. My question may look very vague, but my intention is to understand what happens inside JVM or CLR during the first request from the Client on the App server.
Most app servers (you never said which one!) do lazy loading of database connections. Thus no connections are made until the first request needs a connection,at which point the minimum number of specified connections are created in a pool and one is given to the requestor.
Another significant startup issue is that any JSPs (or similar web page building mechanisms) have to have their Java code generated and compiled.
Thank you for your reply.
I see your point of lazy loading by the App/DB Servers. I have observed this First hit delay in App Servers like JBOSS and IIS 6.
Is there any way the required number of connection be indexed or cached over the App/DB Server layer where the Client gets the connection instantly?