Error SRVE0255E means that the webcontainer could not find a web group (web module) or virtual host to handle the request. Here are the steps to diagnose this error: 1. Make sure that the URL entered at the browser is correct. Particularly, make sure that the context root from the URL matches the context root configured for the application. 2. Review the SystemOut.log to make sure that the application and server are started successfully and without any errors. 3. Verify that the application web module is mapped to the correct/intended virtual... [More]

Tags:  application_server webcontainer application ibm-blog server was websphere_application_ser... srve0255e websphere

  This is the process of investigating cpu utilization for a JAVA™ application server in response to a need to resolve a performance problem or to determine a base line for the application. Specifically, this investigation applies to AIX, linux, Solaris, HPUX, UNIX® like systems, and Windows. This will uncover the amount of cpu resources reported in use, the amount of available cpu used by each process, and the amount of cpu used by threads in processes. We use this process very often in WebSphere Application Server Support, but... [More]

Tags:  hpux aix performance threaddumps thread windows threads cpu was websphere high application java application_server solaris javacores server linux

  WebSphere Application Server v8.0 and Higher :   The HTTPOnly flag on the JSESSIONID is enabled by default. Check and make sure the option " Set session cookies to HTTPOnly to help prevent cross-site scripting attacks " is selected. The Secure flag on the JSESSIONID is not enabled by default. To add the Secure flag to the JSESSIONID, make sure the option " Restrict cookies to HTTPS sessions " is selected. In the administrative console: click on Application servers > servername > Session management > Enable cookies    ... [More]

Tags:  httponly ibm-blog secure websphere_application_ser... application_server jsessionid application server was websphere cookie

  There may be situations where it is necessary to tune the connection pool for optimal performance.  It may be difficult to determine what each property does and which ones need to be tuned.  To help you get a better understanding of the connection pool properties that are available in WebSphere Application Server (WAS), this blog post will explain in detail some of the more common properties and when to tune them. Remember that these are general recommendations and that you will need to test any setting changes thoroughly in your own... [More]

Tags:  was server websphere_application_ser... ibm-blog connection_pool websphere application_server connection properties pool application tuning

  A StaleConnectionException is an exception that is generated by the WebSphere Application Server database connection code when a JDBC driver returns a fatal error from a connection request or operation.   Configuring a WebSphere Application Server datasource includes specifying a datasource helper class, which is selected depending on your JDBC driver type, for example, DB2UniversalDataStoreHelper for DB2, Oracle11gDataStoreHelper for Oracle 11g, etc. Each helper class contains a list of driver specific error codes associated with fatal... [More]

Tags:  ibm-blog websphere_application_ser... jdbc websphere staleconnectionexception staleconnectionexceptions connection application_server was

    NOTE: Java SDK 6, going out of support, is embedded in WAS traditional V8.5 as the default Java SDK. Review details on tWAS: Support ends in April 2018. The end of Java SE 6: Where to go from here       Liberty: Support ends on September 2017 and that fix pack (17.0.0.3) will be compiled at the Java 7 level, so will not run. In this blog we will cover tWAS in detail.   Existing users updating from previous a fixpack continue to have embedded Java SDK 6 until Java SDK 6 goes End Of Support in April 2018. The next fixpack for 8.5.5.x shipped... [More]

Tags:  websphere_application_ser... java application application_server server was sdk websphere wasadm-blog ibm-blog

  I wanted to take some time to explain error "J2CA0045E: Connection not available while invoking method createOrWaitForConnection (ConnectionWaitTimeoutException)." This exception occurs when your JDBC connection pool has reached the maximum number of database connections you allow, and subsequent database connection request from your application cannot be serviced before your datasource configured connection timeout value expires.   When you configure a WebSphere Application Server managed datasource, you set two parameters that can... [More]

