CDI spec specifies that CDI 1.1 must provide a function to disable the scanning of implicit bean archives for compatibility with CDI 1.0.

jeus.cdi.enable-implicit-bean-archive can be configured with system properties. (Default: true)

An option to view associated cloud servers.

list-corelated-servers is available in jeusadmin.

Service Provider Interface(SPI) provided to use Virtual Multicast in a cloud environment.

The followings are supported providers.

To perform session backups more reliably in a cloud environment, backup tables need to be managed in another node (machine). Kubernetes offers the APIs to view the node that pods run on.

Option to enable the cloud server mode in a cloud environment. A cloud license is required to run cloud servers.

The features of cloud server only take effect with a cloud license.

When deploying applications, the target can be server list, cluster list, or all servers.

DAS is excluded from application deployment service. A function is added to exclude DAS from application deployment by using the system property 'jeus.deploy.exclude.das'. (Default : false)

When upgrading applications by using install-application, deploy-application, or redeploy-application command, the short option name '-u' can be entered instead of -upgrade option.

Function to install a server as silent mode. (only applicable to Linux)

Function to enter administrator ID, DAS Name, and DAS port

The config-listener-ssl command is added to configure SSL for listeners in jeusadmin.

Function to receive a notification for JDBC connection leakage if Action On Resource Leak is set to Warning or AutoClose.

In JEUS 6 Fix#8 and earlier versions, backup component data sources are maintained after the primary server is failed back to service. In this release, a function has been added to remove the backup component data sources that remain idle.

Function to forcibly close and return a connection in case of DB connection leakage.

Active Average and Active Max available with connection-pool-info through jeusadmin.

When a DB user account is changed while using a connection pool, the server closes the current DB connection to reconnect.

When this situation often occurs, a user should increase the size of the connection pool and distribute idle connections across DB accounts. However, in previous versions, users cannot figure out the situation because getConnection attempts of an altered DB user were not recorded as logs.

In this release, logs are displayed as shown below to understand the situation.

[CPOOL-0025] There is no idle connection for user [user1] in the connection pool [tibero_pool1].
 A new connection was made for user [user1] whereas a single connection for user [user2] has been destroyed." 

-algorithm available with modify-data-source in jeusadmin.

The following algorithms are applicable.

Function to forcibly disconnect or return a connection when DB connection leakage occurs.

A user must specify the name of the server using a connection. Use -cid(connection id) or -cpid(connection pool id) to specify a connection or connection pool to return or destroy.

In previous versions, test-data-source-confi is only available in jeusadmin of DAS. In this release, test-data-source-confi can be executed on MSs. This function makes it possible to connect to a data source when DAS has been shut down.

Added command to verify whether the data sources in each server are available to connect.

Use of - all option to verify whether the data sources in all servers are available to connect.

function to publish topic messages by using UDP multicast.

When there is a request from DAS such as start of multiple MSs, the read timeout may occur from DAS such as insufficient thread pools. maxPoolSize has been added to prevent this problem.

Specify the system property 'jeus.nm.listener.maxPoolSize' for the startup script of startNodeManager.

Function to display running Java processes and its PIDs

Set jeus.nodemanager.log.level to 'FINEST' in the startNodeManager script.

Function to use -graceful and -shutdownTimeout to shut down a server with jant.

Add the following configuration in build.xml.

<property name="shutdownTmeout" value="3"/>
<property name="graceful" value="true"/> 
<down 
    domainName="${domain.name}"
    serverName="${server.name}"
    host="${host}"
    port="${port}"
    username="${username}"
    password="${password}"
    shutdownTimeout="${shutdownTimeout}"
    graceful="${graceful}"
/>

Config-system-clustering-framework and show-system-clustering-framework have been added to edit 'System Clustering Framework'.

Option to specify security.key for the encryption command. Security.key can be specified by using a node manager (-nm) instead of a domain or directly entering security.key file path.

The -algolist option is used with encryption command to view available encryption algorithms.

Expire-user and unexpire-user are available in jeusadmin.

- s option is added to display encrypted passwords only.

Function to lock an account after consecutive failed login attempts.

