I have two grails(2.1.1) project deploy on the one tomcat(7.0.39).
I deployed a project on tomcat server, its worked but when i deployed other project on same tomcat , its generates heap Space error and and stop the tomcat server.
I have some idea to ignore this error by setting JAVA_OPTS. But I didn't have any rights to access Tomcat/bin directory.
Related
I have a Dropwizard application that works fine locally, but I can not figure out how to deploy it into my Jelastic environment.
I read "Hosting Spring Boot Standalone and Clustered Java Applications with Jelastic Cloud" tutorial but seems like it is more focused on Spring Boot applications. To run my DropWizard app I need to execute
java -jar myJar.jar server config.yml
but from the tutorial it seems that Elastic just executes the jar without providing "server" and "config.yml" parameters.
So when I upload and deploy my jar file (I tried both, jar and zip approaches) all I can see in the output is
Node ID : XXXXX
-----------------------
Deploy failed
/opt/repo/jelastic/scripts/deploy.sh line 66 clearCache command not found
zipinfo cannot find or open /, /.zip or /.ZIP.
zipinfo cannot find or open /, /.zip or /.ZIP.
Error Nothing to run
and SpringBoot log is empty.
Can you please tell me is there a way to deploy a DropWizard application, or the only way to deploy it is using docker registry?
To provide parameters to your application you need to edit file variables.conf from your dashboard, then just restart the application
I am using websphere deployer plugin to deploy application to my local WAS server. Jenkins gives a success message after deployment but the deployed application is not present on the server.
Can anyone suggest how to deal with this. I did this deployment for tomcat and that works fine for me but on WAS server it seems like file not getting correct path. I am new to WAS server. Need suggestions.
GGTS having VMWare vFabric TcServer. But I want to deploy my project
on JBoss.
I'm able to add new JBoss.x AS and JBoss.x Enterprise Servers in GGTS but meanwhile if I try to deploy my application on Jboss I have an error alert message "there are no resources that can be added or removed from the server".
Same application I can deploy on default "VMWare vFabric TcServer" Server.
I installed Ubuntu, GlassFish web server, installed JRuby on Rails using GlassFish's admin tools, deployed my application from .war archive. The problem is only - when I attempt to run this web application nothing happens. GlassFish isn't listening on port 8080 as promised. The GlassFish administration web console listens on port 4848 and works fine. What to do to pair GlassFish and JRuby on Rails the correct way, remembering that it isn't a separate JRuby installation?
Update: it seems that this problem lies somewhere around access rights because I can deploy an application through
sudo ./asadmin deploy
but can not do the same through web console. The output is as if the application has been deployed, without any error messages (web interface shows the presence of application, domain folder contains my application's file/folder structure), but something in server's internals isn't bound to application.
I didn't think much and applied quick and dirty solution: set "777" access rights to /home/glassfish and all its contents. It helped.
I generally run Grails 2.0 from my IDE but have been seeking to deploy an app to a remote Virtual Private Server (linux) where I installed Tomcat and Mysql. I create a production WAR file and copy it to the Tomcat webapps dir, where I can see Tomcat restart and after some "fixing" I see the application come up, adding minimal bootstrap entries into the MySql database fine.
However, I cannot connect to the Grails app (remotely). If I specify www.mydomain.com, I am (finally) able to reach the main Tomcat server "welcome page". I also reach Tomcat if I add a "/" at the end, not my grails app.
As such I'm tried putting in full controller paths that I know work on my dev machine, and then accessing them on the remote machine (note grails.serverURL is configured as http://www.mydomain.com). Doing this, I get
HTTP Status 404 -- The requested resource (/BareBones/bare/create) is not available.
This error is from a BareBones application I created, as I was having some problems with VPS available memory. In any case, on my dev machine I can reach the this BareBones app URL
http://localhost:8080/BareBones/bare/create
as expected. When I deploy, I get the same HTTP Status 404 error (resource not available) when I do:
http://www.mydomain.com/bare/create
In Config.groovy, in this BareBones app I've got the minimal change:
environments {
development {
grails.logging.jul.usebridge = true
}
production {
grails.logging.jul.usebridge = false
grails.serverURL = "http://www.mydomain.com"
}
}
In my Tomcat server.xml file I changed over from the default 8080/8443 ports to 80/443, but using either either set results in the same problem.
I'm probably missing an easy step, just don't know what it is.
P.S. When I deploy the sample.war file that comes with Tomcat (isn't Grails, just a hello-world servlet), it works. I'm able to access that at
www.mydomain.com/sample
Since I FTP'd sample.war from my computer to the server, it would appear to indicate my FTPs are good, and the routing to the server is right, narrowing this down to Grails & Tomcat.
Usually in dev mode Grails mounts, as you pointed out, the context of appName, i.e. http://localhost:8080/BareBones/ here.
But the path it mounts on tomcat is not up to Grails itself, it is wholly dependent on the Tomcat configuration and primarily the name of the WAR file.
Even if you have BareBones as your appName and you deploy it as ROOT.war then it will mount the root "/" context. If you deploy it as BareBones.war then it should mount the same dir as in dev mode.
Because sites are usually mounted as ROOT.war "/", I can recommend setting
grails.app.context = "/"
in your Config.groovy file which will make it so that you will use the root context path also in dev, i.e. http://localhost:8080/
This makes it simpler since both dev and production will now have identical relative paths to everywhere and only the hostname:port will change.