A timeout occurred while attempting to lock ModelGlueInit error - Any help?
186 views
Skip to first unread message
Francis
Nov 20, 2009, 2:20:36 PM11/20/09
to model-glue
Can someone help me with this issue?, I'm clueless about whats causing
this. This is in our production server.
I have an small application that uses model glue 2 and CF is running
on top of Jboss. It has been running fine for couple of years.
Yesterday we had to reboot the server after os patches and when I
restart the jboss server and access the application, I'm getting the
error "A timeout occured while attempting to lock ModelGlueInit". When
I add some content to display before this
<cflock name="ModelGlueInit" type="exclusive" timeout="30"
throwOnTimeout="true"> statement, it displays and then throws the
above error.
It is not accessed heavily. May be 10 users a day.
Strange thing is I have similar setup in my machine and that works
fine.
Any help is appreciated. I'm pulling my hair out here.
Francis
this. This is in our production server.
I have an small application that uses model glue 2 and CF is running
on top of Jboss. It has been running fine for couple of years.
Yesterday we had to reboot the server after os patches and when I
restart the jboss server and access the application, I'm getting the
error "A timeout occured while attempting to lock ModelGlueInit". When
I add some content to display before this
<cflock name="ModelGlueInit" type="exclusive" timeout="30"
throwOnTimeout="true"> statement, it displays and then throws the
above error.
It is not accessed heavily. May be 10 users a day.
Strange thing is I have similar setup in my machine and that works
fine.
Any help is appreciated. I'm pulling my hair out here.
Francis
sipa...@gmail.com
Nov 22, 2009, 1:37:10 AM11/22/09
to model...@googlegroups.com
Verify the following:
Report execution times is off in the CFAdmin
Memory Tracking is off in the CFAdmin
Server monitoring is off in the CFAdmin
Reload is set to false in ColdSpring.xml
--
Model-Glue Sites:
Home Page: http://www.model-glue.com
Documentation: http://docs.model-glue.com
Bug Tracker: http://bugs.model-glue.com
Blog: http://www.model-glue.com/blog
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to model...@googlegroups.com
To unsubscribe from this group, send email to
model-glue+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en
Sent from my Verizon Wireless BlackBerry
Report execution times is off in the CFAdmin
Memory Tracking is off in the CFAdmin
Server monitoring is off in the CFAdmin
Reload is set to false in ColdSpring.xml
Model-Glue Sites:
Home Page: http://www.model-glue.com
Documentation: http://docs.model-glue.com
Bug Tracker: http://bugs.model-glue.com
Blog: http://www.model-glue.com/blog
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to model...@googlegroups.com
To unsubscribe from this group, send email to
model-glue+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en
Sent from my Verizon Wireless BlackBerry
Rich
Nov 22, 2009, 9:41:28 AM11/22/09
to model...@googlegroups.com
Francis-
Have you tried simply refreshing again? I get that message all the
time when restarting an app in MG 2 on a very slow Windows box that we
have, it almost never comes up on the first request attempt, but once
I see that error all I usually have to do is refresh the screen and
the app appears. You can also try adding "&timeout=600" to your URL
which will extend the timeout period and give the app more time to load.
HTH,
Rich
Rich
Rich Leach
Advanced Certified Adobe ColdFusion Developer
ri...@cfsnap.com
http://www.cfsnap.com
303-913-7338
Instant Messenger:
AOL AIM: cfsnaprich
Instant Video Conference:
APPLE MobileMe: rich...@me.com
Have you tried simply refreshing again? I get that message all the
time when restarting an app in MG 2 on a very slow Windows box that we
have, it almost never comes up on the first request attempt, but once
I see that error all I usually have to do is refresh the screen and
the app appears. You can also try adding "&timeout=600" to your URL
which will extend the timeout period and give the app more time to load.
HTH,
Rich
Rich Leach
Advanced Certified Adobe ColdFusion Developer
ri...@cfsnap.com
http://www.cfsnap.com
303-913-7338
Instant Messenger:
AOL AIM: cfsnaprich
Instant Video Conference:
APPLE MobileMe: rich...@me.com
Francis
Nov 22, 2009, 10:38:44 AM11/22/09
to model-glue
I tried refreshing several times. Restarted the server too multiple
times. Increased the timeout to 400 or even 1200 and it just comes
back with the same error message.
Strange thing its been working all this time and what would cause
something like this to come all of a sudden?.
On Nov 22, 8:41 am, Rich <r...@cfsnap.com> wrote:
> Francis-
>
> Have you tried simply refreshing again? I get that message all the
> time when restarting an app in MG 2 on a very slow Windows box that we
> have, it almost never comes up on the first request attempt, but once
> I see that error all I usually have to do is refresh the screen and
> the app appears. You can also try adding "&timeout=600" to your URL
> which will extend the timeout period and give the app more time to load.
>
> HTH,
>
> Rich
>
> r...@cfsnap.comhttp://www.cfsnap.com
> APPLE MobileMe: richle...@me.com
times. Increased the timeout to 400 or even 1200 and it just comes
back with the same error message.
Strange thing its been working all this time and what would cause
something like this to come all of a sudden?.
On Nov 22, 8:41 am, Rich <r...@cfsnap.com> wrote:
> Francis-
>
> Have you tried simply refreshing again? I get that message all the
> time when restarting an app in MG 2 on a very slow Windows box that we
> have, it almost never comes up on the first request attempt, but once
> I see that error all I usually have to do is refresh the screen and
> the app appears. You can also try adding "&timeout=600" to your URL
> which will extend the timeout period and give the app more time to load.
>
> HTH,
>
> Rich
>
> APPLE MobileMe: richle...@me.com
Francis
Nov 22, 2009, 10:42:21 AM11/22/09
to model-glue
Yes these are set up correctly.
> For more options, visit this group athttp://groups.google.com/group/model-glue?hl=en
Rich
Nov 22, 2009, 10:50:27 AM11/22/09
to model...@googlegroups.com
Francis-
Is there anyway you can ghost the files on your troubled server onto
another and work from there? I'm sure the greater minds on the list
may have some better alternative, but if I were you, stuck with a
production issue and limited support resources, I'd try to copy the
exact file structure in its entirety onto a different machine (non-
production), see if I can create the issue there and see what
happens. Since the error is a ModelGlue error, if you can create the
issue on the second machine, I'd try re-installing the ModelGlue core
files and starting over with a fresh install of ModelGlue on that
second box and seeing if the new files helped the problem. Until
someone else comes online, that's what I'd do, hardly to say that's
the right course you should be taking though....
HTH,
Rich
APPLE MobileMe: rich...@me.com
Is there anyway you can ghost the files on your troubled server onto
another and work from there? I'm sure the greater minds on the list
may have some better alternative, but if I were you, stuck with a
production issue and limited support resources, I'd try to copy the
exact file structure in its entirety onto a different machine (non-
production), see if I can create the issue there and see what
happens. Since the error is a ModelGlue error, if you can create the
issue on the second machine, I'd try re-installing the ModelGlue core
files and starting over with a fresh install of ModelGlue on that
second box and seeing if the new files helped the problem. Until
someone else comes online, that's what I'd do, hardly to say that's
the right course you should be taking though....
HTH,
Rich
> For more options, visit this group at
> http://groups.google.com/group/model-glue?hl=en
Rich
Rich Leach
Advanced Certified Adobe ColdFusion Developer
ri...@cfsnap.com
> http://groups.google.com/group/model-glue?hl=en
Rich
Rich Leach
Advanced Certified Adobe ColdFusion Developer
APPLE MobileMe: rich...@me.com
Francis
Nov 22, 2009, 11:39:16 AM11/22/09
to model-glue
That's my plan too. But I'm also looking into rewriting the app since
its very small and my business logic is already in my controller.
Thanx for the suggestions.
> r...@cfsnap.comhttp://www.cfsnap.com
> APPLE MobileMe: richle...@me.com
its very small and my business logic is already in my controller.
Thanx for the suggestions.
> APPLE MobileMe: richle...@me.com
Ezra Parker
Nov 23, 2009, 12:25:37 PM11/23/09
to model...@googlegroups.com
Hi Francis,
Are you still having difficulties with this?
If so, I thought it might be helpful to point out that the error you
posted is a lock timeout, not a request timeout. This means that your
request timed out while waiting for other requests that are being
single-threaded via the lock. When you mentioned that you had raised
the timeout setting, it wasn't clear to me whether you were referring
to an increase to the request timeout value (e.g., via the CF admin or
the use of a <cfsetting> tag) or to the timeout attribute on the
<cflock> tag.
Forgive me if you are already aware of this, but increasing the lock
timeout value will not help this situation if requests that are
executing inside the lock repeatedly time out, as the app will
continue to re-load until a request manages to completely execute all
the code within the lock.
--
Ezra Parker
Are you still having difficulties with this?
If so, I thought it might be helpful to point out that the error you
posted is a lock timeout, not a request timeout. This means that your
request timed out while waiting for other requests that are being
single-threaded via the lock. When you mentioned that you had raised
the timeout setting, it wasn't clear to me whether you were referring
to an increase to the request timeout value (e.g., via the CF admin or
the use of a <cfsetting> tag) or to the timeout attribute on the
<cflock> tag.
Forgive me if you are already aware of this, but increasing the lock
timeout value will not help this situation if requests that are
executing inside the lock repeatedly time out, as the app will
continue to re-load until a request manages to completely execute all
the code within the lock.
--
Ezra Parker
Francis
Nov 23, 2009, 1:41:17 PM11/23/09
to model-glue
No I finally resolved it an hour ago.
Yes, it was a lock timeout. I actually tried increasing thru CF admin,
even changing the timeout in the cflock for modelglueinit. But of
course the real issue has nothing to do with model glue. How about
that?.
My app's business logic is stored in another application as ejbs. So
in my init method for controller.cfc, I get access references to the
home EJB objects and I was using a dns for the provider URL and
somehow that got messed up. So a connection was never made between
these two boxes which in turn created the timeout. This has never
happened before and that's why I never even thought about checking it.
Spending 3 days including my weekend on this and finally a small
change in the provider url fixed it. do'h.
Nothing is too small to ignore I guess or may be don't make
assumptions. lol.
Thanx everyone for all the suggestions.
Francis
On Nov 23, 11:25 am, Ezra Parker <e...@cfgrok.com> wrote:
> Hi Francis,
>
> Are you still having difficulties with this?
>
> If so, I thought it might be helpful to point out that the error you
> posted is a lock timeout, not a request timeout. This means that your
> request timed out while waiting for other requests that are being
> single-threaded via the lock. When you mentioned that you had raised
> the timeout setting, it wasn't clear to me whether you were referring
> to an increase to the request timeout value (e.g., via the CF admin or
> the use of a <cfsetting> tag) or to the timeout attribute on the
> <cflock> tag.
>
> Forgive me if you are already aware of this, but increasing the lock
> timeout value will not help this situation if requests that are
> executing inside the lock repeatedly time out, as the app will
> continue to re-load until a request manages to completely execute all
> the code within the lock.
>
> --
> Ezra Parker
>
Yes, it was a lock timeout. I actually tried increasing thru CF admin,
even changing the timeout in the cflock for modelglueinit. But of
course the real issue has nothing to do with model glue. How about
that?.
My app's business logic is stored in another application as ejbs. So
in my init method for controller.cfc, I get access references to the
home EJB objects and I was using a dns for the provider URL and
somehow that got messed up. So a connection was never made between
these two boxes which in turn created the timeout. This has never
happened before and that's why I never even thought about checking it.
Spending 3 days including my weekend on this and finally a small
change in the provider url fixed it. do'h.
Nothing is too small to ignore I guess or may be don't make
assumptions. lol.
Thanx everyone for all the suggestions.
Francis
On Nov 23, 11:25 am, Ezra Parker <e...@cfgrok.com> wrote:
> Hi Francis,
>
> Are you still having difficulties with this?
>
> If so, I thought it might be helpful to point out that the error you
> posted is a lock timeout, not a request timeout. This means that your
> request timed out while waiting for other requests that are being
> single-threaded via the lock. When you mentioned that you had raised
> the timeout setting, it wasn't clear to me whether you were referring
> to an increase to the request timeout value (e.g., via the CF admin or
> the use of a <cfsetting> tag) or to the timeout attribute on the
> <cflock> tag.
>
> Forgive me if you are already aware of this, but increasing the lock
> timeout value will not help this situation if requests that are
> executing inside the lock repeatedly time out, as the app will
> continue to re-load until a request manages to completely execute all
> the code within the lock.
>
> --
> Ezra Parker
>
Reply all
Reply to author
Forward
0 new messages