[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: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
I just recognized that any activation fails on our testing system. 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:
Thanks |
| Comment by Rainer Blumenthal [ 17/Feb/09 ] |
|
| Comment by Magnolia International [ 18/Feb/09 ] |
|
More questions:
|
| Comment by Rainer Blumenthal [ 18/Feb/09 ] |
|
This happens at activation - for every repository i ve tried. 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. |
| 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 magnolia-core.jar = magnolia-core-4.0-rc3.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). |
| 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. 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. |