Chapter 2. JEUS v7.0 Fix#3

Table of Contents

2.1. New Functions
2.1.1. WebSocket
2.1.2. Network
2.1.3. WebAdmin
2.2. Updates
2.2.1. WebEngine
2.2.2. Session Server
2.3. Bug Patches
2.3.1. WebEngine
2.3.2. EJB
2.3.3. JMX
2.3.4. Deployment
2.3.5. WebAdmin
2.3.6. Session Server
2.3.7. I/O

This chapter describes the new functions and the changes made to JEUS v7.0 Fix#3.

This section describes the new functions of JEUS.

This section describes the changes made to JEUS by module.

This section describes bug patches by module.

  • Fixed: Port number (along with URL information) is returned when calling request.getRequestURL

    • Only URL information, excluding port numbers, is returned from request.getRequestURL() when the HTTP and HTTPS requests use the default ports (e.g., 80 and 443).

  • Fixed: Enter an infinite loop when using WJPv2

    • When WJPv2 is used, a message is divided into multiple submessages, such as "request + body, body, ...", and then sent. Managing the remaining data no longer causes an infinite loop.

  • Fixed: When the HttpSession object is used to record access logs, ClassNotFoundException occurs

    • If a HttpSession that includes a user class is used (with the %u or %s option) to record access logs, a session deserialization error occurs due to ClassNotFoundException.

  • Fixed: ClassLoader cannot find the classes under WEB-INF when accessing the session

    • User Class cannot be deserialized because ClassLoader cannot find classes under the WEB-INF directory when accessing a session.

  • Fixed: URL pattern blocking is case-sensitive

    • The URL pattern is now case-insensitive.

      (E.g., ‘%5c’ and ‘%5C’ are considered the same value.)

  • Fixed: init-param is not applied when jeus.servlet.servlets.JspServlet is registered

    • init-param, which is configured when JspServlet is registered in web.xml, is now applied.

    • StartingException occurs at the deployment stage when registering two or more JspServlets in web.xml.

  • Fixed: Dynamic modifications to the webtob-connector connection configuration are not applied.

    • When using WebAdmin and console commands to dynamically modify the configuration of the webtob-connector connection, a value different from the specified value is set. This bug is fixed.