|
From: Jonas H. <jh...@us...> - 2007-08-17 10:30:58
|
Dear Boppana, A first problem i noticed is the order you discribed in your mail: > I have used reader client and configured it to capture events > Started Event Sink > Added a new tag to Shelf 1 > But this event is not shown in Event Sink The reader establishes a connection to the sink when the command to create a notification channel is sent. If you configured the reader and started the event sink afterwards, no connection is established for the notification channel. When you close the reader and a connection was established, a message should appear in the EventSinkUI that sais 'ERROR: connection reset'. If this message does not appear, there was no connection and thus no notifications were able to reach the EventSinkUI. A potential second problem i noticed in your mail is the usage of non default DataSelector. The DataSelector was buggy and is still buggy in the latest release. I fixed it in the current developer version last week. For further testing of accada, please leave away the DataSelector configuration (steps 4 to 7 in your list of configuration commands below) until next release of a new accada version. Kind regards, Jonas On 8/16/07, Matthias Lampe <la...@in...> wrote: > > > Dear Boppana, > > > Thanks for your using Accada! I am currently travelling but will take a > look at the issue you describe beginning next week. We also fixed several > bugs in the reader module and planing a release for end of next week which > might also deal with your issues. > > Best > Matthias > > > ________________________________ > > > From: acc...@li... > [mailto:acc...@li...] On Behalf Of > Shanthi Boppana > Sent: Dienstag, 14. August 2007 23:02 > To: acc...@li... > Subject: [accada-reader-user] Accada Reader > > > > Hi, > > > I have downloded accada reader and reader client. > > > I am trying to capture reader events using > org.accada.reader.rp.client.EventSinkUI 9001 > > On the reader command line console I do see the debug statement when a > tag is read by the reader but I am not able to see the events using > EventSinkUI. > > > I have used reader client and configured it to capture events > Started Event Sink > Added a new tag to Shelf 1 > But this event is not shown in Event Sink > > > Here is my reader configuration: > > > 1) Create Notification Channel > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>44</id> > <targetName></targetName> > <notificationChannel> > <create> > <name>test</name> > <address>tcp://localhost:9001?mode=connect</address> > </create> > </notificationChannel> > </ns2:command> > > > > > 2) Creating Read Trigger > > > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>28</id> > <targetName></targetName> > <trigger> > <create> > <name>ReadTrigger2</name> > <triggerType>TIMER</triggerType> > <triggerValue>100</triggerValue> > </create> > </trigger> > </ns2:command> > > > 3) Creating NotificationTrigger > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>30</id> > <targetName></targetName> > <trigger> > <create> > <name>NotificationTrigger</name> > <triggerType>TIMER</triggerType> > <triggerValue>500</triggerValue> > </create> > </trigger> > </ns2:command> > > > > 4) Create DataSelector > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>46</id> > <targetName></targetName> > <dataSelector> > <create> > <name>DataSelector</name> > </create> > </dataSelector> > </ns2:command> > > > > 5) Adding Event Filters to Data Selectors > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>52</id> > <targetName>DataSelector</targetName> > <dataSelector> > <addEventFilters> > <eventType> > <list> > <value>EV_OBSERVED</value> > <value>EV_LOST</value> > </list> > </eventType> > </addEventFilters> > </dataSelector> > </ns2:command> > > > > 6) Adding Field Names > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>54</id> > <targetName>DataSelector</targetName> > <dataSelector> > <addFieldNames> > <fieldNames> > <list> > <value>EVENT_TYPE</value> > <value>READER_NAME</value> > <value>TAG_ID</value> > <value>TAG_ID_AS_PURE_URI</value> > <value>TAG_ID_AS_TAG_URI</value> > <value>SOURCE_NAME</value> > </list> > </fieldNames> > </addFieldNames> > </dataSelector> > </ns2:command> > > > > 7) Setting DataSelector > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>58</id> > <targetName>test</targetName> > <notificationChannel> > <setDataSelector> > <dataSelector>DataSelector</dataSelector> > </setDataSelector> > </notificationChannel> > </ns2:command> > > > 8) Setting NotificationTrigger > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>64</id> > <targetName>test</targetName> > <notificationChannel> > <addNotificationTriggers> > <triggers> > <list> > <value>NotificationTrigger</value> > </list> > </triggers> > </addNotificationTriggers> > </notificationChannel> > </ns2:command> > > > > 9) Add Current Source to Notification Channel > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>70</id> > <targetName>test</targetName> > <notificationChannel> > <addSources> > <sources> > <list> > <value>Shelf1</value> > </list> > </sources> > </addSources> > </notificationChannel> > </ns2:command> > > > > 9) Add Read Trigger to Source > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>82</id> > <targetName>Shelf1</targetName> > <source> > <addReadTriggers> > <triggers> > <list> > <value>ReadTrigger2</value> > </list> > </triggers> > </addReadTriggers> > </source> > </ns2:command> > > > Any help is greatly appreciated > > > -Boppana > -- Jonas Haller <jh...@us...> |
|
From: Shanthi B. <sha...@gm...> - 2007-08-20 19:00:08
|
On 8/20/07, Shanthi Boppana <sha...@gm...> wrote:
>
>
> Dear Jonas,
>
> I mentioned the order wrong in the email. I took your advise and did not
> configure DataSelector but i am still not able to capture events in
> EventSinkUI
>
> I alway get an error on first attempt during
>
> - setting notification trigger
> - and adding read trigger to the source
>
> But when I use the same xml and try it for second time it goes through
> fine.
> Following are the exact step I following along with reader log:
>
*Starting Reader:*
C:\RFIDDEV\reader\reader-rprm-core-0.3.1>java -jar
reader-rprm-core-0.3.1.jar
0 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer -
**************
************************
0 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer - *
MessageLayer
is beeing initialized *
0 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer -
**************
************************
47 [main] DEBUG org.apache.commons.configuration.ConfigurationUtils -
Configu
ration loaded from the context classpath (props/ReaderDevice.properties)
297 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer - creating
an In
comingMessageBuffer
297 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer - creating
Clien
ts
297 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer - creating
an Ou
tgoingMessageDispatcher
297 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer - creating =
a
Ser
viceDispatcher
359 [main] DEBUG org.apache.commons.configuration.ConfigurationUtils -
Configu
ration loaded from the context classpath (props/ReaderDevice.properties)
375 [main] DEBUG org.accada.reader.hal.ControllerProperties -
PropertiesFile:
SimulatorControllerProperties.properties
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Trying to
get Pa
rameter simType from file SimulatorControllerProperties.properties
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Property
found:
simType =3D org.accada.reader.hal.impl.sim.GraphicSimulator
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Trying to
get Pa
rameter numberOfReadPoints from file
SimulatorControllerProperties.properties
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Property
found:
numberOfReadPoints =3D 4
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Trying to
get Pa
rameter readPoint_1 from file SimulatorControllerProperties.properties
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Property
found:
readPoint_1 =3D Shelf1
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Trying to
get Pa
rameter readPoint_2 from file SimulatorControllerProperties.properties
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Property
found:
readPoint_2 =3D Shelf2
390 [main] DEBUG org.accada.reader.hal.ControllerProperties - Trying to
get Pa
rameter readPoint_3 from file SimulatorControllerProperties.properties
406 [main] DEBUG org.accada.reader.hal.ControllerProperties - Property
found:
readPoint_3 =3D Shelf3
406 [main] DEBUG org.accada.reader.hal.ControllerProperties - Trying to
get Pa
rameter readPoint_4 from file SimulatorControllerProperties.properties
406 [main] DEBUG org.accada.reader.hal.ControllerProperties - Property
found:
readPoint_4 =3D Shelf4
406 [main] DEBUG org.accada.reader.hal.impl.sim.SimulatorController -
Simulato
r: org.accada.reader.hal.impl.sim.GraphicSimulator
625 [main] INFO org.accada.reader.hal.impl.sim.GraphicSimulator -
GraphicSimu
lator started
781 [main] DEBUG org.accada.reader.rprm.core.mgmt.alarm.AlarmChannel -
Managem
ent agent not yet initialized: Cannot register at the management agent.
781 [main] INFO org.accada.reader.rprm.core.msg.MessageDispatcher -
Initializ
ing the dispatcher!
781 [main] DEBUG org.accada.reader.rprm.core.msg.MessageLayer - creating
Servi
ceConnection
781 [Thread-16] INFO org.accada.reader.rprm.core.msg.MessageDispatcher -
Disp
atcher is now waiting for incoming messages!
781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.IncomingMessageBuffe=
r
-
Message removed from buffer!
781 [Thread-16] INFO org.accada.reader.rprm.core.msg.IncomingMessageBuffe=
r
-
Dispatcher is waiting for next message...
*797 [main] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpServerConnection*
* - Trying to open port 8000*
*797 [Thread-20] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpServerConne*
*ction - Listening to port 8000*
*797 [main] DEBUG
org.accada.reader.rprm.core.msg.transport.TCPServerConnection*
* - Trying to open port 5566*
*812 [Thread-21] DEBUG
org.accada.reader.rprm.core.msg.transport.TCPServerConnec*
*tion - Listening to port 5566*
890 [main] DEBUG org.snmp4j.security.Salt - Initialized Salt to
dd5daae4c3332d
79.
1015 [main] INFO org.snmp4j.agent.mo.snmp.NotificationOriginatorImpl -
Notific
ation 1.3.6.1.6.3.1.1.5.1 issued with []
1015 [DefaultUDPTransportMapping_127.0.0.1/161] INFO
org.snmp4j.transport.Defau
ltUdpTransportMapping - UDP receive buffer size for socket 127.0.0.1/161 i=
s
set
to: 8192
*2) Started EventSink using following command*
C:\RFIDDEV\reader\reader-rp-client-0.3.1>java -cp reader-rp-client-0.3.1.ja=
rorg
.accada.reader.rp.client.EventSinkUI
*3) Started Reader Client using following command*
C:\RFIDDEV\reader\reader-rp-client-0.3.1>java -jar
reader-rp-client-0.3.1.jar
*4) Connection to reader from client using HTTP and port 8000.*
* *
Following is the message on reader console when client is connected to
reader
296656 [Thread-20] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpServerCon
nection - Connection requested by client!
296656 [Thread-20] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpServerCon
nection - Listening to port 8000
296656 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- New HTTP connection thread running!
296656 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpMessageInp
utStream - MessageInputStream created
296672 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- Trying to read header/handshake from the connection.
*5) Creating notification channel =96 ( Used port 9999 ) using following xm=
l*
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>44</id>
<targetName></targetName>
<notificationChannel>
<create>
<name>test3</name>
<address>tcp://localhost:9999?mode=3Dconnect</address>
</create>
</notificationChannel>
</ns2:command>
* *
*Log on reader console*:
432265 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Read next instructions...
432265 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher =
-
di
spatch message
433781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
di
spatch command
433781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
Ca
lling a NotificationChannel Command.
433781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
No
tificationChannel.create(test3, tcp://localhost:9999?mode=3Dconnect)
433781 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.NotificationChannelConn
ections - adding notification client tcp://localhost:9999 to the clients.
433781 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Starting OutgoingMessageClient...
433781 [Thread-16] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Dispatching resumed...
433781 [Thread-26] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
433781 [Thread-26] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
433797 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher =
-
Re
sponse message: <?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"=
?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>44</id>
<resultCode>0</resultCode>
<notificationChannel>
<create>
<returnValue>test3</returnValue>
</create>
</notificationChannel>
</ns2:reply>
433797 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message put into buffer!
433797 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message removed from buffer!
433797 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Read next message...
433797 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Dispatcher is waiting for next message...
433797 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - Response Message sent: <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D"yes
"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>44</id>
<resultCode>0</resultCode>
<notificationChannel>
<create>
<returnValue>test3</returnValue>
</create>
</notificationChannel>
</ns2:reply>
433797 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Sending message to client.
433797 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>44</id>
<resultCode>0</resultCode>
<notificationChannel>
<create>
<returnValue>test3</returnValue>
</create>
</notificationChannel>
</ns2:reply>
433797 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
433797 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
*6) Creating Read Trigger:*
* *
* *
Used following xml to create read trigger
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>28</id>
<targetName></targetName>
<trigger>
<create>
<name>ReadTrigger2</name>
<triggerType>TIMER</triggerType>
<triggerValue>100</triggerValue>
</create>
</trigger>
</ns2:command>
*Log on reader console:*
* *
661250 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- trying to read message from stream!
661250 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- read from stream, message =3D <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D
"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>28</id>
<targetName></targetName>
<trigger>
<create>
<name>ReadTrigger2</name>
<triggerType>TIMER</triggerType>
<triggerValue>100</triggerValue>
</create>
</trigger>
</ns2:command>
661250 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer -
Message put into buffer!
661250 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- Trying to read header/handshake from the connection.
661250 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Read next instructions...
661250 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher =
-
di
spatch message
661687 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
di
spatch command
661687 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
Ca
lling a Trigger Command.
661687 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
Ca
lling Trigger.create()
661687 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher =
-
Re
sponse message: <?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"=
?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>28</id>
<resultCode>0</resultCode>
<trigger>
<create>
<returnValue>ReadTrigger2</returnValue>
</create>
</trigger>
</ns2:reply>
661703 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message put into buffer!
661703 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message removed from buffer!
661703 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Read next message...
661703 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Dispatcher is waiting for next message...
661703 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - Response Message sent: <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D"yes
"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>28</id>
<resultCode>0</resultCode>
<trigger>
<create>
<returnValue>ReadTrigger2</returnValue>
</create>
</trigger>
</ns2:reply>
661703 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Sending message to client.
661703 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>28</id>
<resultCode>0</resultCode>
<trigger>
<create>
<returnValue>ReadTrigger2</returnValue>
</create>
</trigger>
</ns2:reply>
661703 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
661703 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
*7) Creating Notification Trigger*
* *
Created Notification trigger using following xml
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>30</id>
<targetName></targetName>
<trigger>
<create>
<name>NotificationTrigger</name>
<triggerType>TIMER</triggerType>
<triggerValue>500</triggerValue>
</create>
</trigger>
</ns2:command>
*Log on Reader Console:*
931484 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- trying to read message from stream!
931484 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- read from stream, message =3D <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D
"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>30</id>
<targetName></targetName>
<trigger>
<create>
<name>NotificationTrigger</name>
<triggerType>TIMER</triggerType>
<triggerValue>500</triggerValue>
</create>
</trigger>
</ns2:command>
931484 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer -
Message put into buffer!
931484 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnection
- Trying to read header/handshake from the connection.
931484 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Read next instructions...
931484 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher =
-
di
spatch message
931859 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
di
spatch command
931859 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
Ca
lling a Trigger Command.
931859 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher =
-
Ca
lling Trigger.create()
931859 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher =
-
Re
sponse message: <?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"=
?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>30</id>
<resultCode>0</resultCode>
<trigger>
<create>
<returnValue>NotificationTrigger</returnValue>
</create>
</trigger>
</ns2:reply>
931859 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message put into buffer!
931859 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message removed from buffer!
931859 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Read next message...
931859 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Dispatcher is waiting for next message...
931859 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - Response Message sent: <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D"yes
"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>30</id>
<resultCode>0</resultCode>
<trigger>
<create>
<returnValue>NotificationTrigger</returnValue>
</create>
</trigger>
</ns2:reply>
931859 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Sending message to client.
931875 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>30</id>
<resultCode>0</resultCode>
<trigger>
<create>
<returnValue>NotificationTrigger</returnValue>
</create>
</trigger>
</ns2:reply>
931875 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
931875 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
*8) Setting Notification Trigger*
* *
* *
I always get UNKNOW ERROR when I try to set the notification trigger but
when execute the same xml it works the second time without issues:
XML used
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>64</id>
<targetName>test3</targetName>
<notificationChannel>
<addNotificationTriggers>
<triggers>
<list>
<value>NotificationTrigger</value>
</list>
</triggers>
</addNotificationTriggers>
</notificationChannel>
</ns2:command>
First Attempt I get the following:
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>64</id>
<resultCode>1</resultCode>
<error>
<name>ERROR_UNKNOWN</name>
<description>For input string: ""</description>
</error>
</ns2:reply>
Second Attempt log on reader:
1182781 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>64</id>
<resultCode>1</resultCode>
<error>
<name>ERROR_UNKNOWN</name>
<description>For input string: ""</description>
</error>
</ns2:reply>
1182781 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
1182781 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
1354406 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - trying to read message from stream!
1354406 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - read from stream, message =3D <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone
=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>64</id>
<targetName>test3</targetName>
<notificationChannel>
<addNotificationTriggers>
<triggers>
<list>
<value>NotificationTrigger</value>
</list>
</triggers>
</addNotificationTriggers>
</notificationChannel>
</ns2:command>
1354422 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message put into buffer!
1354422 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - Trying to read header/handshake from the connection.
1354422 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Read next instructions...
1354422 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher
- d
ispatch message
1354750 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- d
ispatch command
1354750 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- C
alling a NotificationChannel Command.
1354750 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- N
otificationChannel.addNotificationTriggers()
1354750 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher
- R
esponse message: <?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes=
"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>64</id>
<resultCode>0</resultCode>
<notificationChannel>
<addNotificationTriggers/>
</notificationChannel>
</ns2:reply>
1354750 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message put into buffer!
1354750 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message removed from buffer!
1354750 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Read next message...
1354750 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Dispatcher is waiting for next message...
1354750 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnecti
on - Response Message sent: <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D"ye
s"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>64</id>
<resultCode>0</resultCode>
<notificationChannel>
<addNotificationTriggers/>
</notificationChannel>
</ns2:reply>
1354750 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Sending message to client.
1354765 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>64</id>
<resultCode>0</resultCode>
<notificationChannel>
<addNotificationTriggers/>
</notificationChannel>
</ns2:reply>
1354765 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
1354765 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
* *
*9) Adding Current Source to Notification Channel*
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>70</id>
<targetName>test3</targetName>
<notificationChannel>
<addSources>
<sources>
<list>
<value>Shelf1</value>
</list>
</sources>
</addSources>
</notificationChannel>
</ns2:command>
*Log on reader Console:*
1449781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- d
ispatch command
1449781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- C
alling a NotificationChannel Command.
1449781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- N
otificationChannel.addSources()
1449781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher
- R
esponse message: <?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes=
"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>70</id>
<resultCode>0</resultCode>
<notificationChannel>
<addSources/>
</notificationChannel>
</ns2:reply>
1449781 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message put into buffer!
1449781 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message removed from buffer!
1449781 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Read next message...
1449781 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Dispatcher is waiting for next message...
1449781 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnecti
on - Response Message sent: <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D"ye
s"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>70</id>
<resultCode>0</resultCode>
<notificationChannel>
<addSources/>
</notificationChannel>
</ns2:reply>
1449781 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Sending message to client.
1449781 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>70</id>
<resultCode>0</resultCode>
<notificationChannel>
<addSources/>
</notificationChannel>
</ns2:reply>
1449781 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
1449781 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
*10) Adding Read Trigger to the source*
* *
I always get UNKNOWN ERROR first time I attempt to do this step. Second
attempt with the same xml goes through fine
XML used
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>82</id>
<targetName>Shelf1</targetName>
<source>
<addReadTriggers>
<triggers>
<list>
<value>ReadTrigger2</value>
</list>
</triggers>
</addReadTriggers>
</source>
</ns2:command>
First Attempt message:
1617015 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Sending message to client.
1617015 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>82</id>
<resultCode>1</resultCode>
<error>
<name>ERROR_UNKNOWN</name>
<description>For input string: ""</description>
</error>
</ns2:reply>
Second attempt:
1617015 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
1617015 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Outgoing message client is waiting for next message...
1710437 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - trying to read message from stream!
1710437 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - read from stream, message =3D <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone
=3D"yes"?>
<ns2:command xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>82</id>
<targetName>Shelf1</targetName>
<source>
<addReadTriggers>
<triggers>
<list>
<value>ReadTrigger2</value>
</list>
</triggers>
</addReadTriggers>
</source>
</ns2:command>
1710437 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message put into buffer!
1710437 [Thread-0] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnectio
n - Trying to read header/handshake from the connection.
1710437 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Read next instructions...
1710453 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher
- d
ispatch message
1710781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- d
ispatch command
1710781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- C
alling a Source Command.
1710781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.CommandDispatcher
- C
alling Source.addReadTriggers()
1710781 [Thread-16] DEBUG org.accada.reader.rprm.core.msg.MessageDispatcher
- R
esponse message: <?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes=
"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>82</id>
<resultCode>0</resultCode>
<source>
<addReadTriggers/>
</source>
</ns2:reply>
1710781 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message put into buffer!
1710781 [Thread-16] DEBUG
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Message removed from buffer!
1710781 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Read next message...
1710781 [Thread-16] INFO
org.accada.reader.rprm.core.msg.IncomingMessageBuffer
- Dispatcher is waiting for next message...
1710781 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.transport.HttpConnecti
on - Response Message sent: <?xml version=3D"1.0" encoding=3D"UTF-8"
standalone=3D"ye
s"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>82</id>
<resultCode>0</resultCode>
<source>
<addReadTriggers/>
</source>
</ns2:reply>
1710781 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- Sending message to client.
1710781 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageClient
- message:
<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"yes"?>
<ns2:reply xmlns:ns2=3D"urn:epcglobal:rp:xsd:1">
<id>82</id>
<resultCode>0</resultCode>
<source>
<addReadTriggers/>
</source>
</ns2:reply>
1710797 [Thread-25] DEBUG
org.accada.reader.rprm.core.msg.OutgoingMessageBuffer
- Message removed from buffer!
1710797 [Thread-25] INFO
org.accada.reader.rprm.core.msg.OutgoingMess...
[truncated message content] |
|
From: Jonas H. <jh...@us...> - 2007-08-23 07:01:05
|
Dear Shanthi I was able to reproduce the error you reported by following your detailed description of what you have done. After comparison to commands I use and some trial and error, I found the mistake you made that lead to the error. When creating the two timer triggers, you used '100' and '500' respectively. This format does not comply the reader protocol specification but is not reported as error immediately. The error occures when trying to add these triggers which is kind of bad design. If you have the EPCglobal reader protocol standard specification, you can refer to chapter '6.5 Object Trigger'. In 'Table 7: Possible Trigger values' it sais: - triggervalue: ms=<n> - TriggerType: timer - Description: Periodic interval trigger; <n> is the number of milliseconds for the interval. With exactly the commands you used excepting 'ms=100' and 'ms=500' instead of only '100' and '500' for the trigger value it works for me and should work for you. Kind regards, Jonas On Mon, August 20, 2007 20:55, Shanthi Boppana wrote: > Dear Jonas, > > > I mentioned the order wrong in the email. I took your advise and did not > configure DataSelector but i am still not able to capture events in > EventSinkUI > > > I alway get an error on first attempt during > > > - setting notification trigger > - and adding read trigger to the source > > > But when I use the same xml and try it for second time it goes through > fine. > > I am attaching exact steps I followed along with reader console log > generated after each command. > > Regards > Shanthi > > > On 8/17/07, Jonas Haller <jh...@us...> wrote: > > >> Dear Boppana, >> >> >> >> A first problem i noticed is the order you discribed in your mail: >> >> >>> I have used reader client and configured it to capture events >>> Started Event Sink >>> Added a new tag to Shelf 1 >>> But this event is not shown in Event Sink >>> >> >> The reader establishes a connection to the sink when the command to >> create a notification channel is sent. If you configured the reader and >> started the event sink afterwards, no connection is established for the >> notification channel. When you close the reader and a connection was >> established, a message should appear in the EventSinkUI that sais >> 'ERROR: >> connection reset'. If this message does not appear, there was no >> connection and thus no notifications were able to reach the >> EventSinkUI. >> >> >> A potential second problem i noticed in your mail is the usage of non >> default DataSelector. The DataSelector was buggy and is still buggy in >> the latest release. I fixed it in the current developer version last >> week. For further testing of accada, please leave away the DataSelector >> configuration (steps 4 to 7 in your list of configuration commands >> below) until next release of a new accada version. >> >> >> Kind regards, >> Jonas >> >> >> >> >> >> >> On 8/16/07, Matthias Lampe <la...@in...> wrote: >> >>> >>> >>> Dear Boppana, >>> >>> >>> >>> Thanks for your using Accada! I am currently travelling but will take >>> a look at the issue you describe beginning next week. We also fixed >> several >>> bugs in the reader module and planing a release for end of next week >> which >>> might also deal with your issues. >>> >>> Best >>> Matthias >>> >>> >>> >>> ________________________________ >>> >>> >>> >>> From: acc...@li... >>> [mailto:acc...@li...] On Behalf Of >>> Shanthi Boppana >>> Sent: Dienstag, 14. August 2007 23:02 >>> To: acc...@li... >>> Subject: [accada-reader-user] Accada Reader >>> >>> >>> >>> >>> Hi, >>> >>> >>> >>> I have downloded accada reader and reader client. >>> >>> >>> >>> I am trying to capture reader events using >>> org.accada.reader.rp.client.EventSinkUI 9001 >>> >>> On the reader command line console I do see the debug statement when >>> a tag is read by the reader but I am not able to see the events using >>> EventSinkUI. >>> >>> >>> >>> I have used reader client and configured it to capture events >>> Started Event Sink >>> Added a new tag to Shelf 1 >>> But this event is not shown in Event Sink >>> >>> >>> >>> Here is my reader configuration: >>> >>> >>> >>> 1) Create Notification Channel >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>44</id> >>> <targetName></targetName> >>> <notificationChannel> >>> <create> >>> <name>test</name> >>> <address>tcp://localhost:9001?mode=connect</address> >>> </create> >>> </notificationChannel> >>> </ns2:command> >>> >>> >>> >>> >>> >>> 2) Creating Read Trigger >>> >>> >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>28</id> >>> <targetName></targetName> >>> <trigger> >>> <create> >>> <name>ReadTrigger2</name> >>> <triggerType>TIMER</triggerType> >>> <triggerValue>100</triggerValue> >>> </create> >>> </trigger> >>> </ns2:command> >>> >>> >>> >>> 3) Creating NotificationTrigger >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>30</id> >>> <targetName></targetName> >>> <trigger> >>> <create> >>> <name>NotificationTrigger</name> >>> <triggerType>TIMER</triggerType> >>> <triggerValue>500</triggerValue> >>> </create> >>> </trigger> >>> </ns2:command> >>> >>> >>> >>> >>> 4) Create DataSelector >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>46</id> >>> <targetName></targetName> >>> <dataSelector> >>> <create> >>> <name>DataSelector</name> >>> </create> >>> </dataSelector> >>> </ns2:command> >>> >>> >>> >>> >>> 5) Adding Event Filters to Data Selectors >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>52</id> >>> <targetName>DataSelector</targetName> >>> <dataSelector> >>> <addEventFilters> >>> <eventType> >>> <list> >>> <value>EV_OBSERVED</value> >>> <value>EV_LOST</value> >>> </list> >>> </eventType> >>> </addEventFilters> >>> </dataSelector> >>> </ns2:command> >>> >>> >>> >>> >>> 6) Adding Field Names >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>54</id> >>> <targetName>DataSelector</targetName> >>> <dataSelector> >>> <addFieldNames> >>> <fieldNames> >>> <list> >>> <value>EVENT_TYPE</value> >>> <value>READER_NAME</value> >>> <value>TAG_ID</value> >>> <value>TAG_ID_AS_PURE_URI</value> >>> <value>TAG_ID_AS_TAG_URI</value> >>> <value>SOURCE_NAME</value> >>> </list> >>> </fieldNames> >>> </addFieldNames> >>> </dataSelector> >>> </ns2:command> >>> >>> >>> >>> >>> 7) Setting DataSelector >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>58</id> >>> <targetName>test</targetName> >>> <notificationChannel> >>> <setDataSelector> >>> <dataSelector>DataSelector</dataSelector> >>> </setDataSelector> >>> </notificationChannel> >>> </ns2:command> >>> >>> >>> >>> 8) Setting NotificationTrigger >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>64</id> >>> <targetName>test</targetName> >>> <notificationChannel> >>> <addNotificationTriggers> >>> <triggers> >>> <list> >>> <value>NotificationTrigger</value> >>> </list> >>> </triggers> >>> </addNotificationTriggers> >>> </notificationChannel> >>> </ns2:command> >>> >>> >>> >>> >>> 9) Add Current Source to Notification Channel >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>70</id> >>> <targetName>test</targetName> >>> <notificationChannel> >>> <addSources> >>> <sources> >>> <list> >>> <value>Shelf1</value> >>> </list> >>> </sources> >>> </addSources> >>> </notificationChannel> >>> </ns2:command> >>> >>> >>> >>> >>> 9) Add Read Trigger to Source >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> >>> <id>82</id> >>> <targetName>Shelf1</targetName> >>> <source> >>> <addReadTriggers> >>> <triggers> >>> <list> >>> <value>ReadTrigger2</value> >>> </list> >>> </triggers> >>> </addReadTriggers> >>> </source> >>> </ns2:command> >>> >>> >>> >>> Any help is greatly appreciated >>> >>> >>> >>> -Boppana >>> >>> >> >> >> -- >> Jonas Haller <jh...@us...> >> >> >> >> ----------------------------------------------------------------------- >> -- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> accada-reader-user mailing list acc...@li... >> https://lists.sourceforge.net/lists/listinfo/accada-reader-user >> >> > -- Jonas Haller <jh...@us...> |
|
From: Jonas H. <jh...@us...> - 2007-08-23 15:34:43
|
Hi Paolo
You are right. When getting the address of the NotificationChannel, I get port
number 0 back too. This is not a problem of configuring the reader but of the
answer from the reader. The port should be configured all right. I will try to
fix this bug.
I created a NotificationChannel that connects on port 9999 (standard for
EventSinkUI). Getting the address from the reader returns 0 too. But when I
close the SimulatorReader, I get an 'ERROR: connection reset!' on the EventSink,
so a connection was made when creating the NotificationChannel.
With the following procedure you should get notifications on the EventSink:
- Start the SimulatorReader, the EventSinkUI (standard port 9999) and the
ReaderClient.
- Create a new Tag on the ReaderSimulator interface.
- Connect the ReaderClient to the Reader.
- Use these six commands to configure the Reader:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>2</id>
<targetName></targetName>
<trigger>
<create>
<name>rt</name>
<triggerType>TIMER</triggerType>
<triggerValue>ms=1000</triggerValue>
</create>
</trigger>
</ns2:command>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>4</id>
<targetName>nt</targetName>
<trigger>
<create>
<name>nt</name>
<triggerType>TIMER</triggerType>
<triggerValue>ms=1000</triggerValue>
</create>
</trigger>
</ns2:command>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>6</id>
<targetName></targetName>
<notificationChannel>
<create>
<name>nc</name>
<address>tcp://localhost:9999?mode=connect</address>
</create>
</notificationChannel>
</ns2:command>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>8</id>
<targetName>nc</targetName>
<notificationChannel>
<addNotificationTriggers>
<triggers>
<list>
<value>nt</value>
</list>
</triggers>
</addNotificationTriggers>
</notificationChannel>
</ns2:command>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>10</id>
<targetName>nc</targetName>
<notificationChannel>
<addSources>
<sources>
<list>
<value>Shelf1</value>
</list>
</sources>
</addSources>
</notificationChannel>
</ns2:command>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>12</id>
<targetName>Shelf1</targetName>
<source>
<addReadTriggers>
<triggers>
<list>
<value>rt</value>
</list>
</triggers>
</addReadTriggers>
</source>
</ns2:command>
- Drag the Tag over Shelf1 in the SimulatorReader interface.
This procedure should work (it works for me). Try it out exactly like this as a
starting point. If it works, you can change things as you like. If it does not
work, send me as much debug information as you can, this helps me finding the
problem.
Kind regards,
--
Jonas Haller <jh...@us...>
Paolo Raimondi schrieb:
> Hi, I think I have the same problem becuase the EventSink doesn't
> show anything.... but I have a doubt: after creating the notificationChannel, if
> I use the command NotificationChannel.getAddress the response is :
>
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <ns2:reply xmlns:ns2="urn:epcglobal:rp:xsd:1">
> <id>14</id>
> <resultCode>0</resultCode>
> <notificationChannel>
> <getAddress>
> <returnValue>tcp://localhost:0</returnValue>
> </getAddress>
> </notificationChannel>
> </ns2:reply>
>
> in particular I think that the client sets the tcp port to value zero and not to
> value 9001....
>
> I have do :
>
> NotificationChannel.create: with parameters
>
> channel1 [string]
>
> tcp://localhost:9001?mode=connect [string]
>
> Have I mistaken something?
>
> Best Reagards
>
> Paolo
>
>
>
>
>
> --------------------------------------------------------------------------------
> From: /"Jonas Haller" <jh...@us...>/
> Reply-To: /jh...@us.../
> To: /acc...@li.../
> Subject: /Re: [accada-reader-user] Accada Reader/
> Date: /Thu, 23 Aug 2007 09:01:04 +0200 (CEST)/
> >Dear Shanthi
> >
> >
> >I was able to reproduce the error you reported by following your detailed
> >description of what you have done. After comparison to commands I use and
> >some trial and error, I found the mistake you made that lead to the error.
> >
> >When creating the two timer triggers, you used '100' and '500'
> >respectively. This format does not comply the reader protocol
> >specification but is not reported as error immediately. The error occures
> >when trying to add these triggers which is kind of bad design.
> >
> >If you have the EPCglobal reader protocol standard specification, you can
> >refer to chapter '6.5 Object Trigger'. In 'Table 7: Possible Trigger
> >values' it sais:
> >- triggervalue: ms=<n>
> >- TriggerType: timer
> >- Description: Periodic interval trigger; <n> is the number of
> >milliseconds for the interval.
> >
> >With exactly the commands you used excepting 'ms=100' and 'ms=500' instead
> >of only '100' and '500' for the trigger value it works for me and should
> >work for you.
> >
> >
> >Kind regards,
> >Jonas
> >
> >
> >
> >On Mon, August 20, 2007 20:55, Shanthi Boppana wrote:
> > > Dear Jonas,
> > >
> > >
> > > I mentioned the order wrong in the email. I took your advise and did not
> > > configure DataSelector but i am still not able to capture events in
> > > EventSinkUI
> > >
> > >
> > > I alway get an error on first attempt during
> > >
> > >
> > > - setting notification trigger
> > > - and adding read trigger to the source
> > >
> > >
> > > But when I use the same xml and try it for second time it goes through
> > > fine.
> > >
> > > I am attaching exact steps I followed along with reader console log
> > > generated after each command.
> > >
> > > Regards
> > > Shanthi
> > >
> > >
> > > On 8/17/07, Jonas Haller <jh...@us...> wrote:
> > >
> > >
> > >> Dear Boppana,
> > >>
> > >>
> > >>
> > >> A first problem i noticed is the order you discribed in your mail:
> > >>
> > >>
> > >>> I have used reader client and configured it to capture events
> > >>> Started Event Sink
> > >>> Added a new tag to Shelf 1
> > >>> But this event is not shown in Event Sink
> > >>>
> > >>
> > >> The reader establishes a connection to the sink when the command to
> > >> create a notification channel is sent. If you configured the reader and
> > >> started the event sink afterwards, no connection is established for the
> > >> notification channel. When you close the reader and a connection was
> > >> established, a message should appear in the EventSinkUI that sais
> > >> 'ERROR:
> > >> connection reset'. If this message does not appear, there was no
> > >> connection and thus no notifications were able to reach the
> > >> EventSinkUI.
> > >>
> > >>
> > >> A potential second problem i noticed in your mail is the usage of non
> > >> default DataSelector. The DataSelector was buggy and is still buggy in
> > >> the latest release. I fixed it in the current developer version last
> > >> week. For further testing of accada, please leave away the DataSelector
> > >> configuration (steps 4 to 7 in your list of configuration commands
> > >> below) until next release of a new accada version.
> > >>
> > >>
> > >> Kind regards,
> > >> Jonas
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On 8/16/07, Matthias Lampe <la...@in...> wrote:
> > >>
> > >>>
> > >>>
> > >>> Dear Boppana,
> > >>>
> > >>>
> > >>>
> > >>> Thanks for your using Accada! I am currently travelling but will take
> > >>> a look at the issue you describe beginning next week. We also fixed
> > >> several
> > >>> bugs in the reader module and planing a release for end of next week
> > >> which
> > >>> might also deal with your issues.
> > >>>
> > >>> Best
> > >>> Matthias
> > >>>
> > >>>
> > >>>
> > >>> ________________________________
> > >>>
> > >>>
> > >>>
> > >>> From: acc...@li...
> > >>> [mailto:acc...@li...] On Behalf Of
> > >>> Shanthi Boppana
> > >>> Sent: Dienstag, 14. August 2007 23:02
> > >>> To: acc...@li...
> > >>> Subject: [accada-reader-user] Accada Reader
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> Hi,
> > >>>
> > >>>
> > >>>
> > >>> I have downloded accada reader and reader client.
> > >>>
> > >>>
> > >>>
> > >>> I am trying to capture reader events using
> > >>> org.accada.reader.rp.client.EventSinkUI 9001
> > >>>
> > >>> On the reader command line console I do see the debug statement when
> > >>> a tag is read by the reader but I am not able to see the events using
> > >>> EventSinkUI.
> > >>>
> > >>>
> > >>>
> > >>> I have used reader client and configured it to capture events
> > >>> Started Event Sink
> > >>> Added a new tag to Shelf 1
> > >>> But this event is not shown in Event Sink
> > >>>
> > >>>
> > >>>
> > >>> Here is my reader configuration:
> > >>>
> > >>>
> > >>>
> > >>> 1) Create Notification Channel
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>44</id>
> > >>> <targetName></targetName>
> > >>> <notificationChannel>
> > >>> <create>
> > >>> <name>test</name>
> > >>> <address>tcp://localhost:9001?mode=connect</address>
> > >>> </create>
> > >>> </notificationChannel>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 2) Creating Read Trigger
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>28</id>
> > >>> <targetName></targetName>
> > >>> <trigger>
> > >>> <create>
> > >>> <name>ReadTrigger2</name>
> > >>> <triggerType>TIMER</triggerType>
> > >>> <triggerValue>100</triggerValue>
> > >>> </create>
> > >>> </trigger>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>> 3) Creating NotificationTrigger
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>30</id>
> > >>> <targetName></targetName>
> > >>> <trigger>
> > >>> <create>
> > >>> <name>NotificationTrigger</name>
> > >>> <triggerType>TIMER</triggerType>
> > >>> <triggerValue>500</triggerValue>
> > >>> </create>
> > >>> </trigger>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 4) Create DataSelector
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>46</id>
> > >>> <targetName></targetName>
> > >>> <dataSelector>
> > >>> <create>
> > >>> <name>DataSelector</name>
> > >>> </create>
> > >>> </dataSelector>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 5) Adding Event Filters to Data Selectors
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>52</id>
> > >>> <targetName>DataSelector</targetName>
> > >>> <dataSelector>
> > >>> <addEventFilters>
> > >>> <eventType>
> > >>> <list>
> > >>> <value>EV_OBSERVED</value>
> > >>> <value>EV_LOST</value>
> > >>> </list>
> > >>> </eventType>
> > >>> </addEventFilters>
> > >>> </dataSelector>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 6) Adding Field Names
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>54</id>
> > >>> <targetName>DataSelector</targetName>
> > >>> <dataSelector>
> > >>> <addFieldNames>
> > >>> <fieldNames>
> > >>> <list>
> > >>> <value>EVENT_TYPE</value>
> > >>> <value>READER_NAME</value>
> > >>> <value>TAG_ID</value>
> > >>> <value>TAG_ID_AS_PURE_URI</value>
> > >>> <value>TAG_ID_AS_TAG_URI</value>
> > >>> <value>SOURCE_NAME</value>
> > >>> </list>
> > >>> </fieldNames>
> > >>> </addFieldNames>
> > >>> </dataSelector>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 7) Setting DataSelector
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>58</id>
> > >>> <targetName>test</targetName>
> > >>> <notificationChannel>
> > >>> <setDataSelector>
> > >>> <dataSelector>DataSelector</dataSelector>
> > >>> </setDataSelector>
> > >>> </notificationChannel>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>> 8) Setting NotificationTrigger
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>64</id>
> > >>> <targetName>test</targetName>
> > >>> <notificationChannel>
> > >>> <addNotificationTriggers>
> > >>> <triggers>
> > >>> <list>
> > >>> <value>NotificationTrigger</value>
> > >>> </list>
> > >>> </triggers>
> > >>> </addNotificationTriggers>
> > >>> </notificationChannel>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 9) Add Current Source to Notification Channel
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>70</id>
> > >>> <targetName>test</targetName>
> > >>> <notificationChannel>
> > >>> <addSources>
> > >>> <sources>
> > >>> <list>
> > >>> <value>Shelf1</value>
> > >>> </list>
> > >>> </sources>
> > >>> </addSources>
> > >>> </notificationChannel>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> 9) Add Read Trigger to Source
> > >>>
> > >>>
> > >>>
> > >>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > >>> <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
> > >>> <id>82</id>
> > >>> <targetName>Shelf1</targetName>
> > >>> <source>
> > >>> <addReadTriggers>
> > >>> <triggers>
> > >>> <list>
> > >>> <value>ReadTrigger2</value>
> > >>> </list>
> > >>> </triggers>
> > >>> </addReadTriggers>
> > >>> </source>
> > >>> </ns2:command>
> > >>>
> > >>>
> > >>>
> > >>> Any help is greatly appreciated
> > >>>
> > >>>
> > >>>
> > >>> -Boppana
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Jonas Haller <jh...@us...>
> > >>
> > >>
> > >>
> > >> -----------------------------------------------------------------------
> > >> --
> > >> This SF.net email is sponsored by: Splunk Inc.
> > >> Still grepping through log files to find problems? Stop.
> > >> Now Search log events and configuration files using AJAX and a browser.
> > >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> > >> _______________________________________________
> > >> accada-reader-user mailing list acc...@li...
> > >> https://lists.sourceforge.net/lists/listinfo/accada-reader-user
> > >>
> > >>
> > >
> >
> >
> >--
> >Jonas Haller <jh...@us...>
> >
> >
> >-------------------------------------------------------------------------
> >This SF.net email is sponsored by: Splunk Inc.
> >Still grepping through log files to find problems? Stop.
> >Now Search log events and configuration files using AJAX and a browser.
> >Download your FREE copy of Splunk now >> http://get.splunk.com/
> >_______________________________________________
> >accada-reader-user mailing list
> >acc...@li...
> >https://lists.sourceforge.net/lists/listinfo/accada-reader-user
>
>
> --------------------------------------------------------------------------------
> Sai cosa è successo oggi? <http://g.msn.com/8HMBITIT/2743??PS=47575>
|