Re: seaside Digest, Vol 178, Issue 4

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: seaside Digest, Vol 178, Issue 4

Long Haired David

Thanks for that but what does it mean? How would I resolve the issue?

David

It looks as if your dispatcher has a default name 'seaside' but does not have a *handler* for that name.


On 10/10/17 4:34 PM, David Pennington wrote:
Hi there. I am running a test system at the moment using VAST 8.6.3 and Seaside.

The traffic is infrequent and only when I am testing. I am running a development image on the server which I monitor regularly.

Quite often a debugger window opens as can be seen in the screen shot I have attached. This debugger trace has no connection with the code I am running and I cannot work out what is happening (I am a fairly new user of Seaside but a long, long term user of VAST).

I also attach a stack trace.

I would be grateful if anyone can help me track down what is happening. I have deleted the whole Smalltalk installation Andre-installed everything (twice) but I can't stop this.

Thanks in advance (and if you need any more info please let me know).
David


Message sent using Winmail Mail Server


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



--------- Original Message ---------
From: <[hidden email]>
To: <[hidden email]>
Subject: seaside Digest, Vol 178, Issue 4
Date: 10/11/2017 13:00:12 (Wed)

Send seaside mailing list submissions to
	[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
or, via email, send a message with subject or body 'help' to
	[hidden email]

You can reach the person managing the list at
	[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of seaside digest..."





Today's Topics:

   1. Re: Spurious activity on the Seaside/VisualAge Smalltalk
      server (Bob Arning)
   2. Re: Spurious activity on the Seaside/VisualAge Smalltalk
      server (Bob Arning)





_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



Message sent using Winmail Mail Server

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
David
Totally Objects
Doing Smalltalk since 1989
Reply | Threaded
Open this post in threaded view
|

Re: not having a handler for default name

Bob Arning-2

This bit suggests you received a request for a bare url '/' and since you have a default name of 'seaside' a decision was made to treat '/' as if it were '/seaside'. Your dispatcher does not know how to handle this and an error results.

WADispatcher>>#handleFiltered:named:
    self=a WADispatcher
    aRequestContext=a WARequestContext url: '/'
    aString='seaside'
WADispatcher>>#handleDefault:
    self=a WADispatcher
    aRequestContext=a WARequestContext url: '/'

If you are NOT interested in handling bare urls like '/', then removing the default name would be a good idea by evaluating something like this:

WAAdmin defaultDispatcher defaultName: nil

If you ARE interested in handling bare urls, then the default name needs to match an existing handler. So, either change the default name to match an existing handler or add a handler to match the default name.

On 10/11/17 9:33 AM, David Pennington wrote:
Thanks for that but what does it mean? How would I resolve the issue?

David

It looks as if your dispatcher has a default name 'seaside' but does not have a *handler* for that name.

On 10/10/17 4:34 PM, David Pennington wrote:
Hi there. I am running a test system at the moment using VAST 8.6.3 and Seaside.

The traffic is infrequent and only when I am testing. I am running a development image on the server which I monitor regularly.

Quite often a debugger window opens as can be seen in the screen shot I have attached. This debugger trace has no connection with the code I am running and I cannot work out what is happening (I am a fairly new user of Seaside but a long, long term user of VAST).

I also attach a stack trace.

I would be grateful if anyone can help me track down what is happening. I have deleted the whole Smalltalk installation Andre-installed everything (twice) but I can't stop this.

Thanks in advance (and if you need any more info please let me know).
David


Message sent using Winmail Mail Server


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



--------- Original Message ---------
From: [hidden email]
To: [hidden email]
Subject: seaside Digest, Vol 178, Issue 4
Date: 10/11/2017 13:00:12 (Wed)

Send seaside mailing list submissions to
	[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
or, via email, send a message with subject or body 'help' to
	[hidden email]

You can reach the person managing the list at
	[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of seaside digest..."





Today's Topics:

   1. Re: Spurious activity on the Seaside/VisualAge Smalltalk
      server (Bob Arning)
   2. Re: Spurious activity on the Seaside/VisualAge Smalltalk
      server (Bob Arning)





_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



Message sent using Winmail Mail Server


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside