Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar

Search for    in all of
view all search results right arrow
Support > Technical Documents > Document Types > Release Bulletin > Release Bulletin EAServer 5.5 for Sun Solaris

Release Bulletin EAServer 5.5 for Sun Solaris

Documents known problems and changes to documentation, installation, and functionality for EAServer version 5.5 on the Sun Solaris SPARC 2.8 and 2.9 operating systems.
RSS Feed

Release Bulletin EAServer 5.5 for Sun Solaris


Document ID: DC38031-01-0550-01

Last revised: December 7, 2006

Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase Product Manuals Web site.

Accessing release bulletins at the Sybase Product Manuals Web site
  1. Go to Product Manuals.

  2. Select a product and language and click Go.

  3. Select a product version from the Document Set list.

  4. Select the Release Bulletins link.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.

Product summary

Enclosed is Sybase EAServer version 5.5, build 55014. You may have a later build number if you have installed ESD patches for this release. If so, the cover letters provided with each patch contain the build number and additional documentation.

This EAServer release is compatible with the following platform and operating system configurations:

  • Sun Solaris SPARC 2.8

  • Sun Solaris SPARC 2.9

Verify that you have the required Solaris patches for JDK versions 1.3. See these Web pages for more information:

Note:Solaris 2.8 is the same as Sun OS 5.8 and Solaris 8. Solaris 2.9 is the same as Sun OS 5.9 and Solaris 9.

Table 1 lists versions of various products supported in EAServer 5.5.

Table 1: Product support


Supported versions/builds

Operating system

2.8, 2.9

Redirector plug-ins:





1.3.26, 2.0




Adaptive Server® Anywhere


Adaptive Server® Enterprise

12.0, 12.5

Oracle client

7.3.4, 8.1.7, 9.0.1, 10g


PB 10.5


C++ compiler

Solaris C++ 4.2, C++ 6.0



Web browser

Netscape 6.1 and 7.0

JDK Versions:







Special installation instructions

The Installation Guide describes how to install the software.

Changed functionality in this version

What’s New in EAServer describes features added in this version. You can view this book on the Sybase Product Manuals Web site. Browse to the EAServer 5.5 (Core Documentation) collection, then select this title. This manual is also available in HTML format in your installation.

Known problems

This section describes known problems in this EAServer version.

EAServer Manager issues

This section describes the known issues in the EAServer Manager.

Proxy connection cache

