Quantcast

Does Grails 3 run on any major servers?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc... 

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3? 

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/27e04b03-8d7e-45bd-9368-446b2cf0a34a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

ndn.nguyen
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
        java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc... 

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3? 

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Brad Booth
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers.  It can also produce a self executing jar.  Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed.  We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar.  The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
        java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc... 

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3? 

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAB1NdymLuBb-YXeGxyKtT3RqWWBw88iR%2BwEvM4RNjL4HqhYN7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not. 


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers.  It can also produce a self executing jar.  Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed.  We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar.  The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="csrTSjAOJAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ndn.n...@...> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
        java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc... 

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3? 

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="csrTSjAOJAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="csrTSjAOJAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Graeme Rocher-2
See http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers


On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/1462465568468-9ba0ec70-0fe0fd28-f60b6e79%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time. 

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around  JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us. 

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See <a href="http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;">http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="yktktgE6JAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="yktktgE6JAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="yktktgE6JAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Graeme Rocher-2
When I say WildFly == JBoss the techniques used to configure Grails for deployment for both JBoss and Wildfly are the same.

99% of issues found with Grails on alternative containers is to do with classpath conflicts with JARs that the container ships with it.

So for example JBoss ships with its own version of Hibernate and JTA and so on. Once you have isolated Grails from all of the stuff that JBoss includes (which typically involves tweaking the jboss-web.xml) then it will run fine.

Regards,


On Thu, May 5, 2016 at 7:11 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time.

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us.

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/1462523867794-301874c5-67cec267-56520a03%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
OK, we have success with a basic demo app on JBoss EAP 6.4.0.GA, with Hibernate 4 talking to an Oracle 12c database, but using the Oracle10gDialect. Still no joy on Hibernate 5.

We're now going to try converting our project to Hibernate 4 to see if we can then get a full project deployed on a JBoss EAP domain. Will update again after that process.

On Friday, May 6, 2016 at 1:37:51 AM UTC-7, Graeme Rocher wrote:
When I say WildFly == JBoss the techniques used to configure Grails for deployment for both JBoss and Wildfly are the same.

99% of issues found with Grails on alternative containers is to do with classpath conflicts with JARs that the container ships with it.

So for example JBoss ships with its own version of Hibernate and JTA and so on. Once you have isolated Grails from all of the stuff that JBoss includes (which typically involves tweaking the jboss-web.xml) then it will run fine.

Regards,

Graeme

On Thu, May 5, 2016 at 7:11 PM, DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="ojxP1wdvJAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com> wrote:
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time.

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us.

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See <a href="http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;">http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="ojxP1wdvJAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="ojxP1wdvJAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/b6b6c083-9225-4803-a713-e4201df43a1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
OK, after having two senior people dedicated to this for over a week, we're giving up on getting Grails 3 to run on JBoss EAP 6.4.0.GA, and going back to Grails 2.5.1. We solved many issues, and we're very close to having it running but we're still seeing a lot of URL mapping issues with JSON and with GSON views. I'm sure we could get it to run one day, but at what cost. The schedule cost that we've already taken has been too great.

Graeme, I greatly appreciate your help on the issues we've had and I wish I could justify sticking with Grails 3.

I hope that the Grails team will consider additional testing on a wider selection of app servers in the future. Although I love Grails, and really want to use 3 not 2, I just cannot justify it to my stakeholders at this time for our situation. Again our situation is app server specific so just because we had this much trouble does not mean that other groups will if they are not constrained on server selection. 

Thanks again. 

On Friday, May 6, 2016 at 1:34:01 PM UTC-7, DAC wrote:
OK, we have success with a basic demo app on JBoss EAP <a href="http://6.4.0.GA" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;">6.4.0.GA, with Hibernate 4 talking to an Oracle 12c database, but using the Oracle10gDialect. Still no joy on Hibernate 5.

We're now going to try converting our project to Hibernate 4 to see if we can then get a full project deployed on a JBoss EAP domain. Will update again after that process.

On Friday, May 6, 2016 at 1:37:51 AM UTC-7, Graeme Rocher wrote:
When I say WildFly == JBoss the techniques used to configure Grails for deployment for both JBoss and Wildfly are the same.

99% of issues found with Grails on alternative containers is to do with classpath conflicts with JARs that the container ships with it.

So for example JBoss ships with its own version of Hibernate and JTA and so on. Once you have isolated Grails from all of the stuff that JBoss includes (which typically involves tweaking the jboss-web.xml) then it will run fine.

Regards,

Graeme

On Thu, May 5, 2016 at 7:11 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time.

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us.

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See <a href="http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;">http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Graeme Rocher-2
You could always engage OCi, we’d be happy to help you get up and running.

Apart of that I have not seen any issue reports from yourself. If you provide us with a simple example in a github repo in an issue report that reproduces the issue you are seeing on JBoss we would be happy to take a look.

Regards,


