[MGNLACTIVATION-118] Failed to activate content since java 8u65 Created: 30/Oct/15  Updated: 21/Apr/17  Resolved: 03/Nov/15

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.3.3, 5.4.1
Fix Version/s: 5.3.4, 5.4.2

Type: Bug Priority: Critical
Reporter: Zdenek Skodik Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: 0d
Time Spent: 2h 20m
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLXAA-94 Failed to activate content with the l... Closed
Relates
relates to MAGNOLIA-6462 Failed to activate content since java... Closed
relates to MGNLACTIVATION-137 error Closed
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
Release notes required:
Yes
Date of First Response:
Sprint: Kromeriz 17
Story Points: 5

 Description   

An activation request results in:

ERROR dule.exchangetransactional.TransactionalSyndicator: Failed to activate content.
info.magnolia.cms.exchange.ExchangeException: java.lang.IllegalArgumentException: Illegal character(s) in message header field: mgnl:deleted
	at info.magnolia.module.activation.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:448)
	at info.magnolia.module.exchangetransactional.TransactionalSyndicator$2.run(TransactionalSyndicator.java:205)
	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Illegal character(s) in message header field: mgnl:deleted
	at sun.net.www.protocol.http.HttpURLConnection.checkMessageHeader(HttpURLConnection.java:489)
	at sun.net.www.protocol.http.HttpURLConnection.isExternalMessageHeaderAllowed(HttpURLConnection.java:459)
	at sun.net.www.protocol.http.HttpURLConnection.setRequestProperty(HttpURLConnection.java:3018)
	at info.magnolia.module.activation.BaseSyndicatorImpl.addActivationHeaders(BaseSyndicatorImpl.java:630)
	at info.magnolia.module.activation.BaseSyndicatorImpl.transportActivatedData(BaseSyndicatorImpl.java:478)
	at info.magnolia.module.activation.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:407)
	... 3 more

at

java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)


 Comments   
Comment by Roman Kovařík [ 04/Nov/15 ]

Related forum post: https://forum.magnolia-cms.com/forum/thread.html?threadId=30d71fb8-2078-4302-872d-0acfcd795d7c&page=1

Comment by Pietro Pagani [ 04/Nov/15 ]

Hi,
Im' experiencing the same problem after a migration from Magnolia 5.2.3 (with Tomcat 7 / Java 7) to Magnolia 5.3.11 (with Tomcat 8 / Java 8).
The exact version of Java is 1.8.0_65.
Is the problem still open for Magnolia 5.3.11?

Comment by Roman Kovařík [ 04/Nov/15 ]

Hi Pietro,
The issue will be also fixed for Magnolia 5.3.12.
Roman

Comment by Pietro Pagani [ 04/Nov/15 ]

Hi Roman,
thanks for your reply.
I forgot to mention that we are working with the Enterprise edition.
I think that the last enterprise release for Magnolia 5.3.x is 5.3.11: am I wrong?
Could you tell me when the 5.3.12 will be released?

Comment by Roman Kovařík [ 04/Nov/15 ]

5.3.12 is planned at the end of November and should include activation 5.3.4 with this fix and also the related fix for exchange-transactional 2.2.3 (see MGNLXAA-94).

Comment by Pietro Pagani [ 04/Nov/15 ]

In the meanwhile, do you think that the temporary solution of working with Tomcat 8 and Java 7 is a good one?

Comment by Roman Kovařík [ 04/Nov/15 ]

Apache Tomcat 8.0.x requires Java 7 or later.

see https://tomcat.apache.org/migration-8.html.

Comment by OLD Chris Jennings (Malleus) (Inactive) [ 04/Nov/15 ]

Pietro, The changes to sun.net.www.protocol.http.HttpURLConnection that cause his were introduced in Java 1.8.0_65 and 66. If you downgrade to 1.8.0_45 you will not have the latest Java fixes but you will be able to publish.

This has worked for me in a non-production environment. Fortunately we are not yet in production so have not had to discuss the tradeoff between Java updates and Magnolia functionality.

Comment by Pietro Pagani [ 05/Nov/15 ]

Hi Chris,
thanks a lot for your suggestion.
However, for security reason, in a production environment we prefer to use always the latest Java version: so for the moment we'll go on using the latest 1.7.x version and we'll migrate to java 8 only when Magnolia 5.3.12 will be available.

Best regards,
PIetro

Comment by Mariusz Chruscielewski [ 05/Nov/15 ]

Hi, our website is currently running on Magnolia 5.4.2 and we still have publication problems on 1.8.0_65-b17. While working with 1.8.0_45 problem doesn't exist.

Can you pelase advise?

Comment by Roman Kovařík [ 05/Nov/15 ]

Hi,
The fix version 5.4.2 is the version of the activation module which will be released as part of Magnolia 5.4.3.
Roman

Comment by Mariusz Chruscielewski [ 06/Nov/15 ]

Oh, that makes difference. Thanks Roman, will wait for that fix.

Comment by Thomas Duffey [ 11/Nov/15 ]

Is this possibly also affecting Magnolia w/Java 1.7.0_85-b01? A customer just upgraded to that version this week and now activation isn't working w/the same error message as above.

Comment by Tomáš Gregovský [ 18/Nov/15 ]

I can confirm that on 1.7.0_85 is same issue, downgraded to 1.7.0_75 and works again (workaround).

Comment by Zdenek Skodik [ 15/Dec/15 ]

Experienced also at 1.6.0_105.

Comment by Lea Hänsenberger [ 22/Dec/15 ]

Should this be fixed in Magnolia Enterprise 5.3.5? We experience this problem on such a Magnolia with java 1.8.0_66.

Comment by Roman Kovařík [ 23/Dec/15 ]

Hi Lea,
The issue was fixed in Magnolia 5.3.12 (activation module version 5.3.4).
Regards.
Roman

Comment by Mark Thompson [ 03/Mar/16 ]

We have just updated our Java version and are experiencing this problem with activation module version 5.4.1 and
OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

Comment by Alexander Schörkhuber [ 31/Mar/16 ]

Comfirmed in Magnolia 4.5.19 / java 7u99 (worked on 7u80)

Generated at Sun Feb 11 22:59:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.