GlassFish Web Space Server

This page contains the following information regarding GlassFish Web Space Server

Troubleshooting Tips
Recommended Data Collection for Web Container hang/crash/high CPU
Recommended Data Collection for Common Problems in GlassFish Web Space Server
Sample Support Case Entries

Troubleshooting Tips

Installation plugins

Make sure that property "auto.deploy.dest.dir" is included in the portal-ext.properties
If you change this setting it is mandatory to run ant -f synchronize.xml.

example-
auto.deploy.dest.dir=/java/glassfish/domains/domain1/autodeploy

If you are on a Windows system, use back slashes instead of forward slashes.
auto.deploy.dest.dir=C:\java\glassfish\domains\domain1\autodeploy

Web Space Server Installation Checklist

    - Check if JAVA_HOME is set.
    - JRE must 1.6.0_7 or later.
    - Ant 1.7 or later must be in the PATH.
    - Sun GlassFish Enterprise Server v2.1 is the only supported container for production as of now.

Language setting in Web Space Server

After changing the default language for non-authenticated user, the user still see the default language as English (en_US). This is because WebSpace stores cookie (GUEST_LANGUAGE_ID) for language of last user logged in and therefore you need to clear the browser cookie and reload the page before accessing Webspace for non-authenticated users.

For more details, refer to the following links:

GlassFish Web Space Server Troubleshooting
GlassFish Web Space Server Documentation Center

Recommended Data Collection for Web Container hang/crash/high CPU

Webspace can only be deployed on Sun GlassFish Enterprise Server v2.1. So refer below URL for application server 9.x
data collection. These details can be found on the Application Server Wiki.

Recommended Data Collection for Crashes and Hangs in the Application Server (Solaris)
Recommended Data Collection for Crashes and Hangs in the Application Server (Windows)
Recommended Data Collection for Crashes and Hangs in Application Server (Linux)

Sample Support Case Entries

Sample Case 1 - Issue with hot deploy

List Sun Software Product involved:
Sun Glassfish WebSpace 10.0.4

List NON-Sun Third Party Software Product involved:
N/A

Hardware Platform:
Sun Fire V890

OS and Kernel Version (Solaris # uname -a):
Sinus tapptx01 5.10 Generic_118833-03 sun4u spark SUNW,Sun-Fire-V890

Java Version: (# java -version)

java version "1.6.0_11"

Java(TM) SE Runtime Environment(build 1.6.0_11-b03)

Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode, sharing)

Sun GlassFish Enterprise Server Version (# ./asadmin version --verbose)
Version = Sun GlassFish Enterprise Server v2.1 (9.1.1) (build b60e-fcs)

Command version executed successfully.

Patch Level: Solaris: (showrev -p)
see showrev.txt

Container server.log:
see Server.log

Webspace configuration:
see portal-ext.properties

Dump of the "env" command
see env.txt

Problem Description

After the user changes the Glassfish AS Admin user's password, Web Space Server hot deploy fails with exception of invalid user or password. Below is the error stack from server.log of the container -

The following below is the snippet of the server.log:-

\[#\|2009-07-07T14:13:28.031+0800\|INFO\|sun-appserver2.1\|javax.enterprise.system.core.security\|_ThreadID=92;_ThreadName=httpWorkerThread-4848-22;admin;\|SEC5046: Audit: Authentication refused for [admin].\|#\]
[#|2009-07-07T14:13:28.032+0800|WARNING|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=92;_ThreadName=httpWorkerThread-4848-22;_RequestID=cca2b0ff-b22f-4581-a1b9-24c7461b95c7;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
\[#\|2009-07-07T14:13:28.033+0800\|WARNING\|sun-appserver2.1\|javax.enterprise.system.stream.err\|_ThreadID=79;_ThreadName=com.liferay.portal.kernel.deploy.auto.AutoDeployScanner;_RequestID=498f8f01-86b4-4c2c-ab05-c07afcc1be3f;\|
java.lang.IllegalStateException: java.io.IOException: Invalid user or password
at com.sun.enterprise.deployapi.SunDeploymentManager.getTargets(SunDeploymentManager.java:228)
at com.liferay.portal.tools.deploy.DeploymentHandler.deploy(DeploymentHandler.java:99)
at com.liferay.portal.tools.deploy.BaseDeployer.deployDirectory(BaseDeployer.java:523)
at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.java:739)
at com.liferay.portal.tools.deploy.BaseDeployer.deployFile(BaseDeployer.java:676)
at com.liferay.portal.tools.deploy.BaseDeployer.deploy(BaseDeployer.java:406)

All the data collected is uploaded to http://supportuploads.sun.com/upload.

File name, cksum and the location of the file will be shared with the case/SR owner.

Sample Case 2

List Sun Software Product involved:
Sun Glassfish WebSpace 10.0.3-1.16

List NON-Sun Third Party Software Product involved:
N/A

Hardware Platform:
Windows X86

OS and Kernel Version:
Windows Server 2003 Enterprise x64 Edition

C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt

Java Version: (C:\> java -version)
java version "1.5.0_06"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)

Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

Sun GlassFish Enterprise Server Version (# ./asadmin version --verbose)
C:\webspace-gfv2-windows\glassfish2\bin>asadmin version --verbose

Version = Sun GlassFish Enterprise Server v2.1 (9.1.1) (build b60e-fcs)

Command version executed successfully.

Container server.log:
see Server.log

Webspace configuration:
see portal-ext.propertiessee system-ext.properties

Snoop Dump using Ethereal/Wireshark:
see snoop.txt

Problem Description

Webspace server 10.0.3-1.16 - Plugin updates via GUI fails with error. Web Space Server is behind a http proxy. No issues seen if there are no proxy.

Go to Home -> control panel - > Plugin Installation > Portlet plugins -> Install More portlet ->

get error "An error occured while retriving available plugins"