Java, business and... NetBeans ! [[ Jonathan Lermitage ]]

Tag - GlassFish

Entries feed - Comments feed

Friday 22 March 2013

Why I have planned to move to Apache TomEE, the next-generation Java EE server

TomEE first logo (it may change later)After having worked with GlassFish and Tomcat platforms for several years, I recently planned to quit them and learn the TomEE platform. I'll try to explain why and how.

This news is also available at

Continue reading...

Tuesday 20 November 2012

NetBeans 7.3 cool feature n°1 : GlassFish credentials memorization

NetBeans 7.3 is still under development (you can download and test the Beta2 build) but it already offers many interesting improvements. I'll talk about one of them :

The NetBeans IDE allows you to register application servers like Apache Tomcat and Oracle GlassFish. Once registered, you can deploy application, start and stop the servers, etc.
Usually, the first thing to do on a fresh install of a server is to update the administrator password.

NetBeans 7.2 (and previous versions) is able to memorize the administrator of Tomcat servers but - this is annoying, it is not able to memorize the administrator's password of GlassFish servers. Actually, it is designed to use the default account and password of a fresh GlassFish installation only (something like "admin"/"admin"). If you modify the password and/or the administrator's account name, NetBeans will ask you for GlassFish credentials every time you start the IDE; you can't memorize credentials :

NB72 ask for GlassFish credentials

Continue reading...

Wednesday 29 February 2012

GlassFish 3.1.2 - My remote admin doesn't work. What the hell ?

sparky_3.1.2_blue.gifGlassFish Server 3.1.2 has just been released. If you already have installed it, you probably tried to connect to the administration page from an other computer (in my case, GlassFish is installed on a dedicated server).
If you don't have modified security configuration, you must face a problem : you cannot login to GlassFish administration page, and it shows a message like Secure Admin must be enabled to access the DAS remotely.

This kind of security rule is not new, but GlassFish 3.1.2 now enables it by default : you have to enable Secure Admin first to login remotely.

To activate Secure Admin, you only have to :

  • start GlassFish.
  • go to the "bin" directory of your GlassFish installation.
  • run the "asadmin enable-secure-admin" command. You will have to type admin username and password.
  • restart GlassFish.
  • you can now go to the GlassFish administration page remotely (http://YourServerAddress:4848/). Note that you will be automatically redirected to the secured admin page https://YourServerAddress:4848/. You can log in.

Nota : I have noticed that Secure Admin doesn't work if you have changed the default admin port (4848). To use an other admin port, you may have to make some additional configurations.