You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by Guy Katz <gk...@allot.com> on 2007/08/23 09:39:53 UTC

roller 3.1 posts links system problem

Hi all;

I have a strange problem when trying to deploy on centOS/tomcat 6 roller
3.1 with mysql5 connector-j5 (UTF8 DB and tomcat connector set to UTF8)

 

On my dev PC I have the same roller 3.1 with the same exact DB and
everything works fine.

On the centos the specific post links do not work if they include
special characters (see example below). 

 

Also, there is an exception throws (The stack trace below does not say
much so I can't understand the problem).

 

Again, it's the same DB populates with the same data and the same roller
3.1. 

 

Any help would be great as I don't understand what's wrong and I am out
of my  element here. (note that I am not sure that it has anything to do
with the OS).

 

In roller 3.1 this Works (English only):

http://local:8080/xblogs/kiril/entry/dk_session

in roller 3.1 this does not work (include special characters - return
error 404)):

http://localhost:8080/xblogs/xwave/entry/nofx_%D7%91%D7%93%D7%A8%D7%9A

 

NOTE that I used to have a 2.3 version where everything worked (both
below worked) with the old links system.

http://localhost:8080/xblogs/page/kiril?entry=dk_session

http://localhost:8080/xblogs/page/xwave?entry=nofx_%D7%91%D7%93%D7%A8%D7
%9A

 

 

 

THE EXCEPTION WHEN TRYING TO OPEN THE POST WITH MIXED LANGUAGES:

 

INFO   | jvm 1    | 2007/08/23 03:05:23 | SEVERE: Servlet.service() for
servlet jsp threw exception

INFO   | jvm 1    | 2007/08/23 03:05:23 |
java.lang.IllegalStateException: getOutputStream() has already been
called for this response

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.connector.Response.getWriter(Response.java:604)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.ja
va:198)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:1
18)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.JspWriterImpl.flush(JspWriterImpl.java:173)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTa
g.java:887)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:460)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jsp.WEB_002dINF.jsps._404_jsp._jspx_meth_tiles_005finsert_005
f0(_404_jsp.java:282)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jsp.WEB_002dINF.jsps._404_jsp._jspService(_404_jsp.java:166)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:384)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:290)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
her.java:687)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicatio
nDispatcher.java:471)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp
atcher.java:403)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispat
cher.java:301)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java
:424)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java
:343)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:144)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:104)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:517
)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2
16)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:
697)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.
java:889)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:686)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
java.lang.Thread.run(Thread.java:619)

INFO   | jvm 1    | 2007/08/23 03:05:23 | Aug 23, 2007 7:05:23 AM
org.apache.catalina.core.StandardHostValve custom

INFO   | jvm 1    | 2007/08/23 03:05:23 | SEVERE: Exception Processing
ErrorPage[errorCode=404, location=/WEB-INF/jsps/404.jsp]

INFO   | jvm 1    | 2007/08/23 03:05:23 |
org.apache.jasper.JasperException: java.lang.IllegalStateException:
getOutputStream() has already been called for this response

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServle
tWrapper.java:532)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:420)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:290)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
her.java:687)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicatio
nDispatcher.java:471)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp
atcher.java:403)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispat
cher.java:301)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java
:424)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java
:343)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:144)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:104)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:517
)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2
16)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:
697)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.
java:889)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:686)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
java.lang.Thread.run(Thread.java:619)

INFO   | jvm 1    | 2007/08/23 03:05:23 | Caused by:
java.lang.IllegalStateException: getOutputStream() has already been
called for this response

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.connector.Response.getWriter(Response.java:604)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.ja
va:198)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:1
18)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.JspWriterImpl.flush(JspWriterImpl.java:173)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTa
g.java:887)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:460)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jsp.WEB_002dINF.jsps._404_jsp._jspx_meth_tiles_005finsert_005
f0(_404_jsp.java:282)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jsp.WEB_002dINF.jsps._404_jsp._jspService(_404_jsp.java:166)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:384)

INFO   | jvm 1    | 2007/08/23 03:05:23 |   ... 23 more

 

 

 

 

 


Re: [OT] apache front for roller (was: roller 3.1 posts links system problem)

Posted by Wladimir Boton <wb...@gmail.com>.
I have the same problem and solved it using the command:

Jkoptions +ForwardURIEscaped

on the mod_jk.conf.

