Last updated 05/15/01
This document contains the Release Notes for IBM WebSphere Application Server Version 3.5 with FixPak 4 (also known as Version 3.5.4) for Linux, Windows NT (Windows 2000 supported), Sun Solaris, AIX and HP-UX.
These Release Notes cover both the Advanced and Standard Editions. Because the Standard Edition functions are a subset of the Advanced Edition functions, note that some information in these Release Notes (for example, the mention of enterprise beans) applies only to the Advanced Edition.
You can send comments on the documentation to WASDOC@us.ibm.com. When you send information to IBM, you grant IBM an exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Note: This file is best printed in a landscape format. Also, if you find that all text does not fit on a printed page, a suggestion is to decrease the scaling before printing. Setting the scaling to 80 has proven successful. To change the format and scaling, access the Print Properties -> Advanced -> Change Orientation to Landscape -> Change Resolution to 80.
The following Web site lists the prerequisite products needed for IBM WebSphere Application Server:
http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html
You can find the complete installation instructions for 3.5.4 at http://www-4.ibm.com/software/webservers/appserv/library.html in "Planning and Installation" documentation for the Advanced Edition and the Standard Edition. Before installation, remove any previously installed e-fixes from the machine.
The Release Notes contain information about known defects and the workarounds. This document also includes some supplemental information for topics covered in the Application Server documentation.
Installation and Configuration
Administrative Console and Command Line Tools
Enterprise Beans
Servlets
Java Server Pages Files (JSP files)
Sessions
Connection Pooling
Workload Management
Security
Performance and Stability
OLT and Debugging
Tracing
Samples
Problem | Op System | Workaround |
---|---|---|
If you named your Microsoft SQL Server instead of using the default name (hostname), you will need to configure Sequelink. | Windows NT/2000 | Follow these steps to configure Sequelink: Note:The non-default Microsoft SQL Server name is STLAB20\SQLEJS in this example.
|
On UNIX, permissions of DBConfig.sh need to be changed to make it executable after unzipping the DBConfig.zip. When a radio button for a particular database is selected, the tool does not automatically fill in the correct database driver and database prefix. | AIX, Solaris | Choose the right database driver from the pull down menu and change the database prefix to the appropriate value. |
On UNIX, DBConfig tool changes the permissions of $WAS_HOME/bin/startupServer.sh to nonexecutable. | AIX, Solaris | Change the permissions of startupServer.sh to make it executable before starting the administrative server. |
The IIS filter/extension mechanism requires that the dll be on the virtual directory. Therefore install sets the virtual directory to point to WebSphere bin directory. When setting the virtual directory to point to WebSphere's bin directory, there are files that should not be accessed. For example: If a user types "http://host/SEPlugins/admin.config" they can view that file and the content contains the password. Another file in the bin directory that shouldn't be accessed is NTRegistry.dll. | All | To fix this problem:
|
The Cancel button in the uninstall screen doesn't work. | AIX | If you need to cancel the install, press Ctrl+X. |
A distributed transaction that uses two datasources defined
on separate WebSphere Application Server nodes is failing. Both the data sources
use JTA enabled DB2 7.1/FixPak 2 JDBC drivers. The following exceptions
were thrown by the client:
Failed to debit card: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: debitCard failed: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL30090N Operation invalid for application execution environment. Reason code = "06". SQLSTATE=25000 Note that debit card in the above error message is the application used for testing. |
All | Create the JTA drivers and data sources on the
same node, but ensure that the "database name" in one of the data
sources contains the alias to the database on the remote machine.
For example, suppose the following machines have the following database names: DB2 Server Machine 1: Database A DB2 Server Machine 2: Database B On machine A, you should catalog the remote database B to create the
database alias |
For SQL Server 2000 on Windows NT, there is a problem with
Microsoft Data Access Componentry(MDAC) Version 2.6.
The ODBC driver for SQL Server, embedded with SequeLink 5.x, requires dlls that
are no longer shipped in MDAC Version 2.6. Therefore, if you install SQL Server 2000 on
a clean Windows machine, the following error displays: Specified driver could not be loaded due to system error 126 (MERANT MSSS Driver for SequeLink 5.0) | Windows NT | The SQL Server 7 driver requires dlls that are not required
by the SQL Server 2000 driver and no longer ship with MDAC Version 2.6 or higher. To fix this problem, install the MDAC version that is shipped on the DataDirect SequeLink CD(or version 2.1 from the Microsoft website). Here is a link to the Microsoft website for MDAC Version 2.1: http://www.microsoft.com/data/download_21242023.htm |
If WebSphere or its Web servers are running during the time of installing the FixPak, you will get errors. | All | To avoid errors, follow these steps:
|
When installing the FixPak on a machine with only the administrative console, it will not update. | Windows NT | Copy the admin.config file from a WebSphere machine and put it under WAS_home/bin. |
WebSphere does not recognize multiple instances of IIS. It only recognizes the default instance. | Windows 2000 | Create two virtual directories in the second instance of IIS (IBMWebAS, sePlugins). Make these virtual directories identical to the first instance of IIS. Both virtual directories in both instances should be identical. You can do this for as many IIS instances you have. |
If you select the Lotus Domino plug-in during WebSphere Application Server installation, the new DSAPI filter is not enabled by default. | All | The new DSAPI filter file names, depending on the platform, are as follows:
These files are located under the WAS_HOME/bin directory. Use the following steps to enable the new DSAPI filter. (These steps assume Solaris is the example operating system, but you can use the same steps on other operating systems).
|
After uninstalling the FixPak, and trying to reinstall the same FixPak, your machine detects that the FixPak is still installed. When trying to exit, you are not able to, and the JDK is automatically updated. | All | After uninstalling the FixPak, delete the backup jar files and the uninstaller of the Fix Pack. |
During the WebSphere Application Server installation, the following error displays: ERROR-FUNCTION-entry not found on string table because you are missing a file "lodctr.exe" in the WINNT/SYSTEM32 directory. | Windows NT | WebSphere automatically installs IHS and, when this error occurs, the silent
install will stop and the WebSphere install will continue. IHS does not copy all of its needed files to the hard
drive of the machine, therefore it won't run at all. This may happen if you don't have IHS on your
machine and you install Full, Quick or Custom install with IHS.
To fix this: |
WebSphere Application Server checks for the existence of
an Application Server repository before starting the administrative server.
You may need to manually enter the com.ibm.ejs.sm.adminServer.dbInitialized property to the admin.config file located in the bin directory of the WebSphere installation directory and remove the property when the repository is created. |
AIX, Solaris, Windows NT | The current behavior of the
com.ibm.ejs.sm.adminServer.dbInitialized property with regards to
the repository verification is as follows:
Property: Does not exist in admin.config Repository: Does not exist Action: Create repository and add to admin.config: com.ibm.ejs.sm.adminServer.dbInitialized=true Trace Msg: None Property: Does not exist in admin.config Repository: Exists Action: Attempt to create repository and add to admin.config: com.ibm.ejs.sm.adminServer.dbInitialized=true Trace Msg: Tables already exist Property: Exists in admin.config with a value of true Repository: Does not exist Action: Create repository Trace Msg: None Property: Exists in admin.config with a value of true Repository: Exists Action: Verify table existence Trace Msg: Tables already exist Property: Exists in admin.config with a value of false Repository: Does not exist Action: Create repository, value of com.ibm.ejs.sm.adminServer.dbInitialized remains false Trace Msg: None Property: Exists in admin.config with a value of false Repository: Exists Action: Value remains false for com.ibm.ejs.sm.adminServer.dbInitialized Trace Msg: Tables already exist Property: Exists in admin.config with a value of nocreate Repository: Exists/does not exists Action: Repository will not be created, value of com.ibm.ejs.sm.adminServer.dbInitialized remains nocreate Comment: This flag is for OS/390 users and should not be set otherwise. |
When migrating from Version 3.02 to Version 3.5, Version 3.02 configurations are lost. | All | Before migrating from Version 3.02 to Version 3.5, you must migrate any application files first.
See InfoCenter article 3 for more information. Step 2 of the instructions tells you to migrate or upgrade to IBM WebSphere Application Server 3.5. You need to migrate, then upgrade. Follow steps 3-5 for migration, then go ahead with your upgrade. |
The exception NoSuitableDriver is displayed
when you install WebSphere Application Server using Oracle, Sybase or InstantDB as the
WebSphere Application Repository.
The exception occurs when you use DataSource to access the DB2 database for application data by choosing the DataSource for Connection Pooling function or enterprise bean. |
AIX, Solaris | Set up the DB2 environment properly in the WebSphere Application Server
startupServer.sh if you plan to refer to Oracle, Sybase or IDB databases as administrative databases. To modify startupServer.sh, find the following line in startupServer.sh in a then clause: export LD_LIBRARY_PATH Next, add the following lines BEFORE the export LD_LIBRARY_PATH line: DB2_HOME=/export/home/db2inst1 export DB2_HOME .$DB2_HOME/sqllib/db2profile LD_LIBRARY_PATH=$DB2_HOME/sqllib/java12: $DB2_HOME/sqllib/lib:$LD_LIBRARY_PATH LIBPATH=$LD_LIBRARY_PATH export LD_LIBRARY_PATH LIBPATH For $DB2_HOME, specify your DB2 instance home directory. Also, you should enter the values for LD_LIBRARY_PATH= on one line; they are shown here on two lines to improve readability. |
The README file at the end of the installation is not displayed, and Hotjava is the default web browser. | Solaris | Make sure that the Hotjava browser can be started. If not, use another browser to view the README file. |
Java applications will not run reliably where the LIBPATH length exceeds 1548 characters. | AIX | Reduce the LIBPATH length to less than 1548 characters. |
The Apache server will not start after installing the WebSphere Application Server plug-in for Apache server. | All | The plug-in installation added the line
ose.mode=out to your Apache configuration file srm.conf in the /<apache_home>/conf directory.
Open an editor on the srm.conf file, and remove
or comment out the ose.mode=out line. |
Connection is refused (error 500) when attempting to access servlets and JSP files.
The Web server and application server are under stress and the Web server log contains the following errors: Aug 30 14:52:53 1999 - Error ws_open_domain_client_socket connect return 146 error Mon Aug 30 14:52:53 1999 - Error Ws_open_domain_client_socket socket return 146 error |
Solaris | The default communications configuration between
the Web server and the servlet engine is using TCP/IP sockets. Each socket
represents a file descriptor. If the file descriptor limit per process is
set too low, attempts to open socket connections might be refused (error 146).
To resolve this condition, increase the file descriptor limit for the user from which the administrative server is started (ususally root). Edit the .profile for the user, and add the following: ulimit -n 1024 Depending on the number of connections needed, this number may need to be increased more. For this change to take effect, log off and then log on. To change the hard upper limit of the number of file descriptors in the kernel (which defaults to 1024 per CPU), you can edit the /etc/system config file to include a couple of entries: set rlim_fd_max=4096 set rlim_FD_cur=1024 After you save the file, restart the machine for the changes to take effect. |
The IBM HTTP Server will not install.
There are bad entries in the system file table: /etc/fstab. The swinstall fails in the analysis phase because the mount_all_file_systems option is true by default. |
HP-UX | Remove the bad entries from the /etc/fstab file and reinstall. If you cannot do so, edit the install_ihs_128.sh (or install_ihs_56.sh), adding the -x mount_all_file_systems=false option to the swinstall command. |
The install directory for DB2 7.1 has changed (x:\Program Files\SQLLIB) and
WebSphere Application Server Version 3.5 defaults to the old DB2 directory (x:/sqllib). The following
error displays when WebSphere Application Server is started: 2140:An internal Windows NT error occurred |
All | Check to make sure that the admin.config file is pointing to the new DB2 directory (x:\Program Files\SQLLIB). Otherwise the default will point to the old directory (x:/sqllib). Modify the admin.config pointer to the DB2 driver if you have already installed and tried to start WebSphere Application Server and are getting the error. |
If a non-DB2 database is used with WebSphere Application Server, WebSphere version 3.0.2.4 cannot be migrated to a 3.5.x version using the custom options of the WebSphere migration utility. The migration utility runs the default migration with the default database (DB2). | Linux | Edit the files startupServer.sh, setupCmdLine.sh, and admin.config so that the files set parameters for the database used, and not for DB2. Then, start the WebSphere 3.5 administrative server process. |
When installing the WebSphere Application Server 3.5 FixPak onto a system that has DB2 UDB 7.1 already installed, the WebSphere FixPak will not install and the message "Your current version of DB2 exceeds the level required by this product 7.1" is shown. | Solaris | Copy the prereq.properties file from the /cdrom directory
to the /tmp directory, and edit the SUN packages = db2cliv61 statement in
the /tmp/prereq.properties file to SUN packages = db2cliv71 . Then,
use the following command to install the FixPak:
install.sh /prereqfile /tmp/prereq.properties |
After installation of the FixPak, the product.xml file and the administrative console show the correct FixPak level but the operating system shows only 3.5.0. | All | The WebSphere Application Server FixPak installation program is working as designed. The installation program merely unpacks files to a new fileset. It does not affect the operating system "registry" of filesets, and thus the registry stays at 3.5.0 after a FixPak is installed. |
After installation of the FixPak and after the Application Server console and web server have started, you cannot visit the database page for http://localhost/WSsamples. You use the database page to configure databases. | Solaris, Windows NT | The doc_root for your web server must be set to the
appropriate value.
For IBM HTTP Server and Apache, doc_root must be set to
For other web servers, instead of HTTP_HOME/htdocs supply the following:
|
Problem | Op System | Workaround |
---|---|---|
The administration of an WebSphere Application Server administrative domain will not properly work if all nodes within the domain are at different FixPak levels of a release. | All | WebSphere Application Server administrative domain requires that all nodes be at the same FixPak level for the administration of the domain to properly work. |
In a configuration with one node run as an administrative agent and another node as the administrative server, if the installation directory on the agent node is not the same as the installation directory on the administrative server node, starting an application server fails. | All | In the admininistrative console, edit the properties for the RemoteSRP bean under the Default Container of the administrative agent node so that the "Jar File" property specifies the correct path to the ibmwebas.jar (e.g. C:\WebSphere\AppServer\lib\ibmwebas.jar) |
When starting the Administrative Console, the following error stating that
the maximum number of open cursors is exceeded displays, in part:
5803af6d DBMgr W Exception on database query: "select * from ejsadmin.REL_DEFN_TABLE where SOURCE_TYPE = ? or TARGET_TYPE = ?" com.ibm.ejs.cm.portability. ResourceAllocationException: ORA-01000: maximum open cursors exceeded |
All | To fix this problem:
|
When the administrative console is downloaded from the Internet it doesn't run. | All | A JDK has to be present on the machine using the remote console. And/Or set the JAVA_HOME. And/Or put the JDK location in the PATH. |
In the HTTP Administrative Console, the Web application property sheet does not show up with the Netscape browser. | Windows | Use Microsoft Internet Explorer as your browser. |
The Java administrative console is not displaying correctly after installing the product. You did not install the Java administrative console while installing the product and used adminclient.bat to view the Java administrative console. The Topology view shows green 'objects' listed, but they are not valid objects. They appear to be EJB-related methods. | Windows NT/2000 | Uninstall WebSphere Application Server and reinstall, including the Java administrative console. An alternative is to install the administrative console on a remote machine, which can be used to administer the remote administrative server. |
The Web-based browser administrative console is unavailable if the default server is stopped. | All | The Web administrative console runs under the default server. Stopping the default server makes the HTTP administrative console unavailable. Start the default server and then try restarting the HTTP administrative console. |
Screens are not repainting or resizing properly when running
the Java administrative console changes on a UNIX operating system with the Display
exported to a Windows NT/2000 system running a Hummingbird Exceed 6.0.1 X Windows
server. The window appears to be empty or missing panes. When you manually resize the window, the rest of the text and widgets are displayed. | Windows NT/2000 | Do one of the following:
$WAS_HOME/bin /adminclient.bat <remoteHostName> Window Manager: Window Manager = Native Use Native WM for embedded clients = No First Window to display = No Note: Hummingbird Exceed Version 6.2.0.18 and higher will also work. Follow the above instructions for configuring the window manager. Exceed requires a patch to work. Without the patch, windows are incorrectly sized. With the patch, some of the error and message dialog boxes still have clipped edges, so you need to manually resize these windows. Contact Robek Corporation for a patch to get to Exceed Version 6.2.0.18 or higher. To determine the Exceed patch level you need:
See InfoCenter article 1.2.2.4.1.1 for many more tips and instructions. |
Resizing the left panel of the Java administrative console causes the panel to become squashed and then cannot be resized. | All | Click the Topology view, then resize the left panel. |
The XML import feature of the Java administrative console does not completely handle security configurations. | All | Instead of the Java administrative console import, use the XMLConfig
command line utility for security configurations that include passwords.
The background for this recommendation is as follows: This adversely affects security, which requires the variable substitution feature of XML import to replace password variables in the XML file with actual values. Instead, password variables are exported and are expected to be replaced during import.This would limit password exposure to a single time while invoking the import command. Security configuration areas affected by this password limitation include administrator access, LTPA, LDAP, and enterprise application identities. |
After installing WebSphere Application Server, you elected to install the default configuration, and the fully-qualified domain name (FQDN) is not included in the Alias Host list of the default_host Virtual Host. Access by http://<FQDN>/servlet/snoop may fail. | All | Add a virtual host alias for the fully-qualified domain name (FQDN)
of your machine running the Web Server. The short name is automatically defined, but
some systems do not automatically define the FQDN:
|
Stopping the administrative server while it is initializing or while it is starting up application servers stops the administrative server but also causes some java.exe processes to be left running. These processes can be seen in the Task Manager. | Windows NT/2000 | It is recommended that you not stop the administrative server while it is initializing or starting up application servers. If some java.exe processes are left running, end the processes using the Task Manager. |
The WebSphere Application Server help does not display in a web browser after a user selects an option from the Help menu of the administrative console, clicks a Help push button, or makes a similar request to access Help. | Solaris | A web browser must be running before a user tries to access the product online help. |
The font for the administrative console is ugly. | Japanese Turbo Linux | Java2 has True Type font (TT fonts) rendering capability
for swing components and, if the operating system has TT fonts, Java can take advantage of them.
However, there are some cases where the TT fonts installed on the operating systems
are not satisfactory in quality (as is often the case with Linux).
In such cases, you can use an IBM TT fonts. To install a more attractive IBM TT font:
|
Problem | Op System | Workaround |
---|---|---|
When a database does not support FOR UPDATE clause and
the following access pattern is frequent, deadlocks could occur in the database. | All | Transaction 1: Select * from tb1 where id=1 Select * from tbl2 where id=2 ---------------------------- x Update tbl2 .. where id = 2 Update tbl1 ... where id=1 Transaction 2: Select * from tb1 where id=1 Select * from tbl2 where id=2 ----------------------------- x Update tbl2 .. where id = 2 Update tbl1 ... where id=1 If both transactions are at point x, then both have obtained read locks on data item represented by id=2. Now neither transaction can upgrade to write locks necessary to execute the next update statements. Usually, the database detects the deadlock and aborts one transaction. FOR UPDATE clause on select statements allows us to obtain a write lock while executing the select statement before point x and prevents the deadlock. |
While configuring the Resource Security to an existing Enterprise application a HotSpot Virtual Machine Error might occur while adding a clone of an Enterprise Java Bean. This will cause your administrative server to restart. | HP-UX 11.0 (Advanced Custom Configuration) | Disabling the HotSpot compiler will resolve the issue. This can be done by removing the HotSpot compiler from the runtime path. For example: mv /opt/WebSphere/AppServer/java/jre/lib/PA_RISC/hotspot /opt/WebSphere/AppServer/java/jre/lib/PA_RISC/hotspot.bak mv /opt/WebSphere/AppServer/java/jre/lib/PA_RISC2.0/hotspot /opt/WebSphere/AppServer/java/jre/lib/PA_RISC2.0/hotspot.bak |
The following error displays when trying to deploy specific beans
within a jar file:
Drive, com.transarc.systest.ejs.webpennies. EJBCount does not exist. Please verify the appropriate drive was given. Note: webpennies and EJBCount in the above error message is the application used for testing. |
Solaris, AIX, Linux | The error occurs when you try to deploy only one entity bean stored within a .jar file.
Select the entire *.jar file for deployment. You are then given the option to click Yes to deploying all the entity beans within the file. |
JNDI lookup EJBHome fails to return and instance of
org.omg.CORBA.Object. Try code such the following:
try { tmpObj = ic.lookup ("V3Phone"); } catch (NamingException ne) { System.out.println("MyPhoneBookServlet FAILED to lookup \"EmployeeBean\":"); ne.printStackTrace(); } if (tmpObj instanceof org.omg.CORBA.Object) { phoneHome = (V3PhoneHome)javax.rmi.PortableRemoteObject. narrow(tmpObj,V3PhoneHome.class); System.out.println("after phoneHome narrow" + phoneHome); } Note that the above (V3PhoneHome) statement should all be on one line with no space between PortableRemoteObject. and narrow; the line is divided here to improve readability. Also note that println prints null for phoneHome because tmpObj is not an instance of rg.omg.CORBA.Object. |
All | Comment out the condition //if (tmpObj instanceof org.omg.CORBA.Object) |
There is no BLOB or CLOB support for WebSphere Application Server Version 3.5 on HP using DB2 with Container Managed Persistence (CMP). | HP-UX | Any CMP bean which is to be run on the HP platform with DB2 as its persistent store CANNOT designate a Serializable object type as a CMP field. |
Some enterprise beans request more database connections on DB2 than are configured for the database, resulting in trap errors on 8-way Windows NT systems. | All | |
Enterprise bean clients are unable to interpret server-side exceptions in stack traces. | All | Enterprise bean clients must have access to server-side exception classes to interpret server-side exceptions in stack traces. Examine the server-side trace logs for the complete error information or make server-side classes available on the client. |
When trying to view a distributed transaction, the transaction monitor will not display and, if you persist in trying to access the transaction monitor, the Java administrative console hangs. | All | To stop the console from hanging, restart the administrative console. However, you still will not be able to access the transaction monitor. |
The Jetace tool displays this message when loading a JAR file: java.lang.NoClassDefFoundError |
All | When using the Jetace tool, make sure all dependent
classes (and dependencies those classes have) are on the classpath. See InfoCenter article 6.3 for guidance. |
Because of application programming practices, an application getting an enumeration of objects from an enterprise bean gets fewer than the expected number of objects. | All | Whenever possible, invoke entity bean finders
and the iteration through a resulting enumeration within a single transaction.
Some benefits are:
If an entity bean finder is invoked within one transaction (for example, a transaction which a client started via UserTransaction or from a TX_REQUIRED session bean method), the resulting enumeration must be consumed within the same transaction. The result of a finder becomes invalid once the transaction completes. The following is an example of finder usage which does not meet the above
requirement:
The code should be rewritten as follows:
UserTransaction TX = ...; |
Data in non-persisted fields of an entity bean is not maintained across transactions. | All | Entity beans should not rely on data stored in non-persisted fields (particularly, references to other beans) being maintained across multiple transactions. Entity bean instances are stored in an object pool between transactions. Each time a new transaction begins, it retrieves one of the entity bean instances in the pool and loads persisted data for the requested bean. Non-persisted fields may contain values set by a different bean used previously. If necessary, you can reinitialize the data in the non-persisted field in the bean's ejbLoad() method. |
In an inheritance hierarchy involving CMP beans,
using the results of an enumerated finder outside the transaction the finder
was run in may lead to results which violate the inheritance behavior. The
behavior may be described by the following scenario:
Consider an inheritance hierarchy involving the CMP beans Bean P (Parent) and Bean C (child). Assume that there is one instance of P (P1) and one instance of C (C1). An enumerated finder on P will return P1 and C1. However, attempts to use C1 outside the transaction in which the finder was run would result in its behaving like an instance of P (ie, the methods would have P's behavior, not C's behavior). |
All | Clients should start a transaction before running enumerated finders on CMP hierarchies, and should use the results of the finder within the same transaction. If this is done, using the scenario on the left, attempts to use C1 will demonstrate C's behavior, as expected, instead of P's behavior. |
Session persistence is supported with the following databases:
Session persistence is not supported for Merant drivers.
Note that the API for manipulating WebSphere's dynamic servlet and JSP response cache has been significantly updated. It can be found in the com.ibm.websphere.servlet.cache package. See the InfoCenter for more details.
For this release, Standard/Advanced provides remote and distributed Java debugging support or tracing capabilities on Windows NT/2000, AIX, HP/UX, Linux, Linux/390 and Solaris, as described below:
Problem | Op System | Workaround | Dynamic tracing from the Java administrative console (Console->Trace->Enabled) on a Windows NT workstation does start properly with javaw. | Windows NT | Edit the adminclient.bat file and make the following modification: Change javaw to java in the following line:
|
---|