> Release Notes > WebLogic RFID Edge Server Known Issues and Recommendations

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

WebLogic RFID Edge Server 2.0 is BEA's first release of the RFID Edge Server, which in previous releases was named ConnecTerra RFTagAware Edge Server. You can now reach technical support through the standard BEA means. Select Support on the BEA Web site, at www.bea.com, for more information.

The following sections document known problems and workarounds in WebLogic RFID Edge Server 2.0:

 

Issues with RFID Readers

Tracking Number
Description and Workaround
TT3977
The CAEN Technologies A928 RFID reader cannot successfully program a tag.
TT3957
The CAEN Technologies A928 RFID reader will not connect to the RFID Edge Server when JRockit 5.0 R26.1.0 (J2SE 1.5.0_04) is used as the JDK. (See Product Versioning in Introduction to BEA JRockit JDK for information about JRockit versions.)
Workaround or Solution:
Change the JVM to Sun's JDK 1.5.
TT4173
The ThingMagic Mercury4 reader firmware available at the time of this release supports no Gen 2 memory operations involving multiple tags in field.
TT4174
Due to a bug in the Symbol (Matrics) XR400 reader, the stack light will not reset itself after the display duration expires if you use the following configuration. The current color will stay on indefinitely.
  • Lib Mode
  • Bytestream protocol
  • Workflow module that specifies a finite number (not zero) for the Stacklight Display Duration.
Workaround or Solution:
Do either of the following:
  • Use the HTTP protocol in the configuration for the reader.
  • Use indefinite (zero) value for the display duration.
TT3734
Some versions of SAMSys MP9320 reader firmware can cause unreliable reporting when the reader is in poll mode and an antenna is disconnected but still has an ECSpec triggering from it. Tags read by functioning antennas may appear in ECReports associated with the disconnected antenna.
Workaround or Solution:
Suspend all ECSpecs (or subscriptions to those ECSpecs) for the logical readers representing the to-be-removed antennas before removing the antennas.
TT3722
Reading and writing Philips I-Code tags with a SAMSys MP9210 reader can be unreliable.
Workaround or Solution:
Change tag types, or take care to place I-Code tags to maximize reader accuracy.
TT3700
The SAMSys MP9210 reader can write to tags with different amounts of memory. The software cannot detect whether configuration settings will cause the reader to attempt to write beyond the memory available in a tag.
Workaround or Solution:
If in doubt about tag memory, make sure your application writes to tags as if they are 64-bit.
TT3730
If the SAMSys 9320 reader writes a 96-bit EPC to a 64-bit tag, the tag becomes unreadable and unwriteable. The reader will report that there is no tag in the field.
Workaround or Solution:
If in doubt about tag memory, make sure your application writes to tags as if they are 64-bit.
TT3455
Alien 9780 readers using firmware that does not support Class 1 Gen 2 tags may get the following error on the RFID Edge Server Administration Console:
Config command failed; command = Set TagType=23"; received response = "Error 10: Value out of range.
Legal limits are between 1 and 7."
Workaround or Solution:
Set the RF Protocol reader property to epcClass1 until a firmware version that supports Class 1 Gen 2 tags has been installed.
TT3707
The TAGSYS Medio L100 reader has two antennas. The TAGSYS Medio L200 reader has four antennas. Due to a bug in a third-party API, attempting to configure third and fourth antennas for a Medio L100 reader may cause unpredictable reading results.
Workaround or Solution:
Do not configure (nonexistent) third and fourth antennas for the Medio L100 reader.
TT3522
An Intermec Intellitag IF5 reader may not be able to interact with I-Code V1.19 tags if the reader has a version of firmware that allows the use of EPC Class 1 Gen 2 tags.

 

Miscellaneous Issues

Tracking Number
Description and Workaround
TT4036
You cannot import a PCSpec from one RFID Edge Server to another if it uses an EPC cache that is not defined in the target server.
Workaround or Solution:
Define the EPC cache before doing the import.
TT4085
JMS notifications may fail to restart after restarting WebLogic Server.
Workaround or Solution:
If you encounter this problem after restarting WebLogic Server, restart RFID Edge Server.
TT3728
(Linux systems only) After restarting the RFID Edge Server, the device browser tree in the RFID Edge Server Administration Console may not reflect changes.
Workaround or Solution:
In the RFID Edge Server Administration Console, select View > Refresh Device Browser.


  Back to Top       Previous  Next