Friday Jan 11, 2008

Cannot edit entries on the GlassFish wiki?

You may run into this message when you try to edit a page on the GlassFish project wiki site:


Sorry, but you are not allowed to do that.

Usually we block access to something because you do not have the correct privileges (e.g., read, edit,
comment) for the page you are looking for. In this particular case, it is likely that you are not
listed in the page’s access control list or that your privileges aren’t high enough (you want to 
edit, but ACL only allows ‘read’).

It is also possible that JSPWiki cannot find its security policy, or that the policy is not 
configured correctly. Either of these cases would cause JSPWiki to block access, too.

Better luck next time.

You may ask, "Why can't I add or edit a page on the Glassfish wiki site after I have logged in?"

Due to spamming and wiki vandals, the folks in the GlassFish project have added an extra step to the authoring process.

You may ask, "How do I get permission to add and edit pages on the GlassFish wiki site?"

It is explained in a FAQ entry.

I hope this entry will provide you with "Better luck next time."

Monday Dec 31, 2007


I found this message about SIP in my reader today. If you are thinking about doing SIP application development, you might want to look at the capabilities that we are adding to NetBeans to develop SIP Applications and the Sailfin project.

Monday Jul 30, 2007

Monkeying with the GlassFish Issue Tracker

I am a Firefox user but have never really gotten into customizing it with add-ons. That changed a couple days ago, when I came up with a punk hack that I wanted to enable on Google search result pages.

I started to look at Firefox add-ons that might already perform my hack... which would kind of ruin the fun of implementing it... or help me implement it.

One of the add-ons that I found was Greasemonkey. It doesn't perform my hack, but it has allowed lots of people to implement customizations of web-pages that are similar to what I want to do.

I installed it and started to look for scripts that would teach me how to monkey-around. I found this script by Jesse Glick that modifies the page title for Issuezilla entries. Direct link to Jesse's actual script. If you have Greasemonkey installed clicking the link to Jesse's script will ask you if you would like to install it.

I read through the script and took it for a testdrive... and I liked it. Then I remembered that the NetBeans Issuezilla is hosted by the same folks that host the Issue Tracker for the GlassFish community. So, I decided to try an experiment.

I opened the Greasemonkey Manage User Scripts... dialog and saw this.

I used the Add... button to update the Included Pages list to look like this.

I went to and logged in and went to look for some GlassFish issues that I need to VERIFY. I have been very lazy about that...

When I clicked on a link to see the details on an issue, this is what my Window title looked like.

Then, I figured I would share this with folks in the GlassFish community.

And now, I am done

Thursday Jan 11, 2007

All good things come to an end....

Many of you know that NetBeans 5.5 provides an excellent development environment for Java EE 5 code to deploy on the application servers based on the GlassFish Project codebase for V1 U1, like Sun Java System Application Server 9.0 Update 1 Patch 1.

Many of you have also been taking advantage of the happy accident that the plugin for V1 U1 was also capable of targeting V2 domains.

Slowly but surely, that happy accidental compatability has erroded away. NetBeans 5.5 users have lost the ability to use NetBeans 5.5 as a development environment for apps that they want to target to recent V2 builds.

But all is not lost. NetBeans 5.5.1 is the SLR to NetBeans 5.5's 300 SL. One of the release drivers for NetBeans 5.5.1 is support for application servers based on the GlassFish Project codebase for V2.

Very few changes are getting rolled into the NetBeans 5.5.1 codebase, so builds are functional and very stable. But, it could use more testing because the GF V2 codebase is still in motion.

Friday May 26, 2006

You know what this project needs....

This entry should go in my Compile Time category, because it is totally silly[Read More]

Saturday May 20, 2006

Deploying Liferay : Teaser 1

I intend to write an entry about deploying Liferay onto Sun Java System Application Server Platform Edition 9 using the archive project module for NetBeans 5.5 IDE. It isn't ready yet.

I have run into an issue that has vexed a number of other folks:

The key error message is:
    Error reading configuration for portal: The base properties file was not found

I was able to get around this issue by extracting the file out of the EAR file and placing it into domain1's lib/classes folder. This folder is part of the domain's classpath.

I know that this won't help folks on "other servers" directly. I hope that folks are able to translate this into a work-around that is applicable to their environment.

Wednesday Apr 05, 2006

Access Log in "real-time"

I noticed a thread about delayed updates to the access log for an instance of the app server built by the GlassFish Project.

The user expected the access log to update in real time. In other words, they expected to access a web page and see that access reflected in the access log immediately. When it wasn't, they were concerned.

I found a work-around, that exposed a bug.... But that is a different story....

The news that you can use is in the bug report though. The lag between a web page being accessed and that access being reflected in the access log is controlled by two properties: accessLogBufferSize and accessLogWriteInterval. You can read about them. Making the values of these properties small will decrease the lag between when a user accesses a web page and when that access appears in the servers access log.

It may well slow your server down, too, so you have been forwarned...

You may be able to leverage the self-management features of the GlassFish project's implementation of Java EE 5 to remember to crank up these values (and increase your applications performance "automagically").

That is an entry for another day/author, though.

UPDATE: One of the evaluators provides information about the access log rotation algorithm that is used by the app server implemented by the GlassFish project.

After you read it you will realize why the log hardly ever rotates if you change the rotation suffix to YYYY...


Vince Kraemer writes the entries in this blog.


« July 2016

No bookmarks in folder