Saturday, August 22, 2015

Solution: Error while Integrating Glassfish 4.1 with Apache 2.4 via mod_jk . Shows Blank Page

When you try to use Apache 2.4 as frontend to glassfish 4.1  via mod_jk, you may encounter an error  in a form of Blank page in browser. It may be due to default listener port setting to 8009. Simply... change this default listener port.

It is widely advisable to use Apache Front ending with Glassfish server. One of the reasons is not to expose web container directly in public hosted websites.

The Apache module mod_jk is used to connect Apache and Glassfish. A wide documentation is available on internet about it. One may prefer the link...

I have experienced a peculiar behavior of Glassfish 4.1 during setup. It had not started with its default port 8080 after fresh installation.It gave an error which indicates that port 8080 was in used.But the fact was, none of the application or service was using port 8080 in system.

In order to start the Glassfish 4.1 in  server, I changed the port in domain.xml file to 8090 & it started.But problems didn’t stop here. I spent hours to achieve Apache and Glassfish integration via mod_jk which I have done several times in past years. The connection to Glassfish via mod_jk appeared to be rejected and browser showed blank page. There was no relevant log entry in JK Log file as well no activity in Glassfish console window. A clear indication that connectivity of Apache and Glassfish was not established at all.

First I checked firewall related aspects but there was no such issue.I changed the "docroot"  path in Apache virtual host setting to investigate further, but in vain.I tried with different versions of mod_jk. I rebuilt the latest mod_jk too but it also didn't worked. Finally it appeared to me that like 8080, there might be problem in system with default port 8009 too, on which Glassfish listen for http requests from Apache via mod_jk.
I changed the mentioned port 8009  in “” file to 48009 in Apache’s config folder. I also changed the port in JK listener setting of Glassfish via Admin GUI. And when I restarted the both the servers and tried to connect... Voila.... It worked in no time. It showed Glassfish's default welcome page when I simply put server host name in URI without port number of 8090.

Do inform me... If you faced the same problem and this solution worked for you too..

Happy  " Apache Front ending with Glassfish "

Write your comments....

Tuesday, June 2, 2015

Windows 10 : Last OS upgrade of Windows : D-day 29 July 2015

So Microsoft has announced the date of  release of its last version or upgrade of Windows Operating system as July 29, 2015.

As more and more computing environment is becoming "service oriented " and users don't bother any more about the shrink wrapped products, it is obvious that Microsoft too has to switch its product positioning strategy in the coming times to remain relevant in operating system space.

The graphics and imaging software giant Adobe already transformed their products into services and offering via Adobe CC cloud. Adobe was once a leading software product vendor supplying its products in CD and DVD. Now you have to hook to cloud to use Adobe products... err... means Services.

Google is already offering its software as a services on web since long. It silently and regularly updates the features of it software like Chrome browser etc.

So it is obvious that the product based deployments of operating system will have to change its form in which they have been offered so far.

Not to be surprised that Windows 10,which is code named as " Threshold" and being offered as service is a new but inevitable chapter in the history of Microsoft. This new WAAS ( windows as a services) will have new Apps, new components, new technical capabilities for mobile platforms etc. A lot has yet to emerge.  The 10 will be the last version , after that only components updates will be offered by Microsoft.

No doubt with Windows 10, Microsoft is following the on going trend, set by mobile devices market an cloud computing.