Prev   

Troubleshooting

Table of Contents

1. I created a trigger using the mds-trigger-create, but I don't see any triggers when I type mds-trigger-view! Where are the triggers? Why is nothing happening?
2. I'm sure the registration was made properly, but the trigger script never fires. OR I followed all of the above steps, but where are the triggers? Why is nothing happening?
3. When trying to create the trigger, I get the following error: Error: ; nested exception is: org.apache.commons.httpclient.NoHttpResponseException: The server 127.0.0.1 failed to respond
4. General Troubleshooting

1. I created a trigger using the mds-trigger-create, but I don't see any triggers when I type mds-trigger-view! Where are the triggers? Why is nothing happening?

Did you set up a trigger registration? (See the Trigger Service Admin Guide) The trigger has been created (unless there was an error), but you will not see it and you cannot access it if the trigger registration has not been set up.

2. I'm sure the registration was made properly, but the trigger script never fires. OR I followed all of the above steps, but where are the triggers? Why is nothing happening?

Once you've completed the trigger registration, you can now create individual triggers. Trigger creation is performed using a client. See the User's Guide for more information on clients.

3. When trying to create the trigger, I get the following error: Error: ; nested exception is: org.apache.commons.httpclient.NoHttpResponseException: The server 127.0.0.1 failed to respond

...and I get the following error in the container screen:

      2007-08-21T18:49:39,632-05:00 ERROR container.GSIServiceThread [ServiceThread-18,process:117] [JWSCORE-192] Error processing request
      java.io.IOException: Token length 1347375956 > 33554432
      at org.globus.gsi.gssapi.net.impl.GSIGssInputStream.readToken(GSIGssInputStream.java:98)
      at org.globus.gsi.gssapi.net.impl.GSIGssInputStream.readHandshakeToken(GSIGssInputStream.java:59)
      at org.globus.gsi.gssapi.net.impl.GSIGssSocket.readToken(GSIGssSocket.java:65)
      at org.globus.gsi.gssapi.net.GssSocket.authenticateServer(GssSocket.java:127)
      at org.globus.gsi.gssapi.net.GssSocket.startHandshake(GssSocket.java:147)
      at org.globus.gsi.gssapi.net.GssSocket.getOutputStream(GssSocket.java:166)
      at org.globus.wsrf.container.GSIServiceThread.process(GSIServiceThread.java:115)
      at org.globus.wsrf.container.ServiceThread.run(ServiceThread.java:459)

Be sure that you have properly edited the $G_L/etc/globus_wsrf_mds_trigger/client-config-settings file. The "DefaultServiceAddress" parameter should properly reflect the service prefix from your container, e.g.: https://127.0.0.1:8444/wsrf/services/. The services you wish to monitor should also be consistent.

4. General Troubleshooting

Because the Trigger Service runs on top of the Java WS Core, general troubleshooting information can be found in Troubleshooting.

Prev   
Graphical user interfaces Home