Known Issues

In Agent Ver.1.1.0 or earlier, the ReasonCode [CLOSED_ABNORMALLY] may appear in the output log of Agent when the session between HULFT-WebConnect and Agent was disconnected.

Even if the file transfer ends successfully, the following ReasonCode [CLOSED_ABNORMALLY] may appear in the output log of Agent when the session between HULFT-WebConnect and Agent was disconnected.

2015-07-03 10:00:00,123 AGENTID[example] INFO jp.co.saison.sis.hulft.tsubomi.agent.receiver.ReceiverEndpoint - I120021 - The transfer session was disconnected. SessionID:[c02d1b65-dc9f-41c9-b3e1-89f53ea68205], ReasonCode:[CLOSED_ABNORMALLY], Message:[Closed abnormally.] (ReceiverEndpoint.java:106)

In the case of Windows, an error of Java may appear in the output log of Agent.

When you start Agent or transfer a file in Windows, an error of Java may appear in the output log of Agent even if the file transfer ends successfully.

Example: When the error of Java is 'Can not set SO_KEEPALIVE to true'

Jun 19, 2016 7:45:21 PM org.glassfish.grizzly.nio.transport.TCPNIOTransport configureChannel
WARNING: GRIZZLY0005: Can not set SO_KEEPALIVE to true
java.net.SocketException: Invalid argument: no further information
    at sun.nio.ch.Net.setIntOption0(Native Method)
    at sun.nio.ch.Net.setSocketOption(Net.java:334)
    at sun.nio.ch.SocketChannelImpl.setOption(SocketChannelImpl.java:190)
    at sun.nio.ch.SocketAdaptor.setBooleanOption(SocketAdaptor.java:271)
    at sun.nio.ch.SocketAdaptor.setKeepAlive(SocketAdaptor.java:370)
    at org.glassfish.grizzly.nio.transport.TCPNIOTransport.configureChannel(TCPNIOTransport.java:439)
    at org.glassfish.grizzly.nio.transport.TCPNIOConnectorHandler.onConnectedAsync(TCPNIOConnectorHandler.java:214)
    at org.glassfish.grizzly.nio.transport.TCPNIOConnectorHandler$1.connected(TCPNIOConnectorHandler.java:154)
    at org.glassfish.grizzly.nio.transport.TCPNIOConnection.onConnect(TCPNIOConnection.java:258)
    at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:552)
    at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:117)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.executeIoEvent(WorkerThreadIOStrategy.java:103)
    at org.glassfish.grizzly.strategies.AbstractIOStrategy.executeIoEvent(AbstractIOStrategy.java:89)
    at org.glassfish.grizzly.nio.SelectorRunner.iterateKeyEvents(SelectorRunner.java:414)
    at org.glassfish.grizzly.nio.SelectorRunner.iterateKeys(SelectorRunner.java:383)
    at org.glassfish.grizzly.nio.SelectorRunner.doSelect(SelectorRunner.java:347)
    at org.glassfish.grizzly.nio.SelectorRunner.run(SelectorRunner.java:278)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:565)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:545)
    at java.lang.Thread.run(Thread.java:745)

In Agent Ver.2.3.1 or earlier, even if the log rotation is set in the log configuration file, the log rotation may not be performed or may fail.

Even if the log rotation is set in the log configuration file (logback.xml), Agent behaves as follows and the log rotation may not be performed or may fail.

When the log rotation is performed, the file with the extension '.tmp' might be generated.

In the generated files, the differences between the other files that performed the log rotation are recorded.

Save or delete the generated file as needed.

= Remarks =

In the case of Windows, the log rotation is not performed while Agent is running.

The log rotation is completed successfully when Agent is restarted, so if the log rotation is required, we recommend restarting Agent regularly.

Also, the default setting for the log rotation is daily.

In Agent Ver.2.0.0, when you confirm whether a new Agent update is available, an incorrect check result may be output.

When you confirm whether a new Agent update is available, the version of Agent in use is considered as the latest and the incorrect check result is output to the console screen and the log file.

If communication speed is slow, restarting Agent may resolve the problem.