On Tue, May 10, 2016 at 9:54 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
OK, after having two senior people dedicated to this for over a week, we're giving up on getting Grails 3 to run on JBoss EAP 6.4.0.GA, and going back to Grails 2.5.1. We solved many issues, and we're very close to having it running but we're still seeing a lot of URL mapping issues with JSON and with GSON views. I'm sure we could get it to run one day, but at what cost. The schedule cost that we've already taken has been too great.

Graeme, I greatly appreciate your help on the issues we've had and I wish I could justify sticking with Grails 3.

I hope that the Grails team will consider additional testing on a wider selection of app servers in the future. Although I love Grails, and really want to use 3 not 2, I just cannot justify it to my stakeholders at this time for our situation. Again our situation is app server specific so just because we had this much trouble does not mean that other groups will if they are not constrained on server selection.

Thanks again.

On Friday, May 6, 2016 at 1:34:01 PM UTC-7, DAC wrote:
OK, we have success with a basic demo app on JBoss EAP 6.4.0.GA, with Hibernate 4 talking to an Oracle 12c database, but using the Oracle10gDialect. Still no joy on Hibernate 5.

We're now going to try converting our project to Hibernate 4 to see if we can then get a full project deployed on a JBoss EAP domain. Will update again after that process.

On Friday, May 6, 2016 at 1:37:51 AM UTC-7, Graeme Rocher wrote:
When I say WildFly == JBoss the techniques used to configure Grails for deployment for both JBoss and Wildfly are the same.

99% of issues found with Grails on alternative containers is to do with classpath conflicts with JARs that the container ships with it.

So for example JBoss ships with its own version of Hibernate and JTA and so on. Once you have isolated Grails from all of the stuff that JBoss includes (which typically involves tweaking the jboss-web.xml) then it will run fine.

Regards,

Graeme

On Thu, May 5, 2016 at 7:11 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time.

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us.

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/1462984697707-dbaad9fa-e0363216-3c5ab9ad%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
Thanks Graeme, but we have been posting, and you, Burt, and others have been helping us. The pattern is we track our problems to an existing open issue and then wait for a milestone release to fix it, try again, and repeat. We've been in that pattern for months. Even if we had OCi consultants here, I don't think that would change, the issues would still have to be resolved.

In Grails 3.1.1 Burt helped us with this Hibernate 5 question. After that, we identified existing open issues that had us waiting for 3.1.5, and then 3.1.6, I forget the exact issues, all opened by others, sometimes after our StackOverflow questions.

In version 3.1.6, my coworker (ndn2016) gave you feedback on issue 9783, which prompted you to open issue 9915 and assign it to Grails milestone 3.1.7. So the pattern continues, and we've got customers getting worried because we have no path to production and no ability to predict when the pattern will end.

Thanks Graeme, and to Burt also, you guys have been very helpful and I'm sure you're doing everything you can. I really wish I could stick with Grails 3, and I look forward to upgrading our projects to version 3 one day in the future. I'm just sorry that it can't be now.




On Wednesday, May 11, 2016 at 9:38:21 AM UTC-7, Graeme Rocher wrote:
You could always engage OCi, we’d be happy to help you get up and running.

Apart of that I have not seen any issue reports from yourself. If you provide us with a simple example in a github repo in an issue report that reproduces the issue you are seeing on JBoss we would be happy to take a look.

Regards,

Graeme

On Tue, May 10, 2016 at 9:54 PM, DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="cIT9BycSJgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com> wrote:
OK, after having two senior people dedicated to this for over a week, we're giving up on getting Grails 3 to run on JBoss EAP <a href="http://6.4.0.GA" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;">6.4.0.GA, and going back to Grails 2.5.1. We solved many issues, and we're very close to having it running but we're still seeing a lot of URL mapping issues with JSON and with GSON views. I'm sure we could get it to run one day, but at what cost. The schedule cost that we've already taken has been too great.

Graeme, I greatly appreciate your help on the issues we've had and I wish I could justify sticking with Grails 3.

I hope that the Grails team will consider additional testing on a wider selection of app servers in the future. Although I love Grails, and really want to use 3 not 2, I just cannot justify it to my stakeholders at this time for our situation. Again our situation is app server specific so just because we had this much trouble does not mean that other groups will if they are not constrained on server selection.

Thanks again.

On Friday, May 6, 2016 at 1:34:01 PM UTC-7, DAC wrote:
OK, we have success with a basic demo app on JBoss EAP <a href="http://6.4.0.GA" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;">6.4.0.GA, with Hibernate 4 talking to an Oracle 12c database, but using the Oracle10gDialect. Still no joy on Hibernate 5.

We're now going to try converting our project to Hibernate 4 to see if we can then get a full project deployed on a JBoss EAP domain. Will update again after that process.

On Friday, May 6, 2016 at 1:37:51 AM UTC-7, Graeme Rocher wrote:
When I say WildFly == JBoss the techniques used to configure Grails for deployment for both JBoss and Wildfly are the same.

99% of issues found with Grails on alternative containers is to do with classpath conflicts with JARs that the container ships with it.

So for example JBoss ships with its own version of Hibernate and JTA and so on. Once you have isolated Grails from all of the stuff that JBoss includes (which typically involves tweaking the jboss-web.xml) then it will run fine.

