Provides a function to group (preset) individual monitoring items provided by each server. (The preset is managed and saved by DAS.)

Added function to monitor statement cache and server log.

Added a page search function.

Added function to retrieve patch information and to display nodes (in table format) to which each path file is applied. (Monitoring > Patch Info)

Added function to duplicate servers using the options, Number Of Server (the number of server to be duplicated) and Step (the increment of a port when Listen Port is duplicated).

Checks if there are any duplicated addresses or ports and displays the result with a message.

Provides a function to sort table rows when the table header is clicked.

Three modes are available: unsorted, ascend, and descend.

Separated session cluster from JEUS cluster.

Provides a function to replace Session manager used by Servlet with InfiniCache.

Separated session provider to provide session server SPI.

The GMS managed in the domain level and GMS managed in the cluster level were integrated into a single GMS in the domain level.

JEUS now supports this function, which is also provided by applications.

When an application executes setAttribute with the designated key, it is considered a login. If a duplicate login exists, the existing session is removed.

Implemented a new method of multicast by implementing a protocol similar to TCP on top of UDP, which lacks reliability, to take advantage of the strengths of UDP (to enhance performance) and TCP (to enhance reliability).

If use-virtual-multicast is set to false, use reliable multicast.

Provides a function to run a specific engine using an on/off function.

Required engines are checked according to the application type. Any uninitialized engines are now initialized and then deployed.

Added function that is used when NodeManager is registered as an OS service such as a Windows service.

The function is executed by adding the -stopServer option to the NodeManager stop command so the server can stop before NodeManager stops.

Server, which is stopped by the –stopServer option, can start when NodeManager boots.

By using options, such as username, password, domain, and server, DAS can start when NodeManager starts.

To change the NodeManager type in Fix#1, the NodeManager must be removed and then a new NodeManager must be created with the desired type. However, in Fix#2, a command that changes between the SSH and JAVA NodeManager types was added.

Added function that automatically backs up the domain configuration when DAS is booted (backup directory can be specified).

IP, port, and node information can be modified when the backup file is unzipped in another node.

Added function to completely shutdown NodeManager by reading information in the jeusnm.properties file when NodeManager stops.

Added property to complete deployment even if class loading, which was called by loadAllClasses, fails due to ClassNotFoundException during deployment in Shared Class Loading mode.

The default value of the jeus.deploy.ignore-not-found-classes system property 'false'.

Added to support InfiniLink.

Added ReadOnlyRole, which can display all items (Navigation possible) but cannot edit (action impossible).

When a client sends a HTTP request body in chunks, WebtoB sends each chunk to JEUS as soon as it arrives.

When a HTTP request body to be sent by a client is large, the client connection can be lost while sending the request. Since JEUS cannot determine if the client connection is lost, the Servlet waits for the request Body until timeout occurs. To prevent this situation, WebtoB has the NotifyClientClose option. Even without this option, WJPv2 lets JEUS know that the client connection is lost, and JEUS sends an IOException to Servlet.

Helps to more efficiently process JEUS Dynamic content cache in WebtoB.

When session routing is performed in WebtoB, the total number of sessions created in the JEUS server can be received from JEUS and referred to. (PING configuration in WebtoB is required: WebtoB SvrChkTime)

Added function to support SSL to enhance communication security between JEUS and WebtoB installed on the same system or on separate systems.

Supports a WebtoB-JEUS SSL connection from WebtoB 4.1 SP6 Fix#0.

Added option that ignores any whitespace preceding the HTTP header so it is not considered a Multi Line Header.

The default value of the "jeus.servlet.http.ignoreMultiLineHeader" property is false.

From Servlet 3.0, multipart-config can be set for each Servlet, which allows the web container to handle multipart/from-data of a POST request. ProgressListener can be registered to receive events about the handling progress.

Added function to call the default Servlet even if <mvc:default-servlet-handler/> is set in Spring.

Added function to configure webcommon.xml and web.xml for each server.

The function adds configuration files to DOMAIN_HOME/config/servlet/SERVER_NAME/.

