## 1 Orber Release Notes

### 1.1 Orber 3.5.3, Release Notes

#### 1.1.1 Improvements and new features

- To avoid malicious attacks, it is now possible to configure Orber to only accept incoming requests up to a certain size. To be able to use this option, it must be supported by inet and SSL.
  Own id: OTP-5129

#### 1.1.2 Fixed bugs and malfunctions

-

#### 1.1.3 Incompatibilities

-

#### 1.1.4 Known bugs and problems

- The same as in the last release.

### 1.2 Orber 3.5.2, Release Notes

#### 1.2.1 Improvements and new features

-

#### 1.2.2 Fixed bugs and malfunctions

- If a client tried to connect to Orber and immediately closed the connection, then the process accepting new connections could end up with a message in the queue that would never be removed.
  Own id: OTP-5105
- The INS corbaloc/corbaname URL:s did only accept DNS style host names. Now it is also possible to use, none compressed, IPv6 addresses.
  Own id: OTP-5108
- When Orber was configured to use IPv6 for inter-ORB communication, exported IOR:s did not contain a correct IPv6 address. This did not cause any problems if Orber was configured to use DNS style hostname instead.
  Own id: OTP-5109
- Orber used external operations not exported in R9B.
  Own id: OTP-5111

#### 1.2.3 Incompatibilities

-

#### 1.2.4 Known bugs and problems

- The same as in the last release.

### 1.3 Orber 3.5.1, Release Notes

#### 1.3.1 Improvements and new features

-

#### 1.3.2 Fixed bugs and malfunctions

- When using Light IFR it was not possible unregister data (i.e., invoking 'MyModule':oe_unregister()). Introduced in Orber-3.5.0.1.
  Own id: OTP-5034

#### 1.3.3 Incompatibilities

-

#### 1.3.4 Known bugs and problems

- The same as in the last release.

### 1.4 Orber 3.5.0.1, Release Notes

#### 1.4.1 Improvements and new features

-

#### 1.4.2 Fixed bugs and malfunctions

- orber_ifr:contents/3 always returned an empty list when using Light IFR. Little or no effect.
  Own id: OTP-5018

#### 1.4.3 Incompatibilities

-

#### 1.4.4 Known bugs and problems

- The same as in the last release.

### 1.5 Orber 3.5, Release Notes

#### 1.5.1 Improvements and new features

- It is now possible to configure Orber to use NAT (Network Address Translation) friendly parameters. A new section in the User's Guide describes how to handle communication via firewalls.
  Own id: OTP-4698
- A new module called `orber_diagnostics` have been added, which is intended to aid a user during the test and development phase. For more information, see the reference manual.
  Own id: OTP-4699
- `IPv6` supported.
  Own id: OTP-4937
- Possible to configure Orber so that exported IOR:s contain multiple IIOP components for different interfaces.
  Own id: OTP-4938
- Improved typechecking of typecode supplied to the operations `orber_tc:check_tc/1`, `any:create/2` and `any:set_typecode/2`.
  Own id: OTP-4939
- Server objects can now be started as EXIT tolerant.
  Own id: OTP-4940
- Possible to use interceptors for local invocations as well.
  Own id: OTP-4941
- If the IFR is not explicitly used, Orber can be configured to use a minimal IFR to reduce memory usage and installation time.
  Own id: OTP-5001
- To avoid malicious attacks it is now possible to configure Orber to limit the number of concurrent connections and requests and the amount of IIOP fragments.
  Own id: OTP-5002
- The operation `orber:iiop_connections/0` now also include incoming connections.
  Own id: OTP-5004
- The function `orber:add_node/2` now accepts more options.
  Own id: OTP-5006
- The module `orber_diagnostics` now exports a function which list missing modules generated by IC and required by Orber.
  Own id: OTP-5007

#### 1.5.2 Fixed bugs and malfunctions

- Orber's NameService did not return a NIL object reference if the total number of existing bindings was less than, or equal to, the `HowMany` parameter passed to `'CosNaming_NamingContext':list/2` operation. This have now been changed to be compliant with the OMG standard. Furthermore, the operation `'CosNaming_BindingIterator':next_n/2` did not handle the index correctly in all situations.
  Own id: OTP-4700