Regards,

Graeme

On Thu, May 5, 2016 at 7:11 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time.

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us.

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See <a href="http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;">http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="cIT9BycSJgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="cIT9BycSJgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/5670e84c-2fae-48da-9589-ef632c45b18b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

frederic.henri
hey ‘DAC’,

I am not affiliate with OCI in any case.

There’s a big difference between getting support through mailing list, Stack Overflow, github issues and a commercial engagement from a company that support the framework (and in this case you get THE company with the guys that made the product) - up to you to review your issue and define the engagement if they can commit.

No one will commit on anything through the open-source channel, thats the basic idea - some people dont like it at all and go for commercial product.

It seems in your company you believe in non-open source product, or take the commercial product for support when there’s one (your example with wildly) so just act the same for the  framework you use and get a commercial support for it.

Thanks,
Fred

Le jeudi 12 mai 2016 à 19:54, 'DAC' via Grails Dev Discuss a écrit :

Thanks Graeme, but we have been posting, and you, Burt, and others have been helping us. The pattern is we track our problems to an existing open issue and then wait for a milestone release to fix it, try again, and repeat. We've been in that pattern for months. Even if we had OCi consultants here, I don't think that would change, the issues would still have to be resolved.

In Grails 3.1.1 Burt helped us with this Hibernate 5 question. After that, we identified existing open issues that had us waiting for 3.1.5, and then 3.1.6, I forget the exact issues, all opened by others, sometimes after our StackOverflow questions.

In version 3.1.6, my coworker (ndn2016) gave you feedback on issue 9783, which prompted you to open issue 9915 and assign it to Grails milestone 3.1.7. So the pattern continues, and we've got customers getting worried because we have no path to production and no ability to predict when the pattern will end.

Thanks Graeme, and to Burt also, you guys have been very helpful and I'm sure you're doing everything you can. I really wish I could stick with Grails 3, and I look forward to upgrading our projects to version 3 one day in the future. I'm just sorry that it can't be now.




On Wednesday, May 11, 2016 at 9:38:21 AM UTC-7, Graeme Rocher wrote:
You could always engage OCi, we’d be happy to help you get up and running.

Apart of that I have not seen any issue reports from yourself. If you provide us with a simple example in a github repo in an issue report that reproduces the issue you are seeing on JBoss we would be happy to take a look.

Regards,

Graeme

On Tue, May 10, 2016 at 9:54 PM, DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="cIT9BycSJgAJ" rel="nofollow">grails-de...@googlegroups.com> wrote:
OK, after having two senior people dedicated to this for over a week, we're giving up on getting Grails 3 to run on JBoss EAP 6.4.0.GA, and going back to Grails 2.5.1. We solved many issues, and we're very close to having it running but we're still seeing a lot of URL mapping issues with JSON and with GSON views. I'm sure we could get it to run one day, but at what cost. The schedule cost that we've already taken has been too great.

Graeme, I greatly appreciate your help on the issues we've had and I wish I could justify sticking with Grails 3.

I hope that the Grails team will consider additional testing on a wider selection of app servers in the future. Although I love Grails, and really want to use 3 not 2, I just cannot justify it to my stakeholders at this time for our situation. Again our situation is app server specific so just because we had this much trouble does not mean that other groups will if they are not constrained on server selection.

Thanks again.

On Friday, May 6, 2016 at 1:34:01 PM UTC-7, DAC wrote:
OK, we have success with a basic demo app on JBoss EAP 6.4.0.GA, with Hibernate 4 talking to an Oracle 12c database, but using the Oracle10gDialect. Still no joy on Hibernate 5.

We're now going to try converting our project to Hibernate 4 to see if we can then get a full project deployed on a JBoss EAP domain. Will update again after that process.

On Friday, May 6, 2016 at 1:37:51 AM UTC-7, Graeme Rocher wrote:
When I say WildFly == JBoss the techniques used to configure Grails for deployment for both JBoss and Wildfly are the same.

99% of issues found with Grails on alternative containers is to do with classpath conflicts with JARs that the container ships with it.

So for example JBoss ships with its own version of Hibernate and JTA and so on. Once you have isolated Grails from all of the stuff that JBoss includes (which typically involves tweaking the jboss-web.xml) then it will run fine.

Regards,

Graeme

On Thu, May 5, 2016 at 7:11 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time.

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us.

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="cIT9BycSJgAJ" rel="nofollow">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="cIT9BycSJgAJ" rel="nofollow">grails-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/5670e84c-2fae-48da-9589-ef632c45b18b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/464466D03A7D4B01A81E59BA0DA38A87%40fhsolution.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
Hi Frederic,

I don't think commercial Grails support would help. It's not that we don't know what's wrong, we know exactly what is wrong, at the moment (3.1.6) it is issue 9915 which has been added the the 3.1.7 milestone. What would be the point of paid support, they'd just tell me what I already know and encourage me to wait for the next milestone, which is what we've been doing for the last several milestones.

