> Release Notes > WebLogic RFID Edge Server Known Issues

Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

WebLogic RFID Edge Server Known Issues

The following sections describe the new features and document known problems in WebLogic RFID Edge Server 2.2.

 

What's New in WebLogic RFID Edge Server 2.2

 

Known Problems

The following section describes problems that were found in WebLogic RFID Edge Server 2.2. Entries include a description of the problem, and a workaround or solution where appropriate.

Change Request Number
Description and Workaround
CR302253
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.
CR282951
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.
Workaround or Solution:
Discard the tag.
 
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.
[vendor issue]
If the network connection to the SATO printer is lost, the Edge Server has difficulty reconnecting to the printer.
Workaround or Solution:
Restart the printer (power off and on).
[vendor issue]
If the network connection to the Impinj reader is lost, the Edge Server has difficulty reconnecting to the reader.
Workaround or Solution:
Restart the reader (power off and on).
CR284883
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.

 

Corrected Problems

The following section describes problems that were corrected in WebLogic RFID Edge Server 2.2.

Tagsys Reader Correction

The tag UID value reported for the Phillips_I_code RF Protocl was incorrect. The correct UID is 0x090000000FE024E5.


  Back to Top       Previous  Next