Updates 48000 » History » Version 4
Version 3 (Pierre Marc, 07/26/2013 04:55 PM) → Version 4/9 (Pierre Marc, 06/05/2015 12:38 PM)
h1. 4.8.000 4.7.009 Updates
h2. Bugs
* The date/time format for the http file cache were not set correctly. This could make some web files not accessible in servers with a local not in english.
* The output buffer was truncated if its content is longer than 256 byte in java procedures.
* The unicode option In case of crash the comand line was not working (-u option).
* The machine and local user name were not encoded correctly. This was producing a bad password error if the machine name was not ascii.
* The encoding of line feeds was not made between client and server for the session_open and session_close parameters. This could break the procedure parameters if there were some.
* There was an error in xslt transform for input xml message when the body was greater than the limit (parameter) for memory messages (1024Kb by default).
* The state of the web services operation was not kept after updating (re-install).
* The service renderer content type was not working.
* The application containers were not cleared after a failed application start.
* Renderer compilation was not working on linux.
* Log for web services was not working (nothing logged).
* The success procedure for scheduled tasks were not correctly implemented (procedure not running).
* The file origin was not transmitted from client log table may be corrupted so it becomes impossible to server in analyze the OBJECT:SEND command.
* The double spaces crash in the MISC:EXEC command were replaced by a single space.
* The MAIL:SEND command was not throwing any error in case of error.
h2. Modifications
* Some exceptions of logs. We know rebuild the perl interface were reported in logs as level 2 instead of level 1.
* Web files log now also logs errors when accessing files (instead of only successful accesses).
* Application init: If table from the init procedure fails there was standard message. Now the original error disk if this one is also displayed corrupted in the info field.
* Speed up variable recognition process (command parser).
* Changing the way we write registry in order to avoid loosing information in case of crash (we use now file renaming).
* The service executable path may now be relative. memory.
h2. New features
* Adding list Management of services required by an application (APPLICATION:INFO command) and list of running applications using required services (SERVICE:INFO command).
* Adding a removefile action in the package description file. HTTP X-Forwarded-For header. This action removes parameter allows Nirva to retrieve the specific file or files sender IP address in the target directory. Can be used with wildchard.
* Adding IPV6 protocol for TCP/IP. The server can be configured to listen on IPV4 only case there is a proxy or both IPV4 and IPV6. Client can use IPV4 or IP6 address to connect to server.
* Adding a new NV_HTTP_HOST variable that gives load balancer in the host http header of the original command.
* Adding route. This is a java interface log. security enhancement.
* Application start: adding One can define a reason telling why the starting failed trigger for external commands in the error message.
* Adding possibility to change the command variable identifier at application, service and command level (default application. This is still # character).
* Adding a stop on error and stop on success option for scheduled tasks with repeat mode enabled.
* Adding the task name as parameter (NV_TASK_NAME) to task procedure (and task failed and success procedures).
* Adding listener name to the listener main and failed procedures.
* Adding an information telling when (or several procedures) called before executing a task has been ran manually in the task list.
* Adding socket error information in error info field in command coming from a request.
* Security fix: Adding permission to display error info field to clients. Some information client (browser, xml, c++, java, etc...). The external trigger procedure name is set in the info field can reveal some server application.dsc file paths so this feature corrects this situation. for deployment.
* Adding a flag at application level to disable the trigger if one has been defined chapter in the dsc file.
documentation about applications.
h2. Bugs
* The date/time format for the http file cache were not set correctly. This could make some web files not accessible in servers with a local not in english.
* The output buffer was truncated if its content is longer than 256 byte in java procedures.
* The unicode option In case of crash the comand line was not working (-u option).
* The machine and local user name were not encoded correctly. This was producing a bad password error if the machine name was not ascii.
* The encoding of line feeds was not made between client and server for the session_open and session_close parameters. This could break the procedure parameters if there were some.
* There was an error in xslt transform for input xml message when the body was greater than the limit (parameter) for memory messages (1024Kb by default).
* The state of the web services operation was not kept after updating (re-install).
* The service renderer content type was not working.
* The application containers were not cleared after a failed application start.
* Renderer compilation was not working on linux.
* Log for web services was not working (nothing logged).
* The success procedure for scheduled tasks were not correctly implemented (procedure not running).
* The file origin was not transmitted from client log table may be corrupted so it becomes impossible to server in analyze the OBJECT:SEND command.
* The double spaces crash in the MISC:EXEC command were replaced by a single space.
* The MAIL:SEND command was not throwing any error in case of error.
h2. Modifications
* Some exceptions of logs. We know rebuild the perl interface were reported in logs as level 2 instead of level 1.
* Web files log now also logs errors when accessing files (instead of only successful accesses).
* Application init: If table from the init procedure fails there was standard message. Now the original error disk if this one is also displayed corrupted in the info field.
* Speed up variable recognition process (command parser).
* Changing the way we write registry in order to avoid loosing information in case of crash (we use now file renaming).
* The service executable path may now be relative. memory.
h2. New features
* Adding list Management of services required by an application (APPLICATION:INFO command) and list of running applications using required services (SERVICE:INFO command).
* Adding a removefile action in the package description file. HTTP X-Forwarded-For header. This action removes parameter allows Nirva to retrieve the specific file or files sender IP address in the target directory. Can be used with wildchard.
* Adding IPV6 protocol for TCP/IP. The server can be configured to listen on IPV4 only case there is a proxy or both IPV4 and IPV6. Client can use IPV4 or IP6 address to connect to server.
* Adding a new NV_HTTP_HOST variable that gives load balancer in the host http header of the original command.
* Adding route. This is a java interface log. security enhancement.
* Application start: adding One can define a reason telling why the starting failed trigger for external commands in the error message.
* Adding possibility to change the command variable identifier at application, service and command level (default application. This is still # character).
* Adding a stop on error and stop on success option for scheduled tasks with repeat mode enabled.
* Adding the task name as parameter (NV_TASK_NAME) to task procedure (and task failed and success procedures).
* Adding listener name to the listener main and failed procedures.
* Adding an information telling when (or several procedures) called before executing a task has been ran manually in the task list.
* Adding socket error information in error info field in command coming from a request.
* Security fix: Adding permission to display error info field to clients. Some information client (browser, xml, c++, java, etc...). The external trigger procedure name is set in the info field can reveal some server application.dsc file paths so this feature corrects this situation. for deployment.
* Adding a flag at application level to disable the trigger if one has been defined chapter in the dsc file.
documentation about applications.