How stable is 'shell console' via web browser interface.

28 views
Skip to first unread message

David Marko

unread,
Jun 19, 2010, 2:48:41 PM6/19/10
to web2py-users
I just decided today to explore the 'shell' function the web2py
browser interface offers. But I found it very unstable. This works
very fine until I want to get back to my app. It locks database access
that means entire web2py server is locked and must be killed. I know
the shell interface warns about this and lead me to click on
'unlock ...' links, but it doesnt help. I have tried several times
with the same 'lock' end. My app is connected to PostgreSQL, I run
latest web2py trunk version on WinXP. The 'shell console' is very
powerful thing but useless when it causes server freeze. But maybe I
miss something significant. Can anyone share his experience or maybe
some hint?

David

Yarko Tymciurak

unread,
Jun 19, 2010, 2:55:30 PM6/19/10
to web2py-users
hint is: "...it seemed like a good idea at the
time...." (sqldesigner integration also falls in this bucket, I
think)

The command line shell is more powerful, and less problems --- and
you can run it _while_ you are
running the "other" server (which is, for example, how I would do
custom reports from PyCon registration site -
write a little one-shot function, and run it from a command line shell
for someone, while the registration site
was running on apache):

python web2py.py -S myapp -M

I have never found a situation where I couldn't get some ssh
connection to my server to make this happen (putty, straight ssh, or
otherwise), so the web shell was a curiousity... nice for demos, but
not distinctly useful enough to bother with.

That would be my best hint...

- Yarko

- Yarko
>
> David

Phyo Arkar

unread,
Jun 19, 2010, 8:17:58 PM6/19/10
to web...@googlegroups.com
Not ontopic

But best Ajax Webshell i ever used is AjaxTerm

It is very stable and works very well.

GIT: http://git.kirya.net/?p=ajaxterm.git
Direct : http://antony.lesuisse.org/software/ajaxterm/

mdipierro

unread,
Jun 20, 2010, 10:31:31 AM6/20/10
to web2py-users
Did you do

db.commit()

after you insert/update via the shell?
The web based shall does not commit transactions automatically because
they may span multiple http requests. If you do not commit them
explicitly the database remains lock.

I am not sure this is the problem for you but this would cause the
problem you experience.

Massimo


On Jun 19, 1:48 pm, David Marko <dma...@tiscali.cz> wrote:

David Marko

unread,
Jun 20, 2010, 11:00:29 AM6/20/10
to web2py-users
I just did a few fetches, no inserts or updates at all. I could
reproduce it a several times.

David
Reply all
Reply to author
Forward
0 new messages