(CR #440748) Since both Solaris and Linux are using unixODBC instead of DataDirect, you must enable the set-proxy support property in the cache properties file to make the proxy connection cache works. Before you begin, do the following tasks:

  1. Create a pseudo user “jagadmin” in ASA (to connect to user’s database or server)

    grant connect to jagadmin identified by “ ”
  2. Set the session for jagadmin

    set session authorization “jagadmin”

For more information about the connection cache, see Chapter 4, “Database Access,” and the “Connection cache properties” in Appendix B, “Repository Properties Reference,” in the EAServer System Administration Guide.

JDBC connection cache

(CRs #440605, #440158, and #427244) An error occurs when closing the database connection with jdbc3 driver. To work around this issue, you can use one of the following methods:

  • Modify the connection pool driver from com.sybase.jdbc3.jdbc.SybDriver to com.sybase.jdbc2.jdbc.SybDriver.

  • Retain jdbc3 driver. However, you need to update the jConnect3.jar and jTDS3.jar files. After updating these files, upgrade the database, and set the J2EE_TCK_COMPLIANT to true before running the application:

    1. Download the jConnect for JDBC 6.05 to obtain the latest jConnect3.jar and jTDS3.jar files.

    2. Upgrade the database. Execute the relevant sql file, which is located in \jConnect-6_0\sp. The sql file selected depends on the database version. For example, for ASE 12, select and run sql_server12.sql.

      The following example illustrates how to upgrade Zeus database.

      isql -S Zeus -U sa -P "" -i E:\tempsharedjConnect-6_0\sp\sql_server_recreate12.5store_p.sql -c go.

    3. Modify the following codes to set J2EE_TCK_COMPLIANT to true.

      Original code

      Modified code

      URL = jdbc:sybase:Tds:<hostname>:<portno>

      URL = jdbc:sybase:Tds:<hostname>:<portno>? J2EE_TCK_COMPLIANT=true

      NetworkProtocol = Tds:Server=<hostname>:Port=<portno>: DatabaseName=<dbname>

      NetworkProtocol = Tds:Server=<hostname>:Port=<portno>: DatabaseName=<dbname>:J2EE_TCK_COMPLIANT=true

      con=DriverManager.getConnection(url,user, password)

      Properties p = new Properties();
      con = DriverManager.getConnection(url,p);

    For more information about the JDBC connection cache, see Chapter 4, “Database Access,” in the EAServer System Administration Guide.

Apply buttons

(CR #347498) To apply changes in EAServer Manager dialog boxes, click OK. Some dialog boxes have Apply buttons that are disabled. There is no way to enable these buttons.

No core dump generated

(CR #400621) If Apache is installed after EAServer, you need to add the JAGUAR and the JAGUAR_CLIENT_ROOT environment variables in the environment variables file in Apache directory. Otherwise, either JAGUAR or JAGUAR_CLIENT_ROOT environment variable will prevent Apache from core dumping.

EAServer security libraries

(CR #401487) When EAServer's security libraries and are used by a client program such as JVM on Solaris, the environment variables, JAGUAR and JAGUAR_CLIENT_ROOT need to be set before running the program, which is dependent on the libraries.

Security Administration issues

This section describes the known issues in the EAServer security administration.

Online help Key/Cert wizard

(CR #380451) The online help page for the Key/Cert wizard needs to be updated to reflect the changes in CR #352693. The changes are as follows:

  • The Key Strength property can now support more than 1024 bits. Also, you need to select the restriction “For international users” option.

  • The Mark Private Key Exportable property is no longer available.

For more information about the Key/Cert wizard, see the “Certificate Management” section in Chapter 14, “Managing Key and Certificates,” in the EAServer Security Administration and Programming Guide.

Base64 encoded X.509 certificate not compatible

(CR #400631) If you use the Jaguar Manager to export a certificate in Base64 encoded X.509 certificate, the format is not compatible with Sun’s keytool requirement. To solve this problem, the imported data must either be in a binary encoding format or in a printable encoding format (also known as Base64 encoding). If you use the Base64 encoding format, you need to enclose the imported data with a string that starts with “----BEGIN” and ends with “----END”. An example of the Base64 encoding format is as follows:


EAServer SSL client runtime

(CR #402979) If you are only installing EAServer client runtime to enable SSL connection from the PowerBuilder client, the SSL in PowerBuilder will not work. To work around this problem, you need to set the environment variable, JAGSSL, to true in the shell. SSL in PowerBuilder requires a full EAServer C++ client installation. For more information, refer to Chapter 7, “Using SSL in PowerBuilder Clients,” in the EAServer Security Administration and Programming Guide.

FIPS online help not available

(CR #430403) The FIP online help is not available when you click the Help button in Sybase Central 4.3 | Security Manager | Properties | Help.

To resolve this issue:

  1. Unzip the file, sechelpMap.jhm, located in $JAGUAR/easmgr/doc/sechelp.jar.

    After unzipping the JAR file, get the file at /sechelp/sechelp/sechelp.Map.jhm.

  2. Add the following entry in sechelpMap.jhm:

    <mapID target="helpFipsMode" url ="sechelp/sechelpp1.htm#TI3" /> 

Web Services Toolkit issues

This section describes the known issues in the Web Services Toolkit.

Eclipse runs out of memory when handling large return values

In Eclipse, when testing Web service calls to components that return very large values (greater than 1 million bytes), the Java VM that runs Eclipse may run out of memory. To solve this problem, modify the script file. Change this line; adding the -Xmx option to increase the Java VM heap size from the default:

eclipse -vm jdk-path/jre/bin/java

For example:

eclipse -vm jdk-path/jre/bin/java -vmargs -Xmx512m

This example sets the Java VM heap size to 512MB, specified by 512m. You can adjust the size up or down as needed to prevent out-of-memory errors. For information on the syntax of the -Xmx option, see the Java command line documentation.

Expired VeriSign root certificate

(CR #343954) The VeriSign root certificate has expired in the JDK 1.3 and 1.4 installations used by EAServer. As a result, publishing to the Microsoft UDDI Registry throws a certificate expired exception. For more information on how this problem may affect your applications, see Sun alert notification 57436. To work around this issue:

  1. Shut down EAServer.

  2. Download the most recent VeriSign PCA root certificates from the VeriSign Web site

  3. Unzip the files to a temporary location, for example, /tmp.

  4. Change to the bin directory in the JDK 1.4 installation used by EAServer. Import the new certificates with the keytool command. For example, enter the following, all on one line:

    keytool -import -v -keystore $JAGUAR_JDK14/jre/lib/security/cacerts -alias verisignclass3ca2028 -file "/tmp/VeriSign - Thawte Combined Roots/VeriSign_Roots/PCA3ss_v4.509"

    When prompted, enter the JDK keystore password. The default is changeit. When prompted, accept the new certificate.

  5. Repeat the previous step to update the VeriSign root certificate in the JDK 1.3 installation used by EAServer.

Incorrect datatype in WSDL by Axis 1.2

(CRs #396790 and #399573) EAServer 5.5 now supports Axis 1.2. If you use the JAX-RPC to build Web services and clients, this results an incorrect datatype in the WSDL definition. For instance, after deploying JAX-RPC for an eyeColor element, it generates an incorrect WSDL definition, as follows:

<simpleType name=''eyeColor''>
<restriction base=''soapenc:string''> 
	<enumeration value=''Brown''/> 
	<enumeration value=''Blue''/> 
	<enumeration value=''Green''/> 

The datatype should be xsd:string instead of soapenc:string. If you use the above code to generate into Java code using wdsl2java, this results an error. To work around this problem, Sybase recommends that you refresh the EAServer before using the wsdl2java to generate WSDL to Java code.

Incorrect result with Literal option in Web service operation

(CR #439777) When you deploy a Java file with the Literal option in the document or a Remote Procedure Call (RPC) binding in the Web service operation, it generates an incorrect return value. There is no workaround for this issue.

Web application issue

This section lists the known issue in the Web application.

-syncwebappjavaclasses parameter causes an error

(CR #418643) If you use the -syncwebappjavaclasses option in jagtool that is set to false to synchronize the EJB class files, this results an error. This parameter is ignored if the entity type is Package:PKGName or Component:PKGName.

To work around this problem, add a new sync option in jagtool command, -syncjavaclasses [true | false ]. The default setting is True. This new option has a higher priority over -syncwebappjavaclasses. Refer to “Chapter 12, Using jagtool and jagant” of this document for more details about the sync command used by jagtool.

Other issues

This section lists other known issues in EAServer.

Third-party JARs loaded by system class loader

(CR #397598) If you specify third-party JARs in the CLASSPATH or BOOTCLASSPATH in, they are loaded by the EAServer system class loader. If any class within these JARs calls getClassLoader, it returns null. If any class within these JARs calls JNI, the JVM ignores this and searches only sun.boot.library.path. The problem is that the third-party JARs are typically installed outside the EAServer installation. In EAServer 5.5, JARs cannot be loaded by the server class loader, unless they are in $JAGUAR/java/lib, $JAGUAR/html/classes, or $JAGUAR/java/classes.

To work around this problem, put third-party JARs in the $JAGUAR/java/classes directory, and add “ _party_library.jar" to $JAGUAR/Repository/Server/Jaguar.props. This allows the server class loader, instead of the system class loader, to load the third-party JARs.

Online help

(CR #421583) The current online help in EAServer 5.5 uses online help version 5.2.

Incorrect link to EAServer Cookbook

(CR #449702) After installing EAServer 5.5 Developer Edition (DE), if you browse to <http://hostname:portnumber> and click the EAServer Cookbook link (which points to /doc/easgs/main.htm), the link fails.

To work around this problem, click the User Documentation link on the same page or browse to <http://hostname:portnumber>/doc/index.htm, then click EAServer Cookbook (which points to /doc/easgs/index.htm), the link works.

Incorrect link to What’s New in EAServer

If you browse to <http://hostname:portnumber>/doc/easgs/index.htm, the online documents refer to EAServer version 5.3. The What’s New in EAServer should be referring to What’s New in EAServer 5.5.

To work around this problem, refer to the latest EAServer 5.5 online documents on the Sybase Product Manuals Web site.

Fixed problems

The following issues are fixed in this version:

Bug ID



Upgrade RSA BSAFE libraries to version 6.3.1.


EAServer aborts upon startup with JDK 1.5.


In EAS55, there is a problem using more than one value for a servlet filter property.


EAServer crashes when sending special result set to TDS clients.


If you add "\"(a backslash) to the end of description of context-params of a Web Application, the value disappears.


If there is more than one line of context-params with end character "\", the end of the value could not be recognized correctly.


Upgrade JDKs 1.4.2 and 1.5.0 to versions JDK 1.4.2_13 and 1.5.0_09.


Run PBEJB case failed with JDBC ODBC connection cache.


Update the stack size to 512000 then this issue can be fixed. But, we can't change the source code to do that, because this fix will affect other. Hence, this stack size does not need to change.


Oracle connection cache getting destroyed due to XA error in EAServer 5.3.


When the component is created firstly, the value _newLabel is null.


When the EAServer JAR is deployed successfully, the dialog box is closed directly because that it is not a wizard.


The classpath space for the create a new Class Loader is too small.


EAS55012p1: The copyright year is old.


When user spawns thread in C++ using JagLog interface causes EAS to crash in EAServer 5.3


We can't remove host/port by matching context-path directly.


Merge in new JDBC library for jConnect 6.0.5.


EAServer crashes suddenly after you see server properties.


EAS55012: Invoke Web Service operation gets wrong return value


Class loader warnings in the Jaguar.log


EAServer runs out of memory after 41 service deployments in 24 hours.


Classes under com.sybase.* will not be exported in Jaguar JAR file.


Time presentation of ELFF setting in Jaguarhttprequest.log. This issue has a cross-reference to Bug ID: 437931. Refer to “Appendix B, Repository Properties Reference” of this document for more details.


JSP client generated JSP pages do not compile.


Possible security vulnerability with Sybase Central and Sybase Central plug-ins on Sun Solaris.


Incorrect behavior for related session function on webapplication.sessionid=url.


With EAServer 5.2, the wcharvalue functions of the Message Service are broken.


Cannot change property values by using the cluster wizard.


Unable to use environment variables in the new logging system.


Seeing internal exceptions in web console.


Login wizard crashes Sybase Central.


EJB and JMS failures.


Feature request for config property to disable reverse host name lookup.


Server exists in a HTTP keepalive session with errors when the value is larger than 2147.


Exposing components as Web services, there are some restrictions to the datatype of the component method’s arguments deployed.


Browsing WST Repository takes long time.


Cannot identify database driver com.sybase.ejb.cmp.SybaseDriver.


Deploy fails for applications with name containing “Application”.


Provide support for ASA 9.0.2 with EAServer Samples.


Provide support for AXIS 1.2 GA.


SybAgent DOS window stays in the foreground.


Cannot re-establish a connection once disconnected via network termination.


Redirector problem with EAServer 4.2.4 embedded within EP 6.0.


Jaguarhttpservlet.log and ArrayIndexOutOfBound errors.


Changing hosts of all listeners fails.

391344 cannot take a long string.


Hot Deployment.


Security Manager Key/Cert Wizard error.


Message Service:IGNORE_DUPLICATE_KEY not working properly.


Fix for Stack-Based Buffer Overflow issue with WebConsole.


Compile failure on skeletons on a Java-CORBA component within a particular EAS package, although same component compiles in another package.


HTML files causing delay in server start.


PB 9.0.2 embedded SQL delete where no rows are found, returns -1 in EAServer.


HTTPS listeners not working when FIPS enabled.


DBCS displays problem in Jaguar.log with PB components.


Looping over Context.listBindings("jdbc") always throws NamingException.


jConnect6.0 support.


jagtool not generating Java skeletons.


Eclipse cannot start and shutdown EAServer.


JAR file in EAR not accessible as stream for application isolation deploy.


Process keeps running on server, although the client browser is closed.


EAServer Manager 5.2 cannot deploy very large EAR files.


A JSP in XML syntax written in UTF-8 encoding with non-trivial characters is not compiled correctly. The UTF-8 characters are corrupted in the resulting Java file.


Server crashes due to an incomplete HTTP request.


In jagmgr, the last step of Message Service configuration, if click "Ping Message Service Database", then click "Cancel" button instead of "Finish", the Message Service will also appear in "Installed Services".


Java file compression routine causes EAServer to crash. Problem fixed, in libjcc.dll.


In Axis, Type Array is referenced but not defined.


The Key/Cert wizards in Security Manager and EAServer Manager now work for Key Strength values of 1024 and above.


Named class loader enhancement.


JDBC connection caches exceed the maximum number of physical connections.


Provide support for Oracle 10g database and JDBC drivers.


jagtool pre-compilation uses incorrect JDK versions.


Application refresh problem with two deploys.


Application refresh does not refresh Connectors in the application.


Redirect file:...IIS.Extension_URI /..../libjeas_iis.dll cannot include blank line.


Deploying J2EE EAR file does not display error details.


When you upgrade from an earlier version of EAServer, Sybase Central is also upgraded from version 4.1 to 4.3. The installer does not migrate the existing EAServer Manager profiles from the older version of Sybase Central, so you must re-create the profiles (see the online help for instructions).


To start Sybase Central using scjview, first set the LD_LIBRARY_PATH to include $JAGUAR/lib; otherwise, Security Manager will not connect.


CSS does not work consistently for Mozilla browsers.


When login a Jaguar Manager and check the certificates, click Cryptographic Modules. Double-click the FIPS mode. Click the help. No help content is provided.


An exception is seen if you change IIOP port and restart server.


PB 9.0.2 embedded SQL delete where no rows are found, returns -1 in EAServer.


Support for OpenClient 12.5.1.


Provide EAServer Manager host name history.


Update Web service sample.


When a Web application is deployed but server is restarted prior to the WebApp being refreshed, the WebApp-AppName directory is created as root and not the run as user.


The following changes are required in the readme.txt file located in the sample\wst_samples\CORBAComponent\client subdirectory of the EAServer installation:

  • After the following lines: Expand the Other Components folder. The IntroSamples package should display. Expand this folder to display the IntroJavaIDL (CORBA) component.


    If the IntroSamples package is not listed, go to EAServer Manager and select Servers | Jaguar | Installed Packages, and right-click Installed Packages; click Install an Existing Package; select IntroJavaIDL from the Choose Package to Install list; then click OK. Restart or refresh EAServer.

  • Error at lines: Only the getXXX methods and Boolean b method should be selected. Click OK. The component is now exposed as a Web service.

    should be:

    Only the getXXX methods and Boolean throwException method should be selected. Click Finish. The component is now exposed as a Web service.

  • Step 6 of the readme.txt file describes the file. This should be


Unable to resize drop-down list box in Sybase Cetnral.


jagant tool gives jag_connect local mode error.


Absolute path should be supported when setting JAR file for SAX2 parser factory.


Class is not loaded by customer's class loader during new component creation.


Log SSL properties set to “false” but SSL errors still get logged.


EJB run-as settings result in BAD_OPERATION under certain circumstances.


The Web service name in the Stateless EJB sample has been fixed.


The readme.html file in the EAServer\html\classes\Sample\Intro\ subdirectory of the EAServer installation contains these errors:

  • Error at the line: d. Check “Compile Java Files.”

    should be:

    d. Check “Compile Java Stubs.”

  • Error at the line: a. Uncheck Compile Java Skeletons. b. Under Advanced Options, check “Generate Skeletons on Server.”

    should be:

    a. Under “Skeleton Generation Options”, uncheck “Compile Java Skeletons.” b. Check “Generate Skeletons on Server.”


Currently, EAServer does not support J2SE 5.0 so to make code changes and add support for it.


When there are many log files in a directory (160 or more), the File Viewer will cause EAServer 5.1 to crash during navigating and opening this directory.


When enabling "Custom Class Loader Tracing", no output is being generated when using the default level 1 class loader.


When you upgrade from an earlier version of EAServer, Sybase Central is also upgraded from version 4.1 to 4.3. The installer migrates plug-ins that are compatible with Sybase Central 4.3 to the new installation; other plug-ins remain in the Sybase Central 4.1 installation. To use the migrated plug-ins, start Sybase Central 4.3. To use the other existing plug-ins, start Sybase Central 4.1.


Improve usability of dialog in EAServer Manager dealing with JMS Dead Queue.


Some configuration options of a message driven bean are not set correctly during deployment from EJB-JAR file.


[EXCEPTION_ACCESS_VIOLATION(0xc0000005)] received while executing the getServerEnvironmentVariables method of the Jaguar/Management component.


Memory leak with EJB CMP.


You see errors for unresolved javax.ejb dependencies when importing the EJBSample. This sample is not intended to be built or used in Eclipse, but is rather meant to be compiled manually and then deployed to EAServer using EAServer Manager. EJBSample contains the source code for an EJB and requires classes that Eclipse does not have, such as javax.ejb.*.


You see several errors caused by the lack of Web service client classes that must be generated after importing. This is expected, since the client classes must be generated for each sample project according to the readme files that accompany each sample.


When running the Eclipse plug-in on Solaris 2.9, if you create a server profile that restarts the server, after the first time you use the profile to restart and connect to the server, the folder items under the profile may be out of order and cease to function.

To work around the issue, exit and restart Eclipse.


When you upgrade from an earlier version of EAServer, the installer upgrades the sample test certificates and installs new versions of the VeriSign CA certificates. The upgrade may leave obsolete copies of the Sample1 Test ID and Sample2 Test ID certificates. This is an expected behavior. You can delete these manually using EAServer Manager or Security Manager. Delete the older version of each certificate.


Chapter 4, “Web Services Administration,” in the Web Services Toolkit User’s Guide describes how to use the Apache XML-Security package to provide digital signatures and encryption for the SOAP messages sent to and from the Web services container in EAServer. To use this feature, replace the file xalan.jar in the EAServer java/classes directory with the version that is included with the Apache XML-Security package. Follow the instructions to add the other JAR files to the EAServer CLASSPATH setting.


Trying to create proxies for EJB 1.1 containing public static final String in home interface causes PB to GPF. Basically, when there is a Datamember in the EJBs home, no matter if static, final, and so forth, it will GPF PB.

Product compatibilities

This section contains information about other Sybase products that are compatible with this version of EAServer.


For additional information on PowerBuilder®, see the PowerBuilder Manuals Web Site. The PowerBuilder Release Bulletin for your PowerBuilder version may contain additional late-breaking information.

This version of EAServer includes the following PowerBuilder virtual machines (PBVMs):

  • PowerBuilder 10.5 – build 5063

Note:EAServer 5.5 does not support PowerBuilder versions 7.x, 8.x, and 9.x.

On Solaris, the EAServer binaries and libraries are provided in formats that are compatible with the Solaris C/C++ compiler version 4.x or 6.x. You can specify which version to use with the -compilerversion command line argument. PowerBuilder support requires that you run the server binary that is compatible with version 6.x of the Solaris C/C++ compiler. For more information, see the EAServer System Administration Guide.

On Solaris, this version of PowerBuilder does not support ODBC driver for ASA connection caches, instead Sybase recommends that you use JDBC driver to connect to unicode ASA databases.

If you previously received a private PowerBuilder EBF version containing newer file versions, do not install the PowerBuilder support files included in this version.

If you choose to install the PowerBuilder support files contained in this version:

  • Before installing this version, back up your existing PowerBuilder files by copying them to another location. Back up the following:

    • lib/*pb*

    • html/classes/pbjdbc12105.jar

  • In the setup program, on the Select Products to Install window, click Customize for Sybase EAServer features, and choose the PowerBuilder Support features.

  • After the installation completes, ensure that the corresponding PowerBuilder version is installed on PowerBuilder client machines. To run PowerBuilder components in EAServer, the runtime dynamic shared libraries for the version of PowerBuilder in which the components were developed must be available on the server. The PowerBuilder runtime files on the client and the server must be at the same build level. Using different build levels on client and server machines may result in unpredictable behavior or data corruption.

    You can download the corresponding PowerBuilder Windows client software from the PowerBuilder downloads page of the Sybase downloads site.

  • Use the Library Painter to perform a full rebuild of your PowerBuilder application to ensure that all descendant objects are synchronized with their ancestors and to incorporate any compiler fixes in your code.

Known issue

PowerBuilder with JDK 1.5 (CR #445330) If you use a previous version of PowerBuilder with JDK 1.5 in EAServer, some functions in PowerBuilder may not work.

To workaround this issue, use one of the following solutions:

  • Start EAServer with JDK 1.4 or JDK 1.3

  • Upgrade the existing version of PowerBuilder to 10.5 or later

Code set interoperability

By default, EAServer uses UTF-8 as the transmission code set. This applies to in-server intercomponent calls as well as component invocations from base clients. Since PowerBuilder does not support UTF-8, you must specify another encoding if your application uses character values greater than 127.

To specify the encoding for components, specify the component or server code set properties as follows:

  • For components, specify the Codeset setting on the General tab in the EAServer Manager Component Properties dialog box, or use jagtool or the Advanced tab to set the property.

  • For the server, specify the Codeset setting on the General tab in EAServer Manager Server Properties dialog box, or use jagtool or the Advanced tab to set the property.

To specify the encoding for clients, set the ORBCodeSet property in the PowerBuilder connection object.

Make sure the operating system locale is compatible with the code set used by the server, components, and clients. For example, if the operating system locale is zh_CN.gb18030 on the server machine, set the server code to gb18030. The client and server code sets do not need to match, but both must be compatible with the operating system locale. That is, the client code set must be compatible with the operating system locale on the client machine, and the server code set must be compatible with the operating system on the server machine.

Note:To support logging of localized messages from PowerBuilder components, the component code set and server code set must be identical, and the system locale must be compatible with the specified code set.

Borland JBuilder

Sybase provides an EAServer plug-in that allows you to develop, deploy, and debug EAServer components from Borland JBuilder. For more information, see Sybase EAServer Plug-in for JBuilder X.

Known issue Due to a change in the packaging of runtime classes in EAServer 5.5, deployment from JBuilder may not work after upgrading to EAServer 5.5. To correct this problem, add the java\lib\eastools.jar file from your EAServer 5.5 installation to the configured libraries in JBuilder, as follows:

  1. In JBuilder, select Tools | Configure Libraries...

  2. On the User Home | Sybase EAS Client | Class tab, click Add.

  3. Select the java\lib\eastools.jar file from you EAServer 5.5 installation.

  4. Click OK.


EAServer 5.5 does not include PowerDynamo™, though you can use an existing PowerDynamo installation with this EAServer version. Sybase recommends that you do not use PowerDynamo for new application development. Instead, use the J2EE-standard Java servlet and JSP technologies. Support for PowerDynamo will be removed from later versions of EAServer.

EAServer 5.5 includes the Dyn2JSP utility to convert PowerDynamo Web sites into JSP-based J2EE Web applications. Sybase recommends that you migrate your PowerDynamo Web sites to the J2EE model. For information on using the Dyn2JSP utility, see the HTML documentation included in the PDynamo2JSP directory of the installation.

Note:The Dyn2JSP utility converts static-file or dynamic-file sites. If your site is stored in a database, export it to a dynamic-file site before running the conversion.

Application Integrator

Application Integrator for CICS and Application Integrator for Stored Procedures are no longer included with EAServer. These products are available as open source on the EAServer CodeXchange pages.

Earlier EAServer (Jaguar CTS) versions

Clients using IIOP and earlier versions of the EAServer (or Jaguar CTS®) client runtime files can connect to EAServer 5.5. To manage EAServer 5.5, use a 5.5 installation to run EAServer Manager, jagtool, or a client that calls the EAServer management APIs.

Documentation updates and clarifications

This section contains updates and clarifications for the EAServer product manuals.

EAServer Web Services Toolkit User’s Guide

Chapter 2, Using Sybase Web Services Toolkit—an Eclipse plug-in

Error logging and debugging (CR #435547) In the SOAP inspector section, append the following details to view the SOAP messages:

To view the contents of the SOAP Inbound and Outbound messages:

  1. Select Sybase Web Services | Run ....

  2. Select Sybase Web Services Application in the Configurations treeview in Create, Manage, and Run Configurations dialog box.

EAServer Troubleshooting Guide

Chapter 1, Monitoring Techniques

EAServer log (CR #417448) If you have changed the default configuration, or run user-defined servers, the log file may not be Jaguar.log. To change or verify the log file name:

  1. Select Tools | Connect | EAServer Manager in Sybase Central to connect to EAServer plug-in.

  2. Double-click the EAServer Manager icon.

  3. Expand the connected host name to view the property folders. For example, the host name is the name of the machine that is connected to its default IIOP port number, 9000.
  4. Double-click the Log Profiles folder to expand the folders beneath it.

  5. Double-click prod in the Log Profiles folder.

  6. Select Handlers.

  7. In the right pane, right-click eas, and select Properties.

  8. Select the Type tab in the Handles Properties: eas dialog box and enter the file name in the File Name field.

  9. Click OK.

Chapter 2, Common Problem Areas

Verifying your configuration EAServer 5.5 does not include Merant DataDirect Connect Open Database Connectivity (ODBC) driver. Instead, it now comes with an ODBC driver manger, unixODBC on UNIX. Thus, the ODBC library path specified in the LD_LIBRARY_PATH environment variable for Sun Solaris is now read as:

Solaris platforms

Verify that LD_LIBRARY_PATH includes:


EAServer System Administration Guide

Chapter 4, Database Access

Reconfigure JDBC drivers properties

EAServer 5.5 supports jConnect™ for JDBC™ 6.0. Hence, you need to reconfigure the JDBC connection caches by modifying the instances of jdbc2 to jdbc3. The following lists the affected instances.

JDBC level 1 connection pool drivers (CR #399593) The Sybase jConnect level 1 driver class property should be com.sybase.jdbc3.jdbc.SybDriver.

JDBC level 2 connection pool drivers (CR #399593) The Sybase jConnect level 2 driver connection pool driver property should be com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource.

Table 4-1: UNIX platform connection libraries (CR #399593) If you are using a Sybase ASA or Adaptive Server Enterprise database, the values for the JDBC driver class properties should be:

  • com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource

  • com.sybase.jdbc3.jdbc.SybDriver

Table 4-2: Windows platform connection libraries (CR #399593) If you are using a Sybase ASA or Adaptive Server Enterprise database, the values for the JDBC driver class properties should be:

  • com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource

  • com.sybase.jdbc3.jdbc.SybDriver

Table 4-3: Connection libraries and XA resource libraries for Solaris (CR #399593) The XA resource library for JDBC database driver should be com.sybase.jdbc3.jdbc.SybXADataSource.

Table 4-4: Connection libraries and XA resource libraries for Windows (CR #399593) The XA resource library for JDBC database driver should be com.sybase.jdbc3.jdbc.SybXADataSource.

Configuring an XA resource (CR #399593) The value for the Driver property (DLL or Class Name) to configure the connection cache should be com.sybase.jdbc3.jdbc.SybXADataSource.

unixODBC library path

EAServer 5.5 does not include Merant DataDirect Connect Open Database Connectivity (ODBC) driver. Instead, it now comes with an ODBC driver manger, unixODBC on UNIX. Hence, the ODBC connection library path for SUN, AIX, and HP-UX in table 4-1 is as follows:

  • (installed in $JAGUAR/unixodbc/bin) for Solaris and AIX

  • (installed in $JAGUAR/unixodbc/bin) for HP-UX

Chapter 8, Setting up the Message Service

Using the Configure Message Service Wizard (CR #399593) The value for the database driver in the Note section in step 3 of the Configure Message Service Wizard setup should be com.sybase.jdbc3.jdbc.SybDriver.

Chapter 12, Using jagtool and jagant

sync Synchronizes entities in the current repository to one or more remote repositories. Synchronization can be used to create identically configured servers in a cluster, or to copy entities from one server to another.


Local mode support: No.

Command line:

sync connect-args
[-syncjavaclasses true|false]

Ant build file:

entity=”entity” />






When synchronizing Web application files, whether to include class files included in the Web application’s custom class list. This option has a higher priority than - syncjavaclasses [true | false].



Appendix B, Repository Properties Reference

Connection Cache XA properties (CR #381969) The connection cache XA properties are, as follows: This property specifies the DLL, shared library, or JDBC driver class name used for a two-phase commit (XA) connection. This property specifies the name of the server to connect to, which may be a URL for JDBC connection caches. This property specifies the XA resource DLL used to support two-phase commit transactions.

Server properties (CR #437931) Two new server properties are added for the extended log file format (ELFF) items to allow users to set the date and time in various formats. This property specifies date format (%Y-%m-%d %H:%M: %D GMT) in the ELFF items in the request log.


The ELFF datetimeformat options are:






Abbreviated weekday name. For example, Wed.


Complete weekday name. For example, Wednesday


Abbreviated month name. For example, Apr.


Complete month name. For example, April.


Date and time representation appropriate for locale


Day of the month as in decimal number (01-31)


Hour In 24-hour format (00-23)


Hour in 12-hour format (01-12)


Day of year as decimal in number (001-366)


Month as in decimal number (01-12)


Time in minutes as in decimal number (00-59)


Current locale’s A.M/P.M (as indicator for 12-hour clock)


Time in second as in decimal number (00-59)


Week of the year as in decimal number in which Sunday is the first day of the week (00-53)


Weekday as in decimal number (0-6; Sunday is 0)


Week of the year as in decimal number, with Monday as the first day of the week (00-53)


Date representation for current locale


Time representation for current locale


Year without century as in decimal number (00-99)


Year with century as in decimal number

%z, %Z

Time-zone name or abbreviated time-zone name


No character if time-zone is unknown.

See also This property specifies time format in the ELFF items.


true or false. The default is false.


If the property is set to false, the log file uses the GMT time. Otherwise, the log file uses the local time.

See also

EAServer Security and Administration Guide

Chapter 5, Using SSL in Java Clients

Using SSL in Java applications (CR #415788) The Requirements section provides the information about the runtime files and environment variable settings that are required when installing EAServer client runtime. You need to set the environment variable, JAGSSL to true in $JAGUAR/bin/ You need to create for EAServer to invoke.

EAServer Programmer’s Guide

Chapter 2, Understanding Transactions and Component Lifecycles

Resource recovery and transaction logging This section describes resource recovery, which enables object persistence and recovery operations. You can set the following recovery options on the Transactions tab in the Server Properties dialog box:

  • Enable Recovery – check to enable resource recovery. This value is stored in the property.

  • Recovery Log File Name – enter the name of the transaction log file, which the recovery manager reads to perform transaction recovery. You can specify either a file name only, or an absolute path to a file. If you specify a file name only, the file is created in $JAGUAR/bin or $JAGUAR/devbin. The default is <serverName>Recovery.log. The log file name is stored in the property.

  • Log File Size – enter the minimum size of the transaction log file; the default is 1MB. This value is stored in the property.

Chapter 23, Using Filters and Event Listeners

Application lifecycle event listeners (CR #399593) In the Sample listener example, the following com.sybase.jdbc2.jdbc.SybDriver should be replaced with com.sybase.jdbc3.jdbc.SybDriver in the section where it creates a database connection.

EAServer Performance and Tuning Guide

Chapter 4, EJB CMP Tuning

Using CMP JDBC wrapper drivers (CR #399593) In the section where it specifies Sybase wrapper driver, the connection cache properties for this wrapper driver used should be com.sybase.jdbc3.jdbc.SybDriver.

EAServer Feature Guide

Chapter 1: Introducing EAServer

Support for asynchronous messaging (CR #323517) If you are running the message service and your server is in a cluster, all the servers in the clusters must use the same repository.

EAServer Cookbook

Chapter 4: Creating Enterprise JavaBeans Components and Clients

Creating the connection cache (CR #399593) The value for DLL or Class Name in the Tab/Setting in the Connection Cache wizard should be com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource.

EAServer API Reference Manual

Chapter 5, C Routines Reference

JagCmCacheProps Routine (CR #405596) The property, JAG_CM_CACHEBYNAME found in JagCmCacheProp routine is incorrect. This property that appears in this routine should be replaced with JAG_CM_BYNAMEALLOWED. You may find this property in the Parameter and Usage sections.

Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.

Other sources of information

Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:

  • The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the SyBooks CD. It is included with your software. To read or print documents on the Getting Started CD, you need Adobe Acrobat Reader, which you can download at no charge from the Adobe Web site using a link provided on the CD.

  • The SyBooks CD contains product manuals and is included with your software. The Eclipse-based SyBooks browser allows you to access the manuals in an easy-to-use, HTML-based format.

    Some documentation may be provided in PDF format, which you can access through the PDF directory on the SyBooks CD. To read or print the PDF files, you need Adobe Acrobat Reader.

    Refer to the SyBooks Installation Guide on the Getting Started CD, or the README.txt file on the SyBooks CD for instructions on installing and starting SyBooks.

  • The Sybase Product Manuals Web site is an online version of the SyBooks CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.

    To access the Sybase Product Manuals Web site, go to Product Manuals.

Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications
  1. Point your Web browser to Technical Documents.

  2. Click Certification Report.

  3. In the Certification Report filter select a product, platform, and timeframe and then click Go.

  4. Click a Certification Report title to display the report.

Finding the latest information on component certifications
  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.

Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance
  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.

Accessibility features

EAServer 5.5 has been tested for compliance with U.S. government Section 508 Accessibility requirements. The online help for this product is also provided in HTML, JavaHelp, and Eclipse help formats, which you can navigate using a screen reader.

EAServer Manager supports working without a mouse. For more information, see Chapter 2, “Sybase Central Overview,” in the EAServer System Administration Guide.

The Web Services Toolkit plug-in for Eclipse supports accessibility features for those that cannot use a mouse, are visually impaired or have other special needs. For information about these features refer to Eclipse help:

  1. Start Eclipse.

  2. Select Help | Help Contents.

  3. Enter Accessibility in the Search dialog box

  4. Select Accessible User Interfaces or Accessibility Features for Eclipse

Note:You may need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.

For additional information about how Sybase supports accessibility, see Sybase Accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.


Last Revised: Dec 07, 2006
Part Number: DC38031-01-0550-01
Product: EAServer
Hardware Platform: Sun Solaris SPARC
Business or Technical: Technical
Content Id: 1049501
Infotype: Release Bulletin

© Copyright 2014, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics