[MGNLSTK-288] cannot activate - using Magnolia 4.0 Created: 16/Feb/09  Updated: 12/Jun/09  Resolved: 19/Feb/09

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: base system
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Rainer Blumenthal Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File first_exception.txt     JPEG File screenshot-1.jpg     Text File stacktrace.txt    
Issue Links:
relation
is related to MAGNOLIA-2628 Update dependency commons-beanutils t... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

I just recognized that any activation fails on our testing system.
The subscriber is configured correctly. I hope i just forgot to configure sth.

I add the stacktrace as attachment.



 Comments   
Comment by Jan Haderka [ 16/Feb/09 ]

Could you please export your activation command configuration and attach it to the issue? It seems like there is some configuration error (versionMap property of the command) so the command can't be instantiated properly:

ERROR  info.magnolia.cms.servlets.CommandBasedMVCServletHandler CommandBasedMVCServletHandler.java(execute:102) 
16.02.2009 12:30:32  can't execute command
java.lang.IllegalArgumentException: Cannot invoke info.magnolia.module.admininterface.commands.ActivationCommand.setVersionMap 
on bean class 'class info.magnolia.module.admininterface.commands.ActivationCommand' - argument type mismatch - 
had objects of type "java.lang.String" but expected signature "java.util.List"
Comment by Philipp Bracher [ 16/Feb/09 ]

Can't reproduce here. Can you answer the following questions:

  • do you use workflow?
  • have you changed any configuration?
  • which magnolia version do you use? 4.0 rc3?
  • are there any other exceptions in the log (before the one you attached)

Thanks

Comment by Rainer Blumenthal [ 17/Feb/09 ]
  • no we dont use Workflow - at least i dont see an Inbox
  • not that i know (cant be 100 % sure)
  • 4.0.0 RC3 - with some very new SNAPSHOT modules of yours
  • yes - there is another exception before... please look at the attachment 2
Comment by Magnolia International [ 18/Feb/09 ]

More questions:

  • Does this happen when activating, or when configuring the commands ?
  • If on activation, does this happen with "single node" activation and/or "activate including subpages" ?
Comment by Rainer Blumenthal [ 18/Feb/09 ]

This happens at activation - for every repository i ve tried.
It happens for single nodes and incl. subpages...

BTW you can try to take a look at http://testing.insm2009.aperto.de/author i'll send a mail with access data to the ME-list.

Comment by Jan Haderka [ 18/Feb/09 ]

Unfortunately I could not connect using remote debugger. I think it might be easier if you just put the war file somewhere I can download it from.
Anyway some more info I need - could you please list exact versions of magnolia-core.jar, magnolia-module-admininterface.jar, magnolia-module-exchange-simple.jar and commons-beanutils.jar that are packed in your war file?
I've also noticed that you are deploying on Tomcat 6.0.18 while we are deploying on Tomcat 5.5.27 so I'll try Tomcat 6 in the morning as well to see if it makes any difference.

Comment by Rainer Blumenthal [ 19/Feb/09 ]

Remote Debugging is not possible from your site - cause of Proxy-Usage and Firewalls.

What we have deployed at the moment is this: http://www.aperto.de/transfer/uploads/clean_deploycopy-INSM-2009-02-18-18h12min.war
The WAR file is available until tomorrow in the evening - i think.

magnolia-core.jar = magnolia-core-4.0-rc3.jar
magnolia-module-admininterface.jar = magnolia-module-admininterface-4.0-rc3.jar
magnolia-module-exchange-simple.jar = magnolia-module-exchange-simple-4.0-rc3.jar
commons-beanutils.jar = commons-beanutils-1.8.0.jar

Do you believe it is Tomcat 6? We have a Magnolia 3.6.1 running on Tomcat 6 without any problems until now (just a testing system).

Comment by Jan Haderka [ 19/Feb/09 ]

I can confirm that issue is reproducible with your war file and I can also confirm that it goes away when beanutils in your war file is replaced with previous version (1.7).
You can remove the war file from public location now.
Is it possible for you to use beanutils-1.7 for now or do you need explicitly version 1.8?

Comment by Rainer Blumenthal [ 19/Feb/09 ]

We changed a dependency in our Campaign Monitor module - for the commons-digester from 2.0 to 1.8.
That was the problem.

At the end we hung again with the misconfiguration of mine - multipartRequestFilter... but that is not important for that issue because it was just my fault.

Comment by Rainer Blumenthal [ 19/Feb/09 ]

The first activation was successful at aperto INSM Testing.

Generated at Mon Feb 12 07:25:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.