Developer Guide

Back Next

Troubleshooting Custom Entity Types

The custom entity does not appear in the Administrator tool :: This error occurs if the plug-in is not registered correctly. Check the
<EDS Installation Directory>/admind/logs/register.log
file for errors and correct them.

I get an error when I register a custom entity.: This error occurs if you are using the
Send to
Compressed (zipped) folder
option in Windows to create the custom entity ZIP file. Use a different ZIP utility to create the custom entity ZIP file. For example, you can use the Windows WinZip utility.

I get an error when I upgrade a custom entity.: This error can occur if ZooKeeper is down when you upgrade the custom entity. A ZooKeeper connectivity exception occurs in the
<EDS Installation Directory>/admind/logs/upgrade.log
file.
Navigate to the following directory:
<EDS installation directory>/admind/bin
To verify the status, run the following command:
./admind.sh status
If you have installed a version of ZooKeeper that is not part of the EDS installation package, navigate to the following directory:
<EDS installation directory>/zookeeper/bin
To verify the status, run the following command:
./zkServer.sh status
If ZooKeeper is not running, use the following command to start it:
./zkServer.sh start

The custom entity that I created does not behave as expected.: To identify the cause for the unexpected behavior, you can attach a debugger to the EDS Node.
To attach a debugger, perform the following steps:
Navigate to the following directory:
<EDS installation directory>/node/bin
Edit the
node.bat
file on Windows and edit the
node.sh
file on Linux.
Include the following line in the
JAVA_OPTS
configuration:
-Xdebug;-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9699
For example,
SET "JAVA_OPTS=-Xms256m;-Xmx2G;-XX:+UseCompressedOops;-XX:+UseConcMarkSweepGC;-XX:CMSInitiatingOccupancyFraction=70;-XX:MaxDirectMemorySize=512m;-Dio.netty.leakDetectionLevel=disabled;-DINFA_HOME=%PRODUCT_HOME%;-Dnodename=%NODENAME%;-Dhostname=%HOSTNAME%;-Dlogdir=%LOGS_DIR%;-Dlog4j.configuration=%PRODUCT_HOME%/config/log4j.properties -Xdebug;-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9699
"
Save and close the file.
On Windows, additionally perform the following steps:
Run the following command to uninstall the EDS Node:
Node.bat uninstall <hostname>
Run the following command to install the EDS Node:
Node.bat install <hostname>
You can attach the EDS Node to a remote debugger with the port 9699.

When I run the Maven install command to create a custom entity using the Maven archetypes, I get the following warnings in the Eclipse console:: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
These warnings occur if you are using the Eclipse version Kepler or earlier versions. Upgrade the Eclipse version to Luna or a newer version.