On the Subject Validation page of WebAdmin, set 'Default Subject Validation Service' to true or add jeus.security.subject.validation.maxattempts to jeus.properteis.

Not applicable for the accounts that belong to the group of administrators.

SHA-256 and SHA-512 have been added to encryption algorithms.

In previous versions, a user can only change the password for his/her own account in jeusadmin. In this release, an encryption algorithm can also be changed along with the password.

set-password user1 {password} -algorithm {algorithm}

Function has been added to configure a permission on a log file by using a file handler.

Function has been added to back up a domain in a desired node by using -node with pack-domain.

Function has been added to enable caching for logins by using -cachelogin when shutting down a server by stopSerer

In previous versions, if an application is not deployed successfully to the server that has been started in Standby state, the state has to be changed to Running with start-server.

Function has been added to restart a server to allow deployment if the server has been started in Standby state.

Function has been added to suspend the start of a server when overlapping occurs in the patch file.

Function has been added to wait for certain amount of time instead of immediately throwing an exception after having failed locking on data for dynamic configuration changes.

Option has been added to determine whether to keep a server in Running state at its startup in case that an error occurs while invoking lifecycle.

Configure the jeus.server.invocation.keepBootOnError property.

Function has been added to use -graceful and -shutdownTimout when executing stopServer in jeusadmin or Node Manager to shut down a server.

The spring-support library has been added to JEUS_HOME/lib/shared/spring-support.

Function has been added to configure -ver, -wbhome, and -ipcport with modify-webtob-onnector .

wjp-version has been added to show-web-engine-configuration.

Websocket upgrade handler is provided as a shared library in lib/shared/spring-support/.

Register handshakeHandler in the Spring configuration file as shown below.

<websocket:handlers>
<websocket:handshake-handler ref="handshakeHandler"/>
</websocket:handlers><bean id="handshakeHandler" class="jeus.spring.websocket.JeusHandshakeHandler"/>

Spring 4.0.0 supporting library has been added.

Function has been added to write ServletOutputStream dump to the responses of WebtoB connector.

jeus.servlet.engine.response logs are set to be FINEST.

With scale-in processing of virtual servers in a cloud computing environment, upgrade function has been added to reliably manage sessions on server shutdown. This function move a backup session to the primary node to maintain the connection.

Add jeus.sessionmanager.cluster.failover.strategy=upgrade as a session property.

In JEUS 8, an option was added to configure session manager providers in domain scope that had been configured at JVM level in earlier versions. However, InfiniCache and various other systems still require JVM settings to use different providers for each JVM. In this release, the jvm-option has been added to avoid this issue.

Configure jeus.servlet.sessionmanager.provider property.

Function has been added to configure -f option in offline jeusadmin to use environment variables.

offline>connect -u administrator -p 1111111 -cachelogin -f $JEUS_HOME/bin -domain jeus8

A listener ID is specified with -li option to view the ti information in jeusadmin. A function has been added to use asterisk(*) in the listener ID to display the listeners matching the specified character.

ti -li webtob*

A dirty select is available on applications that use IIOP.

In previous versions, an application cannot select the data inserted by another application if it has not been committed. A dirty select allows to view the data even if it has not yet been committed.

Pack-domain is available in WebAdmin.

Function has been added to select all the data sources of 'Component Data Sources' in the Cluster DS page at once. In previous versions, only one data source is selected at a time.

Function has been added to select all the data sources of 'Data Source' in [Basic Info] at once. In previous versions, only one data source is selected at a time.

License information is displayed at the top of the page in WebAdmin.

The following commands are no longer available from jeusadmin if a cloud server is running.

add-application-target
add-cluster
add-custom-resource-to-clusters
add-data-sources-to-cluster
add-dynamic-servers
add-external-resource-to-clusters
add-server
add-servers-to-cluster
add-server-template
disable-to-resynchronize-applications
enable-to-resynchronize-applications
list-clusters
modify-cluster
modify-dynamic-servers
remove-application-target
remove-cluster
remove-custom-resource-from-clusters
remove-data-sources-from-cluster
remove-external-resource-from-clusters 
remove-server
remove-servers-to-cluster
show-dynamic-servers
show-server-template
start-cluster
start-domain
start-server
stop-cluster
stop-domain
stop-server