In the JSP specification, there is a function that compiles JSP without calling JSP when JSP is called by using "http://[IP:Port]/index.jsp?precompile=true". However, this function is rarely used. To reduce precompilation parsing overhead that occurs whenever JSP is called, the jeus.servlet.jsp.precompile option, which prevents this function, was added.

Added the list-webtob-connections command. (alias: lswjp)

Server name and webtob-connector are required options.

The jeus.servlet.response.force-response-10 option was used to respond to a HTTP 1.0 request with version 1.0. The added function selects the HTTP version automatically, depending on the request, to prepare for HTTP 2.0.

Added function to attach 'Connection: keep-alive' to the header for the configured error code. The function adds the keep-alive-error-response-codes configuration to jeus-web-dd.xml (Default value: 404).

Added the <client-override> option, which sets encoding to a lower priority than the Servlet API but to a higher priority than the charset configured in the Content-Type header of the HTTP request.

The <client-override> configuration has the same meaning as the <forced> configuration of JEUS v7.0 Fix #1 (and earlier).

Added function to run the backup when the main WebtoB malfunctions.

Added function that removes clients that do not send a request for a specific time even though the clients are connected to HTTP Listener in keep-alive mode.

Follows the <keep-alive-timeout> operation of Server Listener, and does not run when <use-nio> is false.

Newly configures JEUS 7 domain by selecting the nodes to be migrated from JEUS 6.

JEUS 6 does not contain a domain, so JEUS 7 Domain and DAS are created with default settings.

Uses JEUSMain.xml, WEBMain.xml, EJBMain.xml, and JMSMain.xml, which are used to configure each JEUS 6 node, to create domain.xml for the migration.

Each Engine Container of JEUS 6 is migrated into a Managed Server of JEUS 7. The configuration for JEUS Manager is not migrated.

Creates a MS, which corresponds to additionally configured Context Groups, when two or more Context Groups are configured in an Engine Container.

When multiple JEUS 6 nodes are migrated, export-name, data-source-id, and application-id can be duplicated. Duplicated values must be manually checked and modified.

Added a concurrent option to the deploy, distribute, start, stop, and undeploy commands that can be concurrently executed.

Added function to check the list of patch files applied to each server by adding the -patch option to the system-info command.

Added function to specify the class path referred to by the EJB when the EJB is compiled by appcompiler.

It can be specified using the –clp option.

Added tool to create or update the jeus-web-dd.xml file of the application when an application file is received as an input value.

Supports the Maven Plugin for JEUS 7.

Supports the start-das, start-ms, install-app, and uninstall-app commands.

Provides an option that outputs a summary when executing the thread-info (ti) command.

Added function to monitor the system thread pool status.

Added the remote server log transfer function.

Added the -duptargetserver option to add-server to allow a user to copy the settings of an existing server when a new server is added.

Specifies the default path of server logs.

The path also applies to the path in which rotated backup logs are created.

Added function to configure NodeManager log files.

Supports the JEUS installation on the IBM Power Linux platform.

Added the connection validity check function using java.sql.Connection#isValid, which was added in JDK 1.6 and JDBC 4.0.

To check connection validity, the isValid method can be used (like “use isValid method”) instead of check-query. check-query-timeout is used as timeout.

check-query-period, non-validation-interval, and check-query-destroy-policy operate in the same way as check-query.

Added function to transfer a JMS client side reliable message using LPQ.

The GMS managed in the domain level and GMS managed in the cluster level were integrated into a single GMS in the domain level.

To support InfiniLink, the lifecycle invocation can now be configured in the domain and a cluster.

The activate task, which uses a single Mbean Call to call Observer in the server, the transferring task, which sends the file to the server, and the LoadConfiguration task, which loads the file from the server, are performed when the configuration is modified and applied.

Even when a server fails, NodeManager can use the start-server command.

Even if the DAS sends the MS shutdown command, MS may not respond due to OOM or a network problem or MS may not shut down until timeout. If any of these events occurs, NodeManager kills the MS.

Windows does not support this process.

Fix#1 only supports the use of one type of NodeManager, but in Fix#2, both types can be used concurrently.