- If the Orber internal gen_server orber_iiop_pm was stopped in such a way that the terminate function was not invoked, then ghost processes would appear.
  Own id: OTP-5003

#### 1.5.3 Incompatibilities

- The work-around introduced in version 3.4.1 (OTP-4608) has now been removed. Make sure you are using IC-4.2 or later.
- Since the OMG has defined a default port number (2809), Orber no longer support the boostrap port.
  Own id: OTP-5005

#### 1.5.4 Known bugs and problems

- The same as in the last release.

### 1.6 Orber 3.4.2.2, Release Notes

#### 1.6.1 Improvements and new features

-

#### 1.6.2 Fixed bugs and malfunctions

- Due to IFR DB lock mechanisms, concurrent creation of non-anonymous IFR types could still result in duplicated entries.
  Own id: OTP-4781

#### 1.6.3 Incompatibilities

-

#### 1.6.4 Known bugs and problems

- The same as in the last release.

### 1.7 Orber 3.4.2.1, Release Notes

#### 1.7.1 Improvements and new features

-

#### 1.7.2 Fixed bugs and malfunctions

- The operation `orber:start()` could return before all Mnesia tables were accessible.
  Own id: OTP-4780
- Concurrent creation of non-anonymous IFR types could result in duplicates in the DB.
  Own id: OTP-4781

#### 1.7.3 Incompatibilities

-

#### 1.7.4 Known bugs and problems

- The same as in the last release.

### 1.8 Orber 3.4.2, Release Notes

#### 1.8.1 Improvements and new features

- Improved type tests for string, wide string and sequence when passed via IIOP.
  Own id: OTP-4759
- Less (internal) processes are needed when Orber act as client-side ORB and communicate with another ORB. Due to this change, closed connections and socket errors are dealt with in a more gentle way. If the latter occurs, the error_logger application is used to generate an error report containing a description of what went wrong.
  Own id: OTP-4655

#### 1.8.2 Fixed bugs and malfunctions

- When communicating with another ORB, via SSL, and a socket error occured, Orber did not recognize the error message. This occured when Orber acted as client-side ORB.
  Own id: OTP-4656
- If an out-going connection was closed and the receiving process had not been scheduled yet, the close connection message was delivered before the correct message.
  Own id: OTP-4657

#### 1.8.3 Incompatibilities

- Since strstream is deprecated and not accepted by gcc-3.3, Orber no longer includes the InitalReference lib. The source code is still included.
  Own id: OTP-4767

#### 1.8.4 Known bugs and problems

- The same as in the last release.

### 1.9 Orber 3.4.1, Release Notes

#### 1.9.1 Improvements and new features

- It is now possible to use IC-versions older than 4.2. But, this is only temporary so it is still necessary upgrade to a correct version.
  Own id: OTP-4608

#### 1.9.2 Fixed bugs and malfunctions

-

#### 1.9.3 Incompatibilities

-

#### 1.9.4 Known bugs and problems

- The same as in the last release.

### 1.10 Orber 3.4, Release Notes

#### 1.10.1 Improvements and new features

- If a call-back module illegally caused an EXIT, clients residing on another ORB was not notified (hanged).
  Own id: OTP-4577
- The stub/skeleton-files generated by IC have been improved, i.e., depending on the IDL-files, reduced the size of the erl- and beam-files and decreased dependencies off Orber's Interface Repository. It is necessary to re-compile all IDL-files and use COS-applications, including Orber, compiled with IC-4.2.
  Own id: OTP-4576
- It is now possible to configure Orber to use the host name in exported IOR:s instead of the IP-number.
  Own id: OTP-4541

#### 1.10.2 Fixed bugs and malfunctions

- When Orber acted as server-side ORB and one tried to setup a SSL-connection and using native Interceptors at the same time it failed.
  Own Id: OTP-4542
- Oneway operations, using a multi-node Orber, failed for inter-node communication.
  Own Id: OTP-4543

#### 1.10.3 Incompatibilities

-

#### 1.10.4 Known bugs and problems

- The same as in the last release.

For information about older versions see release notes history.

Copyright © 1991-2005 Ericsson AB