|
Change Request Number
|
Description
|
|
058211
|
WebLogic Server version 7.0 introduced connection proxies to provide advanced features such as late transaction enlistment and idle connection detection for resource adapters. However, some resource adaptors such as IBM's IMS Connector for Java 1.2.5 could not be used because the server could not create a suitable connection proxy. This is caused by the resource adapter casting the returned proxy as a connection implementation class instead of one if its implemented interfaces.
WebLogic Server 8.1 Beta, enhances the implementation by testing whether connection proxies can be used. The test is done when a connection is first allocated to the pool. If the resource adaptor throws a ClassCastException, proxy generation is turned off and the connection is returned, unchanged, to the resource adaptor. In this case the resource adaptor is available for use, but late transaction enlistment and idle connection detection features are not available.
Note that even when the connection is returned unchanged to the resource adaptor, it is possible for client applications to receive a ClassCastException if they attempt to cast a proxy.
Note that this testing only is possible for resource adapters which return a connection to a client via the getConnection() method taking no security credentials.
|
|
079630
|
Most WebLogic Tuxedo Connector tBridge users will expect to set the Correlation ID using the setJMSCorrelationID(String) method. This will take a 32 character string and turn it into a 64 byte array. JMS stores the string as UTF-16BE. When the tBridge receives the Correlation Id from Tuxedo it is 32 characters as 32 bytes. The tBridge then uses the setJMSCorrelationIDAsBytes(byte[]) method to set the message for JMS receiving queue. The characters may be the same in ASCII but the two will not compare due the length difference.
When it is necessary to compare the Correlation ID with the ID returned from Tuxedo in the receiving JMS queue, create a byte array containing the hexadecimal values of the Correlation ID. Then use the setJMSCorrelationIDAsBytes() and getJMSCorrelationIDAsBytes()methods to create an ID to compare with the ID returned from Tuxedo in the receiving JMS queue.
For example, if the string Correlation ID is "1234567890ABCDEFGHIJKLMNOPQRSTUV":
private byte[] coridbyte={0x31,0x32,0x33,0x34,0x35,0x36,0x37,
0x38,0x39,0x30,0x41,0x42,0x43,0x44,
0x45,0x46,0x47,0x48,0x49,0x4a,0x4b,
0x4c,0x4d,0x4e,0x4f,0x50,0x51,0x52,
0x53,0x54,0x55,0x56};
msg.setJMSCorrelationIDAsBytes(coridbyte);
corIDasBytes = msg.getJMSCorrelationIDAsBytes();
corIDasBytes contains the correct value to compare with the Correlation ID returned from Tuxedo.
|
|
084387
|
If a member of the cluster that plays host to a member of a distributed destination crashes, the behavior of the distributed destination upon reboot is incorrect. Failed reconnection attempts cause all ports on the machine to be tied up. The workaround is to restart all servers that host a member of the distributed destination.
|
|
085718
|
The following exception may occur when starting the server:
java.lang.ArrayIndexOutOfBoundsException
at com.octetstring.vde.Entry.bytesToInt(Entry.java:227)
at com.octetstring.vde.Entry.readBytes(Entry.java:440)
at com.octetstring.vde.Entry.<init>(Entry.java:94)
at com.octetstring.vde.backend.standard.
TransactionProcessor.run(TransactionProcessor.java:22)
This exception may occur the first or second time a 7.x WebLogic Server domain is used with this release of WebLogic Server. To resolve the problem, delete the EmbeddedLDAP.tran file in the domain_name/servername/ldap/ldapfiles directory.
|
|
089243
|
The performance of the Beta thin client .jar files (wlclient.jar and wljmsclient.jar) degrades excessively over time. This problem will be addressed with a future version of Sun's JVM.
|
|
090774
|
If a JDBC connection pool is in use and its associated database server goes down at runtime, connections in the pool are not restored, even if TestOnReserve or TestOnRelease are enabled. The workaround is to set the ConnectionCreationRetryFrequencySeconds attribute of the pool to a positive value using the Administration Console; the recommended value is 30 seconds. Note that setting this attribute is critical if you are using a JDBC connection pool for a JMS store.
|
|
090888
|
WebLogic Server console does not target Jolt, WLEC or WTC service objects. To target an object, users will need to assign the object to the server by editing the config.xml file.
|
|
091181
|
Builder does not support setting values for the create-default-dbms-tables element. Valid values for manually editing this element are CreateOnly, Disabled, DropAndCreate, and AlterOrCreate.
|
|
091266
|
The weblogic.jspc compiler generates extra (unused) local variables in the generated code for jsps with tag libraries. This can lead to ClassCastExceptions when accessing JSPs compiled with the jspc and running on the JRockit JVM.
|
|
091353
|
The following exception may occur when starting the server:
Exception:weblogic.server.ServiceFailureException:Could not get exclusive access to the embedded LDAP data files due to existing server.
This problem occurs occasionally when stopping and immediately restarting a server. Two WebLogic Server instances cannot run at the same time in the same directory. If this exception occurs, most likely the first server instance was not completely shutdown before the second server instance was started. Check to see that the first server instance is completely shutdown and then restart the second server instance.
|
|
092029
|
The Configuration Wizard installed with WebLogic Server 8.1 Beta includes a template for creating domains that include the Sun Pet Store application. However, the Pet Store application is no longer installed with the product. (It will instead be available via the dev2dev site).
Use the WebLogic Server Medical Records application in place of Pet Store for sample J2EE application code.
|
|
092037
|
In the Solaris installation of WebLogic Server, the license.bea file contains extraneous ^M characters. However, the file provides a valid license for WebLogic Server 8.1 Beta.
|
|
092041
|
Load Balancing and certain failover scenarios are not functional with the Beta thin-client .jar files (wlclient.jar and wljmsclient.jar).
|
|
092042
|
The Interactive Query example installed with WebLogic Server 8.1 Beta does not include a sample build.xml script. However, you can use the prebuilt sample that is installed with the Weblogic Server Examples domain.
|
|
092056
|
If an Administration Server fails or shuts down in a domain, you must restart the server using the same listen address and listen port numbers from the last startup. If you reboot the Administration Server with a different address or port number, Managed Servers in the domain will be unable to communicate with the new Administration Server instance.
This problem limits certain failover scenarios for the Administration Server in this Beta release. For example, you cannot restart the Administration Server on a different machine after a hardware failure and resume administration of the domain.
|
|
092157
|
The Web Services runtime fails some TCK tests.
|
|
092225
|
You cannot use the Administration Console to target a JMS Server to a migratable target in this Beta release. If you attempt to target a JMS Server to a migratable target, the operation fails without displaying an error message. The only indication that the operation has failed is that the migratable target selection box reverts to its default value (none).
If you try to target a JMS Server to both a server instance and a migratable target, the operation appears to succeed. However, when you navigate to another area of the console, the Administration Console prompts you with the question, "Save your changes before leaving this page?" If this occurs, click the Cancel button, return to the Targets tab and click the Apply button to apply your changes and target only to the server.
|
|
092251
|
If you start WebLogic Server in an empty directory, or if the ListenAddress element is left blank in config.xml, server startup messages indicate that the server is listening on IP address 0.0.0.0. However, the server actually listens on all IP addresses bound to the primary network interface. The 0.0.0.0 value simply indicates that the ListenAddress value is not set.
|
|
092452
|
In this Beta release, Builder does not persist values specified in the JDBC Data Source Setting panel.
|
