On Mar 13, 2011, at 11:51 AM, nigini_at_gmail.com wrote:
> I cannot confirm that my error was the same as yours, but yesterday
> I've made this same upgrade with a project, and it hanged with the
> --upgrade when starting domain. Searching web about it, I've found this
> post -
> http://thegreyblog.blogspot.com/2011/02/upgrading-oracle-glassfish-serv
> er-to-v.html - that tells that there is an issue related with OSGi
> cache after the domain's upgrade.
If you're upgrading to 3.1, the osgi-cache problem should not be an issue. When you run "asadmin start-domain --upgrade" the launcher renames the directory for you and then proceeds with the upgrade.
Can you tell us exactly what you did and what was in the server log file?
>
> After stopping the server, deleting the cache folder, I was able to
> start-domain without problems. Should it be put in account? (I was not
> using Netbeans!)
The bug is about NetBeans starting the server without using asadmin, so the upgrade never happens. Your issue seems unrelated, and I'd like to know more about it.
Thanks,
Bobby