GigaSpaces 6.0 Known Issues

                                               
Summary: Known issues in GigaSpaces 6.0 GA (build 1855).

Open Spaces

  • GS-2508 – Base event listener result-handler class should throw an exception if updateMultiple is returned with an exception, causing a possible transaction to rollback the operation.
  • GS-2552 – A NullPointerException is thrown when configuring both giga-space-context and giga-space-late-context.

Configuration, Jini Services and Tools

  • 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-1864 - A ClassCastException is thrown when using two different transaction managers in the same space.
  • GS-2263 - Locators and Groups information for a space are getting appended when an IWorker has code to find a Space handle for another space. Support case ID: 3062.
  • GS-2496 - GigaSpaces scripts can not run when installed in a path which contains spaces.

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-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

See the External Data Source known issues.

See the Mirror Service known issues.

  • GS-441 - When shutting down the space, a few threads are not shut down:
    • Thread 0=multicast discovery announcement listener
    • Thread 1=multicast announcement timer
    • Thread 2=LookupDiscovery Task
    • Thread 3=LookupDiscovery Task
    • Thread 4=LookupDiscovery Task
    • Thread 5=gigaSpace Liveness-monitor
    • Thread 6=gigaSpace Liveness-detector
    • Thread 7=ClusteredXtnThread-gigaSpace_container1:gigaSpace
    • Thread 8=SpaceVersionTable$EntryVersionCleaner
    • Thread 9=Replicator-finder-report
  • 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 (Externalizable without NoWriteLease mode works fine). 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).
  • GS-115 – Externalizable does not support versioning. It does set the version to 1 in write, but fails to increase it in update.
  • DropClass is not supported in a partitioned space.
  • GS-2548 – Output replication filter does not work on recovery. Support case ID: 3142.
  • GS-2311 – When using a persistence space with LRU, runtime info does not return the correct number of objects in the space. Support case ID: 3071.
  • GS-2292 – Trying to create a local view on with a POJO that in FIFO mode throws an exception. Workaround: Add &fifo to the space URL. Support case ID: 3088.
  • GS-2409 – Writing an Entry with a small lease, and writing or updating the same Entry (meaning the same UID), throws an exception. Workaround: Perform write with an Entry UID using a replication filter. Support case ID: 3104.
  • GS-2509 – OutOfMemory is thrown in the client when performing readMultiple/takeMultiple – the application keeps running, but a thread is stuck and the call is not returned. Support case ID: 3127.
  • GS-2261 – Unable to write the same object under different uncommitted transactions.
  • GS-2436 – Lease is not supported for transient Entries with persistent LRU.
  • GS-2544 – The ability to filter out Entries before they enter the space (discard them), is not supported.
  • GS-2273 – A NullPointerException is thrown in JSpaceProxyUtil.hashcode when calling readIE on an ExternalEntry.
  • GS-2581 – When registering for multicast notifications, the space requires the user object (Entry, POJO) to be in the classpath.
  • GS-2312 – Inconsistent behavior when creating a transaction with leaseTime=0.
  • GS-2420 – Notify recovery is performed when replicate-notify is false.
  • GS-2596 – The MultiplexNotifyDelegator doesn't support externalizable notifications.
  • GS-2603 – Setting an incorrect <replication-mode> in a cluster schema file does not generate an error.
  • GS-2256 – TokenQuery does not support POJOs.
  • GS-2602 – Trying to set recovery chunk size through the com.gs.recovery_chunk_size system property doesn't seem to change the recovery configuration.
  • GigaSpaces XA transactions can not span over different spaces in the same cluster. For example, writing an object to Member1 under a transaction, and then writing another object to Member2 under the same transaction, does not work. In order to make this work, make sure that you write the object to the same cluster member (e.g. using SpaceRouting). For more details, see the GigaSpaces XA Transaction Support section.

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-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.
  • Read timeout operation is ignored if the template used is a SQlQuery.
  • GS-2240 – When creating a SQLQuery the space filter does not state if the operation is bigger, smaller, equal, etc. Support case ID: 3068.
  • GS-2394 – Issuing a notification registration with an SQLQuery that contains OR operators is not supported. Support case ID: 3105.
  • GS-2518 – Select query from java.lang.Object throws an exception.
  • GS-3118 – SQL queries might return a wrong result when the query contains routing index and the partitioned schema is used. The above happens only when the query contains all of the Entry fields, due to an incorrect ordering of the fields in the load-balancing mechanism.

POJO and Spring

  • GS-1698 - *.gs.xml files are not found using the application class loader when the space loads.
  • GS-2255 – spaceCopy can not be performed with a POJO template.

JMS

See the JMS known issues.

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.

.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-2467 – Potential concurrency problem when introducing new types from multiple threads to the same proxy. Workaround: Introduce all types in the beginning.
  • GS-2277 – - GUID array serialization problem. The interoperability of an array of UUID (GUID) is not supported.
  • 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.
  • Read timeout operation is ignored if the template used is a SqlQuery.
  • DropClass (Clean(Type)) is not supported in a partitioned space.
  • GS-2277 – GUID arrays are not mapped to UUID arrays due to a CodeMesh problem. Instead, they are treated as user defined objects.

Important Tips:

  • If the gs.xml contains a definition of a DTD file, it must be available at runtime (otherwise an exception is thrown). 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).
  • The default logger writes on the Windows Event Viewer – Application log.
    Please configure the Event Viewer – open the Event Viewer - Application log properties, and select Overwrite events as needed.

Service Grid

  • GS-2310 – 64-bit issue when deploying with the Service Grid on AMD using a native lib. Support case ID: 3097.

Labels

 
(None)