WebLogic RFID Edge Server SP 1 Known and Resolved Issues

Install WebLogic RFID Edge Server 2.1 Service Pack 1 by following the instructions in Installing WebLogic RFID Edge Server. If you are upgrading your WebLogic RFID Edge Server 2.1 installation to WebLogic RFID Edge Server 2.1 Service Pack 1, the upgrade installer lets you install the latest software while preserving your existing configuration information. Prior to upgrading, read and follow the steps in Backing Up Your System in Installing WebLogic RFID Edge Server.

The following sections describe the new features and document known problems in WebLogic RFID Edge Server 2.1 Service Pack 1.

For known problems and workarounds in WebLogic RFID Edge Server 2.1, see the 2.1 Release Notes.

What's New in WebLogic RFID Edge Server 2.1 SP1

Known Problems

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

Tracking Number	Description and Workaround
	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.