JEUS 9.1
This chapter briefly describes the new features added to JEUS 9.1.
1. New Features
1.1. Server
-
Added Node Manager feature
-
The previously used Host Manager has been removed and replaced with a more stable Node Manager.
-
-
Added support for Node Manager monitoring management when a managed server is started alone
-
Node Manager monitoring management is enabled when the jeus.server.nodemanager.monitoring-standalone-ms property is set to true, or when the -monNM option is added at startup.
-
-
Added CloudServer feature
-
Added the startCloudServer script and related functionality.
-
-
Added start-node and stop-node features
-
Added a jeusadmin command that allows starting and stopping the server on a node-by-node basis.
-
1.2. Servlet
-
Added a feature to reconnect after a specified interval in the TCP layer
-
Added the jeus.servlet.wjpReconnectTime option (Default: 150 ms)
-
1.3. Session Server
-
Refactored JEUS centralized session server
-
Added the ability to configure primary-backup relationship.
-
Added support for multiple backup servers to enable 1:N configurations.
-
Modified the startup process so that a server can recognize itself as a central session server based on its server configuration.
-
Modified session storage to allow specifying a group for each storage, enabling grouping of central session servers configured in a primary–backup relationship.
-
Added a jeusadmin command to configure the JEUS central session server.
-
Added a jeusadmin command to monitor the JEUS central session server.
-
-
Added Redis Sentinel
-
Added Redis Sentinel support.
-
1.4. IO
-
Added client IP blocking feature
-
Added the ability to block client IPs after a certain number of failed JMX login attempts.
-
1.5. WebAdmin
-
Enhanced WebAdmin
-
Applied a new UI.
-
WebAdmin is supported only in JDK 17 and JDK 21 environments.
-
-
Added centralized session server monitoring in JEUS
-
Added a feature to monitor the JEUS central session server through WebAdmin.
-
-
Added Edit Mode (Lock&Edit)
-
Added the ability for administrators to lock settings and edit safely.
-
-
Added Auto Lock
-
Added the ability to automatically save changes after configuration is modified across all menus.
-
-
Added feature to display modified items when server restart is required
-
Added a feature to display modified items on hover when the server’s the 'Need to Restart' item is marked as 'true'.
-
-
Added monitoring connection pool refresh feature
-
Added the ability to update the current connection pool status to the latest by setting a time.
-
-
Added Webtob Connector replication feature
-
Added a feature to clone a previously created Webtob Connector.
-
-
Added History feature to view setting change history
-
Added the ability to check for changes.
-
Added the ability to restore settings to a specific point in time.
-
Added the ability to apply settings by directly uploading a domain file (XML).
-
Added the ability to download settings files from the history.
-
Added a filtering function to search within the change history.
-
-
Added search functionality for Nodes, Clusters, Servers, Apps, and Resources
-
Added the ability to search for components using filters in the Nodes, Clusters, Servers, Apps, and Resources tabs.
-
1.6. JDBC
-
Added ability to use databaseName as serviceName
-
Added the jeus.jdbc.config.database-name-as-service-name option. (Default: false)
-
Added the jeus.jdbc.config.exclude.database-name-as-service-name option. (Default: " " [empty string])
-
2. Changed Features
2.1. Session Server
-
JEUS Session Manager Name Change
-
The settings that previously divided the session types under the JEUS session manager into distributed and centralized have been changed to distributed session manager (DISTRIBUTED) and centralized session manager (CENTRAL).
-
2.2. Security
-
Changed to require confirmation of the current password when changing a user password
-
To enhance security when changing a user’s password, the existing password is now verified before being changed.
-
2.3. Server
-
Changed JEUS version format
-
The version format has been changed to major.minor.fix.patch build-number.
-
-
Changed to display a notification message when deleting a user account
-
When deleting a user account, a confirmation message is now shown to prevent accidental deletion, and the account is deleted only after user approval.
-
3. Bug Fixes
3.1. Deployment
-
Fixed issue where classes were not found when checking handle type in applications using a Multi-Release JAR
-
Resolved an issue of not finding a class when checking the handle type in an application with a Multi-Release jar.
-
3.2. JMS
-
Fixed issue where messages were not received when reconnecting consumers with remaining messages
-
Resolved an issue where messages were not received upon reconnection after closing a consumer if unprocessed messages still remained.
-
-
Fixed issue where JMS message order was not guaranteed during restoration
-
Resolved an issue where the order of JMS messages was not preserved when recovering after a server restart.
-
3.3. Server
-
Fixed abnormal behavior when the Valid Size option exceeded 3 GB
-
Resolved an issue where log file rotation behaved abnormally when the Valid-Size option exceeded 3 GB.
-
3.4. Servlet
-
Fixed issue where an IllegalArgumentException occurred when the first letter of the domain attribute was a number
-
Resolved IllegalArgumentException that occurred when the first character in the domain attribute of a session cookie was numeric.
-
-
Fixed issue where headers disappeared when sendError was called after response.addHeader in service
-
Resolved an issue where headers were lost when sendError was called after response.addHeader in service.
-
-
Fixed issue where overlapping sections were not properly handled with multiple ranges
-
Resolved an issue where overlapping sections were not handled properly when there were multiple ranges.
-
-
Fixed issue where data messages were not processed when the server did not have a handler for client pong messages
-
Resolved an issue where, if the client endpoint sent a pong message and the server endpoint did not have a handler for it, subsequent data messages were not processed properly.
-
-
Fixed issue where sessions were lost due to deserialization failure when displaying the Access Log
-
Resolved an issue where sessions were lost due to a deserialization failure when retrieving a session during the process of displaying the Access Log.
-
-
Modified to apply the default content type without calling getWriter or characterEncoding related APIs
-
The default content type is now applied without calling the response’s getWriter and characterEncoding related APIs.
-
-
Fixed issue where a WebSocket connection was not established immediately after restarting WebtoB
-
Resolved an issue where a WebSocket connection failed when attempting to send a message immediately after restarting WebtoB.
-
-
Fixed issue where samesite was not applied when cookie was version 1
-
Resolved an issue where samesite was not applied when the cookie was version 1.
-
-
Fixed issue where the WebtoB connection state remained in "reconnecting" when an async servlet was not dispatched
-
Resolved an issue where the WebtoB connection state remained in the "reconnecting" status when an async servlet was not dispatched.
-
-
Modified to raise exception in accordance with the Servlet API specification
-
Modified behavior to raise an appropriate exceptions in accordance with the Servlet API specification.
-