Edge Server can not conect with Emulator nor Prototyper

Questions about using and running the Rifidi Edge Server

Moderators: Matt, kyle

Post Reply
danielrs
Posts: 3
Joined: Sun Oct 30, 2016 2:48 pm

Edge Server can not conect with Emulator nor Prototyper

Post by danielrs » Sun Nov 13, 2016 1:01 pm

I would like to build a simple application using Edge Server, as the first step i am trying to conect the edge server with emulator following the instructions of the "Rifidi Edge Server Quick Start Guide" and "Rifidi Edge Server User" docs. I literally copied and pasted the comands into the osgi command line and created an Alien reader as it is explained at http://wiki.rifidi.net/index.php?title= ... %27s_Guide. The edge server tries to connect with the reader but without success. Here is the messagges that showme the console when i open edge server after have created and started the reader.

Code: Select all

[org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ...
START RIFIDI INITIALIZTION BUNDLE
ALL RIFIDI CONFIGURATION PATHS RELATIVE TO : C:\Program Files (x86)\RifidiEdge-3
.5.1\server
Using log4j configuration at: file:/C:\Program Files (x86)\RifidiEdge-3.5.1\serv
er\config/logging.properties
[org.eclipse.equinox.weaving.aspectj] info Starting AspectJ weaving service ...
osgi> 12:55:08,229  INFO org.rifidi.edge.Activator:43 - Starting Moquette MQTT
log4j:WARN No appenders could be found for logger (org.eclipse.moquette.server.S
erver).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more in
fo.
12:55:09,443  INFO org.rifidi.edge.services.EsperManagementServiceImpl:50 - Espe
rManagementServiceImpl created.
12:55:09,537  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Rea
dZones
12:55:09,541  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Rea
dZones
12:55:09,639  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Sen
sorStatus
12:55:09,646  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Uni
queTagInterval
12:55:09,653  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Sta
bleSet
12:55:09,658  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Lim
itStableSet
12:55:09,662  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Uni
queTagBatchInterval
12:55:09,673  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: RSS
I
12:55:10,391  INFO com.espertech.esper.core.service.EPServiceProviderImpl:415 -
Initializing engine URI 'default' version 5.3.0
12:55:11,254  INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Loo
king for RMI registry at port '1101'
12:55:12,256  INFO org.springframework.remoting.rmi.RmiServiceExporter:404 - Cou
ld not detect RMI registry - creating new one
12:55:12,261  INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Bin
ding service 'SensorManagerService' to RMI registry: RegistryImpl[UnicastServerR
ef [liveRef: [endpoint:[127.0.0.1:1101](local),objID:[0:0:0, 0]]]]
12:55:12,274  INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Loo
king for RMI registry at port '1101'
12:55:12,346  INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Bin
ding service 'CommandManagerService' to RMI registry: RegistryImpl_Stub[UnicastR
ef [liveRef: [endpoint:[192.168.65.1:1101](remote),objID:[0:0:0, 0]]]]
12:55:12,361  INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Loo
king for RMI registry at port '1101'
12:55:12,363  INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Bin
ding service 'EdgeServerManagerService' to RMI registry: RegistryImpl_Stub[Unica
stRef [liveRef: [endpoint:[192.168.65.1:1101](remote),objID:[0:0:0, 0]]]]
12:55:12,380  INFO org.apache.activemq.xbean.XBeanBrokerFactory$1:510 - Refreshi
ng org.apache.activemq.xbean.XBeanBrokerFactory$1@167faa: startup date [Sun Nov
13 12:55:12 BOT 2016]; root of context hierarchy
12:55:12,383  INFO org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionRead
er:315 - Loading XML bean definitions from file [C:\Program Files (x86)\RifidiEd
ge-3.5.1\server\config\rifidi-amq-external.xml]
12:55:12,387  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Tag
s
12:55:12,544  INFO org.apache.activemq.broker.BrokerService:262 - Using Persiste
nce Adapter: MemoryPersistenceAdapter
12:55:12,546  INFO org.apache.activemq.broker.BrokerService:262 - ActiveMQ 5.5.0
 JMS Message Broker (externalBroker) is starting
12:55:12,547  INFO org.apache.activemq.broker.BrokerService:262 - For help or mo
re information please see: http://activemq.apache.org/
12:55:12,551  INFO org.apache.activemq.broker.jmx.ManagementContext:262 - JMX co
nsoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
12:55:12,717  INFO org.apache.activemq.transport.TransportServerThreadSupport:26
2 - Listening for connections at: tcp://127.0.0.1:1100
12:55:12,717  INFO org.apache.activemq.broker.TransportConnector:262 - Connector
 tcp://127.0.0.1:1100 Started
12:55:12,719  INFO org.apache.activemq.broker.BrokerService:262 - ActiveMQ JMS M
essage Broker (externalBroker, ID:Laptop-daniel-50690-1479056112557-0:1) started

12:55:12,746  INFO org.rifidi.edge.services.ProvisioningServiceImpl:156 - Path t
o applications foler: C:\Program Files (x86)\RifidiEdge-3.5.1\server/application
s
12:55:12,829  INFO org.apache.activemq.broker.TransportConnector:262 - Connector
 vm://externalBroker Started
12:55:12,977  INFO org.rifidi.edge.rest.RestletServer:33 - RestletServer called
12:55:12,978  INFO org.rifidi.edge.rest.RestletServer:39 - Starting restlet serv
er on port: 8111
12:55:12,996  INFO org.rifidi.edge.daos.ReaderDAOImpl:167 - Reader bound:Alien_1

12:55:13,000  INFO org.rifidi.edge.sensors.SensorManagementServiceImpl:464 - Sen
sor bound:Alien_1
12:55:13,009  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:244 -
Session not in processing state. Command will be executed when session connects:
 Alien_Push_Start_1
12:55:13,017  INFO org.rifidi.edge.configuration.DefaultConfigurationImpl:238 -
Restarting session: IPSession: 127.0.0.1:20000 (CREATED), [Autonomous Session IP
ServerSession: 0 (CREATED)],[GPIO Session IPServerSession: 0 (CREATED)]
12:55:13,035  INFO org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:204
- Attempting to connect to : 127.0.0.1:20000
12:55:13,048  INFO org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:282
- Session 1 on Alien_1 connected successfully to  127.0.0.1:20000
12:55:13,048  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:328 -
Session not in processing state. Command will be executed when session connects:
 Alien Keep Alive
12:55:13,055  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:357 -
Executing single shot command: Default Reset Command
12:55:13,056  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:357 -
Executing single shot command: Alien_Push_Start_1
12:55:13,056  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:348 -
Scheduling recurring command: Alien Keep Alive
12:55:13,057  INFO org.rifidi.edge.sensors.sessions.AbstractServerSocketSensorSe
ssion:106 - Not starting server socket, since port < 1
12:55:13,058  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:354 -
Executing single shot command: AlienPropertyCommand
12:55:13,059  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:354 -
Executing single shot command: AlienPropertyCommand
12:55:13,097  INFO org.rifidi.edge.daos.CommandDAOImpl:130 - Command Configurati
on Bound: Alien_Push_Start_2
12:55:13,102  INFO org.rifidi.edge.daos.CommandDAOImpl:130 - Command Configurati
on Bound: Alien_Push_Start_1
12:55:13,714  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Rea
dZones
12:55:13,731  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Sta
tsApp
12:55:13,739  INFO org.rifidi.edge.api.AbstractRifidiApp:226 - Starting App: Sen
sorStatus
12:55:18,057 ERROR org.rifidi.edge.sensors.TimeoutCommand:70 - Timeout Exception
 on Sensor: Alien_1:IPSession: 127.0.0.1:20000 (PROCESSING), [Autonomous Session
 IPServerSession: 0 (CREATED)],[GPIO Session IPServerSession: 0 (CREATED)] Comma
nd: Alien Keep Alive
12:55:18,061  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:197 -
Queing command: CommandExecutor: Alien_Push_Start_1 IPSession: 127.0.0.1:20000 (
CLOSED), [Autonomous Session IPServerSession: 0 (CREATED)],[GPIO Session IPServe
rSession: 0 (CREATED)]
12:55:18,062 ERROR org.rifidi.edge.sensors.sessions.ReadThread:90 - java.net.Soc
ketException: Socket closed
12:55:18,067  INFO org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:204
- Attempting to connect to : 127.0.0.1:20000
12:55:18,067  INFO org.rifidi.edge.sensors.sessions.AbstractServerSocketSensorSe
ssion:106 - Not starting server socket, since port < 1
12:55:18,070  WARN org.rifidi.edge.adapter.alien.commandobject.AlienGetCommandOb
ject:72 - Something is wrong with the command: *********************************
**************
*
* Alien Technology : RFID Reader
*
***********************************************

Username>
12:55:18,071  WARN org.rifidi.edge.adapter.alien.commands.internal.AlienProperty
Command:77 - Alien Exception while executing command readerNumber***************
********************************
*
* Alien Technology : RFID Reader
*
***********************************************

Username>
12:55:18,072 FATAL org.rifidi.edge.adapter.alien.Alien9800ReaderSession:196 - Se
nsorSession is not an alien sensorSession:
12:55:18,075  WARN org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:353
- Connection Failed 127.0.0.1:20000
12:55:18,075 ERROR org.rifidi.edge.sensors.sessions.ReadThread:90 - java.net.Soc
ketException: Socket closed
12:55:18,075  INFO org.rifidi.edge.sensors.sessions.AbstractServerSocketSensorSe
ssion:106 - Not starting server socket, since port < 1
12:55:23,060  WARN org.rifidi.edge.sensors.sessions.AbstractSensorSession:298 -
Timed out waiting on command
java.util.concurrent.TimeoutException
        at java.util.concurrent.FutureTask.get(Unknown Source)
        at org.rifidi.edge.sensors.sessions.AbstractSensorSession.submitAndBlock
(AbstractSensorSession.java:280)
        at org.rifidi.edge.adapter.alien.Alien9800Reader.applyPropertyChanges(Al
ien9800Reader.java:722)
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession.getExternalInput
(Alien9800ReaderSession.java:405)
        at org.rifidi.edge.adapter.alien.gpio.AlienGPIOSession.initialize(AlienG
PIOSession.java:92)
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession$2.run(Alien9800R
eaderSession.java:162)
        at java.lang.Thread.run(Unknown Source)
12:55:23,062  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:328 -
Session not in processing state. Command will be executed when session connects:

org.rifidi.edge.sensors.CannotExecuteException: The GPI command may not have exe
cuted12:55:23,062  WARN org.rifidi.edge.sensors.sessions.AbstractSensorSession:2
88 - Cannot wait on command  because the session is not in the processing state

12:55:23,063  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:328 -
Session not in processing state. Command will be executed when session connects:

        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession.getExternalInput
(Alien9800ReaderSession.java:410)12:55:23,065  WARN org.rifidi.edge.sensors.sess
ions.AbstractSensorSession:288 - Cannot wait on command  because the session is
not in the processing state

        at org.rifidi.edge.adapter.alien.gpio.AlienGPIOSession.initialize(AlienG
PIOSession.java:92)
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession$2.run(Alien9800R
eaderSession.java:162)
        at java.lang.Thread.run(Unknown Source)
org.rifidi.edge.sensors.CannotExecuteException: The GPI command may not have exe
cuted
12:55:23,066  WARN org.rifidi.edge.adapter.alien.Alien9800ReaderSession:166 - Ca
nnot connect Alien GPIO Session: [GPIO Session IPServerSession: 0 (CREATED)]
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession.getExternalInput
(Alien9800ReaderSession.java:410)
        at org.rifidi.edge.adapter.alien.gpio.AlienGPIOSession.initialize(AlienG
PIOSession.java:92)
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession$2.run(Alien9800R
eaderSession.java:162)
        at java.lang.Thread.run(Unknown Source)
org.rifidi.edge.sensors.CannotExecuteException: The GPI command may not have exe
cuted12:55:23,068  WARN org.rifidi.edge.adapter.alien.Alien9800ReaderSession:166
 - Cannot connect Alien GPIO Session: [GPIO Session IPServerSession: 0 (CREATED)
]

        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession.getExternalInput
(Alien9800ReaderSession.java:410)
        at org.rifidi.edge.adapter.alien.gpio.AlienGPIOSession.initialize(AlienG
PIOSession.java:92)
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession$2.run(Alien9800R
eaderSession.java:162)
        at java.lang.Thread.run(Unknown Source)
12:55:23,071  WARN org.rifidi.edge.adapter.alien.Alien9800ReaderSession:166 - Ca
nnot connect Alien GPIO Session: [GPIO Session IPServerSession: 0 (CREATED)]
12:55:23,073  WARN org.rifidi.edge.adapter.alien.commandobject.AlienGetCommandOb
ject:59 - Timeout when waiting for the ReaderVersion command to execute
12:55:23,073 ERROR org.rifidi.edge.sensors.TimeoutCommand:70 - Timeout Exception
 on Sensor: Alien_1:IPSession: 127.0.0.1:20000 (CLOSED), [Autonomous Session IPS
erverSession: 0 (CREATED)],[GPIO Session IPServerSession: 0 (CREATED)] Command:

12:55:23,075  INFO org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:204
- Attempting to connect to : 127.0.0.1:20000
12:55:23,078  WARN org.rifidi.edge.adapter.alien.commandobject.AlienGetCommandOb
ject:72 - Something is wrong with the command: *********************************
**************
*
* Alien Technology : RFID Reader
*
***********************************************

Username>
12:55:23,078 FATAL org.rifidi.edge.adapter.alien.Alien9800ReaderSession:196 - Se
nsorSession is not an alien sensorSession:
12:55:23,079  WARN org.rifidi.edge.adapter.alien.commands.internal.AlienProperty
Command:77 - Alien Exception while executing command externalinput**************
*********************************
*
* Alien Technology : RFID Reader
*
***********************************************

Username>
12:55:23,080  WARN org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:353
- Connection Failed 127.0.0.1:20000
12:55:23,081 ERROR org.rifidi.edge.sensors.sessions.ReadThread:90 - java.net.Soc
ketException: Socket closed
12:55:23,081  INFO org.rifidi.edge.sensors.sessions.AbstractSensorSession:328 -
Session not in processing state. Command will be executed when session connects:

12:55:23,081  INFO org.rifidi.edge.sensors.sessions.AbstractServerSocketSensorSe
ssion:106 - Not starting server socket, since port < 1
12:55:23,082  WARN org.rifidi.edge.sensors.sessions.AbstractSensorSession:288 -
Cannot wait on command  because the session is not in the processing state
org.rifidi.edge.sensors.CannotExecuteException: The GPI command may not have exe
cuted
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession.getExternalInput
(Alien9800ReaderSession.java:410)
        at org.rifidi.edge.adapter.alien.gpio.AlienGPIOSession.initialize(AlienG
PIOSession.java:92)
        at org.rifidi.edge.adapter.alien.Alien9800ReaderSession$2.run(Alien9800R
eaderSession.java:162)
        at java.lang.Thread.run(Unknown Source)
12:55:23,085  WARN org.rifidi.edge.adapter.alien.Alien9800ReaderSession:166 - Ca
nnot connect Alien GPIO Session: [GPIO Session IPServerSession: 0 (CREATED)]
The same results are obtained with both, prototyper and emulator. If you could help i'd really appreciate it. Also, somo advices about which should be my next step in order to develop and application are welcome. Thanks in advance.

bppause
Posts: 434
Joined: Sat Oct 03, 2009 12:30 am
Organization: Pramari

Re: Edge Server can not conect with Emulator nor Prototyper

Post by bppause » Mon Nov 14, 2016 9:21 pm

These steps have been validated to my knowledge with Alien and LLRP readers.

I would try to follow the steps using a LLRP reader for starters

Link to latest quick start guide

http://www.transcends.co/www/docs/Rifid ... de_3.5.pdf

As far as guidance on where to go next. It really depends on teh use case. You can leverage the jumpstarts to develop numerous solutions with RFID/sensors.

http://wiki.rifidi.net/index.php?title= ... %27s_Guide

Soon we plan to release ALE which provides stadards for capturing RFID events via pure configuration using webservices

http://wiki.rifidi.net/index.php?title= ... %27s_Guide

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests