6635248
|
*~ wildcard pattern does not work as documented.
The wildcard pattern with tilde in the ppath does
not work as documented.
Solution
Add one of the following to the obj.conf file.
-
<Object ppath="/test[^h].html"> PathCheck fn="htaccess-find"
filename=".htaccess"</Object>
-
<Object ppath="*~*(.testh.html|.testh.html/)">PathCheck
fn="htaccess-find" filename=".htaccess" </Object>
-
<Object ppath="*~*.testh.html*"> PathCheck
fn="htaccess-find" filename=".htaccess" </Object>
|
6631420
|
If htaccess is used, JSP files in the docroot cannot be protected.
HTML files are treated with the complete URL, whereas JSP files have
a relative url. The current webcore implementation has no scope for protecting
JSP files.
Solution
None as yet.
|
4676888
|
On Microsoft Windows 2000, cannot create JVM
when JVM heap size is set to a large value.
If you try to set a larger JVM heap size on Windows 2000, you might
get the following error message:
Error occurred during initialization of VM, Could not reserve
enough space for object heap Internal error: unable to create JVM
Solution
To configure the Sun Java System Application Server with a larger JAVA heap
size on Windows 2000, it is necessary to rebase the Sun Java System Application Server DLLs.
The Rebase utility, which comes both with Microsoft Framework SDK and
Microsoft Visual Studio, allows you to set optimal base addresses for a number
of DLLs starting from some address and thereby increasing JVM heap availability.
The SDK Help Rebase topic recommends using address 0x60000000. For more details
on rebase utility:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tools/tools/performance_tools.asp
Requirements:
To apply rebase to Application Server dynamic libraries do the following:
-
cd into install_dir\bin
-
rebase -b 0x6000000 *.dll
-
cd ..\lib
-
rebase -b 0x6600000 *.dll
|
4686003
|
HTTP Quality of Service limits are not enforced.
Quality of Service (QOS) includes a means of specifying the maximum
number of HTTP connections and the bandwidth limit. When these attributes
are exceeded, a 503 error should be returned to the client. However, after
enabling QOS through the Administration interface, the server does not enforce
the QOS limits.
Solution
To fully enable QOS features, you must manually add an AuthTrans fn=qos-handler
line to the top of the default object in the obj.conf file
of the virtual server. The qos-handler Server Application Function (SAF) and obj.conf configuration file are described in the Developer’s
Guide to NSAPI.
|
4692673
|
Restarting an instance in debug mode seems to
fail if the instance is originally running in non-debug mode.
If an instance is started without checking/selecting the ’Start/Restart
in debug mode’ check box, subsequent settings of this check box do not
work. In the Administration interface, the Debug Enabled check box appears
unchecked, even though it has been checked. The server.xml file
also shows debug-enabled=false.
Solution
None.
|
4699450
|
On Microsoft Windows 2000, deployment fails
for EAR files if total length of the path to a generated file during deployment
exceeds 260 characters.
On the Windows 2000 platform, the Java Virtual Machine (JVM) is limited
to 260 characters for path names to generated files. This is a problem with
Microsoft Windows support in the JVM, and is likely to be fixed in the J2SE
1.5 release.
Solution
When deploying an application, use a path and file name that are less
than 260 characters combined.
|
4723776
|
On Solaris, server fails to restart when converting
to an SSL-enabled environment.
If you attempt to restart the Sun Java System Application Server after installing
a certificate and enabling security, the restart fails. A message is displayed
indicating that the server failed to receive a password. A second click of
the Start button starts the server. When SSL is not enabled, passwords are
not cached which results in the failure of restart. The restart command does
not support the transition from non-SSL to SSL enabled mode.
NOTE: This problem only occurs the first time the server is restarted.
Subsequent restarts work fine.
Solution
If you have encountered this problem:
Click Start.
To avoid this problem, perform the following steps instead of clicking
the Restart button.
Click Stop. Click Start.
|
4724780
|
Cannot start Admin Server if the domain is created
in another system.
-
If the domain is created on a PCNFS mounted drive, the Admin
Server and any instances within such domains cannot be started due to a known
Microsoft issue involving PCNFS drives.
-
If the domain is created in the same local drive as the product
installation but in a different directory path, the instances and the Admin
Server work as expected, and are fully operational.
Solution
None.
|
4734184
|
On Microsoft Windows 2000, the console is sometimes
disabled.
Sometimes (rarely) the Admin Server or Application Server instance hangs
during deployment or when commands are run. This can happen when some of the
text from the console log is selected. If you deselect the text on the console
log, the process continues.
Solution
Disable automatic creation of the console for server1 instance by setting log-service create-console attribute to false.
Clicking the mouse or pressing Enter on the console log might also solve this
problem.
|
4736554
|
After a secure HTTP listener has been removed
from a server, the administrator is still prompted for the (no longer needed)
password.
Solution
Remove the entire server and then add it again.
NOTE: To avoid the problem in the future—Before removing the httplistener,
disable security using the following command:
/export2/build/bin/> asadmin set --user admin --password
adminadminserver1.http-listener.http-listener-1.securityEnabled=falseAttribute
securityEnabled set to false./export2/build/bin/> asadmin delete-http-listener
--user admin --password adminadmin ls2Deleted Http listener with id = ls2
|
4737756
|
On Microsoft Windows 2000, corrupt messages
display on the console.
On Windows 2000, for a non-English locale (such as Japanese) you might
see corrupted messages displayed on the console.
Solution
Use the Admin interface to view the log messages.
|
4739831
|
A partially-deleted instance causes incorrect
responses from some CLI commands.
If a server instance is partially deleted, the following problems are
known to occur with some CLI commands (solutions are provided with each problem
description):
-
The create-instance command in local mode
reports that the instance exists even if there are no sub-directories under
the instance folder.
Solution
Manually remove the leftover instance directory, then run the create-instance command.
-
The list-instances command in local mode
includes the partially-deleted instance name and status.
Solution
Manually remove the leftover instance directory, then run the list-instances command.
-
On Microsoft Windows 2000, the start-instance command
in remote mode displays a null string.
Solution
Manually remove the leftover instance directory, create a new instance,
then run the start-instance command.
-
On Microsoft Windows 2000, the stop-instance command
in both local and remote modes reports incorrect exceptions. In local mode,
the command displays an incorrect message stating that the instance is not
running. In remote mode, the command displays a null string.
On
Solaris, the stop-instance command in local mode incorrectly
reports that the user does not have permission to access the instance’s config directory although the config directory
does not exist.
Solution
Manually remove the leftover instance directory.
|
4739891
|
Deletion of a virtual server fails if the default
web module referred to by the virtual server does not exist or has been undeployed.
Solution
Set the Default Web Module field of the virtual server to None Selected,
click OK to save the changes, then delete the virtual server.
|
4740022
|
SNMP: END OF MIB is returned when adding and
starting a new instance server.
If you add and start a new instance without shutting down the instance
server and subagent, an END OF MIB message is returned.
Solution
-
To view a new instance, make sure the subagent and all the
instance server processes are shut down. Under each server ->Monitoring
-> "Enable SNMP Statistics Collection: on", apply the change, then restart
each instance server, and start only one subagent process again.
-
If the subagent is already running, don’t start any
extra subagent processes in any instance. There can only be one master agent
and one subagent for a Sun Java System Application Server installation (common
for all domains/instances).
|
4737138
|
License expired message does not appear at Microsoft
Windows Services or at the DOS prompt.
When starting servers from Windows Services or from the DOS prompt command
(startserv.bat) after license expiration, appropriate license
expiration messages are not shown
Solution
Start servers from CLI (asadmin) or from Sun program icon
|
4780488
|
Existence of multiple obj.conf files causes
confusion.
Upon creation of a new Sun Java System Application Server instance, the instance-dir/config/ directory will contain
two obj.conf files, one named obj.conf and
the other named virtual-server-name-obj.conf,
where virtual-server-name is the same value as
the instance name for the virtual server that is created automatically during
instance creation. The documentation refers to “modification of the obj.conf file” when it should refer to “modification
of the obj.conf file associated with the virtual server
of interest.”
When the Sun Java System Application Server is installed, the obj.conf and server1-obj.conf files exist under the /domains/domain1/server1/config/ directory. The content in the file named obj.conf is
overridden by the content of the server1-obj.conf file
specified at the virtual server level. In effect, the file named obj.conf is not used by the Sun Java System Application Server instance.
For example, if you modified the file named obj.conf while
configuring the Sun Java System Application Server web server plug-in, your pass
through settings will not take effect because the wrong obj.conf file
has been modified.
Solution
If and when you need to modify the obj.conf file
for an instance, modify the file prefixed with the virtual server name of
interest.
|
4938319
|
Errors when using SSL and web server (reverse
proxy) plug-in.
502 errors occur when using SSL and the web server plug-in
Solution
Set the keepAliveTimout value to the same value in
both the Sun Java System Web Server magnus.conf file and
the Sun Java System Application Server’s init.conf file.
If these values are different the connection may be closed when the Application
Server connects to the Web Server or the Web Server connects to the Application
Server. If the connection is already closed, you see a 502 error.
|
6092475
|
When running the web server (reverse proxy)
plug-in with Sun Java System Web Server 6.1 on Intel-based hardware (such
as Solaris x86, Linux, or Microsoft Windows) the Sun Java System Web Server
may experience crashes and restarts under heavy loads.
Solution
To correct this problem, make the following configuration change to
the magnus.conf file and restart the web server instance:
KernelThreads 1
RqThrottle 1
These changes cause Sun Java System Web Server 6.1 to use native OS
threads on the Intel platform hardware, rather then creating NSCP threads,
which do not scale well on Intel based hardware.
These settings are not needed for other hardware platforms, such as
Sun Solaris SPARC.
|
6157476
|
On UNIX platforms, users in the same group as
the “sysuser” of the Sun Java System Application Server’s
domain and instances do not have write access to deployed applications.
Solution
To avoid this problem:
-
Create the domain with the -sysuser option.
-
As the system user, change the user mask to 2 by running umask 2 at the command prompt. This change turns on the group write
permissions for all files created by the Sun Java System Application Server.
-
Restart the Admin Server.
-
Grant group write permissions to the server instance’s
applications directory by executing chmod -R 775 applications in
the instance directory.
Files of deployed applications will now
have group write permissions. For additional background and more information,
see Info Doc 77800.
|