I agree with you that our server team is different than our software development team in the fact that the server team requires paid support and our software team does not, but in my experience (corporate IT) that is not that unusual. When the end product must be highly available, scalable, and is business or mission critical, you do not normally find middle level managers who are willing to shoulder all of that risk on their own internal human resources. For whatever reasons, this is not usually the case with the software development branch of the organization. No one ever expects new software developed in the next few minutes, but they do expect down servers to be back on-line in the next few minutes. 



On Thursday, May 12, 2016 at 11:12:13 AM UTC-7, Frédéric Henri wrote:
hey ‘DAC’,

I am not affiliate with OCI in any case.

There’s a big difference between getting support through mailing list, Stack Overflow, github issues and a commercial engagement from a company that support the framework (and in this case you get THE company with the guys that made the product) - up to you to review your issue and define the engagement if they can commit.

No one will commit on anything through the open-source channel, thats the basic idea - some people dont like it at all and go for commercial product.

It seems in your company you believe in non-open source product, or take the commercial product for support when there’s one (your example with wildly) so just act the same for the  framework you use and get a commercial support for it.

Thanks,
Fred

Le jeudi 12 mai 2016 à 19:54, 'DAC' via Grails Dev Discuss a écrit :

Thanks Graeme, but we have been posting, and you, Burt, and others have been helping us. The pattern is we track our problems to an existing open issue and then wait for a milestone release to fix it, try again, and repeat. We've been in that pattern for months. Even if we had OCi consultants here, I don't think that would change, the issues would still have to be resolved.

In Grails 3.1.1 Burt helped us with this <a href="http://stackoverflow.com/questions/35212787/how-to-configure-grails-3-1-1-to-use-hibernate-5" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fstackoverflow.com%2Fquestions%2F35212787%2Fhow-to-configure-grails-3-1-1-to-use-hibernate-5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEcYPz19BbwxhQj1DDulimiRi6zmQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fstackoverflow.com%2Fquestions%2F35212787%2Fhow-to-configure-grails-3-1-1-to-use-hibernate-5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEcYPz19BbwxhQj1DDulimiRi6zmQ&#39;;return true;">Hibernate 5 question. After that, we identified existing open issues that had us waiting for 3.1.5, and then 3.1.6, I forget the exact issues, all opened by others, sometimes after our StackOverflow questions.

In version 3.1.6, my coworker (ndn2016) gave you feedback on <a href="https://github.com/grails/grails-core/issues/9783" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Fissues%2F9783\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNELiw1AqBN0R3f1yOrdLvKoT3zs0A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Fissues%2F9783\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNELiw1AqBN0R3f1yOrdLvKoT3zs0A&#39;;return true;">issue 9783, which prompted you to open <a href="https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Fissues%2F9915&amp;sa=D&amp;sntz=1&amp;usg=AFQjCNFugAm63nXzNuqoPrpVJ2YcXZWcSQ" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Fissues%2F9915\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFugAm63nXzNuqoPrpVJ2YcXZWcSQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Fissues%2F9915\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFugAm63nXzNuqoPrpVJ2YcXZWcSQ&#39;;return true;">issue 9915 and assign it to Grails milestone 3.1.7. So the pattern continues, and we've got customers getting worried because we have no path to production and no ability to predict when the pattern will end.

Thanks Graeme, and to Burt also, you guys have been very helpful and I'm sure you're doing everything you can. I really wish I could stick with Grails 3, and I look forward to upgrading our projects to version 3 one day in the future. I'm just sorry that it can't be now.




On Wednesday, May 11, 2016 at 9:38:21 AM UTC-7, Graeme Rocher wrote:
You could always engage OCi, we’d be happy to help you get up and running.

Apart of that I have not seen any issue reports from yourself. If you provide us with a simple example in a github repo in an issue report that reproduces the issue you are seeing on JBoss we would be happy to take a look.

Regards,

Graeme

On Tue, May 10, 2016 at 9:54 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
OK, after having two senior people dedicated to this for over a week, we're giving up on getting Grails 3 to run on JBoss EAP <a href="http://6.4.0.GA" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;">6.4.0.GA, and going back to Grails 2.5.1. We solved many issues, and we're very close to having it running but we're still seeing a lot of URL mapping issues with JSON and with GSON views. I'm sure we could get it to run one day, but at what cost. The schedule cost that we've already taken has been too great.

Graeme, I greatly appreciate your help on the issues we've had and I wish I could justify sticking with Grails 3.

I hope that the Grails team will consider additional testing on a wider selection of app servers in the future. Although I love Grails, and really want to use 3 not 2, I just cannot justify it to my stakeholders at this time for our situation. Again our situation is app server specific so just because we had this much trouble does not mean that other groups will if they are not constrained on server selection.

Thanks again.

On Friday, May 6, 2016 at 1:34:01 PM UTC-7, DAC wrote:
OK, we have success with a basic demo app on JBoss EAP <a href="http://6.4.0.GA" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2F6.4.0.GA\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFSYJSR6hlJuuVc83hn_i6xPdb6yA&#39;;return true;">6.4.0.GA, with Hibernate 4 talking to an Oracle 12c database, but using the Oracle10gDialect. Still no joy on Hibernate 5.