In Fix#0, servers start in sequential order, in Fix#1, servers start concurrently, but in Fix#2, the starting method can be chosen.

If an independent MS joins a domain managed by DAS, applications in the domain are automatically resynchronized, which can cause an issue for servers currently running.

Added the enable-to-resynchronized-applications option (default value: false) so applications are not automatically resynchronized when an independent MS joins a domain managed by DAS.

External Resource and Custom Resource, which were configured for each server, have been modified so they are configured for each domain and overridden in the server.

The cache file used by the Java-type NodeManager is now encrypted with AES to enhance security.

When DAS detected a MS with a failure, it restarted the MS unconditionally. Now, restarting the MS is optional.

A password entered with the -p option is no longer displayed when the ps command is executed for a server process.

When a server fails to shut down, its status changes to DOWN_FAILED, not to the previous status.

If the server status becomes DOWN_FAILED, commands to start and stop the server become available.

When the same exploded module type application is deployed to multiple servers, different context paths can now be set for each server.

When an application is deployed without specifying a type, the default type is WebModule.

Graceful redeployment is now supported for exploded mode applications.

Whether to concurrently deploy EAR modules is optional.

The redeployment policy was modified in the following cases: when an application file is located in APP_HOME, when an application file or a directory is in a repository, and when a file to deploy or a directory is specified using the -path or -dasPath option.

Deployment of an application to multiple MSs is improved.

Removed %l (an unnecessary option) and %u (request.getRemoteUser()) options from the default log.

derby.log is now created in the log directory of each server when embedded derby is used.

Optimized performance when an application writes a byte array that is larger than output-buffer-size.

Improved the buffering function for response data received from JEUS. Modified to reuse the message read buffer and to immediately send a client as much data as was read.

When one WebtoB connects to multiple JEUS servers, it cannot be suspended by one of the JEUS servers. The command to suspend WebtoB is no longer available.

default-error-page of an web engine can now be set by a relative or an absolute path.

When default-error-page is set to a relative path, the path is based on $DOMAIN_HOME/config/servlet/<server-name>.

JSF RI in JEUS_HOME/lib/shared is no longer added to the classpath unless it is explicitly specified in jeus-web-dd.xml.

Connections are forcibly disconnected when a HTTP or AJP13 queue is full. However, if the http-listener queue is full, the 503 error (service temporarily unavailable) is returned.

Unlike WebtoB, JEUS reverse proxy, which adopted Tomcat implementation, unconditionally adds 'via', 'x-forwarded-for', 'x-forwarded-host', 'x-forwarded-server', and 'accept-encoding' to a request header. These items can now be optionally added.

Blocked URL patterns are now configured in domain.xml/web-engine instead of urlblocking.properties.

A Servlet URL pattern to be registered with annotation and registration API is now decoded, like in Tomcat.

Changed the default value of output-buffer-size to the socket send buffer size of each OS.

Servlet 3.0 supported by JEUS v7.0 allows a web application to be deployed without web.xml. Therefore, web.xml was removed.

If disable-pipe is true (use-pipe is false), a connection is unconditionally established to a socket instead of ipcbaseport.

If disable-pipe is false (use-pipe is true), a connection is established to ipcbaseport.

If a file or directory that does not exist is specified in ServletContext.getRealPath(), a context-based path is returned instead of NULL.

If JSP is called when enable-jsp is set to false, the 503 error (service temporarily unavailable) was returned. Now, JSP is treated as a resource.

If AJP13 listener receives a request without a body or if JEUS sends a body as a chunk to a client and reads the body, -1 is returned. EOFException occurred in previous versions.

When a JNDI connection is established, any security information that is unnecessary is no longer exchanged when version information is reused after authentication.

The jeus.jndi.compat option must be configured for backward compatibility.

When InitialContext is shared, synchronization is no longer performed to allow parallel processing, which improves performance.

Integrated the two internal stages of 'prepare' ('beforeCompletion' and 'prepare') into a single stage, which improves performance.

Maintains backward compatibility without special configurations.

