[MGNLSTK-414] Adding STK jar´s to magnolia webapp lib in glasfish 2.1, crashes magnolia webapp Created: 18/Jul/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: templates
Affects Version/s: 1.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: jose mendes Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows XP SP3, Glassfish 2.1 with JDK full update, magnolia-bundled-webapp-4.0.2.war, magnolia-standard-templating-kit-bundle-1.1-bundle.zip


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Installed magnolia-bundled-webapp-4.0.2.war in Galssfish 2.1. First time login,updated all components from magnolia. Stoped Glassfish server, pasted the STK jars into lib directory of magnolia webapp directory, restarted the Glassfish server, magnolia webapp crashed. Removed some of the jars, restarted the server, over and over until magnolia webapp was up again but no sign of the STK in AdminCentral.



 Comments   
Comment by Jan Haderka [ 20/Jul/09 ]

Could you attach log files from the crash? Also please provide info on how much memory (-Xmx) did you assign to glassfish at startup and what other JVM flags are set at startup. If you download magnolia-tomcat-bundle-4.0.2-bundle-jdk15.zip, you can find magnolia-control.cmd batch file in the bin folder of the tomcat that sets all the necessary values. Try to start your glassfish with the same parameters and see if the error will happen again or not.

Just noticed: You are trying to use Magnolia 4.0 with STK 1.1 ... STK 1.1 needs Magnolia 4.1 to run, so you would not be able to install it even if your glassfish didn't start. You would need to install STK 1.0 if you want/need to use Magnolia 4.0.
Out of interest: Why do you use Magnolia 4.0 and not 4.1?

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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