Triggering a method

[Morley]

if you restart servoy
Then again you make new records by invoking that jsp

And you see Output like 35 , 36 or something like that.
Before and End count.

When you restart servoy completely and do exactly the same thing again
So invoke you jsp again. What is the output....
Is it again 35, 36 OR is it greater then that?? is it 36,37 or what ever.

There are days when I'm particularly dense. Where exactly are you seeing "Output", "Before and End count"?

When you say "restart servoy" I'm assuming you are meaning Servoy Server. I'm also running Servoy Developer pulling its data from the server, positioned on the form scraAnalysisNew so I can see the full list of records, including their creation datetime.

Kind regards,

[jcompagner]

output of the server you can see in the console or in the log files

But do it differently.

Start up the developer run the method a view times so that you can see where it stops what the last size is of the foundset.

Then close the developer

run the server

hit the jsp a view times. (count it)

then close the server
and run the developer again.

Where the does size start from? What you did the last time with the developer or is the count + the number of times you accessed the jsp.

[Morley]

output of the server you can see in the console or in the log files

But do it differently.

Start up the developer run the method a view times so that you can see where it stops what the last size is of the foundset.

Then close the developer

run the server

hit the jsp a view times. (count it)

then close the server
and run the developer again.

Where the does size start from? What you did the last time with the developer or is the count + the number of times you accessed the jsp.

This is remarkable!

1. Ran the newRecord method twice with a foundset of 37 at the end. Quit Servoy Developer.
2. Rebooted Servoy Server and ran the JSP twice. Because the server is physically a few miles away and I haven't set it for remote launch I opted instead to just close down the newClient session.
3. Launched Servoy Developer. It looked exactly as before. I then ran the newRecord method again. This time I had a start of 40 and stop of 41. Even more interesting the new records were not at the bottom of the table and the pk of the new records are out of sequence.

The PKs of records 36 and 37 are 2722 and 2723. But the PKs of the two new records generated by the JSP are 2438 and 2439. There are also two other new records in the same 2400 sequence created very early this morning which didn't show themselves earlier.

I'm not sure what to make of this.

An additional note. Still not sure what you mean by the console and log files. /Servoy/server/logs shows three types of logs, none of which present record counts.

Catalina log:
2006-07-03 14:57:57 HttpConnector Opening server socket on all host IP addresses
2006-07-03 14:57:59 HttpConnector[8080] Starting background thread
2006-07-03 14:57:59 HttpProcessor[8080][0] Starting background thread
2006-07-03 15:02:09 HttpProcessor[8080][1] Starting background thread

Localhost access:
70.50.120.175 - - [03/Jul/2006:15:03:03 -0500] "GET /servoy-admin/clients HTTP/1.1" 200 10764
70.50.120.175 - - [03/Jul/2006:15:03:06 -0500] "GET /servoy-admin/clients/shutdown/solution/64 HTTP/1.1" 200 7473
70.50.120.175 - - [03/Jul/2006:15:03:08 -0500] "POST /servoy-admin/clients/shutdown/solution/64 HTTP/1.1" 200 7517
70.50.120.175 - - [03/Jul/2006:15:20:19 -0500] "GET /servoy-admin HTTP/1.1" 302 654
70.50.120.175 - - [03/Jul/2006:15:20:19 -0500] "GET /servoy-admin/ HTTP/1.1" 200 15574
70.50.120.175 - - [03/Jul/2006:15:20:21 -0500] "GET /servoy-admin/log HTTP/1.1" 200 8496

localhost:
2006-07-03 14:57:59 StandardManager[]: Seeding random number generator class java.security.SecureRandom
2006-07-03 14:57:59 StandardManager[]: Seeding of random number generator has been completed
2006-07-03 14:57:59 ContextConfig[]: Added certificates -> request attribute Valve
2006-07-03 14:57:59 StandardWrapper[:default]: Loading container servlet default
2006-07-03 14:57:59 default: init
2006-07-03 14:57:59 StandardWrapper[:invoker]: Loading container servlet invoker
2006-07-03 14:57:59 invoker: init
2006-07-03 14:57:59 jsp: init
2006-07-03 14:58:44 servoy_server_admin: init
2006-07-03 15:01:26 jsp: init

Kind regards,

[Jan Aleman]

Sounds like mixing up various instances of server, developer, etc.

I'm quite sure if you'd do a clean install on a clean machine and run ONLY server OR developer (and don't mix them up) it would work perfectly fine. Both Johan and I have tried your solution and method and we're unable to not let it run right.

[Morley]

Sounds like mixing up various instances of server, developer, etc.

I'm quite sure if you'd do a clean install on a clean machine and run ONLY server OR developer (and don't mix them up) it would work perfectly fine. Both Johan and I have tried your solution and method and we're unable to not let it run right.

Would appreciate some pointers on running a clean install and how to create a "clean machine". There's client data on the server which needs to be preserved.

The server is on an Xserve at a remote location. I use a WinXP machine for development, pulling data from localhost. When I need to see what's going on on the server (which isn't often) I switch Developer to present data from the server (such as checking whether the JSP has indeed created a new record, or to run the newRecord method through the debugger). I don't run Developer directly on the server.

To sort this out, do I need to reinstall both the Xserve and the WinXP machine? Are you saying that if I need to modify data on the server I should not be doing so remotely?

Your counsel on setting this to rights appreciated.

[Jan Aleman]

If you never run both at the same time you are fine.

[Morley]

End of the saga. Reformatted the Xserve from scratch, installed Servoy from scratch, brought back the original database, the JSPs, etc. Re-ran the test JSP and find a new record is created. Probable cause: very early on before I knew any better I ran Developer while Servoy Server was running. The legacy of this action set off something in the innards of this installation. A clean re-install has cleared it.

Much thanks to everyone reading and commenting on this thread.

Kind regards,