https://bz.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #19 from bingal...@gmail.com ---
The work-around is to apply jndiExceptionOnFailedWrite to the context
(https://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Standard_Implementation),
e.g.
--
You are receiving this mail be
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
Mark Thomas changed:
What|Removed |Added
CC||oleg.n.a...@gmail.com
--- Comment #1
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
Mark Thomas changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
ric.alme...@gmail.com changed:
What|Removed |Added
CC||ric.alme...@gmail.com
--
Y
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
ric.alme...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
mmaure...@gmail.com changed:
What|Removed |Added
CC||mmaure...@gmail.com
--
Confi
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #15 from mmaure...@gmail.com 2012-03-27 22:03:48 UTC ---
I'm using Tomcat 7.0.25 and am still seeing this same issue. Any attempt to
close a Context object results in the exception "Context is read only", and I
am unable to insta
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #14 from Leonid Mikhailov 2011-12-01 23:17:40
UTC ---
(In reply to comment #13)
> The correct exception is now thrown and the option to control whether or not
> an
> exception is thrown has been added to the StandardContext.
>
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
Mark Thomas changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #12 from Mark Thomas 2011-10-27 16:11:07 UTC ---
To quote from section EE.5.3.4 of the Java EE spec
The container must ensure that the application component instances have only
read access to their naming context. The container
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #11 from Leonid Mikhailov 2011-10-26 21:24:19
UTC ---
Here you go:
javax.naming.NamingException: Context is read only
at org.apache.naming.NamingContext.checkWritable(NamingContext.java:941)
at org.apache.naming.Naming
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
Konstantin Kolinko changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|F
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
Leonid Mikhailov changed:
What|Removed |Added
Version|7.0.14 |7.0.22
OS/Version|Linux
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #8 from Anjana Fernando 2011-08-31 15:57:33
UTC ---
Mark,
You could have used all those words to give me a simple explanation, I gave the
comments and reported the bug to my ability, I explained the issue as I
understood it, a
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #7 from Mark Thomas 2011-08-31 15:37:20 UTC ---
I'll repeat: "You might also want to investigate when the JNDI context is
writeable."
I really do not appreciate code reviews based on guess work. If you are going
to comment on t
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #6 from Anjana Fernando 2011-08-31 15:32:13
UTC ---
Hi Mark,
OK, sorry, I should have looked at the code before. I just didn't know where
the svn for this was (yeah it was a simple looking around the tomcat project
page), I th
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #5 from Mark Thomas 2011-08-31 14:48:59 UTC ---
Rather than guessing why don't you look at the source code and see what it
actually does? You might also want to investigate when the JNDI context is
writeable.
--
Configure bugm
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #4 from Anjana Fernando 2011-08-31 14:43:14
UTC ---
Hi Mark,
Sorry, maybe I misunderstood, I guessed the modified version would be something
like the following,
public void close() throws NamingException {
if (checkWritea
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #3 from Mark Thomas 2011-08-31 14:35:00 UTC ---
No. The attempt to use the close() method will fail.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because:
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #2 from Anjana Fernando 2011-08-31 14:33:31
UTC ---
Hi Mark,
So for the situation I'm facing, in the close method, if the environment is
cleared, will this be removed from "ContextBindings" also? .. Since that was
the problem
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
Anjana Fernando changed:
What|Removed |Added
CC||laferna...@gmail.com
--
Configu
22 matches
Mail list logo