When the first JEUS TM log is removed, JEUS no longer fails to boot. If jeus.tm.ignore.broken.log.file is set to true, the removed log is regarded as an error, the broken TM log file is removed, and JEUS normally boots.

If the second JEUS TM log is removed, this is not regarded as an error. The TM log file is removed and JEUS normally boots.

If the log files cannot be deleted, JEUS fails to boot and a message indicating that the files must be deleted is displayed.

In Fix#0, when a server is included in a cluster, the server can use both its own DataSource and the cluster DataSource. In Fix#1, the server DataSource could no longer used and only the cluster DataSource could be used. In Fix#2, both DataSources can be used like in Fix#0.

When an Oracle database is used, failover and failback for a cluster DataSource are supported by receiving a DB failure or revival notification through ONS.

Changed the binding method to locally bind a DataSource to a target server by default.

MS performance no longer dramatically decreases when the number of MSs increases.

The ID and the password entered during login are no longer saved in a browser that supports HTML5.

When reacquiring a lock that was released outside, a warning message is displayed because relevant modified information is lost.

Unnecessary links and buttons on the Runtime Info popup window can be no longer clicked.

Added a function to check whether the current subject status is lock or unlock after executing lockuser or unlockuser for the subject.

Multiple threads can no longer concurrently access a single JMS session. An exception is thrown to the client.

The Bean name is now applied to the names of HomeImpl and ObjectImpl classes, which were created by JEUS.

Modified Windows service functions to meet the JEUS v7.0 structure. (Operation of the service itself is the same as in previous versions.)

Optimized the internal communication of a session server to reduce network usage.

If connection failures continuously occur, or if applications are not deployed when MS restarts after a connection failure, a client request is not sent to the session server.

When a connection failure occurs, the number of selector threads no longer continuously increases.

When session backup occurs under heavy load, the http service can be handled first using an option to improve response performance.

Previously, whenever JAR (EJB module) was deployed, all class lists of its archive were registered in the class loader. Now, when all EJB modules are deployed, registration takes place once in EAR, which reduces deployment time.

The option to guarantee the order between ServletOutputStream, the response writer, and JspWriter (used in JSP) is now applied.

If encoding, response-encoding, and force are configured in domain.xml and jeus-web-dd.xml, the encoding configuration set in setContentType(), setLocale(), and response.setCharacterEncoding() must be ignored. However, the configuration set in response.setCharacterEncoding() was not ignored. This bug is fixed.

Added the jeus.servlet.filter.applyOnWelcomeFileRequest option to fix this bug.

The default value is true. If set to false, a filter for welcomefile is applied.

Fixed: When a text field such as a field for a JVM option or an XML export function is used, characters (such as “ and &) are automatically escaped and rendered.

Fixed: When an application is concurrently deployed to multiple MSs, the lock permission is denied in HP-UX.

Fixed: NodeManager fails to boot because an exception occurs when a user modifies the serverName.state file or the file contains an empty string.

If the license is expired when a server boots using NodeManager, the server fails to boot.

The bug was eliminated by updating the Glassfish Corba library to the newest version.

Fixed: The "Under control" and "JEUS version" values displayed as the result of executing the list-nodes command are incorrect.

Commands that retrieve various configurations no longer obtain a lock and display the result information configured in XML configuration files.

ServiceUnavailableException occurs when a server to lookup is not alive. Since the exception is not failed over, JNDI failover is now used.

Fixed: If CN is not set to localhost when configuring SS mutual certificates, "java.security.cert.CertificateException: No name matching localhost found" occurs during runtime of the wsimport tool (provided by the JEUS web service) and a client.

The context map about cluster contexts created in each thread is shared. When attempting to use a closed context, NPE occurs.

Fixed: ClassNotFoundException occurs because the ClassLoader that loads the custom class defined in an application differs from ContextClassLoader of the thread that executes onMessage() of MessageListener.

Fixed: Deadlock occurs when the process of closing JeusPooledConnection and the process of deleting JeusPooledConnection of JeusPooledConnectionFactory require a lock currently being used in the other process.