|
|
Description and Workaround
|
|
|
Readers written against the pre-public driver interfaces in releases prior to Edge Server 3.0 must be updated.
You must rename the following:
- AbstractDispatchingPollingPhysicalReader ==> AbstractPollingPhysicalDevice
- AbstractPhysicalReader ==> AbstractPhysicalDevice
- AbstractPollingPhysicalReader ==>AbstractPollingPhysicalDevice
- Antenna ==> DeviceUnit
- AntennaCapabilities ==> DeviceUnitCapabilities
- AntennaObserver => DeviceUnitObserver
- AntennaReport => DeviceUnitReport
- AntennaRequest ==> DeviceUnitRequest
- PhysicalReader ==> PhysicalDevice
- PollingAntenna ==> PollingDeviceUnit
- PollingLogicalReader => PollingLogicalDevice
- PollingPhysicalReaderScheduler => PollingPhysicalDeviceScheduler
- ReaderConfigurationException => DeviceConfigurationException
- ReaderObserver => DeviceObserver
- ReaderUtil => DeviceUtil
- SimplePollingPhysicalReaderScheduler =>
- SimplePollingPhysicalDeviceScheduler
In addition, related method names were changed. For example, the method getAntenna is now getDeviceUnit.
A number of classes and methods have been deprecated in favor of the new SDK. New drivers should use only the classes and methods described in the SDK Javadoc.
|
|
|
The system returns license verification errors when attempting to deploy the Edge Server from a WAR file when running WebLogic Server 10.0.
- Edit the startWebLogic.cmd or .sh file that is under the /bin directory of WebLogic Server you are using (for example, /wlsinstalls/wls1000/user_projects/domains/base_domain/bin).
- Add the -Dbea.home=yourbeahome to the java command that starts WebLogic server:
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS}
|
|
|
When you attempt to perform operations on a version 2. x Edge Server using a version 3.0 Administration Console, the system returns warnings. Using the Edge Server 3.0 Administration Console to perform operations on an Edge Server 2. x system is not supported.
|
|
|
The Administration Console may hang on some Linux systems using NFS.
To work around this problem, unmount the NFS mounted files systems and restart the Administration Console.
|
|
|
During initialization of the Alien ALR-9800 driver, the following error message is displayed on the Edge Server console:
This message is generated by the Alien RFID library and can be ignored. Driver initialization completes successfully.
|
|
|
Starting the Edge Server with more configured devices than specified by your license, will result in one of the following problems:
- If allowBadDate=True (in the edge.props file), the Edge Server starts, but not all devices are configured. Files for devices that are not configured are moved to the /var/edgestate/bad directory.
Before you restart the Edge Server with the correct license, you must copy the files in the /var/edgestate/bad directory to the /var/edgestate directory.
- If allowBadData=False (in the edge.props file), the Edge Server does not start.
This problems is likely to occurr after you have updated your system from a previous release of the Edge Server.
To correct the problem, contact BEA support to get a license with the correct device count for your configuration.
|
|
|
Occasionally, the ThingMagic Mercury 4 driver returns an "unparsable response" error while reading a tag. Sometimes the reader returns invalid data while reading a Gen2 tag, probably because the tag is not encoded correctly.
|
| |
The Printronix SL5000r reader driver has the following limitations:
- Does not support permanent tag locking. In a PCSpec, if you specify permanent locking no tag programming occurs.
- Enables writing to kill password, access password, and epc memory banks only.
- You cannot write to the access and kill password memory banks without also specifying an epc.
- You cannot write to a tag which was locked previously. In a PCSpec, if you specify an existing access password it will be ignored.
- In a PCSpec, to specify tag locking, you must also specify a new access password; otherwise, no tag programming occurs.
- In a PCSpec, if you specify multiple lock and mask bits, only the last one specified is considered. The workaround is to specify all the lock bits and all the mask bits, each in a single element.
- In a PCSpec, if you specify not locking the access password and locking any of the other memory banks, the access password will also be locked.
- Short write timeout values will likely result in verification failures.
|
|
|
If the network connection to the SATO printer is lost, the Edge Server has difficulty reconnecting to the printer.
Restart the printer (power off and on).
|
|
|
If the network connection to the Impinj reader is lost, the Edge Server has difficulty reconnecting to the reader.
Restart the reader (power off and on).
|
|
|
In order to prevent a deadlock, the com.connecterra.ale.readerConcurrency property in edge.props must be 0 (the default) or greater or equal to the number of readers.
|
