JSLEE Discussions
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
SIS: no triggers matched request, continue
Forum Index » Rhino SLEE Discussions
Author Message
babass


Joined: 11/02/2010 04:58:17
Messages: 180
Offline

Hi,

I'm trying SIS and I have some problem with it. I defined a trigger which has a condition which is always true. Despite this, SIS tells me that no triggers matched request.

Have you an idea about what I missed?

Regards,

Bastien
damiannowak


Joined: 30/07/2010 22:25:44
Messages: 95
Offline

Try reloading the SIS.
I had a similar issue in the past, and after trigger is uploded to SIS, it must be reloaded.

D.
babass


Joined: 11/02/2010 04:58:17
Messages: 180
Offline

Hi,

It's already done and I tried to reboot SDK too...
babass


Joined: 11/02/2010 04:58:17
Messages: 180
Offline

Few news, when I restart the SDK I get this beautiful stacktrace:

2011-08-19 15:16:36.704 Info [trace.in_sis.insis] <main> Loading configuration from profile ProfileID[table=sis-configs-in,profile=in-sis]: (no description)
2011-08-19 15:16:36.710 Warning [trace.in_sis.insis] <main> Configuration error, operational functionality will not be available until configuration errors are resolved
javax.slee.resource.InvalidConfigurationException: Trigger address tracing profile table in-sis-triggers is not of the expected profile specification
at com.opencloud.slee.resources.insis.INSISResourceAdaptor.a(2.3.1.0:1660)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor.a(2.3.1.0:1601)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor.a(2.3.1.0:178)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor$8.b(2.3.1.0:1398)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor$8.run(2.3.1.0:1390)
at com.opencloud.slee.resources.sis.management.server.TransactionExecutor$Action.runInTransaction(2.3.1.0:84)
at com.opencloud.slee.resources.sis.management.server.TransactionExecutor.execute(2.3.1.0:33)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor.a(2.3.1.0:1388)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor.raConfigure(2.3.1.0:293)
at com.opencloud.ob.RhinoSDK.q$a.a(2.2-0.7-42154:304)
at com.opencloud.ob.RhinoSDK.q$a.b(2.2-0.7-42154:302)
at com.opencloud.ob.RhinoSDK.q.a(2.2-0.7-42154:607)
at com.opencloud.ob.RhinoSDK.q.a(2.2-0.7-42154:302)
at com.opencloud.ob.RhinoSDK.jC.a(2.2-0.7-42154:279)
at com.opencloud.ob.RhinoSDK.jN.a(2.2-0.7-42154:717)
at com.opencloud.ob.RhinoSDK.jN.b(2.2-0.7-42154:417)
at com.opencloud.ob.RhinoSDK.jN.a(2.2-0.7-42154:148)
at com.opencloud.ob.RhinoSDK.dX.a(2.2-0.7-42154:156)
at com.opencloud.rhino.node.RhinoStarter.a(2.2-0.7-42154:1162)
at com.opencloud.rhino.node.RhinoStarter.<init>(2.2-0.7-42154:689)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.opencloud.rhino.node.Rhino.startRhinoNode(2.2-0.7-42154:183)
at com.opencloud.rhino.node.Rhino.main(2.2-0.7-42154:153)
2011-08-19 15:16:36.713 Critical [rhino.facility.alarm.manager] <main> Alarm 101:214248158637:0 [RAEntityNotification[entity=in-sis],misconfiguration,SIS] was raised at 2011-08-19 15:16:36.712 to level Critical
SIS is misconfigured, operational functionality disabled
2011-08-19 15:16:37.082 Warning [trace.in_sis.insis.management] <main> error looking up active triggers
javax.slee.management.ManagementException: No trigger profile table has been configured
at com.opencloud.slee.resources.sis.management.server.TriggerManagement.b(2.3.1.0:403)
at com.opencloud.slee.resources.sis.management.server.TriggerManagement.a(2.3.1.0:342)
at com.opencloud.slee.resources.sis.management.server.TriggerManagement.a(2.3.1.0:360)
at com.opencloud.slee.resources.sis.management.server.TriggerManagement.reload(2.3.1.0:264)
at com.opencloud.ob.insis.base.bn.reload(2.3.1.0:187)
at com.opencloud.slee.resources.insis.management.server.INSISManagement.<init>(2.3.1.0:30)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor.U(2.3.1.0:1695)
at com.opencloud.slee.resources.insis.INSISResourceAdaptor.raConfigure(2.3.1.0:315)
at com.opencloud.ob.RhinoSDK.q$a.a(2.2-0.7-42154:304)
at com.opencloud.ob.RhinoSDK.q$a.b(2.2-0.7-42154:302)
at com.opencloud.ob.RhinoSDK.q.a(2.2-0.7-42154:607)
at com.opencloud.ob.RhinoSDK.q.a(2.2-0.7-42154:302)
at com.opencloud.ob.RhinoSDK.jC.a(2.2-0.7-42154:279)
at com.opencloud.ob.RhinoSDK.jN.a(2.2-0.7-42154:717)
at com.opencloud.ob.RhinoSDK.jN.b(2.2-0.7-42154:417)
at com.opencloud.ob.RhinoSDK.jN.a(2.2-0.7-42154:148)
at com.opencloud.ob.RhinoSDK.dX.a(2.2-0.7-42154:156)
at com.opencloud.rhino.node.RhinoStarter.a(2.2-0.7-42154:1162)
at com.opencloud.rhino.node.RhinoStarter.<init>(2.2-0.7-42154:689)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.opencloud.rhino.node.Rhino.startRhinoNode(2.2-0.7-42154:183)
at com.opencloud.rhino.node.Rhino.main(2.2-0.7-42154:153)


