I am attempting to deploy a war (a grails 1.3.7 app) to an jboss 6 which had been in a jboss 5 environment. The war is not dependent on jboss services or j2ee (it could have been deployed straight to tomcat). When deploying to jb6, I get the following error message:
14:54:17,281 ERROR [AbstractKernelController] Error installing to Real:
name=vfs:///opt/jboss-6.0.0.Final/server/jbossweb-standalone/deploy/pip.war
state=PreReal mode=Manual requiredState=Real:
org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///opt/jboss-6.0.0.Final/server/jbossweb-standalone/deploy/app.war
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) [:2.2.0.GA]
...
...
...
Caused by: java.lang.RuntimeException: Neither any mapped-name/lookup/jndi-name
specified nor any ResourceProvider could process resource-env-ref named env/cxf
of type org.apache.cxf.Bus
It seems as though JBoss support services are not able to get created, but don't see any underlying problems preventing the service creation. Also some other web apps are deployed to this instance of jboss, so the overall installation is "sound". I've done some investigation, but not sure where to go next. Any ideas as or pointers as to the likely problem?
This looks like a problem with JNDI, you have a reference to a JNDI in your project, more than likely your web.xml, this resource is not defined as a service in your Jboss server deploy directory, for instance a jdbc.xml definition you are relying on.
Related
I have run into a very serious problem where I can longer deploy a war of a Grails 2.2.5 web application on Tomcat. The build (with 'grails war') proceeds without a problem, and I deploy it to Tomcat. I retsart Tomcat, and the web application simply does not run. It comes up with the deploying message, but clearly doesn't get as far as running Bootstrap.groovy, because logging from there doesn't show up in the log. No error messages are given, but the web app is simply not running.
I ran into a similar problem a few days ago on a different server which I solved by upgrading to Tomcat 7, but this one is already running Tomcat 7. I have no idea why this has started happening, unless it is something obscure to do with the recent change in Maven where only TLS 1.2 connections are allowed (a change which occurred a week or so ago).
So what could be happening? Is there some way I can log what is happening as the web app starts up, such that I might be able to see where the problem is occurring?
If it is of any relevance, it works OK when I do 'grails run-war' on my development machine.
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.
Issue on Websphere 6.1 I hope I'm missing something obvious: We have an application which gets deployed to a configured Websphere environment. We're trying to mimic this WebSphere configuration on a different platform (Linux vs Solaris), but maybe we're missing some obvious settings. The application deploys and starts without an error, but after logon on url localhost:port/app/index.jsp
(via j_spring_security_check) Websphere redirects to localhost:port/index.jsp. This gives an JSP processing Error (HTTPError 404), with code JSPG0036E.
The webapplication is wrapped in an ear, because those are the standards here. And that ear works well on our solaris WAS 6.1 environment but not on the linux WAS. Furthermore in development we've the wrapped war running on Tomcat without problem.
I think I missed the context root somewhere but It's not to be found in Websphere's console, I wouldn't be surprised if it is a Websphere (6.1.0.33) Bug, hopefully I'm wrong or are there workarounds?
after updating my grails app's security plugins, i get the following error when deploying to tomcat:
2012-01-17 09:13:04,970 [pool-2-thread-1] ERROR context.ContextLoader - Context initialization failed
org.springframework.beans.factory.access.BootstrapException: Error executing bootstraps; nested exception is org.codehaus.groovy.runtime.InvokerInvocationException: groovy.lang.MissingMethodException: No signature of method: static org.example.SecRole.findByAuthority() is applicable for argument types: (java.lang.String) values: [ROLE_USER]
the app works fine when being tested via run-app.
the SecRole class has been automatically generated by the spring security plugin.
i had previously deployed the app on the same server without a problem when using an older version of the spring security plugin.
have been knocking my head against this for hours. ideas much appreciated.
This is a bug in v1.2.7 of the plugin. I released v1.2.7.1 to fix it; you can also downgrade to v1.2.6.
Are you using your own Spring Security's User and Role class?
Did you tried to create a fresh grails project and install it with vacation request sample app to test it out?
Lastly, may I know which Grails version and OS you use?
Cheers,
Chee Kin
My prod Env: Tomcat 7, Fedora, Grails 1.3.7, activiti-spring-security 0.4.6, spring-security-core 1.2.7 activiti 5.8.2
Dev Env: Mac OS 10.6, Grails 1.3.7, activiti-spring-security 0.4.6, spring-security-core 1.2.7, activiti 5.8.2
I have installed vacation request app on fresh grails project and that works fine when I run using grails run-app (both in dev and prod mode).
As per Peter's comment above, upgrading to Grails 2.0 solved the problem I described above. However, I had subsequently run into a host of upgrade issues with the app.
When I run my grails application locally under Tomcat, I get no errors. When I deploy my WAR on my remote web server, I get this exception when I try to make an AJAX request that uses HTTPBuilder.
How could this be happening?
Are you running your application is an IDE like STS? if so maybe the Jars for HTTPBuilder are in your build/run path but are not in your lib directory for the Grails app OR not listed as a "Production" Dependency.