[MAGNOLIA-1370] Activation may be not working when proxied over Apache httpd with mod_jk Created: 09/Feb/07  Updated: 23/Jan/13  Resolved: 11/Apr/07

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.0.1
Fix Version/s: 3.1 M1

Type: Bug Priority: Major
Reporter: Robert Gacki Assignee: Sameer Charles
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Apache2
mod_jk-1.2.19
Java 1.5.0_10


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Activation (author <-> public) was not working going through mod_jk.

Unfortunately, I'm not able to post any further error messages except than this communication failure notification:

ERROR info.magnolia.cms.exchange.simple.SimpleExchangeServlet 17.01.2007 17:24:08 – Either server not configured or user is not valid
info.magnolia.cms.security.AccessDeniedException: Either server not configured or user is not valid
at info.magnolia.cms.exchange.simple.SimpleExchangeServlet.validateRequest(SimpleExchangeServlet.java:417)
...

It may be a service problem (incomplete strange header entries, bad body etc).

Because mod_jk is a wide spread setup, I suggest, you look into this in more detail.

Currently, I do activation through tomcat's 8080 again, because authoring and public instances are sharing the localhost. But I'm thinking of moving the author to my local network with activation over WAN. And with this situation, I'd like to address the httpd only.

This issue may be one to mod_proxy, too.



 Comments   
Comment by Sameer Charles [ 13/Feb/07 ]

We have been using mod_proxy and mod_jk1.2.x with magnolia without any problem.
you are right almost all service providers have apache and mod_jk in between and we never heard of activation problem.

I had a look at the code and your error shows that either

  • credentials are not the same on public server
  • server is not configured yet
  • *** the IP you are using is not allowed by magnolia IPConfig

If you have more info on this lets discuss this on users list.

Comment by Sameer Charles [ 11/Apr/07 ]

Tested with JK1.2.21 and Apache 2.0

  • Please reopen if you can list the steps to reproduce.
Generated at Mon Feb 12 03:26:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.