We're now going to try converting our project to Hibernate 4 to see if we can then get a full project deployed on a JBoss EAP domain. Will update again after that process.

On Friday, May 6, 2016 at 1:37:51 AM UTC-7, Graeme Rocher wrote:
When I say WildFly == JBoss the techniques used to configure Grails for deployment for both JBoss and Wildfly are the same.

99% of issues found with Grails on alternative containers is to do with classpath conflicts with JARs that the container ships with it.

So for example JBoss ships with its own version of Hibernate and JTA and so on. Once you have isolated Grails from all of the stuff that JBoss includes (which typically involves tweaking the jboss-<a href="http://web.xml" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fweb.xml\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGBozQD1gnNo1Yvdf1prH6_lazM3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fweb.xml\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGBozQD1gnNo1Yvdf1prH6_lazM3Q&#39;;return true;">web.xml) then it will run fine.

Regards,

Graeme

On Thu, May 5, 2016 at 7:11 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Thank you Graeme, I'll apply this and reply with the results.

Be aware however, that Wildfly 10 != JBoss EAP (commercially supported version), nore will it for a long time.

WildFly code takes years to transition over to the JBoss EAP supported version. The latest commercially supported version of JBoss EAP is a Java EE 6 certified container. I think it is somewhere around JBoss AS 7 and/or WildFly 8 code.

For the corporate IT world the big supported servers are WebLogic, WebSphear, and JBoss EAP, not WildFly. WildFly == The Wild West, as you saw in their documentation. Corporate IT isn't going anywhere near that for any business critical application.

But I'll review your post and see if this will get me closer to running on one of the supported servers that are options for us.

On Thursday, May 5, 2016 at 9:26:11 AM UTC-7, Graeme Rocher wrote:
See <a href="http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgrails.io%2Fpost%2F142674392718%2Fdeploying-grails-3-to-wildfly-10\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEy97Y-fQPgXljZ8-IPFZIQAxvgzg&#39;;return true;">http://grails.io/post/142674392718/deploying-grails-3-to-wildfly-10

Wildly == JBoss

Cheers

Graeme

On Thu, May 5, 2016 at 5:37 PM, DAC' via Grails Dev Discuss <[hidden email]> wrote:
Yes, it's a war file but it's not that simple. As you said we have a classpath, or dependency issues. The one mentioned here is just an example, there are others, a seemingly never ending supply of them. Once we solve one, another comes up. We're starting to wonder if we'll ever get it to run. We're wondering if anyone else has.

Does anyone have a Grails 3 project actually running on any of the major supported scallable servers, such as JBoss, WebLogic, or WebSphear?

I'm starting to think they don't. I know it runs on Tomcat, that's great if you're organization has those skills internally. But many corporate IT shops want someone to call, someone to blame, if anything goes horribly wrong. For that segment of the market it has to run on the big ticket supported servers, and as far as I can tell, right now (Grails 3.1.6), it does not.


On Wednesday, May 4, 2016 at 8:03:13 PM UTC-7, Brad Booth wrote:
Grails 3 can produce a standard war, which can be deployed in any of the major servlet containers. It can also produce a self executing jar. Since Grails is based on Spring Boot it can be deployed how any other Spring Boot app can be deployed. We use tomcat and have no issues (war) as well as cloud deployments on Cloud Foundry using an executable jar. The error you are getting is usually a classpath problem.

On Wed, May 4, 2016 at 3:29 PM, <[hidden email]> wrote:
Deploying Grials 3.1.16 to JBOSS EPA 6.4 failed with this error:
java.lang.NoSuchMethodError: org.grails.orm.hibernate.cfg.CollectionType.<init>(Ljava/lang/Class;Lorg/grails/orm/hibernate/cfg/GrailsDomainBinder;)


On Wednesday, May 4, 2016 at 3:10:27 PM UTC-7, DAC wrote:
I'm several months into a new project developed in Grails 3. Now we're starting to configure a production server, but we can't seem to find any of the major prod servers that we can deploy a Grails 3 application to. By major I mean JBoss EAP, WebLogic, etc...

Is everyone else having these issues with Grails 3?

What major production servers are others having success on with Grails 3?

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/380b9942-e949-445f-8e23-3d1a8ca6e72a%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/ed561cab-c277-460a-93dd-6e9a78c934a0%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/75678f26-138a-4b4b-b0db-07ffef0fb104%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/a5513fb8-ef87-4187-872d-5144ff560a39%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="9xDTDNtlJgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="9xDTDNtlJgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/5670e84c-2fae-48da-9589-ef632c45b18b%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/5670e84c-2fae-48da-9589-ef632c45b18b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/5670e84c-2fae-48da-9589-ef632c45b18b%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/5670e84c-2fae-48da-9589-ef632c45b18b%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/99e47f3e-5527-46a1-882e-0ecf7effe169%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Jeff Brown

> On May 12, 2016, at 12:39 PM, 'DAC' via Grails Dev Discuss <[hidden email]> wrote:
>
> Hi Frederic,
>
> I don't think commercial Grails support would help. It's not that we don't know what's wrong, we know exactly what is wrong, at the moment (3.1.6) it is issue 9915 which has been added the the 3.1.7 milestone.

You said “...but we're still seeing a lot of URL mapping issues with JSON and with GSON views.”.  

Has that since been resolved?



JSB


Jeff Scott Brown
Principal Software Engineer
Grails Development Team
Object Computing Inc.
http://www.ociweb.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/0CB97B3F-B856-45C5-9C6A-CFBFBD969B53%40ociweb.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
No, I do not believe the URL mapping issues we were seeing have been resolved. We were using the web profile with the assetPipeline, jsonViews, and hibernate features. It ran fine on localhost but on the latest version of JBoss EAP we had multiple .gson view files that did not get the correct URL mapping. I'll try to find time to checkout back to that version and get a URL mapping report and post it. 

On Thursday, May 12, 2016 at 1:23:02 PM UTC-7, Jeff Scott Brown wrote:

> On May 12, 2016, at 12:39 PM, 'DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="wxfYcv5sJgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com> wrote:
>
> Hi Frederic,
>
> I don't think commercial Grails support would help. It's not that we don't know what's wrong, we know exactly what is wrong, at the moment (3.1.6) it is issue 9915 which has been added the the 3.1.7 milestone.

You said “...but we're still seeing a lot of URL mapping issues with JSON and with GSON views.”.  

Has that since been resolved?



JSB


Jeff Scott Brown
Principal Software Engineer
Grails Development Team
Object Computing Inc.
<a href="http://www.ociweb.com/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;">http://www.ociweb.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
<a href="http://www.autismspeaks.org/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;">http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/0e5d2430-76c9-451a-a606-357b3042d8a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Jeff Brown
In reply to this post by Grails Dev Discuss mailing list

> On May 12, 2016, at 12:39 PM, 'DAC' via Grails Dev Discuss <[hidden email]> wrote:
>
> What would be the point of paid support, they'd just tell me what I already know and encourage me to wait for the next milestone, which is what we've been doing for the last several milestones.

I don’t know where that information came from but it isn’t correct.  That is not how our support requests are handled.  I don’t think we have ever handled a support request that way.  Paid support requests are prioritized, someone is assigned to the issue until it is resolved, we work with the client to help validate the fix, then we ship it.  As part of the diagnostic process, if a workaround is identified we relay that in the meantime.



JSB

Jeff Scott Brown
Principal Software Engineer
Grails Development Team
Object Computing Inc.
http://www.ociweb.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/1426BB4A-4E79-461C-9960-C5BDE3AA2C8F%40ociweb.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Jeff Brown
In reply to this post by Grails Dev Discuss mailing list

> On May 12, 2016, at 4:40 PM, 'DAC' via Grails Dev Discuss <[hidden email]> wrote:
>
>  It ran fine on localhost but on the latest version of JBoss EAP we had multiple .gson view files that did not get the correct URL mapping. I'll try to find time to checkout back to that version and get a URL mapping report and post it.

That would be helpful.

I don’t know what "we had multiple .gson view files that did not get the correct URL mapping” means.  .gson view files generally don’t get URL mappings.  If you can provide an app that demonstrates the problem, or describe it in a way that we can recreate it, we will take a look.

Thanks for the feedback.



JSB

Jeff Scott Brown
Principal Software Engineer
Grails Development Team
Object Computing Inc.
http://www.ociweb.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/5E2A8984-9D3E-4CAC-96BD-685CC3C847B0%40ociweb.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
In reply to this post by Jeff Brown
Hi Jeff,

Sounds like we're saying about the same thing, ok, so they would prioritize the fix and we'd wait a little less time for the fix, but we'd still be waiting for fixes. My point is we needed it to work back in late 2015, not mid 2016, and certainly not late 2016. We've been waiting for one fix after another. Each fix just gets us a step closer and a chance to see what else needs to get fixed. There is no way for us to predict when that cycle of fixes is going to end. We're at 3.1.6 now, and I don't believe any of the Grails 3 versions to date are compatible with the latest version of JBoss Enterprise App Server. That's a serious problem. I don't think prioritizing our issues is going to change that enough. 

On Thursday, May 12, 2016 at 5:28:58 PM UTC-7, Jeff Scott Brown wrote:

> On May 12, 2016, at 12:39 PM, 'DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Lis0IGp6JgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com> wrote:
>
> What would be the point of paid support, they'd just tell me what I already know and encourage me to wait for the next milestone, which is what we've been doing for the last several milestones.

I don’t know where that information came from but it isn’t correct.  That is not how our support requests are handled.  I don’t think we have ever handled a support request that way.  Paid support requests are prioritized, someone is assigned to the issue until it is resolved, we work with the client to help validate the fix, then we ship it.  As part of the diagnostic process, if a workaround is identified we relay that in the meantime.



JSB

Jeff Scott Brown
Principal Software Engineer
Grails Development Team
Object Computing Inc.
<a href="http://www.ociweb.com/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;">http://www.ociweb.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
<a href="http://www.autismspeaks.org/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;">http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/af2229be-030c-43b9-9877-a51395bb93bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
In reply to this post by Jeff Brown
Hi Jeff,

Sorry, I guess I worded it poorly. I'm going from memory. I'll deploy it again and try to be more specific. Making something that I can post is very time consuming. I can't post our application, obviously. So each time I find the problem, I have to recreate the problem in a demo app and then post that. It's a tedious process. But I will go through one more iteration for the sake of the community and since you're asking. 

I do very much appreciate your interest and everyone's help.

On Thursday, May 12, 2016 at 5:30:53 PM UTC-7, Jeff Scott Brown wrote:

> On May 12, 2016, at 4:40 PM, 'DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="_eUbzYR6JgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com> wrote:
>
>  It ran fine on localhost but on the latest version of JBoss EAP we had multiple .gson view files that did not get the correct URL mapping. I'll try to find time to checkout back to that version and get a URL mapping report and post it.

That would be helpful.

I don’t know what "we had multiple .gson view files that did not get the correct URL mapping” means.  .gson view files generally don’t get URL mappings.  If you can provide an app that demonstrates the problem, or describe it in a way that we can recreate it, we will take a look.

Thanks for the feedback.



JSB

Jeff Scott Brown
Principal Software Engineer
Grails Development Team
Object Computing Inc.
<a href="http://www.ociweb.com/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;">http://www.ociweb.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
<a href="http://www.autismspeaks.org/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;">http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/9a08100b-2b79-4cdb-9284-bb6f30846fd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Does Grails 3 run on any major servers?

Grails Dev Discuss mailing list
In reply to this post by Jeff Brown
Hi Jeff,

OK, more specific information on our mapping issues. Maybe these are not actually mapping issues, but whatever the case JBoss cannot find the files.

Grails 3.1.6 profile = web, features = asset-pipeline, hibernate, and jsonViews. We have Hibernate4 configured. Works on localhost. JBoss EAP 6.4.0.GA has following issues:

1. If we have a main controller but no main directory in our view folder and instead we put index.gsp in the view root, and then in MainController.groovy we have the following: 
render view:"../index", model:[user:[id:"default"]]
This works on localhost, but on JBoss EAP it results in this error:
2016-05-13 10:11:30,148 ERROR [org.springframework.boot.context.web.ErrorPageFilter] (http-/[redacted]) Forwarding to error page from request [/] due to exception [Could not resolve view with name '/main/../index' in servlet with name 'grailsDispatcherServlet']: javax.servlet.ServletException: Could not resolve view with name '/main/../index' in servlet with name 'grailsDispatcherServlet'
The above also works in Grails 2 when deployed to JBoss EAP, but not the Grails 3 project that I specified above. In fact anything that we try to render using the ".." notation to go up one in the relative path fails. This breaks all global templates or _template.gson files that are supposed to be shared by multiple controllers/views. 

2. All json views that use a json view template from a different controller/view fail. On localhost we have to do the following relative paths or we get a template not found error. As I remember the json view documentation says that specifying the relative path to a .gson template file is not necessary, and that the it will be found by name alone, but that is not what we've found, we have to specify the relative path even on localhost. The following works on localhost but breaks on JBoss EAP.

DayTypeController.groovy:
            render view: 'dayTypeList', model: [dayTypes: dayTypeService.getDayTypesByDistrictNbr(cmd.districtNbr)]

dayTypeList.gson:
        model{
            ArrayList<DayType> dayTypes
        }
        json{
            rows g.render(template:"dayType", collection:dayTypes, var:'dayType')
        }

_dayType.gson:
        import Color
        import DayType
        
        model {
            DayType dayType
        }
        json{
            id dayType.id
            version dayType.version
            description dayType.description
            code dayType.code
            workingFlag dayType.workdayFlag
            activeFlag dayType.activeFlag
            district g.render(template:"../districtList", model:[district:dayType.district])
            color g.render(template:"../system/color", model:[color:(Color) dayType.color])
            category g.render(template:"../dayType/dayTypeCategory", model:[dayTypeCategory:dayType.category])
        }


But when we get to JBoss EAP these all break, presumably because of the .. in the relative path.

We get the following error message in the JBoss EAP log file:
2016-05-13 12:52:28,027 ERROR [org.springframework.boot.context.web.ErrorPageFilter] ([redacted]) Forwarding to error page from request [/dayType/getDayTypesByDistrictNbr] due to exception [javax/servlet/http/HttpUpgradeHandler]: java.lang.NoClassDefFoundError: javax/servlet/http/HttpUpgradeHandler
at java.lang.Class.getDeclaredMethods0(Native Method) [rt.jar:1.8.0_60]
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) [rt.jar:1.8.0_60]
at java.lang.Class.privateGetPublicMethods(Class.java:2902) [rt.jar:1.8.0_60]
at java.lang.Class.getMethods(Class.java:1615) [rt.jar:1.8.0_60]
at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:1336) [rt.jar:1.8.0_60]
at java.beans.Introspector.getTargetMethodInfo(Introspector.java:1197) [rt.jar:1.8.0_60]
at java.beans.Introspector.getBeanInfo(Introspector.java:426) [rt.jar:1.8.0_60]
at java.beans.Introspector.getBeanInfo(Introspector.java:173) [rt.jar:1.8.0_60]
at groovy.lang.MetaClassImpl$15.run(MetaClassImpl.java:3289) [groovy-2.4.6.jar:2.4.6]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_60]
at groovy.lang.MetaClassImpl.addProperties(MetaClassImpl.java:3287) [groovy-2.4.6.jar:2.4.6]
at groovy.lang.MetaClassImpl.initialize(MetaClassImpl.java:3263) [groovy-2.4.6.jar:2.4.6]
at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:254) [groovy-2.4.6.jar:2.4.6]
at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:285) [groovy-2.4.6.jar:2.4.6]
at grails.views.mvc.GenericGroovyTemplateView$HttpViewRequest.$getStaticMetaClass(GenericGroovyTemplateView.groovy) [views-core-1.0.9.jar:]
at grails.views.mvc.GenericGroovyTemplateView$HttpViewRequest.<init>(GenericGroovyTemplateView.groovy) [views-core-1.0.9.jar:]
at grails.views.mvc.GenericGroovyTemplateView.prepareWritable(GenericGroovyTemplateView.groovy:96) [views-core-1.0.9.jar:]
at grails.views.mvc.GenericGroovyTemplateView.renderMergedOutputModel(GenericGroovyTemplateView.groovy:59) [views-core-1.0.9.jar:]
at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:303) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1243) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1027) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:971) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:968) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:870) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:844) [spring-webmvc-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.springframework.boot.actuate.autoconfigure.EndpointWebMvcAutoConfiguration$ApplicationContextHeaderFilter.doFilterInternal(EndpointWebMvcAutoConfiguration.java:237) [spring-boot-actuator-1.3.3.RELEASE.jar:1.3.3.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.springframework.boot.actuate.trace.WebRequestTraceFilter.doFilterInternal(WebRequestTraceFilter.java:112) [spring-boot-actuator-1.3.3.RELEASE.jar:1.3.3.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.grails.web.servlet.mvc.GrailsWebRequestFilter.doFilterInternal(GrailsWebRequestFilter.java:75) [grails-web-mvc-3.1.6.jar:3.1.6]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.grails.web.filters.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:67) [grails-web-mvc-3.1.6.jar:3.1.6]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:121) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.springframework.boot.actuate.autoconfigure.MetricsFilter.doFilterInternal(MetricsFilter.java:103) [spring-boot-actuator-1.3.3.RELEASE.jar:1.3.3.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.springframework.boot.context.web.ErrorPageFilter.doFilter(ErrorPageFilter.java:120) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE]
at org.springframework.boot.context.web.ErrorPageFilter.access$000(ErrorPageFilter.java:61) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE]
at org.springframework.boot.context.web.ErrorPageFilter$1.doFilterInternal(ErrorPageFilter.java:95) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
at org.springframework.boot.context.web.ErrorPageFilter.doFilter(ErrorPageFilter.java:113) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpUpgradeHandler from [Module "deployment.GalaxyEta.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.6.Final-redhat-1]
... 72 more

Here's our mappings-report, but as you said, I don't think this is related:

        Dynamic Mappings
         |    *     | ERROR: 500                                        | View:   /error           |
         |    *     | /${controller}/${action}?/${id}?(.${format)?      | Action: (default action) |
        
        Controller: main
         |    *     | /                                                 | Action: index            |
        
        
Hope this helps. Thanks again for everyone's help.



On Thursday, May 12, 2016 at 5:30:53 PM UTC-7, Jeff Scott Brown wrote:

> On May 12, 2016, at 4:40 PM, 'DAC' via Grails Dev Discuss <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="_eUbzYR6JgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com> wrote:
>
>  It ran fine on localhost but on the latest version of JBoss EAP we had multiple .gson view files that did not get the correct URL mapping. I'll try to find time to checkout back to that version and get a URL mapping report and post it.

That would be helpful.

I don’t know what "we had multiple .gson view files that did not get the correct URL mapping” means.  .gson view files generally don’t get URL mappings.  If you can provide an app that demonstrates the problem, or describe it in a way that we can recreate it, we will take a look.

Thanks for the feedback.



JSB

Jeff Scott Brown
Principal Software Engineer
Grails Development Team
Object Computing Inc.
<a href="http://www.ociweb.com/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.ociweb.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGmJq4FzWg40kVUyr9KFZMiSj7t1Q&#39;;return true;">http://www.ociweb.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
<a href="http://www.autismspeaks.org/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.autismspeaks.org%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHLOilSQBYB1lzLN6Ms6K6DtQY5DQ&#39;;return true;">http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/37eef486-0f9b-4987-b05e-1f4c163dc2d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
12
Loading...