RE: [4.1.9] Fix for major bugs

[David Oxley]

catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:256)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:355)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:563)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:535)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:638)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:533)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.rmi.UnmarshalException: error unmarshalling arguments;
nested exception is:
java.lang.ClassNotFoundException: access to class loader denied
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:252)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:7
01)
... 1 more
Caused by: java.lang.ClassNotFoundException: access to class loader denied
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:421)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:159)
at
java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:631)
at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:257)
at
sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:200)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513)
at
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626)
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:297)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:246)
... 6 more
Caused by: java.security.AccessControlException: access denied
(java.io.FilePermission C:\Tomcat\webapps\spweb\WEB-INF\- read)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java
:270)
at
java.security.AccessController.checkPermission(AccessController.java:401)
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:542)
at
sun.rmi.server.LoaderHandler$Loader.checkPermissions(LoaderHandler.java:1128
)
at
sun.rmi.server.LoaderHandler$Loader.access$000(LoaderHandler.java:1082)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:385)
... 17 more

> -Original Message-
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> Sent: 20 August 2002 16:59
> To: Tomcat Developers List
> Subject: Re: [4.1.9] Fix for major bugs
> 
> David Oxley wrote:
> > Hi Remy,
> >
> > I've just attached some comments to the bug log
> > (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082) that were
> posted to
> > the user list a week or so ago. They seem to explain exactly why this is
> > happening. Have a read through and see what you think.
> 
> I think the root cause of the problem is just that the URLs should be
> encoded. As I said, this will be fixed after the first stable 4.1.x
> release to avoid the possibility of introducing

Re: [4.1.9] Fix for major bugs

[Remy Maucherat]

David Oxley wrote:
> Hi Remy,
> 
> I've just attached some comments to the bug log
> (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082) that were posted to
> the user list a week or so ago. They seem to explain exactly why this is
> happening. Have a read through and see what you think.

I think the root cause of the problem is just that the URLs should be 
encoded. As I said, this will be fixed after the first stable 4.1.x 
release to avoid the possibility of introducing new bugs.

In more complex scenarios, I suppose other problems can happen, but the 
stack trace which was attached seemed to hint at a simple issue.

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [4.1.9] Fix for major bugs

[David Oxley]

Hi Remy,

I've just attached some comments to the bug log
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082) that were posted to
the user list a week or so ago. They seem to explain exactly why this is
happening. Have a read through and see what you think.

Cheers.
Dave.