On 8/26/07, Guy Katz <gk...@allot.com> wrote:
>
> Hi;
>
> Well it turned out that the problem was that the apache front end was
> configured in a way that impacted the URI such that when it got to
> roller is was different (thanks to roller debug for the conclusion).
>
>
>
> As I need all the help I can get. I would like to hear if someone had
> the same difficulties deploying roller 3.1 new post URLs system and
> maybe can share his solutions and ideas with me.
>
>
>
> I have posted a question to tomcat mailing list that describes my
> problem. Here it is (any feedback would be great):
>
>
>
> Hi; (using: centos, apache 2.0.52, mod_jk 1.2.21, tomcat 6)
>
>
>
> Recently, I encountered a problem with URIs that has 'non western
> European' characters (for example:
> http://www.somehost.com/roller/admin/entry/nofx_%D7%91%D7%93%D7%A8%D7%9A
> ). I noticed that apache was forwarding to tomcat a different URI than
> the original which caused problems in my site.
>
>
>
> Digging into the subject I found the JkOptions +ForwardURICompatUnparsed
> fixed my problem. However, I then encountered a different problem then.
> On the first hit, some images were not displayed in the browser (not
> served to it). So I checked the forums and found out about the
> JkStripSession. I figured it might help so I turned it on but nothing
> happened.
>
>
>
> My questions are:
>
> Should the JkStripSession help in this case? Was there a known bug in my
> apache/mod_jk versions related to this (couldn't find in bugzilla)?
>
> How should I solve this? The only thing I need is to be able to forward
> URIs with 'special characters' as is to tomcat for a specific
> application (context)
>
>
>
> I am really out of my element here so I would appreciate your help
> greatly.
>
>
>
> Thanks in advance
>
>
>
> Related forum topic I found:
>
> http://www.nabble.com/Image-problem-tf3629476.html#a10141944
>
> http://www.nabble.com/-mod_jk--JkStripSession-directive-tf3294527.html#a
> 9164432
>
>
>
> The configuration I thought would work but had the image loading
> problem:
>
> JkMount /* ajp13
>
> JkStripSession On
>
>
>
> JkOptions +ForwardURICompatUnparsed
>
>
>
>
>
>
>
> -----Original Message-----
> From: Guy Katz [mailto:gkatz@allot.com]
> Sent: Thursday, August 23, 2007 5:08 PM
> To: user@roller.apache.org
> Subject: RE: roller 3.1 posts links system problem
>
>
>
> My next step is to put a clean roller 3.1 install (not an upgraded one)
>
> and see if I get the same problem
>
> I will send an update then.
>
> Thanks for the help.
>
>
>
>
>
> -----Original Message-----
>
> From: Dave [mailto:snoopdave@gmail.com]
>
> Sent: Thursday, August 23, 2007 4:34 PM
>
> To: user@roller.apache.org
>
> Subject: Re: roller 3.1 posts links system problem
>
>
>
> On 8/23/07, Guy Katz <gk...@allot.com> wrote:
>
> > I have a strange problem when trying to deploy on centOS/tomcat 6
>
> roller
>
> > 3.1 with mysql5 connector-j5 (UTF8 DB and tomcat connector set to
>
> UTF8)
>
> >
>
> > On my dev PC I have the same roller 3.1 with the same exact DB and
>
> > everything works fine.
>
> >
>
> > On the centos the specific post links do not work if they include
>
> > special characters (see example below).
>
>
>
> This is pretty mysterious. If your database and Tomcat configurations
>
> are the same, then I cannot understand why the OS would make any
>
> difference.
>
>
>
>
>
> > Also, there is an exception throws (The stack trace below does not say
>
> > much so I can't understand the problem).
>
>
>
> That horrible exception just means that Roller has returned a 404 (and
>
> yes, I know, 404s should not cause such exceptions -- I'm working on
>
> fixing that now).
>
>
>
> - Dave
>
>


-- 
Wladimir Boton
http://www.wboton.com

[OT] apache front for roller (was: roller 3.1 posts links system problem)

Posted by Guy Katz <gk...@allot.com>.
Hi;

Well it turned out that the problem was that the apache front end was
configured in a way that impacted the URI such that when it got to
roller is was different (thanks to roller debug for the conclusion).

 

As I need all the help I can get. I would like to hear if someone had
the same difficulties deploying roller 3.1 new post URLs system and
maybe can share his solutions and ideas with me.

 

I have posted a question to tomcat mailing list that describes my
problem. Here it is (any feedback would be great):

 

Hi; (using: centos, apache 2.0.52, mod_jk 1.2.21, tomcat 6)

 

Recently, I encountered a problem with URIs that has 'non western
European' characters (for example:
http://www.somehost.com/roller/admin/entry/nofx_%D7%91%D7%93%D7%A8%D7%9A
). I noticed that apache was forwarding to tomcat a different URI than
the original which caused problems in my site.

 

Digging into the subject I found the JkOptions +ForwardURICompatUnparsed
fixed my problem. However, I then encountered a different problem then.
On the first hit, some images were not displayed in the browser (not
served to it). So I checked the forums and found out about the
JkStripSession. I figured it might help so I turned it on but nothing
happened.

 

My questions are:

Should the JkStripSession help in this case? Was there a known bug in my
apache/mod_jk versions related to this (couldn't find in bugzilla)? 

How should I solve this? The only thing I need is to be able to forward
URIs with 'special characters' as is to tomcat for a specific
application (context) 

 

I am really out of my element here so I would appreciate your help
greatly.

 

Thanks in advance

 

Related forum topic I found:

http://www.nabble.com/Image-problem-tf3629476.html#a10141944

http://www.nabble.com/-mod_jk--JkStripSession-directive-tf3294527.html#a
9164432

 

The configuration I thought would work but had the image loading
problem:

JkMount /* ajp13

JkStripSession On

 

JkOptions +ForwardURICompatUnparsed

 

 

 

-----Original Message-----
From: Guy Katz [mailto:gkatz@allot.com] 
Sent: Thursday, August 23, 2007 5:08 PM
To: user@roller.apache.org
Subject: RE: roller 3.1 posts links system problem

 

My next step is to put a clean roller 3.1 install (not an upgraded one)

and see if I get the same problem

I will send an update then.

Thanks for the help.

 

 

-----Original Message-----

From: Dave [mailto:snoopdave@gmail.com] 

Sent: Thursday, August 23, 2007 4:34 PM

To: user@roller.apache.org

Subject: Re: roller 3.1 posts links system problem

 

On 8/23/07, Guy Katz <gk...@allot.com> wrote:

> I have a strange problem when trying to deploy on centOS/tomcat 6

roller

> 3.1 with mysql5 connector-j5 (UTF8 DB and tomcat connector set to

UTF8)

> 

> On my dev PC I have the same roller 3.1 with the same exact DB and

> everything works fine.

> 

> On the centos the specific post links do not work if they include

> special characters (see example below).

 

This is pretty mysterious. If your database and Tomcat configurations

are the same, then I cannot understand why the OS would make any

difference.

 

 

> Also, there is an exception throws (The stack trace below does not say

> much so I can't understand the problem).

 

That horrible exception just means that Roller has returned a 404 (and

yes, I know, 404s should not cause such exceptions -- I'm working on

fixing that now).

 

- Dave


RE: roller 3.1 posts links system problem

Posted by Guy Katz <gk...@allot.com>.
My next step is to put a clean roller 3.1 install (not an upgraded one)
and see if I get the same problem
I will send an update then.
Thanks for the help.


-----Original Message-----
From: Dave [mailto:snoopdave@gmail.com] 
Sent: Thursday, August 23, 2007 4:34 PM
To: user@roller.apache.org
Subject: Re: roller 3.1 posts links system problem

On 8/23/07, Guy Katz <gk...@allot.com> wrote:
> I have a strange problem when trying to deploy on centOS/tomcat 6
roller
> 3.1 with mysql5 connector-j5 (UTF8 DB and tomcat connector set to
UTF8)
>
> On my dev PC I have the same roller 3.1 with the same exact DB and
> everything works fine.
>
> On the centos the specific post links do not work if they include
> special characters (see example below).

This is pretty mysterious. If your database and Tomcat configurations
are the same, then I cannot understand why the OS would make any
difference.


> Also, there is an exception throws (The stack trace below does not say
> much so I can't understand the problem).

That horrible exception just means that Roller has returned a 404 (and
yes, I know, 404s should not cause such exceptions -- I'm working on
fixing that now).

- Dave

Re: roller 3.1 posts links system problem

Posted by Dave <sn...@gmail.com>.
On 8/23/07, Guy Katz <gk...@allot.com> wrote:
> I have a strange problem when trying to deploy on centOS/tomcat 6 roller
> 3.1 with mysql5 connector-j5 (UTF8 DB and tomcat connector set to UTF8)
>
> On my dev PC I have the same roller 3.1 with the same exact DB and
> everything works fine.
>
> On the centos the specific post links do not work if they include
> special characters (see example below).

This is pretty mysterious. If your database and Tomcat configurations
are the same, then I cannot understand why the OS would make any
difference.


> Also, there is an exception throws (The stack trace below does not say
> much so I can't understand the problem).

That horrible exception just means that Roller has returned a 404 (and
yes, I know, 404s should not cause such exceptions -- I'm working on
fixing that now).

- Dave