-cluster and -clusters have been removed from jeusadmin as they are not available on a cloud server.

In this release, users are not allowed access any option that is not available on a cloud server if a cloud server is running.

Only specified file extensions can be used to install an application with install-application through jeusadmin. The applicable extensions are WAR, JAR, EAR and RAR.

JAR files and classes are scanned for deploying EAR files. A function has been added to only scan the modules specified in applicaton.xml if the file exists.

The version of the embedded WebtoB has been changed to WebtoB 5 SP0 Fix#2.

Encryption method has been changed from BASE64 to ASE to enhance the security.

The following criteria are used for the validity.

File and directory permissions have been changed to 700 when installing on Unix systems.

Changed time for the port binding of the listeners other than base listener. In this release, to make engines get ready to service at the same time as port binding occurs, port binding is enabled only after the start of all engines.

Before a user deploys an application, the application is checked to see whether it contains batch jobs. If the application contains many archive files, which can be time consuming, the following files are checked to use batch jobs.

META-INF/batch.xml
WEB-INF/classes/META-INF/batch.xml
META-INF/batch-jobs/*.xml
WEB-INF/classes/META-INF/batch-jobs/*.xml

This function is only supported in Connection Pool DataSource in previous versions, and is now available in XA DataSource.

In previous versions, it is inconvenient to change database account information because MS has to be restarted. Associated connection pools are refreshed after the changes are made on the data source configuration.

Failed server list contains a list of failed servers. A server is removed from the failed server list when it is removed from the cluster.

Default configuration values in jeusnm.xml has been changed.

.jeuspasswd file for cache logins has been changed as follows.

domain_name:ID encode(ID:PW)

Usage

The location of the security.key file used for cache logins has been changed to JEUS_HOME/bin.

The usage of the -cachelogin option becomes consistent across startup/shutdown commands.

When shutting down a cluster that contains DAS, DAS is excluded from the shutdown process and remain in Running state.

In this release, a user cannot delete the domain of a server by using delete-domain if the server is currently being connected.

Backup files are created for a domain by using set-domain-backup or pack-domain. The default path to the backup files has been changed from JEUS_HOME/bin to ${JEUS_HOME}/backups.

Default value '127.0.0.1:9736' has been added for the host option to execute 'stopServer'. This function allows to execute 'stopServer' without specifying the host option.

The use-nio setting was removed from JEUS 8, and is fixed to operate as true.

The max-keep-alive-request setting has been removed as it is only applicable when the use-nio setting is set to false.

The max-post-size setting issues "413 Request Entity Too Large response" if the request body size exceeds its maximum size limit.

In this release, the response body is read in chunks. If the content length is known, then a body size of specified size is used to read the response body, issuing the 413 error.

When there is no included JSP file, a 500 error code will occur instead of 404. All page errors are considered as a code error.

In previous versions, backups are performed regardless of the backup level, which could degrade performance during the backup. This function has been changed to back up to the server specified in the backup level. Therefore, a backup can be performed based on the user-specified values.

Session searches have been changed into asynchronous operating mode.

In a distributed session servers environment, it is necessary to search for a session from all servers. In previous versions, session searches are performed in a synchronously way by connecting to all the servers sequentially. This may cause a severe performance degradation in an environment in which multiple MSs exist. Therefore, session search operation has been changed from synchronous mode to the asynchronous mode to send a query to the servers at once.

Localhost is used as a default value for using the connect command in jeusadmin. A user don't need to specify a host.

Patch information is not displayed when executing a tool such as jeusadmin.

To display the patch information, edit the 'jeus.properties' file to set the 'jeus.tool.console.patchinfo' system property value in TOOL_OPTION to true.

In previous versions, the -f option is used to set dir-path. However, in general, '-f ' means 'force'. This option has been replaced by the -p option.

Function to filter uploading of a file with disallowed extensions in WebAdmin.

In previous versions, users of the Monitoring role cannot access the [Start], [Stop], [Resume], [Suspend], and [GC] buttons of the [Servers] page without the Config role.

For users with the Monitoring role only, the Resource Manager, Basic Domain Information, Web Console, and Monitoring menus will become invisible if they don't have a permission.

Redeployment failed if an application using CDI in a Windows environment contained a JAR file in WEB-INF/lib. This bug has been fixed.

The CDI specification defines that it is required to scan only empty archives under the application class path.

In this release, the changed operation only scans the libraries under WEB-INF/classes and WEB-INF/lib, and those being referenced in other ways.

It does not implement unnecessary scans of the files or resources that reside outside WEB-INF, in particular the classes or libraries not being reference.

Fixed a bug where JEUS version in an application DD file would not change when using the upgrade option with install-application, deploy-application, or redeploy-application command.

RuntimeException while attempting to read an XML file for deployment. Fixed a bug where the path information would not be provided.

Fixed a bug where a library deployed to JEUS server through Library Deployment would fail to be added to the class path for JSP compilation.

When an application is deployed a directory, the deployment is succeeded without having a permission on the directory.

At the first deployment attempt, the user is ensured to have a permission on the directory. However, the following application deployments are proceeded without checking the required permissions on the directory.

A permission is checked for the first deployment attempt. However, after the deployment succeeds, the permission is not checked for the following deployment attempts even if the permission is changed even

Unable to update an application with the changes to archive modules (JAR, WAR, and so on) in the directory of EAR after the server's reboot. This bug has been fixed.

Fixed a bug where EJB clustering would be performed with a node that was shut down abnormally. This problem occurred because that failed node remained until the entire cluster was rebooted.

After a user removes the information of a node that has been removed from the cluster during EJB clustering, UnknownHostException may occur if the node information still remains in the DLR link. A failover operation did not implement for UnknownHostException. This bug has been fixed.

Fixed a bug where EJB clustering would be performed with a node that was shut down abnormally. This problem occurred because that failed node remained until the entire cluster was rebooted.

During a dynamic configuration change, DLR dynamically checks its links and removes any server are not currently present in the cluster.

Fixed to register events in Selector even after an exception occurs on the selector thread.

Fixed an unclear error message when deploying an EJBs that use IIOP and enable-interop element set to false.

serialversionUID has been defined in the classes relating to getEJBMetaData, getHomeHandle, and getHandle API, subject to RMI/IOP rules.

Fixed a bug where sender id, sender password, and property could not be specified in the Email Notify configuration.

Unable to restart an EJB engine properly when the number of blocked threads exceed the value specified in the schema. For this reason, a restart warning message has been added.

Fixed wrong statistical values for block threads.

Fixed a bug in which beans are not removed immediately from the EJB cache if the stateful-timeout and @StatefulTimeout annotation elements are set to 0 in ejb-jar.xml as defined in EJB 3.x specification.

The same changes are applied to the disconnect-timeout value in jeus-ejb-dd.xml, which functions the same as stateful-timeout.

Unable to initialize SSLConext when there are more than one Key Alias in the KeyStore. This bug has been fixed.

Fixed a bug where Automated Transaction Recovery didn't perform well.

Fixed a bug where listener would not be released after changing the setting to false.

Unused connections were created in a data source after failback in an RAC environment. This bug has been fixed.

When a user changed cluster data source setting dynamically in the state that connection pool is unavailable, 'Need to Restart' in serer-info was set to true and a message requiring to restart the server was displayed. This bug has been fixed.

Fixed a bug where a failback operation would perform even if 'Use Failback' in Cluster DataSource was set to false.

If a logical connection is lost from the server in the overloaded state, the server will check the status of the connection. Fixed a bug where the physical connection would be lost due to timing problems with status check.

WaitTimeoutException occurred after a getConnection failure even if there as an idle connection under overloads. This bug has been fixed.

Ensures the synchronization by checking whether a thread is eligible to get a connection.

Fixed a bug in which a transaction rollback would be sent to DLQ.

Tibero 5 and later versions implement the changed way of getting Max Chunk Size from JDBC driver. This has been applied to JEUS.

Unable to consume messages from topics during Topic clustering. This bug has been fixed.

Unable to send messages to the temporary destination specified when creating a producer. A message was successfully routed to the client in the temporary destination, but failed to return due to incorrect connection id set in the destination's routing information. This bug has been fixed.

Fixed a bug where NPE(NullPointerException) would occur when an invalid value was set for Message Bridge.

Even after OnMessage closed the consumer, the amount of messages were left the same due to the recovered messages. This bug has been fixed.

Fixed a bug where messages would not be received if Durable Subscription Message Store was set to JDBC.

Fixed a bug where only one client ID would be displayed when monitoring the client IDs with the same durable subscriber name.

Now, durable subscriptions are now ordered by DurableName. Client ID is used to identify the durable subscriptions with the same DurableName.

The servers in a cluster send and receive messages based on Global Order Message. This information could be lost during message transmission.

Now, messages are distributed to all servers in a cluster first, and then sequentially processed according to specified Global Order Message.

Fixed a bug where one more client was connected than the specified client limit.

Fixed a bug where the server would fail to process an XA transaction message if the message was prepared or committed without an XA end request.

Fixed a bug where ClassNotFoundException would occur if failing to find the classes of the ClassNotFoundException package when XA mode was enabled.

The information of server's failover is shared across other live servers. Due to this information, a previously failed server skipped the recovery operation when it has failed again. This bug has been fixed.

Unable to operate topic with dynamic clusters. This bug has been fixed.

Fixed a bug where NullPointerException would occur when a server was restarted by setting up a virtual listener for the service group.

Unable to asynchronously consume the messages produced from clustered queue after it is restarted. Fixed a bug where onMessage() was not called after the recovery.

Unable to perform failover, switchover and recovery operations successfully when the server is shut down abnormally. Fixed a bug where jeus.net.ping.enable, jeus.net.ping.period, and jeus.net.ping.timeout settings were not applied in the JMS engine in order to resolve this problem.

Fixed a bug where all patches would be located in the jext directory when executing the apply-patch command. The jext/jnext/jlext patches must be generated to the relevant directories.

Fixed a bug where the nodas option would not work properly by executing apply-patch or remove-patch.

Unable to start up NodeManager as a server if the ID and password of the server are encrypted with AES. This bug has been fixed.

Saved the backup data in the wrong directory when performing a domain-level backup because the various file delimiters are used across the various operating systems. This bug has been fixed.

Fixed a bug where permissions would take a long time when deploying an application that includes a large volume of EJBs.

When adding a new algorithm to the security.key file, it was overwritten rather than being added. This bug has been fixed.

javax.security.auth.login.Configuration.getAppConfigurationEntry() is called with the name information as a parameter. Fixed a bug where an exception would be thrown instead of null if name was not given in LoginModule information.

Fixed a bug where the 'Need to Restart' status would be changed to true when adding a server to a cluster on WebAdmin.

An object name was displayed for properties of the add-external-resource, add-custom-resource, modify-external-resource, and modify-custom-resource commands. Now, properties value is displayed.

Fixed a bug where cachelogin would not operate properly when executing connect -cachelogin on jeusadmin in offline.

Fixed a bug where wrong error message would be received due to incorrect SMTP handler configuration.

Unable to specify a subject properly in thread state notify when sending email with SMTP handler. This bug has been fixed.

Fixed a bug where a server would not start up when a password in SMTP handler was encrypted.

Fixed a bug where a handler would not be added to the logger if 'Send for All Messages' configuration was not set.

Unable to use the f option and domain option to run cachelogin with the stopServer command. This bug has been fixed.

Fixed a bug where an incorrect file would be created when RotationDir was set to absolute-path.

Fixed a bug where existing file would be overwritten if Log Rotation failed.

Fixed a bug where an NPE(NullPointerException) would occur when the remove custom resource was executed.

Fixed a bug where jarscan.properties file would not be removed when DAS/MS used different file separators to communicate across Windows/ and Unix.

Fixed a bug where launcher logs would not be saved when DAS was started without domain and server options.

Unable to dynamically specify lifecycle-invocation in Cluster settings. This bug has been fixed.

Fixed a bug where an SO file would not be applied due to LD_LIBRARY_PATH setting.

When creating a domain with create-domain and delete-domain, special characters were used to set the name of the domain. Now a domain name cannot include special characters.

When a SecurityException occurred after calling LogManager.reset(), the call was intercepted through JeusLogManager.reset(). This bug has been fixed.

Fixed a bug where graceful and shutdowntimeout would not work when shutting down a server from jeusadmin or a node manager.

Fixed a bug where OverlappingFileLockException occurred while multiple MSs attempting to get a lock on domain.xml files sent from DAS.

Fixed a bug where the formatter-class settings would not operate when it was set to jeus.util.logging.SimpleMillisFormatter.

Fixed a bug where a thread hang occurred during the log rotation of FileHandler.

Fixed a bug where NoSuchMethodException would occur when the smtp-handler setting was dynamically changed.

Fixed a bug where a patch file would not be sent if the file name was not set when executing the apply-patch command.

When deploying a Web module, Annotation(@) scanning is performed to check whether an EJB exists.

Fixed a bug where certain functions of a reverse proxy would still work even after undeploying applications configured with reverse proxy.

Fixed a bug where error-page didn't work after configuring a reverse proxy.

Fixed a bug where reverse proxy-enabled cluster didn't work.

Fixed a bug where a Korean character was broken in the reverse proxy configuration.

Fixed a bug where a request for HTTPS was redirected to HTTP.

Fixed a bug where a file was not downloaded from a reverse proxy.

Fixed a bug where the jsp-config settings in web.xml would not operate when executing the appcompiler.

OOM (Out Of Memory) occurred when calling a TCP application through HTTP URL. Now, when a request exceeds the specified Max Post Size of the TCP Listener, the call is logged and closed.

Fixed a bug where a delay or IllegalSateException would occur when the status of the WebSocket sessions were not normally managed.

Fixed to sequentially process requests without removing OP_READ.

Fixed a bug where the asyncSupported=true would setting not operate when using a Filter in AsyncServlet.

Fixed the -tidle option of modify-web-listener.

Fixed a bug where the max-idle-time settings were not changed according to -tidle.

Fixed the description of the add-web-listener option.

Fixed the description for the - tmin Tmax settings and the options of ajp and tcp listeners.

Fixed a bug where postdata-read-timeout didn't work.

Fixed a bug where a filter would be registered in the wrong order when it was added using the addMappingForUrlPatterns method. This was the case that the specification of the isMatchAfter parameter was interpreted incorrectly.

When configuring 7 http-methods under web-resource-collection in web.xml, the methods that were called after 7th didn't work.

Fixed a bug where a request would not be processed if the response from ajp-listener exceeded 8KB.

JDK is declared to use reflection APIs when EL invokes a call. An exception would be thrown if the class modifier was not declared public. The classes for EL has been declared public.

Fixed a bug where OOM (Out Of Memory) would occur due to infinite loop if a TLD file name to search had a backslash (\).

Unable to flush the buffer if an exception occurred while processing the headers and body. In this case, it is possible to receive out-of-order responses.

'sessionid' is set to the path parameter when using encodoingURL(). Fixed a bug where the changes to the default setting of jsessoind-name were not applied.

Fixed a bug where ClassNotFoundException didn't occur at JSP compilation when a tag file was used in multiple JSPs.

Different WASs interpret the servlet spec differently. Fixed a bug where the result values of javax.servlet.forward.request_uri were incompatible with other WASs.

Fixed a bug where a connection between ajp listener and JEUS failed.

Fixed a bug where the body was not processed for a HTTP POST request.

Fixed a bug where modify-tmax-connector didn't work in jeusadmin.

Fixed a bug where graceful-jsp-reloading didn't work due to invalid reloading interval operations.

When different WJP protocols are used in WebtoB and JEUS, unknown attributes will be ignored.

An exception occurred while attempting to close JAR files passed through a URL defined in Spring's ContextLoader. This function has been modified not to close external JARs.

Fixed a bug where IllegaArgumentException would occur when entering only % in QueryString.

Unable to perform deployment because validation failed even if the <url-pattern> settings in <security-constraint> of web.xml were valid. This bug has been fixed.

When the Web container expires a session, sessionDestroyed() is called on the registered HttpSessionListener. In this case, a classloader other than the classloader to which the listener belongs was acquired. This bug has been fixed.

Fixed a bug where the values not specified in web.xml would be displayed when retrieving parameters using ServletContext.getInitParameterNames().

Fixed a bug where remove-session only removed active sessions but not backup sessions.

Fixed a bug where backup-server status would become null when deploying EJB applications and Web applications simultaneously at boot.

HttpSessionBindingListener.valueUnBound() can be invoked when a session is removed. Fixed a bug where 'Removed session' log would be displayed when implementing session. invalidate() in this method. In this release, session. invalidate() is not called twice in succession.

Fixed a bug where a session would be maintained even after calling invalidate() if a session server was specified not to perform migration.

In this release, session information is saved in the primary server so that the information can be used to perform UPDATE and REMOVE operations.

Unable to perform backup when setting attributes in Korean to enable duplicate login prevention. This bug has been fixed.

OOM (Out Of Memory) occurred when executing the same command many times with the repeat option in jeusadmin. The implementation of the repeat option has been changed not to generate OOM.

Unable to remove the backupDir and nodeName settings. Now, when 'unset' is set as the value of each option, the default value is used.

Added validation for the node option.

Changed results message for the success/failure of the node option.

Unpack-domain requires the listen address, port, and node name settings of DAS. Fixed a bug where these settings were applied to domain.xml but not nodes.xml.

Fixed a bug where jeusadmin onestep command didn't work with verbose option in jeusadmin.

When JEUS propagated global transactions using Internet Inter-ORB Protocol (IIOP), transaction IDs would become split due to the prefixes appended to the global transaction IDs. The prefixes have been removed to fix this problem.

EJB clients use EJB homes and objects, and the EJB homes reuse an EJB home object.

When an EJB client was reused that has the transaction information of SubCoordinator, the transaction was forcibly cast to RootCoorinator causing a ClassCastException. This bug has been fixed by adding defensive code.

When an EJB is called from a client application, SubCoordinate is created. If that EJB is needed again and recalled by another EJB, the pre-created SubCoordinator is to be reused.

In this case, SubCoordinator can only operate upon the response from RootCoordiantor. Thus, a SubCoordinator would cause TMException after waiting for two minutes if RootCoordiantor had not received any request regarding the registration of the SubCoordinator.

Now, when SubCoordinator is first created for transaction propagation, the RootCoordinator changes the status value assuming that the SubCoordinator has been already registered before propagating the transaction. In this way, SubCoordinator does not need to wait for confirmation from the RootCoordinator.

When a client running on the different platform sent a request to two JEUSs through an IIOP call, if the DB operation succeeded in one JEUS server but failed on the other JEUS server with timeout issue, the IIOP timeout would occur on the client, causing a rollback and violating data integrity. Fixed a bug where data integrity would be violated when trying to acquire a lock to execute getConnection, rollback, and queries.

RootCoordinator had correct TM information for SubCoordinator, but an endpoint socket ID of the transaction associated with SubCoordinator had TM information of the SubCoordiator that had already terminated.

Fixed a bug where performance problems would occur due to gradually increased memory usage when calling an EJB using CORBA IIOP.

Entering single quotation mark(' ') or double quotation mark(" ") caused an error because the characters was changed into &$#39;. This bug has been fixed.

Fixed a bug where a user would be moved to an error page, instead of the details page when an ID includes a slash (/).

Fixed a bug where FileHandler was not created for the log created in System logging.

Fixed a bug where an error would occur when adding ajp13, http, and tcp for WebtoB or Tmax with no 'server luistener ref' settings.

When deploying applications to virtualhosts configured for each MS, the first deployment would complete successfully. However, the applications specified with remove-target and add-target could not be deployed successfully. This bug has been fixed.

Added validation for the MinLength and MaxLength items of password validator.