Showing posts with label performance_tuning. Show all posts
Showing posts with label performance_tuning. Show all posts

Friday, 22 February 2013

IHS ServerIOTimeout

There can be a number of reasons for seeing a message like the one below in your http_plugin.log

ERROR: ws_common: websphereHandleRequest: Failed to execute the transaction to 'myClusterMember' on host 'myHost'; will try another one

... but a common reason is that ServerIOTimeout in plugin-cfg.xml is set too low 

To verify, set your log level to trace (i.e in plugin-cfg.xml change LogLevel from "error" to "trace"), wait for RefreshInterval (or bounce IHS if you're impatient) and look for the following message...

lib_rio: wait_on_socket: ServerIOTimeout fired.

Point to note.. if you are seeing this message in an environment where you have SSL Client Authentication enabled (aka 2-way SSL) chances are that you'll also be seeing GSK errors (look for PARTNER CERTIFICATE). I saw this and spend a while chasing down a non-existent trust issue. I then realised that the reason this was happening is because (I think) that the ServerIOTimeout was firing during the SSL handshake.

ps... don't forget to set your LogLevel back to "error"




Thursday, 10 January 2013

Dropping a JSP into an existing WebApp



I'll use IBM's WebSphere Perf Servlet as an example...

Placing hello.jsp in /opt/bpm/profiles/profile_name/installedApps/cell_name/perfServletApp.ear/perfServletApp.war allows this URL to be called
http://<host>:<port>/wasPerfTool/hello.jsp


Thursday, 20 December 2012

Looking at Solaris JVM heap

Carry out a a full heap dump
  • jmap -d64 -dump:format=b,file=/tmp/heap.hprof  <PID>

Read the heap dump
  • jhat  -port <port> -J-mx2048m /tmp/heap.hprof
  • Point a browser at the host you are running jhat on using the port specified by -port above