Known Issues and Bugs

The following known issues and bugs affect the operation of the Sun GlassFish Mobility Platform 1.1 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 

MySQL Character Set Value Can Cause Installation Errors

If you use MySQL as the Sun GlassFish Mobility Platform 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.

J9 JVM Does Not Support Sun GlassFish Mobility Platform Client Provisioning

The client provisioning feature in Sun GlassFish Mobility Platform 1.1 does not work with the J9 JVM on the Palm mobile devices.

Excessive Prompting with Some Unsigned Client Applications on Some Mobile Devices

Problem Summary: The Sun GlassFish Mobility Platform 1.1 client bundle includes several unsigned mobile client applications. Java ME JVMs that strictly follow security requirements may excessively prompt users before allowing data retrieval and writing. The MusicDB client application running on the Palm device requires the user to answer approximately 30 prompts before the application can be run. The Salesforce client application on the Palm device never stops prompting, rendering the application on that device unusable. The same application on the BlackBerry device, however, does not prompt the user at all.

Workaround: If you have a Palm device, it is recommended that you run the Salesforce client application using the Windows Toolkit emulator.

FastInfoset.jar and jaxb-impl.jar Files Missing From Sun GlassFish Enterprise Server v2.1

Problem Summary: Under certain conditions, Sun GlassFish Mobility Platform performance may be slower than it should be. This degradation is caused by the removal of the FastInfoset.jar and jaxb-impl.jar files from the Sun GlassFish Enterprise Server v2.1 distribution.

Workaround: Download the appropriate JAR files for FastInfoset 1.0 and JAXB 2.2 and put them in your classpath.

Can't View the Sun GlassFish Mobility Platform Log With Internet Explorer

Problem Summary: The Show Log function on the Edit Users tab in the Sun GlassFish Mobility Platform Administration Console does not work with Internet Explorer. This problem has been filed as CR 6803604.

Workaround: Use a different browser, such as Mozilla Firefox, to view the log.

Synchronica Log Contains Irrelevant Data

Problem Summary: Although all logging in the Sun GlassFish Mobility Platform product now uses the Sun GlassFish Enterprise Serverlogging capability, a Synchronica log file (domains/mep/lib/ds/log/synchronica.log) is still created. This log file contains meaningless data.

Workaround: Ignore the Synchronica log file.

Searching Provisioned Archives Returns Incomplete results

Problem Summary: Searching provisioned archives returns BlackBerry archives only.

Workaround: Use the Repository tab in the Sun GlassFish Mobility Platform Administration Console to view all archived repositories. Client applications can see all archived bundles that have been provisioned by browsing http://gateway_hostname:8080:/sync/admin/client.

Improper Sync Type Could Be Performed with Salesforce Sample Application

Problem Summary: When directed to perform a synchronization, the Salesforce sample application will perform an initial synchronization the first time the Salesforce sample application is run or after local data has been deleted from the client using the Delete function under Options. This is the expected behavior. After the initial synchronization, however, the Salesforce sample application will continue to perform restoration (initial) synchronizations only; no updates will be sent from the client to the server, even if new data on the client has been created. This issue only arises when there is no data on the client.

Workaround: Exit the application after the initial synchronization completes. Then restart and reenter the application.