|
Problem(Abstract) |
Because the JVM™ is allowed to load a particular .dll file
only once, starting a second enterprise application that attempts to load
the same .dll will result in errors. Associating a shared library with an
application server instead of an enterprise application will help you
avoid .dll load errors. |
|
|
|
Resolving the
problem |
The JVM is limited to loading a .dll file only once,
resulting in an Enterprise Application error when a second attempt to load
the same .dll occurs.
To circumvent this problem, you should associate shared libraries with the
Application Server instead of with the Enterprise Application. To do this,
keep the shared libraries that have been defined, but remove the
association with the enterprise application.
Create a new classloader for WebSphere® Application Server:
- Open the Administrative Console, then from the left side expand
Servers, then Application Servers, then click on the Server you want to
work with.
- On the Configuration tab of the Application Server, scroll down and
under Additional Properties click on Classloader then New.
NOTE: The Application Server extension classloader will be the parent and
any application classloader will be the child.
- Keep the default settings of PARENT_FIRST, then OK.
- Click on the new classloader, under Additional Properties click on
Libraries, then Add.
- Map the shared library or libraries created earlier.
- Save and synchronize.
- Restart the Application Server. If you do nott recycle the application
server with the new setting the shared library files will not be
loaded.
This should solve the problem because the shared libraries are now server
specific. So, restarting any application will have no effect on it.
WebSphere
Application Server V5.0 Information Center article on shared
libraries |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|