GigaSpaces 6.0 RC1 Known Issues

Added by Limor Maayan, last edited by Aleia Hutcherson on Jul 02, 2008  (view change)
Search Release Notes
Searching Release Notes
Browse Release Notes
GigaSpaces Early Access Program
GigaSpaces Release Notes
Release Notes Archives

                                                              
Summary: Known issues in GigaSpaces 6.0 RC1 (build 1809).

Configuration, Jini Services and Tools

  • GS-2161 - Configuring custom log handlers is not yet supported.
  • GS-2186 - startJiniTX_Mahalo script starts a stand alone Mahalo with a wrong codebase. Workaround: Set -Dcom.gs.start-embedded-mahalo=true to start an embedded Mahalo service inside the space container.
  • GS-2216 - In a non-multicast environment, it appears that a client may not "re-acquire" a Lookup Service after all Lookup Services have been killed.
  • GS-2176 - Windows script fails when setting the LOOKUPGROUPS variable with a comma-separated list of locators in the setenv script. Workaround: Specify the list of locators as a SpaceURL locators attribute.
  • GS-1864 - A ClassCastException is thrown when using two different transaction managers in the same space.

GigaSpaces Management Center

The new GigaSpaces Management Center includes the Space View tab, formerly known as the GigaSpaces Browser, and the Deployments tab, formerly known as the Service Grid UI.
  • GS-1541 - In the Object Inspector, the UserDefinedClass is shown as string.
  • GS-1413 - A POJO with nullValue(100) is presented in the Space View with a value of 0, when the actual value is 100.
  • GS-656 - SQL tables show incorrect values in Double type fields.
  • GS-508 - The GigaSpaces Management Center becomes unresponsive if the temp directory does not exist or is not accessible. Workaround: Configure the temp directory: 
    -Djava.io.tmpdir=<path>
  • GS-766 - The target machine derived when docking a window is not taken into account. An arbitrary machine is taken from the available pool of machines. Moreover, the Deployments tab is not refreshed automatically. getAdmin fails when using a clustered proxy, meaning re-deploy with a clustered proxy does not work at all at this stage.
  • GS-2085 - Using the Object Inspector with objects that are written to the space using light serialization throws a java.lang.ClassCastException. Workaround: Use object snapshot instead.

Core

  • Disabling the take operation using the replication matrix does not work.
  • When shutting down the space, a few threads are not shut down:
    • multicast announcement timer
    • multicast discovery announcement listener
    • gigaSpace Liveness-monitor
    • gigaSpace Liveness-detector
    • ClusteredXtnThread-gigaSpace_container1:gigaSpace
    • SpaceVersionTable$EntryVersionCleaner
  • GS-1386 - An OutOfMemoryError might be thrown when loading very large objects from the database.
  • GS-1414 - A SpaceSecurityException is thrown when trying to restart a secured space.
  • GS-1420 - Filter Replication output mode shares the same data with remote spaces.
  • GS-1444 - writeMultiple can not be called on Entries in an object array.
  • GS-1758 - When writing an externalizable Entry with __setEntryUID, the UID can not be obtained.
  • GS-1748 - Unable to copy Entries to a secured space using IRemoteJSpaceAdmin.spaceCopy().
  • GS-1688 - LRMI Thread pool: LRMI client-side distributed cache configuration is not set - server-side configuration is used instead.
  • GS-143 – A deadlock occurs in persistent spaces when there are a low amount of connections. Workaround: Increase max_sa_connections in the space schema file (a few hundreds).
  • GS-1414 – Secured spaces cannot be restarted – a SpaceSecurityException is thrown.
  • GS-1662 – Space Entry classes implementing the Entry interface must have setters and getters (as POJOs) when used with Mirror or CacheLoader/CacheStore. Workaround: Add setters/getters to all public attributes.
  • GS-1688 – The client side distributed cache configuration of the LRMI (LRMI Thread pool) is not overridden, and the server side configuration is used instead.
  • GS-1825 – The CacheLoader/CacheStore load by key returns null on a call to IGSEntry.getUID().
  • GS-2103 – Space operations throw a TransactionException when under a transaction and failover occurs.
  • GS-142 – A non comprehensive exception is thrown when trying to commit a nested transaction.
  • GS-149 – When calling update() with timeout, the AFTER_UPDATE filter event is never called.
  • GS-156 – In Serialization mode 1, 2, or 3, a ClassCastException is thrown when ExtendedMatchCodes are used. Workaround: Work in Serialization mode: 0.
  • GS-488 – POJOS don't support null templates – cannot derive general inheritance semantics. Workaround: Use a plain object (new Object()).
  • GS-572 – The ExternalEntry.routingFieldName doesn't include the first index as its default value, in case the user did not specified one. Workaround: Set routingFieldName.
  • GS-1748 – Copying Entries to a secured space by calling the IRemoteJSpaceAdmin.spaceCopy() method does not work.
  • GS-1772 – When a space schema is saved using the GigaSpaces Management Center, a few tags disappear from the XML file. The tags that disappear are mainly newly updated tags, related to filters/workers.
  • GS-1936 – When missing a setter for a POJO class field, a Failed to convert the POJO to Entry.. exception is thrown. When using an annotation to the same class, this field's value is null. Workaround: Add setters/getters.
  • GS-1964 – Load-balancing timeout is correlated with fail-over-find-timeout.
  • GS-1978 – space.readMultiple(template,null,0) gets stuck. Workaround: Avoid using a 0 value.
  • GS-2110 – Externalizable with NoWriteLease does not set the UID. The UID is not set only in MetadataEntry, and fails in: POJO, ExternalEntry(lookout DotNet), Entries with __setEntryInfo(). Work around: If a UID is needed – use read after write, or create your own UID (like autoGenerate=false in a POJO).

    Working without NoWriteLease mode returns the UID, and works fine. However, an Externalizable Entry with __setEntryInfo() does not return the UID, even with NoWriteLease.
  • GS-115 – Externalizable does not support versioning. It does set the version to 1 in write, but fails to increase it in update.

