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

Even some WebSphere MQ veterans may be unfamiliar with the term MQTT (MQ Telemetry Transport) although they probably are affected by it in their everyday lives. Do you receive Facebook Messenger notices on your smartphone? If so, then it’s likely you’re getting that notification through the MQTT protocol. The protocol was invented by Dr Andy Stanford-Clark of IBM, and Arlen Nipper of Arcom (now Eurotech), and is openly published with a royalty-free license. MQTT is included as the MQ Telemetry component of WebSphere MQ version 7.1 software... [More]

Tags:  scada websphere redbooks qos internet wmq mqxr mq telemetry rfid mqtt

  Introduction Java heap is the area of memory that is used by the Java virtual machine (JVM) for storing Java objects. Optimal Java heap size is application and use dependent. Setting the JVM heap size is directly related to the number of server instances that needs to be started on a specific node and the total RAM available on the machine. The maximum heap should be incremented not to exceed 50% of overall physical memory.  The Java heap memory is used by the applications that are deployed and the component running in WebSphere... [More]

Tags:  heapsize was websphere_application_ser... java heap

    Starting with IBM WebSphere Application Server (WAS) v8.5.0.0, you can install Java 7.0 as an optional feature. WAS v8.5.0.0 comes with Java 6 as the default Java SDK. Java 7.0 can be added at any point in time to the installation, thereby adding the Java 7.0 SDK selection to the possible choices of Java SDKs that can be used. For completeness: Java 7.0 was shipped as an optional feature that can be installed with WAS v8.5.0.0 Java 7.1 is shipped with WAS v8.5.5.2 (in a full installation) which can be installed as an optional feature on WAS... [More]

Tags:  install application optional wasadm-blog java ibm-blog websphere was server

  In one of Vish's blogs, he explains how to install the optional Java 7.x on WebSphere Application Sever 8.5:   Installing optional Java 7.x on WebSphere Application Server 8.5 https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/installing_optional_java_7_x_on_websphere_application_server_8_5_0_0?lang=en   Once it is installed, however how can you tell which version of Java is actually being used?  You can look at the SystemOut.log header, but the output may be a little bit confusing.  Here are some examples to help... [More]

Tags:  was wassdk-blog version server websphere ibm-blog managesdk wasadm-blog java

  We've probably all see a hung JVM at one time or another and chances are you've figured this out in one of two was if you're dealing with WebSphere Application Server: 1. the users are complaining that the browser just “spins” and never returns a web page, or 2. you've noticed output in the WebSphere logs (SystemOut.log) that indicate potentially hung threads. For the purposes of this discussion, we'll focus on the latter method.   WebSphere Application Server provides a feature that detects hung... [More]

Tags:  thread hangs websphere_application_ser... websphere was java threading

WebSphere MQ V7.1 introduced a channel security feature called Channel Authentication Records, or CHLAUTH for short. The feature allows you to set rules to indicate what should happen to inbound connections to your queue manager, i.e. channels and clients. Should they be allowed to connect or should they be blocked from connecting. If you migrate up from an earlier release to V7.1, i.e. you created your queue manager at an earlier release, then CHLAUTH will be disabled by default. However, if you create your queue manager with the V7.1... [More]

Tags:  channel wmq 2035 chlauth blocked security mq

I talked with a WebSphere Application Server support analyst the other day and they mentioned they had seen some "easy problems" coming in to Level 2 support recently.  I thought it would be good to blog about these easy ones so you can solve on your own without consuming your time contacting support and sending documentation. Looking at documentation, such as a javacore, can sound like a daunting task if you do not know what to look for.  But a javacore is just a readable text file with snapshot information of a running JVM.  It... [More]

Tags:  server was application core heap native websphere javacore java outofmemory