> In instance1 server.log of 3.1 build that I migrated into, there are these errors:
>
> [#|2010-11-09T16:45:01.536-0500|INFO|glassfish3.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=17;_ThreadName=Thread-1;|Perform lazy SSL initialization for the listener 'http-listener-2'|#]
>
> [#|2010-11-09T16:45:01.543-0500|SEVERE|glassfish3.1|null|_ThreadID=17;_ThreadName=Thread-1;|Cannot parse port value : ${ASADMIN_LISTENER_PORT}, using port 8080|#]
>
> [#|2010-11-09T16:45:01.556-0500|SEVERE|glassfish3.1|null|_ThreadID=17;_ThreadName=Thread-1;|Unable to start v3. Closing all ports
> java.lang.NumberFormatException: For input string: "${ASADMIN_LISTENER_PORT}"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Integer.parseInt(Integer.java:449)
> at java.lang.Integer.parseInt(Integer.java:499)
> at com.sun.grizzly.config.GrizzlyEmbeddedHttp.configure(GrizzlyEmbeddedHttp.java:251)
> at com.sun.grizzly.config.GrizzlyServiceListener.initializeListener(GrizzlyServiceListener.java:104)
> at com.sun.grizzly.config.GrizzlyServiceListener.configure(GrizzlyServiceListener.java:89)
Were there any issues *during* the upgrade? I've seen various reports of failure at almost all points of the upgrade, and it looks like the problem changes based on the day you tried it.
With a new workspace, I can't even *build* right now. Will catch up on email after being away and try again.
"You need Maven 2.2.1 or above!" -- when did that happen? :)