Query Engine

  • GS-1623 - SQLQuery doesn't completely support querying primitive fields - querying these fields doesn't return any result.
  • GS-1720 - SQL Queries or Local View with externalizable objects - when using an SQL Query with a null expression and an externalizable POJO when registering for notifications in a remote space, a ClassCastException exception is thrown.
  • GS-1385 - Fixed: A NullPointerException was thrown when using HibernateDataSource.init().
  • GS-1937 – When using SQLQuery with the JavaSpaces API (read, readMultiple, etc.) and a POJO template, the template parameter must be cast to Object, otherwise an Entry is returned.
  • GS-2013 – SQLQuery does not support .NET generics.

POJO and Spring

  • GS-1552 - A NullPointerException is occasionally thrown when reading a POJO from the space under load.
  • GS-1698 - *.gs.xml files are not found using the application class loader when the space loads.

JMS

J2EE/JCA

  • GS-452 - Permission issues when running an embedded Lookup Service in an embedded space, that is running integrated in a WebSphere AppServer. Workaround: Do not run an embedded Lookup Service when running a space inside the AppServer process. Instead, you can disable it setting -Dcom.gs.start-embedded-lus=false and start a stand alone Lookup Service.

.NET and C++

  • GS-1765 – DateTime values are converted to the space with a wrong value – the problem occurs when PONO fields include dates around the 1/1/01. Once read from the space, the value is correct again.
  • GS-1193 – The .NET and C++ interfaces cannot be run from the same process.
  • GS-1770 – DateTime fields which contain fractions of milliseconds are not stored precisely. Since there is a difference in precisions, microseconds might be lost.
  • GS-1776 – Unsigned types are treated as user-defined objects. Since no Java objects match unsigned .NET types, they are stored in the space as user-defined objects and not as Java primitives.
  • GS-1938 – .Net-Java interoperability limitation: When mapping a .NET array to a Java array, an Incompatible Class Change Error exception might be thrown.
  • Distributed transactions (Jini transactions) can not be created directly from the .NET API. Jini transactions must be constructed using the exposed CodeMesh API.
  • PONOs with generics are displayed with textual representation of characters:
    • [ is represented by GS_LEFT_BRACKET.
    • ] is represented by GS_RIGHT_BRACKET.
    • , is represented by GS_COMMA.
    • ' is represented by GS_APOSTROPHE.
Important Tips:
  • The DTD file defined in gs.xml must be available when loading the gs.xml file. An exception is thrown if the file is not found when loading the .gs.xml file. Workaround: If the file is not available through the Web, it can always be defined through the DTD to a local path.
  • The space supports only UTC time format:
    • A date time written to the space is always stored as UTC.
    • If a GMT format is used, it is converted to UTC and stored in the space.
    • Once a DateTime value is returned, it is returned as UTC.
    • The GigaSpaces Management Center displays time using the current local time, and not UTC.
  • When using the gs.xml file, System.IO.PathTooLongException is thrown when a class is created under a deep namespace (the Windows limitation is 255 characters).

Service Grid

  • Using Focal server with Java 6 is problematic.

Additional resources: XAP Application Server | XAP Data Grid | XAP for Cloud Computing | XAP J2EE Support

Labels

 
(None)