Known Issues and Bugs

The following known issues and bugs affect the operation of the MEP 1.0 release.

Client MIDlet Disappears on Palm Treo (Windows Mobile)

Problem Summary: When you launch a MIDlet on the Palm Treo with Windows Mobile and the IBM J9 JVM, the client GUI display seems to disappear; it is in the background.

Workaround: To bring the MIDlet to the foreground, close the Windows Mobile file explorer by clicking the X in the upper right hand corner.

Running the BlackBerry Client Sample Applications

The BlackBerry client applications all use the same directory on the filesystem: /home/user/pictures. The files are not removed when you erase a client application. Be aware that files written to the filesystem by the secure client will be visible to the nonsecure client, but will not be readable, since they will be encrypted.

Incorrect SMS User Name or Password Causes IllegalStateException

If you configure an incorrect Username or Password with the SMS tab of the Admin Console, and you try to send an SMS message to all user accounts from the Upload sub-tab of the Provisioning tab, you see a misleading error message in the synchronica.log file that reports an IllegalStateException. It does not mention the incorrect username or password that is the real problem. The error message looks something like this:

ERROR [StandardSendShortMessageUseCase] Send SMS to phone number '+17815551212' with 
short message 'Hello! There is a new MEP client available for download at 
http://129.148.71.115:8080/sync/admin/client' has failed: Failed to send text SMS; 
nested exception is: java.lang.IllegalStateException: not bound 

Installation of Enterprise Tier Generates Database Warnings

When you install the second tier (the Enterprise tier) of a two-tier MEP installation, two warnings appear near the end of the installation process, as a result of the execution of a deployRar and a deployWar target. The warnings look like this:

Command deploy executed successfully with following warning messages: WARNING:

JDO76614: Deployment encountered SQL Exceptions:
       JDO76609: Got SQLException executing statement "CREATE TABLE DBCREDENTIALS 
(USERNAME VARCHAR(255) NOT NULL, BACKENDUSERNAME VARCHAR(255), BACKENDPASSWORD 
VARCHAR(255), PRIMARY KEY (USERNAME))": java.sql.SQLException: Table 'dbcredentials' 
already exists

You can safely ignore these warnings.

MySQL Character Set Value Can Cause Installation Errors

If you use MySQL as the MEP Sync database, make sure that the default character set is latin1. A setting of utf8 causes installation errors that look like this:

JDO76614: Deployment encountered SQL Exceptions:
       JDO76609: Got SQLException executing statement "CREATE TABLE PARSTAMPBEAN 
(TIMESTAMP9 BIGINT NULL, PARFILE VARCHAR(256) NOT NULL, CONSTRAINT PK_PARSTAMPBEAN 
PRIMARY KEY (PARFILE)) ENGINE=InnoDB": java.sql.SQLException: Specified key was too 
long; max key length is 767 bytes
       JDO76609: Got SQLException executing statement "CREATE TABLE PARCOUNTERBEAN 
(COUNTER BIGINT NULL, COUNTERNAME VARCHAR(256) NOT NULL, CONSTRAINT PK_PARCOUNTERBEAN 
PRIMARY KEY (COUNTERNAME)) ENGINE=InnoDB": java.sql.SQLException: Specified key was too
long; max key length is 767 bytes

To change the character set, you can restart MySQL with a particular character set, as described in Server Character Set and Collation. On Windows, you can run the MySQL Server Instance Config Wizard to change the character set.

Use of Apache Ant 1.7 Causes Installation to Hang

MEP installation does not work with Apache Ant 1.7 releases. The installer script is designed to use the copy of Ant 1.6.5 that is built into the version of Application Server installed with MEP. You may have a release of Ant 1.7 on your system, but do not set the ANT_HOME environment variable to point to it; otherwise, MEP installation will hang.