Tags:  was websphere_application_ser... connectionwaittimeoutexce... j2ca0045e ibm-blog createorwaitforconnection connection application_server

  This blog contains some common questions and answers that are related to the use of JMS connection pools and session pools. Hopefully this information will help you in your environment tuning efforts. Q: WebSphere MQ Queue Connection Factories in WebSphere Application Server releases contain both a connection pool and a session pool for configuration. When configuring the session pool, is this configuration for each connection? For example, if my connection pool has a maximum size of 10, and my session pool also has a maximum size of 10, does... [More]

Tags:  session_pool application_server configure jms was websphere_application_ser... ibm-blog connection_pool

  The WebSphere L2 Support team handles its fair share of WebSphere Application Server performance analysis. Often it appears as though the Monitoring Agent (that thing that reports whether the system is behaving - or not) is the problem itself. The truth is, the more problems that the agent has to report, the more noise the agent is going to interject into the diagnostic data. It's a vicious cycle.   One of the common agents that are encountered is Wily. Like any performance monitoring tool, Wily can introduce a significant amount of noise... [More]

Tags:  agent java websphere_application_ser... websphere wily tuning ibm-blog performance was diagnostic monitoring application_server

  Sometimes servers do not start. Maybe it is due to a bad build, the configuration has gotten corrupted, or it just stopped working. This blog helps you understand the anatomy of the Application Server start up process. It provides you with troubleshooting and debugging techniques to determine why the server is not starting or why the server is not stopping.   Starting the server Let's see what happens when a server is started using the startServer.sh /bat server1 command. Two Java virtual machines (JVM) are actually launched. The first... [More]

Tags:  application_server startup was websphere_application_ser... wasadm-blog wassdk-blog websphere jvm ibm-blog

  A wealth of valuable JVM diagnostic data can be gathered by doing the following tasks: Generate a Java™ thread dump. Enable logging of verbose garbage collection data for Server. Generate a Java heap dump. Generate a system core dump & snap trc file.   In the overall process of problem determination, diagnostic data must be collected or generated, and the data must be analyzed. Various tools are available to help you analyze diagnostic data for solving problems. Below are the links for the analysis of javacore, verbosegc,... [More]

Tags:  verbosegc javacore dump tools websphere troubleshooting application_server websphere_application_ser... was thread snap.trc java

  List of firewall ports that must be open for communication between the deployment manager, nodeagent, and Application Server   It's very important to know the ports that should be opened in the firewall for proper communication between deployment manager, nodeagent, and application servers. Follow the below steps to achieve this task.   Find the port numbers in the serverindex.xml file or from the ISC (Integrated Solution Console) The serverindex.xml file can be found under the profile-root/config/cells/cellName/nodes/nodeName folder.  ... [More]

Tags:  ibm-blog port firewall was ports communication websphere application_server deployment wasadm-blog nodeagent websphere_application_ser...

  The HAManager/HAM (High Availability Manager) Framework is an integral WebSphere Application Server (WAS) part designed to provide an infrastructure for making selected WAS services highly available. It is present in all JVMs including Deployment Manager and Node Agents. HAM can be used by other internal WebSphere components to provide automatic failover support. Four basic HAManager services: Bulletin Board    - Used by WLM and ODC HA Groups         - Used by Transaction Log recovery, Messaging engine failure etc .. (Policy based fail-over)... [More]

Tags:  hamanager wasadm-blog websphere_nd wascet-blog ibm-blog was application_server high_availability_manager hamgr websphere_application_ser... websphere ham failover

  Troubleshooting Web Services Performance Problems In IBM WebSphere Application Server With Web Services Performance (WSPerf) Trace Introduction - Web Services Performance (WSPerf) Trace The WSPerf trace is a feature of IBM WebSphere Application Server. The WSPerf is a troubleshooting aid to assist analysts to resolve web services problems, especially performance problems. WSPerf trace can be used to analyze the speed of web services message traffic in IBM's WebSphere Application Server web services engine. WSPerf trace helps to... [More]

Tags:  troubleshoot troubleshooting was soap websphere jaxrpc server websvcs jax-rpc application axis2 application_server wsperf trace web services webservices jax-ws performance jaxws webservice