> -Original Message-
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> Sent: 15 August 2002 17:07
> To: Tomcat Developers List
> Subject: Re: [4.1.9] Fix for major bugs
> 
> David Oxley wrote:
> > Has anyone looked at
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082.
> > Can anyone look at fixing this for 4.1.x?
> 
> It may not be that easy to fix, but at least I undestand now why so many
> people reported problems with RMI. The bug has an easy workaround, and I
> don't want to risk braking things, so it may not be fixed for the first
> 4.1.x stable release.
> 
> Remy
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:tomcat-dev-
> [EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: [4.1.9] Fix for major bugs

[Remy Maucherat]

David Oxley wrote:
> Has anyone looked at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082.
> Can anyone look at fixing this for 4.1.x?

It may not be that easy to fix, but at least I undestand now why so many 
people reported problems with RMI. The bug has an easy workaround, and I 
don't want to risk braking things, so it may not be fixed for the first 
4.1.x stable release.

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [4.1.9] Fix for major bugs

[David Oxley]

Has anyone looked at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082.
Can anyone look at fixing this for 4.1.x?

Cheers.
Dave.


> -Original Message-
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> Sent: 09 August 2002 11:10
> To: Tomcat Developers List
> Subject: [4.1.9] Fix for major bugs
> 
> A few major bugs were fixed in CVS (two tricky bugs in Coyote HTTP/1.1,
> one in Jasper, and possibly one in the Catalina CL - bug 11307). I plan
> to release a 4.1.9 milestone when 11307 is confirmed to be fixed.
> 
> We may then consider 4.1.9 as a candidate for a stable release, as there
> are no real showstopper problems left I can think of (and huge
> improvements over 4.0.x).
> 
> One of the issues left is that DBCP is not stable yet. Could this be
> addressed anytime soon ?
> 
> Remy
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:tomcat-dev-
> [EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: [4.1.9] Fix for major bugs

[Amy Roh]

What is the status of http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11191?  Is this
fixed in 4.1.9?

Thanks,
Amy

Glenn Nielsen wrote:

> Remy Maucherat wrote:
> > A few major bugs were fixed in CVS (two tricky bugs in Coyote HTTP/1.1,
> > one in Jasper, and possibly one in the Catalina CL - bug 11307). I plan
> > to release a 4.1.9 milestone when 11307 is confirmed to be fixed.
> >
> > We may then consider 4.1.9 as a candidate for a stable release, as there
> > are no real showstopper problems left I can think of (and huge
> > improvements over 4.0.x).
> >
> > One of the issues left is that DBCP is not stable yet. Could this be
> > addressed anytime soon ?
> >
>
> I am using DBCP in production and it seems stable.  Is the issue that
> there hasn't been a release of DBCP?  If so, we will need to propose
> a release of DBCP on commons-dev.
>
> Also the docs need updating.
>
> I just checked the docs at:
>
> http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
>
> and some things are out of date, plus they don't mention some of the new features in
> DBCP such as recovering abandoned db connections.
>
> Regards,
>
> Glenn
>
> > Remy
> >
> >
> > --
> > To unsubscribe, e-mail:
> > 
> > For additional commands, e-mail:
> > 
>
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [4.1.9] Fix for major bugs

[Remy Maucherat]

Glenn Nielsen wrote:
> Remy Maucherat wrote:
> 
>> A few major bugs were fixed in CVS (two tricky bugs in Coyote 
>> HTTP/1.1, one in Jasper, and possibly one in the Catalina CL - bug 
>> 11307). I plan to release a 4.1.9 milestone when 11307 is confirmed to 
>> be fixed.
>>
>> We may then consider 4.1.9 as a candidate for a stable release, as 
>> there are no real showstopper problems left I can think of (and huge 
>> improvements over 4.0.x).
>>
>> One of the issues left is that DBCP is not stable yet. Could this be 
>> addressed anytime soon ?
>>
> 
> I am using DBCP in production and it seems stable.  Is the issue that
> there hasn't been a release of DBCP?  If so, we will need to propose
> a release of DBCP on commons-dev.

Ok. Yes, the main issue is that there's no release of the component. 
Releasing 1.0 would help (apparently, since DBCP now also depends on 
"lang", a 1.0 release of that component is also needed).

> Also the docs need updating.
> 
> I just checked the docs at:
> 
> http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html 
> 
> 
> and some things are out of date, plus they don't mention some of the new 
> features in
> DBCP such as recovering abandoned db connections.

Cool :)

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [4.1.9] Fix for major bugs

[Glenn Nielsen]

Remy Maucherat wrote:
> A few major bugs were fixed in CVS (two tricky bugs in Coyote HTTP/1.1, 
> one in Jasper, and possibly one in the Catalina CL - bug 11307). I plan 
> to release a 4.1.9 milestone when 11307 is confirmed to be fixed.
> 
> We may then consider 4.1.9 as a candidate for a stable release, as there 
> are no real showstopper problems left I can think of (and huge 
> improvements over 4.0.x).
> 
> One of the issues left is that DBCP is not stable yet. Could this be 
> addressed anytime soon ?
> 

I am using DBCP in production and it seems stable.  Is the issue that
there hasn't been a release of DBCP?  If so, we will need to propose
a release of DBCP on commons-dev.

Also the docs need updating.

I just checked the docs at:

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html

and some things are out of date, plus they don't mention some of the new features in
DBCP such as recovering abandoned db connections.

Regards,

Glenn


> Remy
> 
> 
> -- 
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

[4.1.9] Fix for major bugs

[Remy Maucherat]

A few major bugs were fixed in CVS (two tricky bugs in Coyote HTTP/1.1, 
one in Jasper, and possibly one in the Catalina CL - bug 11307). I plan 
to release a 4.1.9 milestone when 11307 is confirmed to be fixed.

We may then consider 4.1.9 as a candidate for a stable release, as there 
are no real showstopper problems left I can think of (and huge 
improvements over 4.0.x).

One of the issues left is that DBCP is not stable yet. Could this be 
addressed anytime soon ?

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: