Resolved Issues for WLS 5.1.0 |
|
|
- Service Pack 1
- Service Pack 2
- Service Pack 3
- Service Pack 4
|
Service Pack 1
ISSUE 9488/9459/9512:
Fixed a problem with clients not registering sockets correctly. The problem arose with
Solaris' native muxer. When a connection was initiated, the side doing the
initiating never registered the socket performing this task with the socket
readers. The problem originated in a logic flaw in the determination of whether or
not the socket is closed. This is done in the JVMSocketT3 class before the
socket is registered.
ISSUE 9665:
ISSUE 9731:
Fixed an IOException in SSL. The problem was located in the native
RSA's implementation of the RSA algorithm. A NullPointerException was being
thrown while trying to benchmark SSL performance. This exception occurred
when SSL was configured to native.
ISSUE 9737 & 10117:
Fixed a problem with Verisign's global server id. Global Server ID needed
testing to be done and changes to be made accordingly. This was an
integration issue.
ISSUE 9879:
Fixed a problem with NoSuchObjectException being thrown under concurrent entity access. When one client had access
to pk-1 and was thrown an exception, NoSuchObjectException was thrown to any
client waiting on the lock for access to pk-1. Essentially the bean was being removed
from the container, and therefore not available to the next client on the
lock.
ISSUE 9902:
Fixed a problem with EJBC and spaces in the classpath. The problem occurred because, in EJBC,
space characters were appearing in classpaths. Some string operations were
placing these unwanted characters in the classpaths.
ISSUE 9936:
Fixed a problem with debug messages being printed by default in servlets and socket communications. A SocketException was thrown while
holding the refresh button on a browser. Exceptions were being thrown by
default in MuxableSocketHTTP and ListenThread.
ISSUE 9999:
Fixed a post-compilation problem
with postStoreGeneration. Since some vendors postprocess the byte codes
generated from compilation, compilation must occur before the call of
postStoreGen.
ISSUE 10032:
Fixed a problem with immediately rolling back
transactions which have been marked for rollback. These
rollbacks were being held for an extra 60 seconds if the transactions were
not in the active state. If a bean was marked rollbackOnly, the rollback call
returned immediately, but the actual rollback took 60 seconds to occur.
ISSUE 10132:
Fixed an IOException exception that was being raised in FileServlet when serving multiple requests
ISSUE 10138:
Fixed a problem with some broken
casts in the JDBC20 jts driver. The jts connection class was being used to
cast dbms connections, rather than giving itself as the argument to the cast
call.
ISSUE 10149:
Fixed a problem where debuggers
were not notified of dynamic class loads. Debugging from different platforms
into the WebLogic Server required forcing the loading of the class before setting a breakpoint that will be hit, and cycling the server every time a class is changed. Essentially, tools needed access to an alert that warns of classes being dynamically loaded.
ISSUE 10159:
Fixed the rewriting of empty tags and namespaces which caused problems for XSL in combination with JSP
ISSUE 10170:
Fixed a problem with WebApp formauth. The authorization checking for webapps requires credentials for everything that has a <login-config> tag. Authorization checking should only require credentials for those with <security-constraint>s containing something of the form <url-pattern>/.../*</url-pattern>.
ISSUE 10173:
Fixed a problem with server-side stub clustering. Server-side stubs were not being recognized as clusterable by the replica-aware stub framework. EJBs that are deployed using call-by-value rather than call-by-reference could not be clustered. In the case where call-by-value EJBs were used, ConflictHandler messages were logged.
ISSUE 10175:
Fixed a problem where an entire JSP file within a tag extension caused the compilation to fail
ISSUE 10186:
Fixed a problem with runtime evaluated attributes failing to compile when %lt;%=%%gt; is used instead of <%=%> for XML compliance
ISSUE 10194:
Allowed for isolation to be set in Session and Bean Managed Entity Beans. With a change in the spec, EJB isolation level moved to cmp specific files. This posed the problem of setting isolation for bmp EJBs. Another side-effect of this change was that the setting of the isolation level was changed from that of a per method basis to that of a per bean basis.
ISSUE 10214:
Fixed a problem with encoding when dealing with post data that is a form. The problem was with WAP. The server was not taking encoding into account when checking to see whether post data is a form.
ISSUE 10340:
Fixed a rebuild problem with taglib/jsp. Customers using "old style" tags were having problems because 5.1.0 did not support these tags.
Service Pack 2
ISSUE 8463:
Fixed a problem where ejbc silently accepted the lack of a weblogic-ejb-jar.xml file. The pertinent code did not throw an exception when the search for a file was unsuccessful. This caused additional problems in that, if the weblogic-ejb-jar.xml file was not found, the system would set all properties to defaults without alerting the user.
ISSUE 9282:
Fixed a problem with EJB deployer element detail view not tracking the selected element correctly. The problem was in the JDK used, which was throwing bad exceptions.
ISSUE 9665:
Fixed session ID length problem so that it may be modified by session.sessionIDLengthURL. WAP dependent devices were having
difficulty accessing some URLs due to increased URL length after rewriting.
A particular problem was the session id, which is lengthy and often appended
in the rewrite of the URL.
ISSUE 9692:
Fixed a problem with getting a java.lang.ArrayIndexOutOfBoundsException when deploying EJB. This stemmed from an error existing in exception handling.
ISSUE 9945:
Fixed a problem in the console after peer gone encountered by a cluster member. The server gets into a loop trying to re-establish connection with gone peer while bad connection still exists. The server connects, and then drops the connection due to the existence of a matching connection on the server.
ISSUE 9997:
Fixed a problem with EJB Wizard throwing an exception when loading a jar file.
ISSUE 10027:
Fixed EJB1.1 compliance check to allow transient Context in Entity Beans. The restriction of transient EJBContexts in session beans ended up being enforced with entity beans as well. However, entity beans should have no restrictions placed on whether or not they are transient.
ISSUE 10054:
Provide row locking for finders to
simlulate pessimistic locking. "Can't serialize error" could appear with multi-client use of Oracle because row level locking did not work together with the isolation level TRANSACTION_SERIALIZABLE.
ISSUE 10071:
Fixed a problem with hot deploying
a servlet in the Console. If the servlet was registered in the properties
file, the servlet was deployed. However, that fact was not displayed in the
console, and attempting to load the servlet in the console resulted in an
error message "Property change error for property 'Load'. Unable to load
servlet." Contrary to this error, the browser was able to load the servlet,
and after that, the console does show that the servlet was deployed. In
attempting to hot deploy the servlet from the console(i.e. the servlet is not
registered in the properties file), the console reported the error "Property change error for property 'RegisterNewServlet'. Servlet could not be loaded or instantiated." when the user attempted to register the servlet into the register servlet dialog box.
ISSUE 10110:
Fixed a problem with allowing
access to EJBC compiler options. Tools run internally by EJBC(like the java
compiler) have access to flags controlling EJBC compiler options. The
problem was that tools coded seperately by WebLogic users were not given a
way to gain access to these EJBC compiler options.
ISSUE 10120:
Fixed a problem with ambiguous
homes not doing user selections. When loading EJBs via the deployer tool,
the error "weblogic.ejb.ui.jarbuilder.AmbiguousException: Ambiguous home for
bean..." was reported. When there existed more than one possible bean home,
the deployer had no way to determine the correct home.
ISSUE 10121:
Fixed a problem with incorrect
path to javac in the deployer tool. Windows filepaths, such as that of
javac, when stored in java.util.Properties files, cause a problem because the
":" in the path is seen as a special character to the properties file.
ISSUE 10143:
Fixed a problem with jhtml. JHTML
requests were being overwritten. 404 errors were
thrown when the incorrectly requested jhtml page was not found.
ISSUE 10172:
Changed session-timeout from
web.xml to minutes(converts to seconds). This property was set in seconds,
but the specification requires it to be set in minutes.
ISSUE 10189:
Fixed a problem with the console
assuming the identity of the default port erroneously. The code assumed that the
protocols were being reported in order. This was incorrect. The protocols
were being reported in the order in which their listen threads finished. So,
upon the start of a server, the first listening thread of this protocol to complete was
assumed to be reporting the default port.
ISSUE 10190:
Fixed a problem with missing
remote interface class not being properly reported. This was an exception
handling problem. When the user does not provide a remote class needed by a
bean correctly, a ClassNotFoundException is caught. However, this exception
does not get to the point where it is outputted to the user.
ISSUE 10245:
Fixed registering of
weblogic.servlet.utils.ServletStartup failing to recognize the servlet alias
name. The method getServlet() was deprecated, and made to return NULL.
However, the method had not been changed in the servlet registration code.
ISSUE 10257:
Fixed a problem with JMS
ObjectMessage.getObject returning null, rather than the object payload sent
by the user, when called from server side code.
This is due to the fact that messages were not going through serialization.
ISSUE 10258:
Fixed a problem with StreamMessage
throwing a MessageNotReadableException on read when used in an EJB or
servlet. A transient variable that indicates the state of the stream data
was being serialized, and therefore being reset. The payload was then seen
as NULL, causing the MessageNotReadableException.
ISSUE 10262:
Fixed an
ArrayIndexOutOfBoundsException which was occurring during deployment. While
deploying an Entity Bean with bean managed persistence, the bean went through
EJBC, but logged the error in deployment.
ISSUE 10264:
Fixed a problem with tx isolation
level not having corresponding xml writing classes. This problem only arose
if the tag specifying tx isolation level was not already in the
weblogic-ejb-jar.xml. In this case, both the converter and the deployer tool
need a way to write tx isolation level.
ISSUE 10279:
Fixed a problem with an assertion
error being thrown when certain files are added to the jar. The drive
letters were sometimes entered into the file path as lowercase. This difference
in case prevented the path from being recognized.
ISSUE 10283:
Fixed a problem with timing out of
read-only beans. Once the cache timed out, ejbLoad only called on one bean,
even when the load attempt involved a number of read-only bean instances.
ISSUE 10294:
DDConverter should just do the
simple thing when mapping roles to principals. In order to simplify the
mapping of roles to principals, it is not always necessary to do the mapping
manually.
ISSUE 10323:
Improved documentation for
LogOutputStream (replacement for LogServicesDef). Class is deprecated and
documents are updated.
ISSUE 10331:
Fixed a problem with descriptors
not being created early enough in the Provider project. Container managed
persistence was superceding the DeploymentUnit objects which encapsulate it.
This creates a circular need for .xml to exist in order to describe what belongs in
the .xml.
ISSUE 10334:
Fixed a problem with
setSessionContext not being called if initial-beans-in-free-pool is set to
some value greater than 0. This was discovered when the server was unable to
create bean instances upon start-up.
ISSUE 10348:
Fixed a problem with MM:EndLock
not being generated for useBean tag.
ISSUE 10360:
Fixed a problem with RDBMS
Deployer UI not holding container managed field mappings. This created
problems maintaining data within beans, and compiling and deploying beans at
the same time.
ISSUE 10368:
Fixed a problem with the POSIX
socket muxer losing threads. This was an exception handling error. When
threads were lost, the operation didn't always have the means to catch an
exception.
ISSUE 10381:
Fixed a problem with messed up
headers to the browser from NSAPI plug-in causing problems with IE5. A
related problem was that, when dealing with NES and the plug-in, connection
status would be set twice. This was also problematic for IE5.
ISSUE 10384:
Fixed a problem with the CMP
finders which return Collections not working correctly. The CMP finders were
dependent on a flag that was being set incorrectly.
ISSUE 10385:
NFS is no longer required for EJBs
to work in a clustered environment. In the cluster, servers were
attempting to gain access to beans they already had through another server's
directory. This became problematic when the servers were not on a shared
filesystem because one server would not be allowed to access another server's
beans.
ISSUE 10417:
Fixed problem with EJB Deployer
and the save menu item. The only button appearing active after initial
project save was the SaveAs button. When users selected this button, they
received a warning that their file would be overwritten. The Save button
should be active after the initial projects save.
ISSUE 10546:
Service Pack 3
ISSUE 5352:
Fixed a problem with the DOCTYPE
flag in weblogic.html.FrameSet. The row and column attributes were being interpreted as element
attributes rather than the type requiring quotations.
ISSUE 6756:
Fixed a problem with servlet
sessions timing out in 3600 seconds although getMaxInactiveTimeInterval
method returns -1. The session is timing out according to
weblogic.properties. However, with getMaxInactiveInterval returning -1,
the session should not time out. It is apparent with this value that the
user has tried to override the weblogic.properties file in terms of timing
out. The user should be able to specify timing out properties via the
setMaxInactiveInterval method.
ISSUE 7462:
Fixed a problem with large number of
jms topic subscribers causing problems with the server. The server can run
out of execute threads when the number of subscribers surpasses the number of
execute threads. In addition, it does not occur if neither auto-acknowledge
nor onMessage are being used.
ISSUE 8547:
Fixed problem with EJBJarLoader
unable to export EJBObject's parameters to server classloader. The EJBObject is being
loaded by the classloader, so its parameters should be exported to
the classloader as well.
ISSUE 9765:
Removed BETA message from JDBC
Solaris OCI and NT.
ISSUE 9864:
Fixed problem with Dynamic
classloader not loading exception classes of parent of Remote Interface.
Essentially, though a parent interface method would throw an exception, the
inherited interface methods didn't necessarily throw that exception.
ISSUE 9994:
Fixed problem of
Message.setJMSDeliveryMode(DeliveryMode.PERSISTENT) not persisting the
message.
ISSUE 10073:
Fixed a problem with JSP java file
naming convention. With some characters in the names of jsp files, the
compiler was reading them as ASCII values, rather than as characters.
ISSUE 10077:
Fixed a problem with the JTS
driver assuming JDBC 1.0 when deferring to the pool driver
weblogic/jdbcbase/jts/Driver.class \. This occurs even if the request is
made to a different version of the JTS driver.
ISSUE 10144:
Fixed problem with EJB classloader
not loading user defined utility classes. This is similar to ISSUE
8547. The arguments to the home and remote interface were not being exported
to the ServerClassLoader.
ISSUE 10147:
Fixed a problem with using
multiple threads to send queue messages. Messages would get crossed across
queues in JMS in 5.1. Also, after sending messages to a queue, upon
receiving those messages, the client will receive more messages than are in
the queue. For instance, after all messages are sent from the queue, the
message count in the queue could be a negative number.
ISSUE 10154:
Fixed a race condition in
JMSMessageConsumer.receive. Essentially, two methods are competing for
shared resources. When a client calls receive, the server is called with a
request for a message. The client-side code is then supposed to wait for the
server's response. In some cases, the response appeared to be received by
the client before the client began its wait.
ISSUE 10235:
Fixed a problem with pages that
don't require auth in a webapp returning null for a logged in user. The data
of logged-in users was not used in a way that would provide them access to
both restricted and unrestricted web resources consistently throughout a
session.
ISSUE 10248:
Fixed some connection problems.
The server would break T3 connection after 5-7 minutes with a
PeerGoneException. Aside from the lack of a T3 connection the server would
run fine. This stemmed from problems resetting the flag that determines when
heartbeats are sent out.
ISSUE 10268:
Fixed a problem using POST with
form based authentication in servlet 2.2. Neither GET nor POST methods allow
for a secure log-on that will allow user access to protected pages.
ISSUE 10308:
Fixed a problem with receiving
assertion errors from MBuf.getHeader in ConnectionManagerLocal. An
AssertionError is logged when server tries to connect. This is caused by a
method that is called before getting the source ID.
ISSUE 10320:
Fixed a problem with case
sensitivity and tagexts. The way in which case conversion of attributes was
done was causing problems.
ISSUE 10327:
Fixed the NoClassDefFoundError
problem when deploying EJB. This problem was found while attempting to
deploy the ShoppingClientController EJB. A necessary interface could not be accessed
from its jar file.
ISSUE 10431:
Fixed a problem with compliance
check complaining if you have a no-arg constructor and another constuctor.
The compliance should only complain if there is not a no-arg constructor in
the bean class. There should be no problems with constructors in addition to
the no-arg constructor.
ISSUE 10524:
Fixed problem with JSP's unable to
load resource bundles. The server is logging a MissingResourceException.
This problem also extended to inner classes.
ISSUE 10529:
Fixed a problem with ejbRemove not
running correctly in a transaction. An error was present between
connection pool users.
ISSUE 10546:
Fixed a problem with finding
taglibs if the home is different from current dir.
ISSUE 10550:
Fixed a problem where deploying a
WAR file was masking servlet calls with a call to the file servlet. The path
was not formatted in a way that would allow for access into subdirectories.
ISSUE 10563:
Fixed a problem with stateless
instances not being returned to freepool after app exception. The stateless
session beans weren't being marked for ROLLBACK upon completion.
ISSUE 10594:
Extended
weblogic.servlet.security.ServletAuthentication to use sessions to store
AuthUser. This extension allowed for the inclusion of
examples.security.formauth.
ISSUE 10608:
Fixed a problem with the deployer
tool filtering out methods from Home and Remote super-interfaces. The
methods defined by the super-interfaces of a bean's home and remote interfaces are not displayed when
attempting to set Method-transactions or Method-permissions.
ISSUE 10610:
Fixed a problem with with the
plugin having the ability to disable failover with "connection reset". While
doing transactions, the NSAPI plug-in could get a connection-reset from the
server and duplicate a request. Failover was only being done for connection
refuse, not connection reset.
ISSUE 10664:
Fixed the problem of
RequestDispatcher.forward() breaking on hitting the browser back button.
After forwarding a request through main.jsp to template.jsp, clicking the
back in browser button will result in a junk previous page.
ISSUE 10678:
Fixed a problem with
ServletRequest.getServerPort returning 7001 if no port is specified, when it
should be returning 80. The scheme (http/https) was not set in
weblogic.servlet.internal.ServletContextManager before dependent methods were
called.
ISSUE 10680:
Fixed a problem with the Apache
plugin. If attempting to set multiple cookies, only the first one was being set. The
setting of multiple cookies worked fine without the Apache plugin.
ISSUE 10730:
Fixed problem with Form based
authentication returning the login page whenever an
attempt is made to access a secured resource. However, the browser does not
recognize that it has received the wrong content and the superdirectory in
the URL is that of the requested page, not that of the login page. This
means a lot of broken images and links.
ISSUE 10741:
Made compliance checker message
clearer. This was an update in program documentation.
ISSUE 10758:
Fixed a problem with the ACL's on
Windows NT. There exist different issues of case-sensitivity on this
platform.
ISSUE 10762:
Fixed a problem with stateless
beans created on server startup not having the jndi environment set. The
server logs a NoInitialContextException, and cannot initialize the bean.
ISSUE 10786:
Fixed the security problem with
RequestDispatcher.forward(request, response). The method call can get past
security restraints set in the deployment descriptor.
ISSUE 10794:
Fixed problems with FileServlet
unable to handle EBCDIC pages on USS390 and Error Pages, like 404 not being
encoded properly on USS390. UTF8 encoding must also be set prior to the
generation of an error page.
ISSUE 10826:
Fixed a problem with *.abc mapping
correctly in URLHelper. If an extension mapping was included in a url
pattern, a 404 error was returned.
ISSUE 10885:
Fixed a problem with apache
plugin, the 401 Error code was not being propegated back to the client. If
the client calls a servlet, on which an ACL is set, through apache, there
will not be a prompt for username and password, but rather "No credentials
supplied".
ISSUE 10895:
Fixed finder code for ejbLoad so
that it is only generated when needed.
ISSUE 10897:
Fixed a problem with finder code
generation.
Service Pack 4
ISSUE 9029:
Fixed problem that use
weblogic.system.DNSname with Weblogic Server acting as proxy of Weblogic
cluster. A NumberFormatException error was logged. This made it impossible
to use a WebLogic proxy in front of the firewall.
ISSUE 9161:
Fixed problems with logging in Http
and also preventing JVMID.toString doing a reverse DNS Lookup. A property
needs to be included that would allow for reverse DNS lookups to be enabled
or disabled.
ISSUE 9213:
Dynamic load-balancing algorithm in
WL cluster proxy may be broken. In the WL proxy, an application benchmark
was heavily "favoring" one server over two other servers in the cluster.
ISSUE 9341:
JSP engine will now include and check
version information in compiled JSP's. Previously, in order to upgrade,
previously compiled JSPs had to be manually deleted and recompiled.
ISSUE 9536:
Fixed problem with NSAPI Failing to
load balance with load balancer and fire-wall. The servers in the cluster,
except for the primary server, were not receiving the DNSNames of the other
servers, so they were returning local IP addresses instead.
ISSUE 10228:
Certified Apache with
Covalent's Raven(SSL Module for Apache 1.3.19). Extension of support to
cover Raven was requested.(additional
details)
ISSUE 10368:
Fixed the problem with POSIX
socket muxer losing threads. The problem was in that not all of
processSockets was protected by a try/catch block, essentially a mistake in
exception handling. Exceptions or errors could by caught eventually, but
would not necessarily be indicative of what is actually causing the problem.
ISSUE 10399:
Rebuilt Apache plugin
with the EAPI patch to support Raven(SSL). To use shared memory
functionality, a patch containing a portable library must be received and
applied.(additional details)
ISSUE 10428:
Certified C-2.net stronghold
1.3.12 with Apache plugin. This was the most recent available version.(additional details)
ISSUE 10465:
Fixed problem with
HttpClusterServlet failover has problems with primary/secondary servers
situation. A default list of servers should be used once the updated list is
empty.
ISSUE 10546:
Fixed a problem with finding
taglibs if the home is different from current dir.
ISSUE 10642:
Fixed problem with
HttpClusterServlet going into an infinite loop and tying up a thread.
IOException is thrown and the service method continues its attempts to
connect to a dead server.
ISSUE 10659:
Retired T3 JDBC Driver that is
causing sessions to time out after one second. The invalidator is running
every second, rather than at its set intervals.
ISSUE 10679:
Fixed a problem with a cookie
never being set if setCookie is issued, and a res.sendRedirect is issued
after. With the apache plugin, the redirect is sent before the cookie is set
in the header.
ISSUE 10787:
Fixed problem with WAP and UTF-8
support not working with 5.1 with and without SP1. Weblogic misreads headers
and doesn't decode into UNICODE 16bit format from UTF-8.(additional details)
ISSUE 10807:
Fixed problem with ASSERTION
FAILED getServlet() returning null. Servlet init() method was throwing an
exception. The exception caused the server to bail out of the
createInstances() method and the synchronized block before the servlet
instance and the servletPool could be initialized.
ISSUE 10893:
Updated JSP code to use new
session get/set API to prevent deprecated method calls. Previously, two
deprecated methods were being generated by WebLogic.
ISSUE 10894:
Fixed a problem with an incorrect
reference to a *.jsp causing Netscape/Internet Explorer to popup file
download. The dialog associated with this download box reports an error that
the text/jsp MIME type is not recognized. However, a 404 error should be
reported.
ISSUE 10927:
Fixed setMaxInactiveInterval() NPE
when ReplicatedSession is used. An unitialized variable was being used in
this method, so setMaxInactiveInterval() did not have all the data it needed.
ISSUE 10961:
Modified server's timing as heart
beats are not being processed in time. This is because the server was not
processing heart beats in the same thread.
ISSUE 10986:
Certified Apache plugin with Raven
1.4.3/Apache 1.3.12. Previous version of Covalent Raven SSL used Apache
1.3.9, but is no longer available.(additional
details)
ISSUE 11017:
Fixed problem with plugins
returning double Content-Type headers for JSP pages for 510SP3. This problem
appears differently on different browsers. Something in the plugin is
inserting Content-type=text/jsp into the header, when it should be
text/html. This bug is in the proxy.
ISSUE 11019:
Fixed problem with Home interfaces
not being inherited. In searching for bean homes, those which inherit from
another home interface are discarded. This is due to the method used to
check for the existence of particular methods in those interfaces.
ISSUE CR025483:
Fixed an error relating to
multi object finders and complex primary keys in RDBMS CMP code
generation. The finder code needs to allocate a new primary key object for
each bean that is found in the database, instead of reusing a single object.
ISSUE CR028549:
: Fixed a BadStatusException being thrown in clusters.
Under load, servers in a cluster were timing out as heartbeats were not processed in time.
ISSUE CR030881:
Fixed problem with jsp
precompiler not accepting certain formats of attributes.
ISSUE CR031317:
Fixed the problem with
Apache plugin not working properly using VirtualHosts. Apache has the
ability to perform different functions depending on the host it is using.
However, our plugin does not utilize the functionality.
ISSUE CR031397:
Fixed problem with NSAPI
plugin sending two host headers to WebLogic. In addition, with the
ServletRequestImpl, if https and the host header came in without a port,
another host header was added rather than setting the port.
ISSUE CR031491:
Fixed the problem with
looking for session ID in parameters if
weblogic.httpd.session.URLRewriting.enable=false. The server should not look
for a session ID if the parameter ...URLRewriting.enable-false. There was a
problem with processing WL-Proxy-SSL. The server should not add another
Host: header while in this state.
ISSUE CR031492:
Fixed the problem with Jolt
session pool not providing a mechanism to set RECVTIMEOUT. In slow systems,
this causes a problem because RECVTIMEOUT is often exceeded and
administrators are unable to tailor the setting.(additional details)
ISSUE CR031500:
Fixed the problem with the
compliance checker by prohibiting declaration of methods that return
com.sun.java.util.collections.Collection. EJBC has problems with its own
generated code if this is returned. It should, however, allow for a return
of java.util.Collection.
ISSUE CR031503:
Fixed the problem with
read-only entity beans refreshing when dbIsShared is set to true.
ISSUE CR031532:
Implement features that are
available in NSAPI/ISAPI plugin in HttpClusterServlet. Added new
functionality to HttpClusterSevlet such as pathtrim, trim extension,
connection timeouts, and various other changes for better performance.
ISSUE CR031557:
Fixed the ClassCastException obtained by using JAXP with
EJB. The bug is in the parser used with JAXP.
ISSUE CR031575:
Cluster containing many EJBs
will cause multicast problems. Symptomatic of this was lack of JNDI
replication and trouble with load balancing. Properties needed to be added
to make administration and management easier.
Return to Top
Return to README