nt="X"
Nov 28 17:28:24 app/web.2 at=INFO
request_id=aa3101c9-0502-4015-86d3-2fc420815240
logger=db.backends.postgis.base Closed connection 1105751 user_agent="X"
Nov 28 17:28:24 app/web.2 at=ERROR
request_id=aa3101c9-0502-4015-86d3-2fc420815240
logger=db.backends.postgis.b
Michele,
> ... the database connection seems to shut down randomly.
Could be the same problem as I described in
Database "InterfaceError connection already closed" with asgi.
https://groups.google.com/g/django-users/c/RmtFuCVLfPE/m/dBQjq7FsBQAJ
Django doesn't stick
).
The issue I have is that the database connection seems to shut down
randomly. Django reports errors like this:
InterfaceError: connection already closed File
"django/core/handlers/exception.py", line 55, in inner response =
get_response(request) File "django/core/handlers/base.py
sessions which are set to be expired after
> the browser is closed but they don't seem to expire.
>
> [image: code.PNG]
> The output:
> get_expire_at_browser_close: True
> All sessions: (A QuerySet contains all the sessions including the ones
> that are changed after t
I'm trying to clear the expired sessions which are set to be expired after
the browser is closed but they don't seem to expire.
[image: code.PNG]
The output:
get_expire_at_browser_close: True
All sessions: (A QuerySet contains all the sessions including the ones that
are changed
Database "InterfaceError connection already closed" with asgi.
This often seems to happen when an exception was triggered, e.g., even
a simple Http404 due to incorrect URL.
A suspicion is discussed below. Ideas about this suspicion, how to
validate it and how to avoid the probl
hare/virtualenvs/chat-A0fEktPe/lib/python3.8/site-packages/django/db/backends/base/base.py",
line 237, in _cursor return self._prepare_cursor(self.create_cursor(name))
File
"/home/ross/.local/share/virtualenvs/chat-A0fEktPe/lib/python3.8/site-packages/django/utils/asyncio.py",
>>
>> folder path, EXTENSION
>>
>> for example
>>
>> C:\users , .CSV
>> C:\Windows, .PDF
>>
>> etc
>>
>> so, the CSV file will contain more than 200 folder paths and their
>> extensions. What I have to do in code is I should
; etc
>
> so, the CSV file will contain more than 200 folder paths and their
> extensions. What I have to do in code is I should loop through the CSV file
> and print the contents of the CSV file parallelly by assigning it to
> workers in a POOL
>
> So below is my Code, but it
, the CSV file will contain more than 200 folder paths and their
extensions. What I have to do in code is I should loop through the CSV file
and print the contents of the CSV file parallelly by assigning it to
workers in a POOL
So below is my Code, but it throws "I/O operation on closed file&
Hi Mike,
I tried with custom persistent connection, but results in same error. My
environment is Django + postgres + nginx + gunicorn
On Saturday, August 29, 2009 at 5:38:58 PM UTC+5:30, Mike wrote:
>
> Hi,
>
> I made some small custom psycopg2 backend that implements persistent
> connection us
local server. But when I launch it on the VPS
> and if call send_mail more than once, below mesasge appear:
>
> "SMTPServerDisconnected: Connection unexpectedly closed: [Errno 104]
> Connection reset by peer"
>
> But if only one backlog been filtered and only call once send
I'm also seeing this with a slightly simpler scenario that also involves a
requests.get inside a LiveServerTestCase. Success/failure is random with
failures reporting the same ConnectionError message. Any ideas?
--
You received this message because you are subscribed to the Google Groups
"Djan
.6/http/client.py", line 297, in begin
> version, status, reason = self._read_status()
> File "/usr/lib64/python3.6/http/client.py", line 266, in _read_status
> raise RemoteDisconnected("Remote end closed connection without"
> http.client.RemoteDisco
p/client.py", line 297, in begin
version, status, reason = self._read_status()
File "/usr/lib64/python3.6/http/client.py", line 266, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed co
Thanks, this fixed my issue.
On Tuesday, 12 April 2016 04:28:21 UTC+1, thinkwell wrote:
>
> I'd parked this problem for quite some time, until it finally became
> incontestably necessary to wrestle the issue to the ground.
>
> What I found, after many hours of experimenting - too much like the r
Great. Thanks Jason.
On Friday, November 17, 2017 at 8:29:02 AM UTC-5, Jason wrote:
>
> You can do this with pip, check out
> http://www.nyayapati.com/srao/2014/06/how-to-pip-install-python-packages-offline/
>
>>
>>
--
You received this message because you are subscribed to the Google Groups
You can do this with pip, check out
http://www.nyayapati.com/srao/2014/06/how-to-pip-install-python-packages-offline/
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an
I need to upgrade Django 1.9 to 1.11 on a closed network. Is there a way
to upgrade from a downloaded source file ?
I've successfully upgraded on our Cloud environment using "pip3.5 install
-U Django" but can't use this command on a closed network since pip is
looking to
103 if c == six.b("\n"):
>
> c:\Python27\lib\site-packages\websocket\_socket.pyc in recv(sock, bufsize)
> 78
> 79 try:---> 80 bytes_ = sock.recv(bufsize)
> 81 except socket.timeout as e:
> 82 message = extract_err_mes
gt; 80 bytes_ = sock.recv(bufsize)
81 except socket.timeout as e:
82 message = extract_err_message(e)
error: [Errno 10054] An existing connection was forcibly closed by the remote
host
I have redis running, manage.py runserver running, and I'm using
django-channels.
> self.connect()
> File
> "/usr/local/bin/lib/python2.7/site-packages/django/db/backends/base/base.py",
> line 119, in connect
> self.connection = self.get_new_connection(conn_params)
> File
> "/usr/local/bin/lib/python2.7/site-packages/django/db
ct()
> File
>
> "/usr/local/bin/lib/python2.7/site-packages/django/db/backends/base/base.py",
> line 119, in connect
> self.connection = self.get_new_connection(conn_params)
> File
>
> "/usr/local/bin/lib/python2.7/site-packa
ase.py",
> line 119, in connect
> self.connection = self.get_new_connection(conn_params)
> File
> "/usr/local/bin/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py",
>
> line 176, in get_new_connection
>
t__
> six.reraise(dj_exc_type, dj_exc_value, traceback)
> File
> "/usr/local/bin/lib/python2.7/site-packages/django/db/backends/base/base.py",
> line 130, in ensure_connection
> self.connect()
> File
> "/usr/local/bin/lib/python2.7/site-pac
se.py",
line 176, in get_new_connection
connection = Database.connect(**conn_params)
File "/usr/local/bin/lib/python2.7/site-packages/psycopg2/__init__.py",
line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
django.db.utils.Operatio
On May 20, 2017 8:33 PM, "djangorobert" wrote:
hi james im going off of andrew godwins django channels example on github
the multi chat example and using Webfactions hosting services.
im getting the error of the websocket being closed
I know your saying to maybe chaning it to wss ins
hi james im going off of andrew godwins django channels example on github
the multi chat example and using Webfactions hosting services.
im getting the error of the websocket being closed
I know your saying to maybe chaning it to wss instead of ws do you mean to
change it in the javascript
Thanks james going to try it out will post my results in a bit thank you
for your time its appreciated.
On Friday, May 19, 2017 at 11:21:33 PM UTC-5, James Schneider wrote:
>
>
>
> On May 19, 2017 8:02 PM, "djangorobert" > wrote:
>
>
> var connect = function () {
> log('connect');
>
On May 19, 2017 8:02 PM, "djangorobert" wrote:
var connect = function () {
log('connect');
var oldWs = ws;
ws = new config.constructor(url, protocols);
thats part of what the error points me to in google tools:
(index):182 Disconnected from chat socket
VM170 webs
throws an error the error that i am getting is this:
> WebSocket connection to 'ws://openchat.us:24711/' failed: WebSocket is
> closed before the connection is established.
>
>
> settings.py
>
> CHANNEL_LAYERS = {
>"default": {
>
et connection to 'ws://openchat.us:24711/' failed: WebSocket is
> closed before the connection is established.
>
>
> settings.py
>
> CHANNEL_LAYERS = {
>"default": {
> "BACKEND": "asgi_redis.RedisChannelLayer
throws an error the error that i am getting is this:
WebSocket connection to 'ws://openchat.us:24711/' failed: WebSocket is
closed before the connection is established.
settings.py
CHANNEL_LAYERS = {
"default": {
"BACKEND": "a
It looks like the source of this error is related to a spatialite internal
connection leak (discussed in this
post: https://groups.google.com/forum/#!topic/spatialite-users/xrV7CA_GlwM)
Each time Django requests a connection to the database sqlite loads the
spatialite extension module, which cr
On Tue, Jan 17, 2017 at 7:58 PM, Fred Stluka wrote:
> Mike,
>
> As of version 1.6, Django supports persistent DB connections
> (connection pooling).
Pedantry: Persistent connections are not the same as connection
pooling. With persistent connections, if a worker does not have a
currently open con
27;re seeing doesn't
seem to match this
documented behavior. I'd have expected
CONN_MAX_AGE = 0
to prevent connections from being reused, so
they should be
clo
>> and close its own connection. You can set it to None to allow
>> an unlimited number of connections. See:
>> - https://docs.djangoproject.com/en/dev/ref/databases/
>>
>> However, the behavior you're seeing doesn't seem to match this
>> documented be
havior. I'd have expected CONN_MAX_AGE = 0
to prevent connections from being reused, so they should
be
closed at the end of the request that used them. So,
unless you
have 65 or more concurrent req
t; - https://docs.djangoproject.com/en/dev/ref/databases/
>
> However, the behavior you're seeing doesn't seem to match this
> documented behavior. I'd have expected CONN_MAX_AGE = 0
> to prevent connections from being reused, so they should be
> closed at the end
_AGE = 0
to prevent connections from being reused, so they should be
closed at the end of the request that used them. So, unless you
have 65 or more concurrent requests, you should not be hitting
your limit.
I'm not surprised that CONN_MAX_AGE = None has an effect, but
When Django closes a database connection at the end of a request/response
cycle does that connection still maintain its hold on the database?
I ask because I am running an app on a spatialite (v4.3.0a) database,
which, due to a limitation in the GEOS library (v3.6.1-CAPI-1.10.1 r0), can
onl
response complete for
>> http.response!lCwBwWsyjxGf
>>
>> ...
>>
>>
>>
>>
>> The rqworker also:
>>
>>
>> mysite.local
>>
>> 2016-12-22 10:58:31,984 - DEBUG - worker - Got message on http.request
>> (reply http.response!MLkDhtLSmyEy)
>>
ponse!MLkDhtLSmyEy)
>
> 2016-12-22 10:58:31,985 - DEBUG - runworker - http.request
>
> 2016-12-22 10:58:31,985 - DEBUG - worker - Dispatching message on
> http.request to channels.staticfiles.StaticFilesConsumer
>
>
> The error I am getting in safari & chrome is:
> &qu
mer
The error I am getting in safari & chrome is:
"WebSocket connection to 'wss://mysite.local/chat/stream/' failed:
WebSocket is closed before the connection is established. response code:
200"
When I access the site on from the server via localhost:8000/chat
everything w
mail_to)
This command can run well in local server. But when I launch it on the VPS
and if call send_mail more than once, below mesasge appear:
"SMTPServerDisconnected: Connection unexpectedly closed: [Errno 104]
Connection reset by peer"
But if only one backlog
I'd parked this problem for quite some time, until it finally became
incontestably necessary to wrestle the issue to the ground.
What I found, after many hours of experimenting - too much like the random
walk, I suppose, is that every time I overrode setUpClass, I also had to
override tearDownC
>> Traceback (most recent call last):
>> File
>> "/usr/local/lib/python3.4/dist-packages/django/db/backends/base/base.py",
>> line 137, in _cursor
>> return self.create_cursor()
>> File
>> "/u
line 137, in _cursor
>> return self.create_cursor()
>> File
>> "/usr/local/lib/python3.4/dist-packages/django/db/backends/postgresql_psycopg2/base.py"
>> , line 212, in create_cursor
>> cursor = self.connection.cursor()
>> psycopg2.InterfaceError: co
n _cursor
> return self.create_cursor()
> File
> "/usr/local/lib/python3.4/dist-packages/django/db/backends/postgresql_psycopg2/base.py"
> , line 212, in create_cursor
> cursor = self.connection.cursor()
> psycopg2.InterfaceError: connection already closed
>
lib/python3.4/dist-packages/django/db/backends/postgresql_psycopg2/base.py"
, line 212, in create_cursor
cursor = self.connection.cursor()
psycopg2.InterfaceError: connection already closed
The above exception was the direct cause of the following exception:
Traceback (most rece
ursor()
File
"C:\Python27\lib\site-packages\django\db\backends\postgresql_psycopg2\base.py"
, line 212, in create_cursor
cursor = self.connection.cursor()
InterfaceError: connection already closed
It looks like the postgresql database is closing mid-test,
Russ,
I have a view which create a new thread to process files user uploaded. I
found either InMemoryUploadedFile or TempUploaedFile is closed in the new
thread. I think that might be caused by the exit of the view thread. Do you
have any idea how to re-open the closed UploadedFile or clone
)
> File
> "C:\MyProjects\WuWuKe\venv\lib\site-packages\mysql\connector\connection.py",
> line 722, in cmd_query
> result = self._handle_result(self._send_cmd(ServerCmd.QUERY, query))
> File
> "C:\MyProjects\WuWuKe\venv\lib\site-packages\mysql\conne
packages\mysql\connector\connection.py",
line 510, in _send_cmd
return self._socket.recv()
File
"C:\MyProjects\WuWuKe\venv\lib\site-packages\mysql\connector\network.py",
line 253, in recv_plain
errno=2055, values=(self.get_address(), _strioerror(err)))
DatabaseError: Lost
to Django 1.7, I got an error "I/O operation on closed file" when
>> getting to the second view function. I found out the root cause for this
>> error is that on Django 1.7, InMemoryUploadedFile object retrieved from
>> request.FILES got automatically closed at the end
On Tue, Dec 16, 2014 at 4:53 AM, Hong Yi wrote:
> Hello,
>
> I am new to Django and have implemented two views and their corresponding
> template pages and they are working well in Django 1.6. However, when
> migrating to Django 1.7, I got an error "I/O operation on closed
Hello,
I am new to Django and have implemented two views and their corresponding
template pages and they are working well in Django 1.6. However, when
migrating to Django 1.7, I got an error "I/O operation on closed file" when
getting to the second view function. I found out the root
uld I be doing
> in my code that is screwing with the DB connection?
>
> The full stack trace is below. It seems to be happening while the request
> is starting that the DB connection has already been closed?
>
> We are running this on:
> Ubuntu 12.04
>
> Django 1.6.5
>
doing
in my code that is screwing with the DB connection?
The full stack trace is below. It seems to be happening while the request
is starting that the DB connection has already been closed?
We are running this on:
Ubuntu 12.04
Django 1.6.5
Psycopg 2.5.3
File "django/core/handlers/base
ance as
> the `content` parameter to `FieldFile.save`.
>
> In summary: The method `FieldFile.save` saves `content` to `self.storage`
> (which causes `content` to be closed) but then attempts to access the size
> of `content`. This causes a ValueError("I/O operation on closed f
BytesIO instance as the `file` parameter
to an ImageFile instance, then supply that ImageFile instance as the
`content` parameter to `FieldFile.save`.
In summary: The method `FieldFile.save` saves `content` to `self.storage`
(which causes `content` to be closed) but then attempts to access the size
ession open and a new user arrives at the same
navigator after that session expired, if the new user attempts to use that
same session, the session will be automatically closed. However, if now
this new user logs in again, he is redirected to the last page where the
previous user was.
I have t
;
> SESSION_EXPIRE_AT_BROWSER_CLOSE denotes whether the session cookie is
> set as a session cookie (browser removes the cookie when it closes) or
> whether it is a permanent cookie (with lifetime equal to the expiry
> date set in the model).
>
> It does not affect anything to d
pls check browser settings.
On Tue, Sep 18, 2012 at 5:20 PM, Pervez Mulla wrote:
> Hi,
>
> I have developed simple website with Django framework.
>
> When i want to switch to other page, the browser getting closed..:(
>
> What the problem for this ?
>
> Thank You
>
are you using internet explorer?
On Tue, Sep 18, 2012 at 7:50 AM, Pervez Mulla wrote:
> Hi,
>
> I have developed simple website with Django framework.
>
> When i want to switch to other page, the browser getting closed..:(
>
> What the problem for this ?
>
> Than
Hi,
I have developed simple website with Django framework.
When i want to switch to other page, the browser getting closed..:(
What the problem for this ?
Thank You
Pervez
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To po
l. In this, creating a superuser
is described, using
manage.py createsuperuser --username=joe --email=j...@example.com
<mailto:j...@example.com>
Using this leads to an error, which I could match to the closed
ticket #16017.
But I couldn't find how to pr
;m a newbie following the tutorial. In this, creating a superuser is
> described, using
>
> manage.py createsuperuser --username=joe --email=j...@example.com
>
>
> Using this leads to an error, which I could match to the closed ticket
> #16017.
>
> But I couldn'
a het
volgende:
I'm a newbie following the tutorial. In this, creating a superuser
is described, using
manage.py createsuperuser --username=joe --email=j...@example.com
<mailto:j...@example.com>
Using this leads to an error, which I could match to the closed
ticket #
On Fri, Sep 14, 2012 at 10:26 AM, Bob Aalsma
wrote:
> macpro1:~ bobaalsma$ locale
> LANG=
> LC_COLLATE="C"
> LC_CTYPE="UTF-8"
> LC_MESSAGES="C"
> LC_MONETARY="C"
> LC_NUMERIC="C"
> LC_TIME="C"
> LC_ALL=
> macpro1:~ bobaalsma$ python -c 'import locale; print
> locale.getdefaultlocale()'
>
> Traceba
> manage.py createsuperuser --username=joe --email=j...@example.com
>
>
> Using this leads to an error, which I could match to the closed ticket
> #16017.
>
> But I couldn't find how to proceed from there. It seems some software was
> changed about 4 weeks ago:
>
macpro1:~ bobaalsma$ locale
LANG=
LC_COLLATE="C"
LC_CTYPE="UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=
macpro1:~ bobaalsma$ python -c 'import locale; print
locale.getdefaultlocale()'
Traceback (most recent call last):
File "", line 1, in
File
"/Library/Framework
On Fri, Sep 14, 2012 at 8:52 AM, Bob Aalsma wrote:
> The command & error from createsuperuser:
> macpro1:dripFeedSite bobaalsma$ python manage.py createsuperuser
> …
Can I ask you to try some things, just to see how your environment is
setup. All of these commands run on the bash shell as a regul
0x1F5:0:5',
'Apple_Ubiquity_Message': '/tmp/launch-iTRGIn/Apple_Ubiquity_Message',
'PWD': '/Users/bobaalsma/Programmatuurontwikkeling/DripFeed/dripFeedSite',
'DJANGO_SETTINGS_MODULE': 'dripFeedSite.settings', 'COMMAND_MODE'
olgende:
I'm a newbie following the tutorial. In this, creating a superuser
is described, using
manage.py createsuperuser --username=joe --email=j...@example.com
<mailto:j...@example.com>
Using this leads to an error, which I could match to the closed
ticket #1601
com
>>
>>
>> Using this leads to an error, which I could match to the closed ticket
>> #16017.
>>
>> But I couldn't find how to proceed from there. It seems some software was
>> changed about 4 weeks ago:
>> "Made createsuperuser more robust wh
creating a superuser is
> described, using
>
> manage.py createsuperuser --username=joe --email=j...@example.com
>
>
> Using this leads to an error, which I could match to the closed ticket
> #16017.
>
> But I couldn't find how to proceed from there. It seems som
mber 2012 16:58:11 UTC+2 schreef Bob Aalsma het
volgende:
>
> I'm a newbie following the tutorial. In this, creating a superuser is
> described, using
>
> manage.py createsuperuser --username=joe --email=j...@example.com
>
>
> Using this leads to an error, which
he tutorial. In this, creating a superuser is
> described, using
> manage.py createsuperuser --username=joe --email=j...@example.com
>
> Using this leads to an error, which I could match to the closed ticket #16017.
>
> But I couldn't find how to proceed from there. It s
al. In this, creating a superuser is
>> described, using
>>
>> manage.py createsuperuser --username=joe --email=j...@example.com
>>
>>
>> Using this leads to an error, which I could match to the closed ticket
>> #16017.
>>
>> But I couldn't fi
>
> Using this leads to an error, which I could match to the closed ticket
> #16017.
>
> But I couldn't find how to proceed from there. It seems some software was
> changed about 4 weeks ago:
> "Made createsuperuser more robust when getting current OS username."
I'm a newbie following the tutorial. In this, creating a superuser is
described, using
manage.py createsuperuser --username=joe --email=j...@example.com
Using this leads to an error, which I could match to the closed ticket
#16017.
But I couldn't find how to proceed from there
n - and you have IDLE IN TX error right there.
The above went a little off-topic. So in short: you are responsible
for closing connections manually except in request processing, where
connections are closed automatically.
- Anssi
--
You received this message because you are subscribed to the Googl
Hi,
I am running django-1.2 with postgresql.
I am facing the problem.
Django is not closing the connection and the connection is
retained by db-server until DBA goes and kill the connection manually.
--
You received this message because you are subscribed to the Google Groups
"Django users" grou
Django-orm looks very useful. Any high DB traffic site using it in
production?
How mature is it?
On Jan 15, 12:06 pm, Daniel Gerzo wrote:
> On 15.1.2012 3:36, ydjango wrote:
>
> > Any updates on MySQL connection pool for django. Has anyone
> > implemented it yet and willing to share?
> > Graham
You might also want to consider:
(1) Will anybody actually want to compete with you using your code or
a fork of same?
People often assume ravenous competitors when in real life, nobody is
that interested, for whatever reasons. Or at least they will not
become interested until you are way out in
On 16/01/2012 3:09pm, Alec Taylor wrote:
Initially I was going closed-source all the way, or at least until we
have a good reputation, and open-sourcing will only improve that rep.
Recently though, I've been thinking about open-sourcing the entire solution.
Various popular SaaS solutions
Initially I was going closed-source all the way, or at least until we
have a good reputation, and open-sourcing will only improve that rep.
Recently though, I've been thinking about open-sourcing the entire solution.
Various popular SaaS solutions have open-sourced under AGPL and are
gener
On 15.1.2012 3:36, ydjango wrote:
Any updates on MySQL connection pool for django. Has anyone
implemented it yet and willing to share?
Graham Dumpleton also raised it in G+ today.
On Nov 20 2011, 5:45 am, Jonathan wrote:
Does anyone know if this progressed anywhere since '09?
You can use d
I've heard/read that MySQL proxy supports a connection pool. See
(http://forge.mysql.com/wiki/MySQL_Proxy_FAQ) Basically this was a
good original observation about the overhead of opening/closing DB
connections for every request. I think tools exist out there such as
MySQL proxy that can practic
I haven't used it, but this might help
http://node.to/wordpress/2010/02/11/database-connection-pool-solution-for-django-mysql/Also,
have you tried using SQLAlchemy?
On Sun, Jan 15, 2012 at 8:06 AM, ydjango wrote:
> Any updates on MySQL connection pool for django. Has anyone
> implemented it yet
Any updates on MySQL connection pool for django. Has anyone
implemented it yet and willing to share?
Graham Dumpleton also raised it in G+ today.
On Nov 20 2011, 5:45 am, Jonathan wrote:
> Does anyone know if this progressed anywhere since '09?
--
You received this message because you are subsc
Does anyone know if this progressed anywhere since '09?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/0fmsTMQC_tAJ.
To post to this group, send email to d
I'm trying to run a unittest, but it crashes with an exception, saying
"Cannot operate on a closed dabase". I'm not using the orm to insert
records, but raw SQL - and raw sql is the only option. When or what
closes the connection to the database?
--
Mvh/Best regards
I hear you, Russ.
I'll see if I can't get something more repeatable down in code, but as
I stated, it's an intermittent problem.
Didn't meant to sound like your 3rd option wasn't an option ("issues
with the code" is always an option). I just wanted to make sure this
wasn't a "postgres thing" that I
> __init__.py", line 79, in close
> self.connection.close()
> InterfaceError: connection already closed
>
> I'm seeing this maybe every 20-30th page request.
>
> Looking at the issues on trac, I see a handful of tickets that share
> this error, however I
4, in close_connection
> conn.close()
> File "./lib/python2.6/site-packages/django/db/backends/
> __init__.py", line 79, in close
> self.connection.close()
> InterfaceError: connection already closed
>
> I'm seeing this maybe every 20-30th pag
t;./lib/python2.6/site-packages/django/db/__init__.py",
line 84, in close_connection
conn.close()
File "./lib/python2.6/site-packages/django/db/backends/
__init__.py", line 79, in close
self.connection.close()
InterfaceError: connection already closed
I'm seeing
Ok thanks. I'm trying to limit the number of concurrent users using
sessions.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
djan
AFAIK there is a known bug in FireFox preventing it from working correctly. Try
(nearly) any other browser.
"Stodge" schrieb:
>I have SESSION_EXPIRE_AT_BROWSER_CLOSE set to True in my settings.
>When the user visits my custom login page a new session is created for
>them in the database. The
1 - 100 of 143 matches
Mail list logo
