Tomcat just displays 404 error after upgrading from 1.3.6 to 2.1.0

[mauricio]

Hello,

I'm at the moment an intern in a company outsourced for a widely known company famous for making printers (I don't know if that really matters to you, but just to maybe give you some motivation to keep your nice work on grails).

We are at the moment building our servers for a specific product entirely in grails (actually it's likely a release candidate now).
Our system is at the moment in 1.3.6 grails version, we are looking to upgrade to 2.1.0.

Guess what, they gave that task to the intern (me) and I'm at the moment trying to upgrade a considerably big system to 2.1.0.

We have 2 separate grails application, one that is most likely just a welcome screen and have all the "about pages" and such (really simple), and the other which is the application itself.

I'm at the moment just trying to update this "welcome applicaton", the problem is that after running upgrade on it (and changing hsqldb to h2) the application theorically runs, but every page returns 404 error (even the "index" which grails prints on console, just displays 404).
Grails returns no errors on terminal.

I've tried to search about it, but the most accurate information that I could get from it was from people trying to access views directly through the URL, which I think I'm not doing (unless something must be changed on UrlMappings, even though our UrlMappings lists controllers and actions).

I've tried to create a new application to check if I have everything configured correctly, and it works, so I don't think that it may be the problem.


I have also tried to run upgrade on the main application (the second one), but it returns an error:
"| Error Failed to resolve dependencies (Set log level to 'warn' in BuildConfig.groovy for more information):

- org.springframework:org.springframework.test:3.0.5.RELEASE"

But this one I've just put on hold, I haven't really searched about that yet. But I will focus it in case I'm unable to solve the 404 error on "welcome application".



Sorry for making this "simple" request a wall of text.

Thank you.

[mauricio]

(replying to my own thread because I thought I was already a subscriber to dev list, my bad)

Hello,

I'm at the moment an intern in a company outsourced for a widely known company famous for making printers (I don't know if that really matters to you, but just to maybe give you some motivation to keep your nice work on grails).

We are at the moment building our servers for a specific product entirely in grails (actually it's likely a release candidate now).
Our system is at the moment in 1.3.6 grails version, we are looking to upgrade to 2.1.0.

Guess what, they gave that task to the intern (me) and I'm at the moment trying to upgrade a considerably big system to 2.1.0.

We have 2 separate grails application, one that is most likely just a welcome screen and have all the "about pages" and such (really simple), and the other which is the application itself.

I'm at the moment just trying to update this "welcome applicaton", the problem is that after running upgrade on it (and changing hsqldb to h2) the application theorically runs, but every page returns 404 error (even the "index" which grails prints on console, just displays 404).
Grails returns no errors on terminal.

I've tried to search about it, but the most accurate information that I could get from it was from people trying to access views directly through the URL, which I think I'm not doing (unless something must be changed on UrlMappings, even though our UrlMappings lists controllers and actions).

I've tried to create a new application to check if I have everything configured correctly, and it works, so I don't think that it may be the problem.


I have also tried to run upgrade on the main application (the second one), but it returns an error:
"| Error Failed to resolve dependencies (Set log level to 'warn' in BuildConfig.groovy for more information):

- org.springframework:org.springframework.test:3.0.5.RELEASE"

But this one I've just put on hold, I haven't really searched about that yet. But I will focus it in case I'm unable to solve the 404 error on "welcome application".



Sorry for making this "simple" request a wall of text.

Thank you.

[pledbrook]

> (replying to my own thread because I thought I was already a subscriber to
> dev list, my bad)

This should be on the user list. The dev list is for discussion of the
development of the framework itself. The user list is for issues and
questions related to developing Grails apps. It would be great if we
could continue the discussion there.

> I'm at the moment just trying to update this "welcome applicaton", the
> problem is that after running upgrade on it (and changing hsqldb to h2) the
> application theorically runs, but every page returns 404 error (even the
> "index" which grails prints on console, just displays 404).
> Grails returns no errors on terminal.

What does the 404 page say exactly? Which resource does it not find?
Is this when you do grails run-app? Are the pages doing any redirects?
Have you read the upgrade notes in the user guide? What do you mean
Grails prints "index" on the console? Is that because the controller
action prints it?

Answers to those would be a good start :)

Peter

--
Peter Ledbrook
Developer Advocate
VMware

t: @pledbrook

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[mauricio]

Sorry for posting on dev mailing list (I had in mind that this one is for those who develop grails itself, I have used user's list once, but since I haven't found anything really related to the problem that I'm having now I thought that I wouldn't get much help from user list)

Thanks for taking your time for me.

The 404 error page says:

"HTTP Status 404 - /

type Status report

message /

description The requested resource (/) is not available.

Apache Tomcat/7.0.27"

- Which resource does it not find?
It does not find any resources (at least those mapped on UrlMappings that I could open on grails 1.3.6, now on 2.1.0 I can't)
I was not able to open anything at the moment.

- Is this when you do grails run-app?
Yes, that's when I'm trying to run-app on dev environment (I always run on dev, btw)
But the application looks like that it runs ok (I mean, run-app does not display any errors on grails console).
I have also ran "clean", and it didn't make a change.

- Are the pages doing any redirects?
The pages are not.

- Have you read the upgrade notes in the user guide?
I have, but I haven't found anything that could be causing this.

- What do you mean Grails prints "index" on the console?
I mean that URL that grails' console prints, for example: "Server running. Browse to http://localhost:8080/"
If I try to access that, tomcat returns me a 404
When running on 1.3.6, I can access that without any problem (and I don't get redirected to another URL or something)

- Is that because the controller action prints it?
Does my previous answer eliminates this question? Sorry, I didn't really understand it.


--

I have also read something about "web.xml", but we don't have it...



Again, thanks a lot.

[mauricio]

Ah! Another thing that could help and I forgot to mention...

I tried to set a custom 404 error (I just set a "404" entry on the beginning of UrlMappings and set it to the same controller and action of the index) but I kept receiving the same message that I quoted in my previous reply.

[pledbrook]

> Sorry for posting on dev mailing list (I had in mind that this one is for
> those who develop grails itself, I have used user's list once, but since I
> haven't found anything really related to the problem that I'm having now I
> thought that I wouldn't get much help from user list)
>
> Thanks for taking your time for me.
>
> The 404 error page says:
>
> "HTTP Status 404 - /
>
> type Status report
>
> message /
>
> description The requested resource (/) is not available.

There are a couple of reasons this may be occurring:

1. The application is not running in the root context ('/') but at
'/<appName>'. I think this unlikely though.

2. The files in web-app/WEB-INF have not been upgraded. In particular,
the applicationContext.xml file should be new.

Also, do you have the file src/templates/war/web.xml in your project?
If so, you will need to upgrade that.

Peter

PS Please reply to [hidden email]

--
Peter Ledbrook
Developer Advocate
VMware

t: @pledbrook

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email