in-sis-triggers profile table has been built by the installation script of SIS.
stevena


Joined: 27/03/2008 13:43:16
Messages: 274
Location: Cambridge, UK
Offline

Well that's something I've never seen before, and I can't reproduce it either using the same versions of Rhino and the SIS. It suggests to me that the Rhino database has been corrupted somehow.

Do you only have the one version of SIS installed?

If you still have this setup can you please try doing a rhino-export of the configuration and check the profile table create command in the resulting build.xml? It should look like this:Going back to your original question, did you activate the trigger?

Steven Adams
Senior Software Engineer
OpenCloud
babass


Joined: 11/02/2010 04:58:17
Messages: 180
Offline

Hi Steven,

I solved the problem when I completely reinstalled the SIS. (I did exactly the same things than the first time...)

FYI, the trigger was activated ;)

stevena


Joined: 27/03/2008 13:43:16
Messages: 274
Location: Cambridge, UK
Offline

Good that it's fixed now but I can't explain why it broke in the first place.
All I can assume is that whatever broke the profile table was also the reason why the SIS wasn't finding your trigger.

Regards,
Steve

Steven Adams
Senior Software Engineer
OpenCloud
michael.klimenko


Joined: 22/11/2015 23:29:41
Messages: 6
Offline

Hi ,
Exact same problem here with SIS v2.5. :(
Log:


Reinstalling SIS + Restarting Rhino SLEE does not help.

Here is my Trigger :


Here is my composition:


Service Ref:


SIS Network Interface :


What am I doing wrong ?

michael.klimenko


Joined: 22/11/2015 23:29:41
Messages: 6
Offline

Solved!
My problem was with stating wrong variable names/values.
At trigger <on-condition> I used initial-dp.service-key instead of initial-dp.arg.service-key.
Also initial-dp.event-type-bcsm should have been changed to "collectedInfo", as of v2.5.
Now everything is working as expected.

This message was edited 2 times. Last update was at 04/01/2017 10:07:08

 
Forum Index » Rhino SLEE Discussions
Go to:   
Powered by JForum 2.1.8 © JForum Team