Problems of the subscribe and notify in SES

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Problems of the subscribe and notify in SES

Chenfeng
I am already worked with SES several month, I connected SES with SOS database
via sos-ses-feeder . however, until now i still cannot understand why after
I subscribe and predefined some rules. the consumer port cannot received
anything.
Only if I do notify operation then the costumer port can received the same
massages as the notify contents which i have requested it.
My question is when some emergency really happened and even though I have
subscribe it and I still cannot get any response on the costumer port? Why i
have to do the notify operation? And how do I know if something really
happened when the values are over the threshold which I have predefined?

the version of SES i use 1.2.2,
the feeder I use 1.0.0,
the SOS I use 4.4.0.
the system in my computer is windows7.
Tomcat is 8.5



--
View this message in context: http://sensorweb.forum.52north.org/Problems-of-the-subscribe-and-notify-in-SES-tp4028983.html
Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problems of the subscribe and notify in SES

Matthes Rieke (52North)
Hi Chenfeng,

do better understand the issue, it would be good if you could send the
log files of the SES (should be in the tomcat log folder: 52n-ses.log).
Also, could you provide the subscribe request (XML) as this would help
to understand the logic you intend to create.

If I understand correctly, the consumer receives messages if you simply
use the Notify operation. This lets me assume that the issue might be in
the sos-ses-feeder (maybe related to your other email).

Best regards
Matthes


On 25.07.2017 15:01, Chenfeng wrote:

> I am already worked with SES several month, I connected SES with SOS database
> via sos-ses-feeder . however, until now i still cannot understand why after
> I subscribe and predefined some rules. the consumer port cannot received
> anything.
> Only if I do notify operation then the costumer port can received the same
> massages as the notify contents which i have requested it.
> My question is when some emergency really happened and even though I have
> subscribe it and I still cannot get any response on the costumer port? Why i
> have to do the notify operation? And how do I know if something really
> happened when the values are over the threshold which I have predefined?
>
> the version of SES i use 1.2.2,
> the feeder I use 1.0.0,
> the SOS I use 4.4.0.
> the system in my computer is windows7.
> Tomcat is 8.5
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/Problems-of-the-subscribe-and-notify-in-SES-tp4028983.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines

_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problems of the subscribe and notify in SES

Chenfeng
Hey Matthes,
Thanks for you answer my question. I think my problem is on the sos-ses-feeder side. I don not know did I connect it correctly or not. Because I subscribed all on the SES side, so it means when i insert any observations into SOS database, on the SES side, i can received  the notifications via the costumer endpoint. However, when i test it and no matter how do i insert observations into SOS database, i cannot received anything.
Is it mean that the sos-ses-feeder doesn't connect the SES and the SOS database? I confused about this, because on the feeder's readme file it said that  only SOS version 1.0.0 is supported,but my SOS version is 4.4.0,  I don not know is this problem, but nowadays all the SOS version have already over than 4.0.0. Or maybe I did some wrong configuration in sos-ses-feeder. Could you help me?

The version I used:
Tomcat: 8.5
SOS: 4.4.0
SES: 1.2.2
System: Windows7

This is my configuration information of the feeder:
in the file configuration.xml:

<properties>
       
        <entry key="capabilities_task_period">86400</entry>
       
        <entry key="observations_task_period">300</entry>
       
        <entry key="update_observation_period">5</entry>
       
        <entry key="maximum_number_procedures"></entry>
       
        <entry key="procedure_name_constraints"></entry>
   
    <entry key="prohibit_procedure_names">general</entry>
   
        <entry key="nodatas">-999999999</entry>
       
        <entry key="sos_version">4.4.0</entry>
   
    <entry key="start_timestamp">900</entry>
   
    <entry key="sleep_time_observation">1000</entry>

       
         <entry key="ses_url">http://localhost:8080/52n-ses-1.2.2/services/Broker</entry>
       
        <entry key="ses_basic_port_type_path">/Broker</entry>
        <entry key="ses_version">1.2.2</entry>
        <entry key="ses_default_topic_dialect">http://docs.oasis-open.org/wsn/t-1/TopicExpression/Simple</entry>
        <entry key="ses_default_topic">ses:Measurements</entry>
        <entry key="ses_register_publisher_lifetime">2999-12-31T23:59:59+00:00</entry>
        <entry key="ses_register_publisher_endpoint">http://localhost:8080/</entry>
       
</properties>



in the file hibernate.cfg.xml:

<property name="connection.url">jdbc:postgresql://localhost:5432/postgre_sample</property>
    <property name="connection.username">postgres</property>
    <property name="connection.password">1234</property>
    <property name="connection.driver_class">
      org.postgresql.Driver
      </property>
    <property name="dialect">
      org.hibernate.dialect.PostgreSQLDialect
      </property>
    <property name="cache.provider_class">
      org.hibernate.cache.EhCacheProvider
      </property>
    <property name="current_session_context_class">thread
      </property>
    <property name="hibernate.transaction.factory_class">
      org.hibernate.transaction.JDBCTransactionFactory
      </property>
  <property name="hibernate.hbm2ddl.auto">create</property>
    <mapping resource="org/n52/sos/feeder/baw/hibernate/SOS.hbm.xml" />
    <mapping resource="org/n52/sos/feeder/baw/hibernate/Sensor.hbm.xml" />
    <mapping resource="org/n52/sos/feeder/baw/hibernate/Offering.hbm.xml"/>
    <mapping resource="org/n52/sos/feeder/baw/hibernate/ObservedProperty.hbm.xml"/>
  </session-factory>
</hibernate-configuration>




This is all the sos-ses feeder logs:
 2017-07-26 12:17:39,076 INFO (Configuration.java:316) - ######################################################################
2017-07-26 12:17:39,076 INFO (Configuration.java:317) - ######################  Configuration loaded   #######################
2017-07-26 12:17:39,076 INFO (Configuration.java:318) - ######################################################################
2017-07-26 12:17:39,110 INFO (DescriptionTask.java:79) - ############ Do Description task #############
2017-07-26 12:17:39,112 DEBUG (DescriptionTask.java:83) - MaxNumberProcedures: 2147483647



Loading...