This could prove very useful in multiple cases although I think this could be a bit hard to achieve. The PermGen space value is defined as a VM argument in the service startup so we need to access the service configuration from the web app. Also, if the Tomcat server is not running as a service, this needs to be done from another way (modifying the startup script?).
We will keep this suggestion in mind and try it sometime in the future. It would indeed be very nice if you could modify the memory parameters directly from MeerCat. Good suggestion!
This is an idea we already thought about and, while it is not implemented, this could come in the near future for MeerCat.
Do you have any suggestions on how this would work best for you (a supervisor email per Tomcat, an email address for the whole Tomcat farm, multiple email addresses for certain kind of problems, etc.) ?
We are currently running a promo for MeerCat here on the ranch. If you want to try your luck with winning a copy of MeerCat, come ask me some questions about the product on the Tomcat forum!
1.) This feature is not currently in MeerCat but it would clearly be very useful. We already thought about having MeerCat stop and start Tomcat instances but this would only be available in a later version of the software.
2.) For now, this is not possible. One way we could implement this fairly quickly would be to have MeerCat execute a certain script (configurable) when checking for Tomcat status or deploying an application for example.
3. ) MeerCat does not restart your Tomcat server when deploying (it deletes the old WAR file, waits for the Tomcat instance to clean up the files and then copies the new WAR file) although this could be done via a script (mentioned at answer #2).
4. ) If there is interest for MeerCat with Jenkins, we could implement this good idea but for now this is not supported.
We certainly plan on keeping up with any of the new versions of Tomcat. For now, MeerCat is fully compatible with Tomcat 6 & 7 but we haven't put much time on testing it on earlier versions of Tomcat.
If there is an interest for MeerCat running on older versions of Tomcat, we could make a compatible version for sure!
Since your Tomcat server is running as a Service, check the username used by the Tomcat service (in services.msc).
If you are using a specific user instead of Windows authentication, make sure that the password you typed in there is the new password (the good one for the Tomcat service user).
The message : ORA-28001: the password has expired says that the password of the user used by the Tomcat has expired and you need to change it.
This is why it happenned suddenly, password expire after a certain number of days. You need to check with your network administrator to unlock the user and change its password.
After changing the password, you will need to change it also in the server.xml of the Tomcat/conf directory.
As Ulf mentionned, it is clearly a username/password problem.
It looks like you are using a connection pool (DBCP), did you check that the credentials in the server.xml (located in the Tomcat/conf directory) are correct ?
Saif Asif wrote:Well I would definitly want to try out the trial version to see what is it all about and how it works . I will download it and play along with it and get back to you .
Tell me if you want to try the Linux version, it is almost ready for release so I could send you a working Linux trial version!
