Borland Deployment Platform 6.0 Release Notes

This release note contains information specific to the Borland Deployment Platform 6.0 release. This release of the Borland Deployment Platform 6.0 addresses most of the customer-reported problems and includes the value-added features set.

This release note contains the following sections:

Borland Deployment Platform Products

The Borland Deployment Platform includes three products:

- Borland Deployment Op-Center

- Borland Enterprise Server

- Borland Janeva (not covered in this Release Note. See http://www.borland.com/devsupport/janeva/relnotes/6_0.html for Janeva Release Notes.)

Borland Deployment Op-Center

This is the premier release of Borland Deployment Op-Center, a product that provides deployment monitoring, management and visualization to ensure the availability of mission critical applications. Major features include:

Borland Enterprise Server 6.0

BES 6.0 new features include:

BES now based upon BDOC Management Architecture

BES is now based upon the new BDOC management architecture. Therefore, all the benefits of this architecture are now realized for BES server instances. For BES this means:

It is important to note that many familiar BES characteristics have changed subtly. In particular:

 

BES 6.0 VisiBroker Edition Release Notes

Click here for BES 6.0 VisiBroker Edition Release Notes (Windows and Solaris)

Click here for BES 6.0 VisiBroker Edition Release Notes (HP-UX on PA-RISC and IA, AIX, SuSE on x86, Red Hat on x86 and IA, Windows on IA and Windows-BCB)

Click here for BES 6.0 VisiBroker Edition Release Notes (SLES 8 on zSeries)

Click here for instructions on migrating secure VB application from 5.x to 6.0.

 

Platform Information

Supported platforms for this version of Borland Enterprise Server is available at:
for visibroker edition, http://techpubs.borland.com/am/bes/platforms/60xplatformvbe.htm
for appserver edition, http://techpubs.borland.com/am/bes/platforms/60xplatformase.htm

Installation Instructions

For installation instructions on other platforms, check the updates on the main Tech Pubs page: http://www.borland.com/techpubs/bes

Important note on licensing:

BES and Op-Center MUST be licensed and registered before they will run - there is no grace period. See http://www.borland.com/devsupport/bes/faq/6.0/licensing/index.html for instructions on how to license your product.

     

    Borland Enterprise Server Known Issues

    1. Compiling examples which use iastool on Linux may fail with Signal 11. GUI tools dump core on exit. There is a known issue in the Linux C libraries affecting Java applications which call System.exit(x). This is the recommended practice for GUI applications. iastool and Console both use this method to exit the VM. This problem is resolved in a later version of the C libraries. Please see http://java.sun.com/j2se/1.4.1/relnotes.html for more information. The suggested workaround is to edit the makefile to ignore the failing command. Since the necessary work has been accomplished by the time the tool exits, this is not a serious problem. (Case ID: 40159, 40138)
    2. The specification of a localhost for Tibco JMS in a partition's configuration file must be consistent with the specification of hostname in a dar file (jndi-definitions) file. For example if localhost name is "myhost", if you specify "localhost:7222" in jndi-definition file you must also specify "localhost:7222" for the Tibco managed object in the configuration file. Similarly if you specify "myhost:7222" in the jndi-definitions file you must also specify "myhost:7222" in the configuration file. (Case ID: 41633)
    3. For deployment situations where transaction manager is run as an external process, VBJ thread dispatch pool size [threadMax limit] should be set to high value to allow transaction synchronization callback threads to enter the VM under high transaction concurrency. If there are as many concurrent transactions in the partition, as the VBJ thread max of the partition then synchronization callbacks that need to happen as part of the transaction commit process, can't happen. In other words, a situation can happen where all the threads in the partition are trying to call commit(), and hence wait on the transaction service to finish the commit process, and transaction service is waiting on the partition process to allow synchronization callback threads to enter the VM. Due to this cyclic dependency the partition process will appear to hang. As mentioned, the situation may only happen when the transaction service is configured to run as an out-of-partition process, and the partition has small value for VBJ threadMax. Usually it is rare to have out of process transaction service, but should that be a requirement, the situation can easily be avoided by keeping the partition's VBJ threadMax at a high value or by keeping the threadMax un-bounded. We should know that VBJ creates only as many threads as are necessary to meet the concurrency, so keeping the threadMax un-limited doesn't mean there will be too many threads . (Case ID: 40300) When OTS is used as the external transaction manager, it must also have its thread dispatch pool size configured with a high value for applications involving high transaction concurrency. This can be achieved using VisiBroker property : vbroker.se.iiop_tp.scm.iiop_tp.dispatcher.threadMax Set this property to 50 or 100, depending on the expected concurrency level, in OTS related vbroker.properties file specified through -DORBStorage parameter. (Case ID 41605)
    4. With the new jdk (1.4.2_0x), it is observed that a J2EE archive like ejb-jar built on windows was able to open on Solaris using DDEditor. But the vice versa is not true, ie., the jar built on Solaris with the new jdk was unable to open on windows using DDEditor. Similarly, there is one more observation, the jar built using JBuilder on windows platform was unable to open on solaris platform using DDEditor. The problem seems to be due to an incompatibility between the jar files produced by the jar command on Solaris and Windows. This appears to be a JDK bug (Case ID 39631)
    5. The JBuilder project files for EJB examples shipped with BES 6.0 will work with JBuilderX and not with earlier release(s) of JBuilder.
    6. There seems to be a concurrency issue in SonicMQ 5.0. Under high load ie when many concurrent threads in a JMS client try to send messages, SonicMQ throws an exception "javax.jms.JMSException: java.net.ConnectException: Connection refused: connect:localhost:2506". The problem can be reproduced in a standalone client outside of BES. It seems to occur when the number of connections required by Sonic client exceeds the current number of available connections. In our setup if we ran the client with 21 threads specified, the exception occurs. However, if you quit that client and wait for all messages to be consumed from the queue and then rerun the same client with 21 threads it will work without any reported exception. The same is true if you specify 30 threads. The first run of the client produces the exception but subsequent runs generate no exception (Both BES partition and SonicMQ should not be shutdown between runs). (Case ID : 41376). A case (W311114101) has been filed with Sonic support. Please contact Sonic support for more details, current workaround is to have SonicMQ with large number or unlimited connections.
    7. There is a known issue in the database level cascade delete support which is only relevant for the "Exclusive" (option-A) commit mode. Please note that the default commit mode in BES is "Shared" (option B) . The symptom of the problem is the unexpected occurrence of "javax.ejb.ObjectNotFoundException" in situations where a transaction involves large number of entity beans. The workaround is to either use the "Shared" commit mode or to simply increase the value of the entity property called ejb.maxBeansInTransactions or disable transaction cache compaction by setting this property to zero. (Case ID : 41269)
    8. The JBuilder project for the ejb/basic/order example has an absolute path name in it.  Please perform the following steps:
    9. When creating an Apache managed object, the managed object name must NOT contain any spaces. If spaces are included in the managed object name, e.g. 'Apache Web Server', then Apache will fail to start.
    10. When deploying a DAR from a Windows console to a Solaris 64 server, a CORBA.TRANSIENT error sometimes occurs, and the DAR is not loaded. In this case, the DAR does get deployed, but to load it you must restart the partition.
    11. The default security profile shipped is not ssl-enabled. If your partition requires secure transport (EJB container sometimes does), then change the security profile for your partition to the 'ssl_enabled' profile. Right-click on partition, select 'Properties' command, select 'Security' tab, and change the profile in the dropdown.
    12. Compiling JSPs using IASTOOL consumes large amounts of memory, and can exhaust a system's virtual memory in many cases. An 'out of memory' exception will be thrown in this case. For example, compiling JSPs in a WAR with 370 JSPs may use as much as 1.5GB of memory. There are two workarounds:
    13. Editing, with DDEditor/EJB Designer, an EJB jar that does not have borland proprietary deployment descriptor file (ejb-borland.xml) will create the proprietary file, but will include some extraneous information in that file. This jar will deploy and function correctly.
    14. Dump stack to log function should NOT be used on Linux Red Hat Itanium. This function is accessible on the right-click menu of the Partition. Executing this function will not cause a stack trace to be dumped, and will prevent the Partition from being stopped normally.

    Borland Deployment Op-Center Known Issues

    1. Confused managed-object states will be reported if you accidently start a second SCU on the same machine configured as a local-hub or slave-agent.

    2. The SCU will be unable to stop a JDatastore server as a managed-object process on Unix or Linux platforms unless it is started '-ui none' option. See the Petstore cluster for an example.

    3. To allow the SCU to manage the IIS you must set the IISAdmin and WWW services to have Startup Type = Manual. Use the Windows management console to do this. Also be sure all the Recovery actions are 'Take No Action'.

    4. If you will be using the Janeva Petshop web site with the Petstore cluster you will have to disable security in the petstore security profile.

    5. The Petstore cluster template requires a Op-Center license to run.

    Known Issues common to BES and Op-Center

    1. License files can become corrupted if not licensing if not configured properly. This is most likely when deploying VB applications.

      If a licensed component is configured to access a license file on another system (via a network mounted drive, e.g.), the following error will be reported:

      Cannot start: Borland Enterprise Server License error[1023]: Sanctuary Initiation Error :License storage {0} does not apply to current user. Please register your Borland product(s).

      If this occurs, the licence files will be marked as unusable. You must re-register that license to activate it again.

      As a precaution, after registering your product, you may save a copy of the <install dir>/var/borland.lic and borland.pkg files to another location. Should the license file corruption occur again, licensing can be restored by simply copying these files to the <install dir>\var folder.


    2. Deleting a license in the License Manager GUI does not fully delete a network license (a license that uses a license server).

      In the License Manager GUI (available in the Console via the Tools/License Manager menu command, or on command line: <install dir>/bin/lmadm -r info), you can right-click on a license and delete it. However, this does not fully delete the license. To delete a network-nased license, you must manually delete the regxxx.txt file and/or the concurrent_xxxx.slip file in the <install dir>/license folder. Deletion of node-locked licenses does not have this problem.

    3. On RedHat Linux (Pentium), the Installer, when calculating available disk space, displays the following:

      Disk Space Information (for Installation Target):

       Required: 605,149,820 bytes

       Available: Error!

      You should check your available disk space manually at this point. If you have sufficient disk space, installation will proceed normally.

    4. On Windows and RedHad Linux on Itanium, and RedHat Linux on Pentium, the Installer will complete with warnings, because it is unable to succesfully check free disk space (see above issue).

      In this case, the resultant install log will contain a warning:

      <action name="Check Disk Space" status="warning">

      This warning can be ignored.

    5. On Linux systems, a fully qualified domain name and IP address needs to be the first entry in the "hosts" file.

      When running the BES Server on Linux, the Management Console and iastool are sometimes unable to discover that server when run from a different system. This is because the default Linux hosts file has only the loopback entry (127.0.0.1).

      In order to correct this, you must add an entry for the local host. For example, on a machine named mylinux that is called mylinux.work.mydomain.com at 172.1.1.1, the following must be added to the hosts file and must be the first entry in that file:

      172.1.1.1 mylinux.work.mydomain.com mylinux

    Additional copyright info

    jUDDI Open Source Project Copyright

    Copyright (c) 2003, Steve Viens and contributors. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    Made in Borland © 2003 Borland Software Corporation. All rights reserved.