Administration Console

8/9/2019 Administration Console

1/138

Administration ConsoleChang

eReque

st

Numb

er

Description and Workaround or Solution Fo

und

In

Fix

edIn

When importing security data that was exported using releases ofWebLogic Server prior to 9.2, B! recommends"

#f the default formats for providers in the exporting and

importing security realm are exactly the same, there should be no

problems

#f the default formats for the providers in the exporting and

importing security realms are different, the original security realm

should be upgraded to WebLogic Server 9.2, the security datashould be exported, and then imported into the 9.2 security

realm.

#f the older domain can not be upgraded, the original domainshould be booted and instead of using the xport feature in the

realm, use the $igration % xport tab for each provider andexport the security data into a file. &o import the security data

into a provider in a new security realm, use the $igration %#mport tab for each provider.

'()

*+9-

#nformation about cached /B' statements is not displayed on the /B'

$onitoring pages.

9

.)

Be

ta

'()09+0

&he Start, Shutdown, 1orceShutown, and (estart operations for /B'connection pools were missing from the !dministration 'onsole.

Workaround or Solution:

&hese operations have been added to the !dministration 'onsole.

0.

9.2

'( &he !dministration 'onsole uses the $3 management interfaces to 9 9


2/138

0*9**

interact with WebLogic Server. WebLogic Server supports several $Beanservers that provide access to management features from different

perspectives. !lthough these $Bean servers may be disabled in theWebLogic Server configuration files, the !dministration 'onsole re4uires

these $Bean servers during operation and will not run successfully

without them.

.)

.2

'(

90*50

&he !dministration 'onsole still shows the default table si6e even after

the preferred table si6e is set to something other than the default si6e.

9

.)

9

.2

'(2

))*25

!fter a page flow completes in the !dministration 'onsole, it forwards to

a different page, typically a table.

7ressing the browser bac8 button at this point results in an attempt to

load the last S7 file in the completed assistant. !t this point, all of the

context for this assistant is discarded.


B! recommends that you do not use the browser bac8 button to step

bac8 into an assistant once changes are cancelled or finished, and thatyou do not go bac8 to a previous step in an assistant. #nstead, use the

navigation lin8s and buttons in the !dministration 'onsole.

9

.)

'(2)2

*

ou can use the !dministration 'onsole to shut down the !dministrationServer, but as the !dministration 'onsole attempts to refresh itself, it

often encounters a problem displaying the page because the!dministration Server is no longer available to service re4uests. &his

failure manifests itself in different ways, depending on the timing,machine load, and other deployments.

9.

)

9.

2

'(2

)-00*

:o more than ) users or groups from an external L/!7 server or

database can be displayed in the !dministration 'onsole.

9

.)

Be

ta

9

.2

'(2

)*92

/eployment to one target server in a cluster deployed an application to

all servers in the cluster. &he avascript that selected the appropriateuser selection computed the incorrect ;&$L element representing the

cluster.

&his problem has been resolved.

9

.)

9

.2


3/138

'(2)0

2)

&he /ump &hread Stac8s feature in the !dministration 'onsole dit ==% /ump &hread

Stac8s? only wor8s if the server is running on (oc8it.


9.

)

9.

2

'(2

)020

!pplications deployed on a cluster did not appear in the list of

deployments for each server in the /eployments tab.


9

.)

9

.2

'(2)0+

5+

$essage=/riven Beans


4/138

:o warning pop=up or message appears to tell you that leaving the pagewithout clic8ing Save negates your changes.

'(2

--0

Specifying a8arta 'ommons Logging in the system classpath prevents

the !dministration 'onsole from initiali6ing.

&he problem occurred when a user specified a class in the system

classpath that was already used by the !dministration 'onsole. &heclassloader could load versions of the classes that were potentially

incompatible. Specifically, the version of Struts used internally by the

!dministration 'onsole was certified with a particular version of Log-@and 'ommons logging. ;owever, when a newer version of 'ommons

logging was specified in the classpath, the !dministration 'onsole failedto initiali6e because Struts failed to initiali6e classes needed by the

!dministration 'onsole.


&he resolution was to use a 1iltering classloader. ! 1iltering classloader

allows applications to be configured to use the application classloaderover the system classpath for configured ava pac8ages. &hese

pac8ages are"

org.apache.log4.*

org.apache.commons.*

org.apache.beehive.*

org.apache.struts.*

org.apache.oro.*

org.apache.taglibs.*

9

.)

9

.2

'(22)

*2

!fter you enable the administration port from the !dministration'onsole and clic8 the !ctivate button, the !dministration 'onsole is not

reachable until the (L used to communicate with the !dministration

'onsole is changed to ;&&7S and the administration port number.

Because the administration port setting is dynamic, the !dministration'onsole should redirect after activating any changes regarding the use

of the administration port.


9.

)

9.

2

'(2

2+*

#f you uploaded a non=ascii name application in the !dministration 9

.

9

.


5/138

-+ 'onsole, the file name appeared garbled.


) 2

'(22*25)

!fter you specify the location for the new plan for a resource adapter,the !dministration 'onsole ta8es you bac8 to the DSettings for Eadaptername%D screen where it says that no /eployment 7lan is selected.

Workaround or Solution"

ou must have separate directories for the application and the plan

instead of placing both files in the same directory.

9.)

9.2

'(22*+

)

&he /eployment 7lan tab in the !dministration 'onsole was missing forstand=alone module deployments. &herefore, the user could not ma8e

changes to the deployment plan or the descriptors of the standalone

resource adapter.


9.

)

9.

2

'(220

09

&he olt 'onnection 7ool monitoring pages in the !dministration 'onsolecannot access the olt (untime $Beans, and therefore olt connection

pools cannot be monitored or reset using the !dministration 'onsole.


se WebLogic Scripting &ool


6/138

the entire domain.

/efault" #(%%%%%

Max&esource&e)uestn+erver

weblogic.management.configuration.!AM"ean

$aximum number of concurrent re4uests to resources allowedfor each server in the domain.

/efault" ,%

$inimum" #%

$aximum" java.lang.nteger.MAX/A0'1

'(2

+5+-

&he chooser control is used in several pages in the !dministration

'onsole and presents a list of available items, chosen items, andcontrols to move items from one list to the other. &his control does not

support moving more than one item at a time using a '&(LFmouse clic8

interaction.


Select and move one item at a time.

9

.)

9

.2

'(2

++59

#f you register custom $Beans in a WebLogic Server $Bean server, you

can use roles and policies along with the WebLogic Security Service toprotect your $Beans. :ote the following restrictions"

our $BeanGs ob@ect name must include a 2!3pe=value28ey

property.

ou must describe your roles and policies in an 3!'$L 2.)

document and then use the WebLogic Scripting &ool to add thedata to your realm.

#f your 3!'$L document describes authori6ation policies, your

security realm must use either the WebLogic Server 3!'$L

!uthori6ation 7rovider or another provider that implementsthe weblogic.management.securit3.authoriation.

5olic3+toreM"eaninterface.

#f your 3!'$L document describes role assignments, your

security realm must use either the WebLogic Server 3!'$L (ole$apping 7rovider or another provider that implements

the weblogic.management.securit3.authoriation.

9

.

9

.2


7/138

5olic3+toreM"eaninterface.

'(2++0

*2

#f an installed /B' module has a password=encrypted field encryptedwith the wrong 8ey, an exception occurs in the !dministration 'onsole.

&his exception can occur when you copy a /B' module from onedomain to another.


&o re=set the password correctly, use java

weblogic.securit3.1ncr3pt 7passwor89in the domain home

directory and modify the module file to change the password value.

9.

)

9.

2

'(2

+-

2

When you use the Summary of !synchronous &as8s function in the

!dministration 'onsole, invo8ing 'ancel on a running tas8 results in

a'Control1xception.

9

.

)

9

.

2

'(2

+-*

#f the !dministration 'onsole has been modified through a 'onsole

extension, images and 'SS pages get cached by the browser. ou maynotice the caching when you use the $ed(ec !dministration 'onsole.


'lose all the browser windows and then re=open the browser.

9

.)

9

.2

'(2

+--

When you create a security provider


8/138

version on the 1rench locale.


Switch the browserGs locale to en=us.

'(2+0*

2

Web Services deployed in a Web library module did not show up in theWebLogic Server !dministration 'onsole. &he problem was caused by

the way in which the !dministration 'onsole attempted to loo8=uplibrary modules. #n some circumstances, the library module

deployments did not appear.


&he code that 4ueried for library modules was updated andmodifications were made to the &argetting tabs in the !dministration

'onsole in an effort to consolidate targetting functions.

Note: !lthough the !dministration 'onsole problem has been

resolved, other problems related to merged descriptors stillexist.

9.

)

9.

2

'(2-))

)*

&he 'hooser control in the !dministration 'onsole was not disabled in$o6illa if an dit loc8 was not ac4uired. Some Web browsers do not

treat the Disable8attribute in the same manner as #nternet xplorer

does.


&he resolution was implemented in two parts"

avascript is not emitted when the dit loc8 is held by a 'hoosercontrol that needs to participate in single change. &his change

prevents items from being selected.

#tems are explicitly greyed out when the dit loc8 is not held for a

'hooser that needs to participate in single change. &his gives theintended appearance and behavior as in #nternet xplorer, even

though #nternet xplorer is still using the IdisabledJ attribute.

!lso, no scrollbars are shown when the control is disabled for allbrowsers.

9.

9.

2

'(2-5

9-

&he !dministration 'onsole did a -re8eplo3instead of an -up8ateof an

application regardless of whether dynamic property changes are

supported or not. &his means, for example, that changes to dynamicproperties in resource adapters result in a full redeploy of the resource

adapterCapplication instead of simply an update.

9.

)

9.

2


9/138


&he resolution was implemented in two parts"

&he re8eplo3action is no longer called on the +aveaction.

#nstead, the user now has the choice of explicitly invo8ingan up8ateinstead of re8eplo3for changes that are dynamic

and re8eplo3for non=dynamic changes.

#cons have been added to the !dministration 'onsole. &hese

icons indicate whether changing the value of an attribute re4uiresa redeploy of the application.

Note: &he first time a configuration change is saved, a redeployaction is initiated. &his redeploy is re4uired to associate the

deployment plan initially with the deployment in 4uestion. Butsubse4uent changes follow the preceding rules.

'(2

-50

*

&he deletion and recreation of a /B' /ata Source in the same edit

session results in an exception, IBean already exists.J


&he configuration code was modified to handle deleted system resourcefiles

9

.

9

.

2

'(2

-0*25

&he !dministration 'onsole does not provide an option for displaying

S!1 !gent Log files.


&his feature has been added to the !dministration 'onsole.

9

.

9

.2

'(2-)

0

&he !dministration 'onsole does not honor the value specified forthe &etire !imeout !extfield when updating applications that have

the version as:eblogic-Application-/ersionin the MA;


10/138

/ersionin the MA;


11/138

-0

and password, the client does not get the expected -)+ forbidden error.! )) internal error occurs.

.2

.2

'(2

02

#f a security role or security policy definition has three or more

conditions and the first condition is removed, the action fails with anexception. Similarly, if a security role or security policy definition has

three or more conditions and all of them are removed, the action failswith an exception.


#f you want to remove only the first condition, move the second

condition up to the first position, and then remove the original firstcondition.

Similarly, if you want to remove all the conditions, remove all the

conditions except for the first condition, then move the first condition

last.

1or example"

Ko to a new domain

Select the Security=%7olicies tab.

Select the iew Log tab.

#nitially, the security policy is" &ole A8min, &ole Deplo3er, &ole

perator, or &ole Monitor.

#f you want to remove only the A8minrole, select Deplo3erand move itto the first position in the list on the iew Log tab, select A8min, and

clic8 (emove.

#f you want to remove all the conditions, selectthe Deplo3er?perator, and Monitorroles, and clic8 (emove. &hen

select A8minand clic8 (emove.

9

.

9

.2

'(2**

*

&he 9. version of the !dministration 'onsole could not be used tocreate $S messages for a 4ueue because the !ssistant page was read=

only.


9.

9.

2

'(2

00

&he !dministration 'onsole does not support a way to define a log-

watch-severit3element. &he Watch :otification configuration page

does not include form fields for configuring the 1nable8, +everit3,

and 0og :atch +everit3 attributes of the Watch notification.

9

.)

9

.2


12/138


&hese features have been added to the !dministration 'onsole.

'(2*2-)

When cloning a server using WebLogic Server 9., the custom 8eystoreand SSL settings were not cloned.


9.

9.2

'(2*9*

0

#f a user of Weblogic Server 9. used the !dministration 'onsole tochange the domainGs user loc8out security policy


13/138

59*2)


14/138

9)5-

exception when accessing a users list or a groups list, if there are toomany matches of users or groups for the specified filter.


.2

.2

$7

'(29)

)

WebLogic Server fails to reboot whenever an ;&&7 logging configurationfor the server or the virtual host is changed using WebLogic Server

!dministration 'onsole.


9.

)

9.

2$

7

'(2

9*)05

When a new deployment plan was created or an existing deployment

plan was updated for a deployed application through WebLogic Server!dministration 'onsole, the system did not provide users any

information on how to bring that deployment plan into effect.


9

.2

9

.2

$7

'(2905

*5

&he default !ccept Bac8log is set to ). &his may be insufficient forhigh=throughput applications.

Workaround

&o increase the value of !ccept Bac8log, follow the instructions provided

inhttp"CCdownload.oracle.comCdocsCcdC+222O)CwlsCdocs92C'onsole;

elpCtas8helpCtuningC&une'onnectionBac8logBuffering.html

9.

2

9.

2$

7

'(+))0

+9

WebLogic Server !dministration 'onsole does not display custom WS=7olicy files


15/138

and deployed them as libraries"

Manifest-/ersion@ #.%

Archiver-/ersion@ 5lexus Archiver

Create8-"3@ Apache Maven

"uilt-"3@ xxxx

"uil8-8E@ #.,.%%F

1xtension-;ame@ m8b

mplementation-!itle@ m8b

mplementation-/ersion@ #.%-+;A5+!

Workaround

se weblogic./eployer or WLS& instead of !dministration 'onsole.

2 )

'(29)0

-9

#t was not possible to set the Weblogic7luginnabled attribute of'luster$Bean from !dministration 'onsole.

&his problem has been resolved by providing a chec8 box in !dvancedSettings of the 'luster % 'onfiguration % Keneral tab that sets

Weblogic7luginnabled attribute of 'luster$Bean.

9.

9.

2$

7

2

'(2990)

#n the !dministration 'onsole Anline ;elp publishedathttp"CCdownload.oracle.comCdocsCcdC+222O)CwlsCdocs92C'onsole;elpCpagehelpC'orecoreserverchannelconfiggeneraltitle.html, as per the

description for the configuration option, 0isten 5ort, a value of =

indicates that the networ8 channel should obtain this value from the

serverGs configuration.


Setting no values to 0isten 5ortindicates that the networ8 channel

obtain this value from the serverMs configuration.

9.2

'(2

9*5)2

'(+2-+

*2

When you navigate the file structure to deploy an application and if

some of the directories in the file structure does not have (ead access,!dministration 'onsole used to raise ;ull5ointer1xceptioninstead of

displaying a message that says no files are selectable.


9

.

9

.2

$

72
http://docs.oracle.com/cd/E13222_01/wls/docs92/ConsoleHelp/pagehelp/Corecoreserverchannelconfiggeneraltitle.htmlhttp://docs.oracle.com/cd/E13222_01/wls/docs92/ConsoleHelp/pagehelp/Corecoreserverchannelconfiggeneraltitle.htmlhttp://docs.oracle.com/cd/E13222_01/wls/docs92/ConsoleHelp/pagehelp/Corecoreserverchannelconfiggeneraltitle.htmlhttp://docs.oracle.com/cd/E13222_01/wls/docs92/ConsoleHelp/pagehelp/Corecoreserverchannelconfiggeneraltitle.html


16/138

'(+)2

2

&here was no option in !dministration 'onsole to monitor connectiondetails for a olt 'onnection 7ool.


ou can now use the !dministration 'onsole to view details for each olt'onnection 7ool connection. 'lic8 on a connection pool entry in themonitoring table to display a page with details for each connection.

9.

9.

2$

7

2

'(+

)2*+*

Slow performance was observed for !dministration 'onsole when user

accessed it for the first time.


9

.2

9

.2

$7

2

'(+)00

52

#n !dministration 'onsole, tabs that were not selected used to display D=SelectedD in their alternative text.


9.

2

9.

2$

72

'(+

2*)+

#n !dministration 'onsole, on the 'onfiguration % /efault /elivery page

of a $S connection factory, there was no K# control to set the/efault(edelivery/elay attribute of the $S connection factory.

&his problem has been resolved by providing a text field named /efault(edelivery /elay in the /efault /elivery 'onfiguration 7arameter

Settings page of the $S connection factory.

9

.2

9

.2

$

72

'(+++

*)

ntering invalid characters in a 'onsole field used to cause full stac8trace instead of rendering an error message.


9.

2

9.

2$

72

'(+)200*

apanese characters on the 7erformance page of the Server are garbledafter clic8ing the (efresh button.


9.2

9.2

$7

2

'(+ When you deploy an application with a web module that has an empty 9 9


17/138

)2+*+

string as the context root, the following error message was displayed on!dministration 'onsole"

'nable to access the selecte8 application


.2

.2

$7

2

'(+

)--+

&he value of !ctive xecute &hreads displayed on the Server %

$onitoring %&hreads page was incorrect.

&his problem has been resolved. &he value of 71xecute !hrea8 total

count9= 7+tan8b3 !hrea8 Count9is displayed now.

9

.2

9

.2

$7

2

'(+)+

+2

#f &uxedo Server was down, WebLogic &uxedo 'onnector


18/138

&his problem has been resolved. 2

'(20)9

+9

When you exported or imported a large $S 4ueue using the!dministration 'onsole, utofMemor3exception used to occur.


9.

2

9.

2$

7+

'(2

0+)+5

&he !dministration 'onsole was not showing the status of

$essagingBridge run time instances.


9

.2

$7

2

9

.2

$7

+

'(+

*

2

&he 7revious and :ext lin8s on the /eployments page of the

!dministration 'onsole were disabled when the deployments were

expanded.


9

.

2

9

.

2$

7+

'(+*

05

&he /eployment page on the !dministration 'onsole used to displayonly ten deployments per page.


9.

2

$7

9.

2

$7

+

'(+2*0

55

'(+

+)+2+

sers accessing the !dministration 'onsole using a proxy server weredisconnected from the !dministration Server as it redirects the (L to

port 5)), which did not access the !dministration 'onsole from the

client side.


9.

2

$7

9.

2

$7

+

'(+

-+)+-

'(+-2

)5

$odifying the !dministration 'onsole context path by changing the (L,

the :/# view for the :/# tree of the Server did not use the newcontext path and it was not displayed correctly.


9

.2

$7

2

9

.2

$7

+


19/138

'(+-*0

92

'(+-

9

When $anaged Server was not running, ;ull5ointer1xceptionused tooccur in the Store=and=1orward !gent $onitoring page of the Server.


9.

2$

72

9.

2$

7+

'(+

+25)2

An the Server % 'onfiguration % Keneral page, the icons which

indicated that the server need to be restarted, for a change to ta8eeffect, were not displayed correctly.


9

.2

$7

2

9

.2

$7

+

'(+++0

59

'(+

-90)

!n exception used to occur while accessing the Server % $onitoring %7erformance page from the !dministration 'onsole.


9.

2

9.

2$

7+

'(++-9

&he content of a $S text message was getting changed when exportingthe $S text message from the !dministration 'onsole.


9.2

$7

9.2

$7

+

'(++-0

5+

'(+

222-

WebLogic !dministration 'onsole was not allowing the user to createmore than )) W&' #mportCxport services.


9.

9.

2$

7

+

'(+

+9-)2

&he connection factory was displayed in the :/# tree whenever the

name is prefixed with GWG, otherwise it was not getting displayed thoughit was created in the config.xml file.

9

.2

$7

9

.2

$7


20/138

&his problem has been resolved. 2 +

'(+2+9

9

ou were not able to create a data source through the !dministration'onsole when [email protected]/ataSource was used as the driver

class.


9.

2

9.

2$

7+

'(+

-*-90

&he !dministration 'onsole failed to open the $S $odules page

with javax.servlet.+ervlet1xceptionif the page was customi6ed to

add some filter criteria.


9

.2

9

.2

$7

+

'(+

-5-

-*

&he administration port must accept only secure, SSL traffic, and all

connections via the port re4uire authentication. But you were able to

select non=secure protocol as !dministration 7rotocol from the!dministration 'onsole.

&his problem has been resolved. :ow non=secure protocols are notavailable on the !dministration 'onsole.

9

.

2$

72

9

.

2$

7+

Apache Beehive SupportChange

Request

Number

Description and Workaround or Solution Foun

d In

Fixe

d In

'(2)9

)5

:etui databinding expression language fails when Bean#nfo

overrides avaBean property names.

valuation of expressions in the :etui databinding expressionlanguage throws errors when Bean#nfo netui databinding Ldoes not to wor8 when @ava.beans.Bean#nfo is used to override

avaBean property names.


/o not override avaBean property names using Bean#nfo if youuse a avaBean in :etui databinding. #f you must databind to

9.) 9.2


21/138

such a bean, wrap the bean in a # version of the bean thatfollows the avaBean property naming convention.

'(225-

29

&he service control generator does not support implicitly

wrapped WS/L types.

#n the 0. release of WebLogic Server, service controls

generated from wrapped style WS/Ls hid the wrapping detailsfrom the user, resulting in implicitly wrapped types.

#n WebLogic Server 9.) and 9., implicitly wrapped types arenot supported, that is, the generated control does not hide that

parameters are wrapped when the service is called.

9.) 9.2

'(2+-995

&he application.xml file containedin "1AM1weblogic%common8eplo3able-

librariesweblogic-beehive-#.%.earhas whitespacesbefore the xml declaration and causes errors when parsed with

the 3erces 3$L parser.

7Gxml version=G#.%G enco8ing=G'!


22/138

ar!asE cannot be foun8


!dd the following line to the !nt build script"

7propert3 name=2controls.jars.prop2refi8=2controls.8epen8enc3.path29

after importing weblogic-beehive-

imports.xmland weblogic-beehive-tools.xml, but before

importing weblogic-beehive-buil8mo8ules.xml. 1or

example"

7import file=2IJbeehive.homeKweblogic-beehiveantweblogic-beehive-imports.xml297import file=2IJbeehive.homeKweblogic-beehiveantweblogic-beehive-tools.xml29

7propert3 name=2controls.jars.prop2refi8=2controls.8epen8enc3.path297import file=2IJbeehive.homeKweblogic-beehiveantweblogic-beehive-buil8mo8ules.xml29

'(+-)

2+

!pache 2.2 plug=ins


23/138

Pdependency

Pdeclaration

Pdynamic

'(2**)92 &he application descriptors application.xml, weblogic-

application.xml, and weblogic-extension.xmlwere not

validated.

#f an invalid application descriptor is used in WebLogicServer 9.2 it brea8s even if it wor8ed in WebLogic Server

9.) and 9.. &he wor8around was to modify the application

code to use a valid descriptor.

9.2 9.2

'(2*9-+9 #n /&/=based B deployment descriptors, the GCG character

is permitted in the B name, but when these descriptorswere upgraded to schema=based deployment descriptors, it

used to cause failure. &hat is because schema=based Bdeployment descriptors were not permitting the GCG

character in the B name.

&his problem has been resolved. &he GCG character in an Bname in schema=based B deployment descriptors.

9.2 9.2

$7

ConnectorChange

Request

Number


d In

Fixed

In

'(2-)-

-

&he //'onverter fails to convert (!( deployment descriptors

created with WebLogic Server 0. to deployment descriptorscompatible with WebLogic Server 9.x. &he symptom for the

user showed up as an inactive-connection-timeout-

secon8selement in the descriptor. #t should have been simply

ignored because it no longer applies when a .) adapter isconverted to ..


9.) 9.2


24/138

&he inactive-connection-timeout-secon8selement is now

ignored.

'(25)2+

9

&he Debugflag used for profiling (! connection pools was

always set to true with no provision to turn it off. &his causeda lot of clutter in the log > event files.


7rofiling is disabled by default. &o enable profiling, use the

following system property"

-Dweblogic.connector.Connection5ool5rofiling1nable8=true

9.2 9.2

'(250++

&he (esource !dapter container, to function correctly, used totrac8 connection instances created to each of the managedconnections for internal use. ;owever, a few connection

instances were lea8ing due to a timing issue betweenthe close>and the finali6ation of these instances.


9. 9.2$7

'(20*+

When 2 deployment descriptors included Esecurity=permission=spec% using custom Security7ermission classes,

which were pac8aged as part of the 2 archive, WebLogic

Server raises a 'lass:ot1oundxception.


9.2 9.2$7

'(255)

When multiple threads modified the data member of aWebLogic 'onnector

'onnection7ool, ConcurrentMo8ification1xceptionwas

raised.


9. 9.2$7

2

Core ServerChange Description and Workaround or Solution Foun Fixe


25/138

Request

Number

d In d In

'(2-0-

)-

/epending on the timing, during the service migration, the

persistent store associated with the $S server may get closed

before a clean shutdown record is written. #f this occurs, a7ersistentStore exception is thrown during $S Service

migration.


9. 9.2

'(2*2)0

Wor8 $anagers created from a domainMs configuration file


26/138

+5 Byte!rray/iff ob@ect larger than )* bytes, only )* byteswere receivedN bytes in excess of )* were not received. &his

caused a 'ollocated(emote(efxception in some casesN forexample, when a replicated S1SB was used.


$7

'(2*90-*

Soc8ets opened through an !!5'rlConnectionor soc8ets that

were part of health chec8s were getting stuc8

in C0+1:A!state. &hose soc8ets also used to incur memory

lea8s in the ava heap of the $anaged Servers. &he impact of

this memory lea8 varied depending on the soc8etimplementation of the operating system and $.


9. 9.2

'(255--

WebLogic ServerGs ##A7C'A(B! implementation was generatingthe wrong repository #/ for @ava.lang.StringQR.


9. 9.2$7

'(25-909

! ClassCast1xceptionwas being raised and connection used

to fail from the W&' service to an B deployed as a different

application, in a different !(.


9. 9.2$7

'(2595

5

/efining a custom, global Wor8 $anager, with the name

G8efaultG, would not override the system=wide default Wor8

$anagerN it used to cause run=time $Bean registration errors.

&his problem has been resolved. ! custom, global Wor8$anager can now be defined, which overrides the predefined

default Wor8 $anager.

9. 9.2

$7

'(2590-*

! ;ull5ointer1xceptionused to be raised

by javax.rmi.5ortable&emotebject.narrow> when a thin

client tried to access Bs deployed with version information.

&his problem has been resolved. ersion information is now

encoded in such a manner that this problem does not occur.

9. 9.2$7

'(20--*

Sharing (oot7A! was causing a problem because it isdeactivated during application shutdownN the (oot7A! cannot

9. 9.2$7


27/138

be reused because it is in #:!' state.


'(29*20 (outer information in the clientGs ($ was getting corrupted.&herefore, $S was unable to establish connection afterrestarting.

&his problem has been resolved. (outer information in theclientGs ($ is updated correctly.

9.2 9.2$7

'(29*50

sing SunGs ;&&7 handler was causing a 'lass'astxception.

&his problem has been resolved. sing SunGs ;&&7 handler nolonger causes a 'lass'astxception.

9.2 9.2$7

'(+))9

--

!utomatic migration of Singleton services from a WebLogic

Server instance ta8es +) seconds when the graceful


28/138

'(2592))

Scripts install+vc.cm8and uninstall+vc.cm8were not

available with WebLogic Server 9.2 $7 release.

&his problem has been resolved by adding these scripts toWebLogic Server 9.2 $72 installation.

9.2$7

9.2$7

2

'(+)+

0+

'(29++-

'(+2+-

5*

'(++09-

'(+5*

9+

&he WebLogic :# layer was not

raising utofMemor31xceptionto the ava layer when it failed

to allocate memory. &his resulted in core dump.


9. 9.2

$72

'(+)*0

When !dministration ServerMs Listen !ddress was left blan8,WebLogic Server 9.2 used to listen only to the physical #7 and it

was unable to be accessed by other alias #7.


9.2 9.2$7

2

'(+)59) &he cluster messaging receiver that receives and dispatchesmulticast messages was using the WebLogic Server thread pool.&he receiver never released the thread and continued to use it

forever. &his is the expected behavior but the thread wasreported as hogging.


&he cluster messaging receiver has been moved to its own

dedicated daemon thread outside of the thread pool to preventthe reporting of the hogging thread.

9. 9.2$72

'(+)-)

M++ession.execute>ConMessagethreads were getting stuc8and being logged.


9.2$7

9.2$72

'(+)9

0*

!pplying patches for '(+)59) and '(2592)5 used to get

conflicting results in MulticastManager.java.

9. 9.2

$7


29/138

&his problem has been resolved by creating a combo patch for'(+)59) and '(2592)5.

2

'(+9

0+

nsynchroni6ed ;ash$ap resulted in stuc8 threads and high

'7 usage.


9.2 9.2

$72

'(+0)

+

!n error used to occur while adding 1/ to poll.


9.2 9.2

$72

'(+*+

+

'alling a remote B by ##A7 with

transaction, weblogic.corba.cos.transactions.Coor8inator

mplused to result in a memory lea8 on the client=side server.


9.2 9.2

$72

'(+2-529

'(+++55-

'(+--

;ull5ointer1xceptionused to occur during ;&&7 Session

State (eplication under load.


9.2$7

9.2$7

+

'(+22

00

'(+-0*

When a startup class performed :/# loo8up for B in a

deployed application,the A8minMo8ean8ler.checE0ooEup>method used to fail.


9. 9.2

$7+

'(+-*00

&he SSL soc8et was not getting closed when SSL close theconnection.


9.2 9.2$7

+

'(++)-25

'(+-9-+)

&he !dministration 'onsole used to hang when a remote$anaged Server was restarted.


9.2 9.2$7

+


30/138

'(+-*++

'ancelling #CA for 7ollSoc8et$uxer resulted in utf

Memor3exception.


9.2$7

9.2$7

+

'(+

9

! memory lea8 used to occur in 7ermKen space after modules

were undeployed.


9.2

$7

9.2

$7

+

'(+2*52)

! failure in heartbeat trigger for ($ used to occur whenoutbound channel was configured with t+ protocol.

&his problem has been resolved. :ow outbound channels arepreferred over the default channel.

9.2 9.2$7

+

'(++

0

&rigger used to close the reused soc8et prematurely and this

resulted in +ocEet1xception.


9.2 9.2

$7+

'(+2

50

While starting $anaged Servers in a domain where domain wide

administration port is enabled, ;ull5ointer1xceptionis

observed in the !dminServer log.

9.2

$7+

DeploymentChange

Request

Number

Description and Workaround or Solution Found

In

Fixed

In

'()*5)05 &he securit3-permissionelement is available in

the weblogic.xmland weblogic-ejb-jar.xmldeployment

descriptors, but is not available in theweblogic-

application.xmldescriptor. &herefore, in an nterprise

application, you can only apply security policies to !( files

that are Bs or Web applications.

5.)

'()5+0 &he weblogic.Deplo3ertool interprets any extra string 5.)


31/138

values between command=line arguments as a filespecification. 1or example, if you enter the command"

java weblogic.Deplo3er -activate -nostage true-name m3name -source c@Hm3appHm3mo8ule

the tool attempts to activate a file specification namedItrueJ, because the -nostageoption ta8es no arguments

and ItrueJ is an extraneous string value.

'(20-) When you use wlconfig !nt tas8 for configuring a newapplication, the source path entry was incorrectly updated

in the !dmin serverGs configuration file. &his used to causefailure in application deployment.


9.) 9.2

'(29555 WebLogic Server 9. was not bac8ward compliant withWebLogic Server 0. weblogic./eployer tool.


9. 9.2

'(2*299 /eployment service messages between servers in the samedomain were authenticated every time when they were

sent and hence it degrades server performance.


Servers in the same domain now use S!L& authentication.

9. 9.2

'()9)2) #f you deploy an application to a cluster and one or moreclustered servers are unavailable


32/138


&he !dmin$ode on Wor8'ontext for callbac8s is

now set in the "A+CD150LM1;!A;D01&.

&he Web !pplication contains now fires the listener

as the Deplo3mentnitiatoruser and not

as Anon3mous.

#f a custom classloader is used, its parent

classloader is chec8ed to determine whether or not it

is a generic classloader. #f the parent class is ageneric classloader, then the application name is

extracted from the parent classloader.

'(250**) !pplications can contain descriptor files that extend the

descriptors supported by WebLogic Server. &hese descriptorextensions are defined by a weblogic-

extensions.xmlfile, either in an application itself or by a

library module that an application references. &hesedescriptor extensions reference ava factory classes,

providers, and schema urls that must be available to the!dministration 'onsole as a console user navigates through

an applicationMs descriptors, deployment plan, andconfiguration. #f these extension classes are not found in

the server classpath, then assertion errors will beencountered by the console and displayed to the console

user. $ore detailed exception information will be recordedin the server logs.


WebLogic Wor8shop and WebLogic 7ortal applications

fre4uently ma8e use of these descriptor extensions tosupport their configuration. &hese descriptor extensions are

defined by libraries that are normally included in domainsthat support WebLogic 7ortal. &herefore, it is important

that these libraries are also available on the administrationserver so that they are available to the console.

9.2 9.2

'(25920 Some AS and :1S combinations result in deploymentfailures or configuration updates. xample exception is"

weblogic.management./eploymentxception" !ttempt to

operate GdistributeG on null Basic/eployment$Bean


(un statd


33/138

client that accesses a remote :1S volume.

#f multiple servers that share the same domain root

are started with different user #ds of same group, setthe correct Iumas8J for the server processes so that

a file created by one server can be opened for

readCwrite by other servers without securityexceptions.

'(20*9+* WebLogic Server used to log a large number of redundantmessages regarding config modules


34/138

'(+)*05 !n application in which the web module mapped withdifferent context roots used to fail to deploy.


9.2 9.2$72

'(29090- When starting with $S# mode, $anaged Server used to failto deploy libraries and Deplo3ment1xceptionwas being

raised.


9.2 9.2$72

'(+2)9 WebLogic Server used to create the plan.xmlfile in two

different locations = in system tempfolder and in a folder

under I8omainHconfigH8eplo3ments.

&his problem has been resolved. WebLogic Server nowcreates plan.xmlonly in

the I8omainHconfigH8eplo3mentsfolder.

9.2 9.2

$72

'(+-0* WebLogic Server used to ignore the /eploymentArderattribute specified for a startup class element

in config.xml.

&his problem has been resolved. #f /eploymentArder is

specified, it is used to determine the execution order forstartup classes.

9.2 9.2$72

'(+)59 When the weblogic.deployer utility was used multiple times

to redeploy static files in an application, the applicationstate used to hang in the+!A!1'5DA!151;D;status.


9. 9.2

$7+

'(++9 !n application with a deployment plan was not getting

deployed from a Windows machine remotely to a :#3

machine using the weblogic.deployer utility because thepath was not resolved correctly.


9.2 9.2

$7+

'(+502+ When an application which referred a 2 library wasupdated, the 2 Library Averview page of the

!dministration 'onsole was not displaying the referencebetween the application and the library.

9.2 9.2$7+


35/138


'(++0+ $emory lea8 used to occur in 'lassLoader when using side=by=side deployment.


9.2 9.2$7+

'(+2*9 #f there were multiple session-8escriptorelements in

the plan.xml file, the value of session-8escriptorwas

overwritten with a new value after merging with thedeployment plan.


9.2 9.2$7+

'(+29- &he sample wor8list application exported from Weblogic

Wor8shop could not be deployed using the !dministration'onsole.


9.2

$72

9.2

$7+

'(+229)

'(++*0*)

When the weblogic.deployer utility was used to deploy an

application, the temporary directory that cache theapplication was created in a different location other than

CvarCtmp.


9.2

$7

9.2

$7+

'(++*+ &he configOprevOba8 directory was not deleted after the

deployment. When WebLogic Server instances are rebootedwithout deleting configOprevOba8, some configurations

used to get reverted or removed.


9.2

$7

9.2

$7+

'(+-59 &he weblogic.deployer utility was not using previous

targets when redeploying a newer version of the

application and the deployment used to fail.


9.2

$7

9.2

$7+


36/138

EJBsChange

Request

Number

Description and Workaround or Solution Fou

nd

In

Fixe

d In

'(2+)5*

$onitoring information is not always available for $essage=/rivenBeans.

9.)

9.2

'(2+

9)9

sing automatic table creation to deploy Bs for Sybase results in

every column in every table being non=null. !s a result, if the Bcreate method only ta8es a few of the '$7 fields, creating Bs

fails with the following error"

column 8oes not allow nulls

9.

)

9.

2

'(2+2

5*

&he primary 8ey in an Aracle table is a ';!( but the 4uery field in

the SL table is a !(';!(2.

'hange database schema from ';!( to !(';!(2. sing ';!( as

a primary 8ey is not recommended for the Aracle database.

9.

2

'(2+25*

&he primary 8ey in a Aracle table is ';!( while the 4uery field inan SL statement is a !(';!(2.

Wor8around or Solution"

sers with Aracle databases should not use ';!( as the primary

8ey.

9.2

9.2

'(2++

25

! $essaging 7roxy Service still receives and routes messages after

it has been deleted if the user sends the messages to it.

Workaround"

/o not use the $S destination to which the deleted $essaging7roxy Service was listening.

9.

)

'(2-92+

Because of an issue in the B container, the Wor8 $anagerconfigured for a $essage=/riven Bean was not used in some cases.

!s a result, specific settings on the configured Wor8$anager, suchas a Max!hrea8Constraint, did not ta8e affect.

9.)

9.2


37/138


'(2+5-5

/uring the deletion of an ntity B instance that participates in arelationship with another B instance and if 'ascade /elete is set

to !rue, a;ull5ointer1xceptionwas raised.

&he problem has been resolved.

9.)

9.2

'(2

50+

'(22

*2-

! constraint violation occurred when creating one=to=one related

beans in ejb5ostCreate>.


9.

)

9.

2

'(29

+55

&he internal B deployment logic caused B timers to be removed

when an application was redeployed.


B timers are only removed when an application is explicitly

undeployed or removed.

9.

2

9.

2

'(2*)+99

BKen does not support -noDDenand -88nl3enoptions.


Support was added for the -noDDenand -88nl3enoptions. oumust specify the -88nl3en option for BKen to generate

deployment descriptor files.

9.2

9.2

'(2*)0)

#n a cluster environment, '$7CAne=&o=Ane '$( field returned astale reference of the child bean when cache-between-

transactionswas set to true.


9.

9.2

'(2*

+-2

WebLogic Server does not support an BKen annotation for

the 2entit3-alwa3s-uses-transaction2element.

!n BKen annotation2:eblogicCompatibilit32which has only

anNentit3Alwa3s'ses!ransactionNattribute has been added.

&his attribute allows you to specify whether an entity bean must

always use a transaction.

#n previous releases of WebLogic Server, when an entity bean ran

9.

)

9.

2


38/138

in an unspecified transaction, the B container would create atransaction for the entity bean. #n WebLogic Server 9.2, the B

container no longer creates a transaction when an entity bean runsin an unspecified transaction.

&o disable the new behavior and cause the B container to createa transaction for entity beans that run in unspecified transaction,

set the value of theNentit3Alwa3s'ses!ransactionN attribute

to Constants."ool.!&'1.

'(2*2

9*

#n some scenarios, when deleting a child bean and when the

tags 7enable-batch-operations9and 7or8er-8atabase-

operations9in the [email protected] file are set to false,

WebLogic Server used to raise ptimisticConcurrenc31xception.


9.

9.

2

'(2*

)--

B entitlement policies set using the !dministration 'onsole on

B methods with array parameters did not ta8e effect because ofthe way the entitlement policies were registered with the

underlying security code. &his issue only affected policies set usingthe !dministration 'onsole, and did not affect standard B method

permissions set using ejb-jar.xml.


9.

2

9.

2

'(2*

0

#f a $essage=/riven Bean


39/138


&he pEvalue which is set in the B'ontext should be used instead.

'(25))

! ClassCast1xceptionused to occur when $essage=/riven Beans


40/138

'(2090+0

&he cached classinfo ob@ects for the value ob@ects were not gettinggarbage=collected during redeployment of applications, causing a

'lass'astxception.


9.2

9.2

$7

'(29+

902

'(299

)2

ven with the start=mdbs=with=application flag set to false,

$essage=/riven Beans


41/138

'(+)55-

ntity Bean from the pool was not being initiali6ed before re=use insome scenarios and it used to cause unexpected Bean data.


9.2

9.2

$72

'(209

0)

'lass=level Keneric Bs were not supported in WebLogic

Server 9.2.


9.

2

9.

2$

72

'(292+5

WebLogic Server used to raise 1n8pointActivation1xceptionin

scenarios where endpoint was activated as part of connect call.


9.2

$7

9.2

$72

'(+52

! ;ull5ointer1xceptionwas being raisedin 1ntit3CacheIM&'1lement.remove>.


9.

9.2

$72

'(+2*0*

$/Bs were not able to connect to $S destination after the $Sserver was migrated from one server to another.


9.2

9.2

$72

'(2*-)59

When an inner class was passed as an argument to an B method,such as ejbCreate, the generated code was not converting the

inner class argument to a correct representation.


9.

9.2$

7+

'(200**9

/eadloc8 could happen on multiple entity beans and an exceptionused to raise in

the 1xclusive1ntit3Manager.afterCompletion> method.


9.2

9.2

$7+

'(299

9)

When an B had Aracle'lob as dbms=column=type in the weblogic=

[email protected] file and if you navigated to /eployments %$yntityBean % &esting % 'onsole, the !dministration 'onsole

used to throw an error.


9.

9.

2$

7+


42/138

'(+)92+

&he ejbomePuer3method used to raise ;ull5ointer1xceptionin

the B container.


9.2

9.2

$7+

'(+2-*5*

ach time you stopped and started an $/B that has a durablesubscription to a topic, the client #/ string used to get longer.


9.2

$7

9.2

$7+

'(+++

0)9

&he B=L 4uery that contained parenthesis was wrongly

transformed in the appc=generated ava code.


9.

2

9.

2$

7+

'(++9-5

#nvo8ing an B finder method twice used to causean 1ager0oa8ing1xceptionwhen ager 'aching was enabled.


9.2

$72

9.2

$7+

'(+-9

*-

$S'onnection7oller failed to wor8 for customi6ed decorator

pattern.

&his problem has been resolved. ! systemproperty, weblogic.m8b.M+5rovi8ers.;ee8Continuous5olling ,

has been added. 1or customi6ed $S 7rovider or when another

type of $S 7rovider needs to turn onthe ;ee8Continuous5ollingflag, you can use this property as

follows"

weblogic.m8b.M+5rovi8ers.;ee8Continuous5olling=provi8er#?provi8er$?provi8erB

'ase is ignored for comparison.

9.

2$

7

9.

2$

7+

'(+-50)

'(+-059

While obtaining an B from the Session Bean pool,(emotexceptions were raised and these exceptions were

corrupting the Session Bean pool.


9.2

9.2

$

7+


43/138

ExamplesChange

Request

Number


d In

Fixe

d In

'(9+-

$edical (ecords does not yet use deployment plans. 9.)Bet

a

'(2)09*

&he medrec.wls.config target inS!$7LSO;A$CserverCmedrecCsetupCbuild.xml has a 8nown

issue with respect to security configuration.

9.)Bet

a

'(2+-22

#n the $S ueue example instructions, the 4ueueGscorresponding connection factory instance is referred to

as examplePueue. ;owever, the actual connection factory name in

the xamples server

is weblogic.examples.jms.PueueConnection


44/138

thews8l0ocationattribute of

the Qweblogic.jws.+erviceClientannotation. ou should

not specify this attribute in the client Web Service becauseit is possible that the runtime retrieval of the WS/L file

might not succeed. &o prevent this potential problem, it isbest to not specify the attribute at all so that WebLogic

Server always uses the local WS/L.

&o wor8around this problem, update

the &eliableClientmpl.javaWS file and remove

the ws8l0ocationattribute of

the Q+erviceClientannotation.

!fter you have fixed these two problems, re=compile the

example.

InstallationChange Request

Number

Description and Workaround or Solution Found

In

Fixed

In

'(2++*)9 &he Beehive documentation on the install '/ does notcontain Web Service $anagement information, which

may result in bro8en lin8s.


se the Beehive documentation that is on the install'/ rather than the documentation on the !pache

website.

9.)

J2EEChange

Request

Number


d In

Fixed

In

'(2-* &he context-paramelement was not declared as 9.2 9.2


45/138

configurable, which prevented it from being updated from thedeployment plan.


&he context-paramelement is now mar8ed configurable inthe /escriptor Bean.

'(2-5-5

)

&here was no easy way to access the subdeployments of a

library


46/138


WebLogic Server now chec8s whether the parent class loadedis K'L. #f it is, WebLogic Server extracts the application name

from the parentMs classloader.

'(25+92

9

Web descriptors are generated in the M1!A-;


47/138

displays an error message if the user does not have writepermission.

'(+)+++

&he user was not able to re=deploy Bs individually without

re=deploying the entire application.


9.2 9.2

$72

'(++2+

2

&he startupCshutdown classes registered in weblogic-

application.xmldescriptor file were re4uired to extend from

a WebLogic=specific

class,weblogic.application.Application0ifec3cle0isten

er.


9.2 9.2

$72

'(29*5)

'(+9+5+

! ;ull5ointer1xceptionused to occur when deploying an

application which was using shared libraries and had

Specification=ersion or #mplementation=ersion in itsmanifest.


9.2 9.2$7

+

'(+)00

When running the appc tool using the command line against avery large !( application and if the memory specified was

less than +. KB, anutfMemor31xceptionwould occur.


9.2 9.2$7

+

'(+))

0

&he service control handler annotation used to result

in DuplicateRe3exception during a publish to WebLogic

Server 9.2.


9.2 9.2

$7+

'(+----

ClassCast1xceptionused to occur during cluster

synchroni6ation when custom ob@ects were bound to :/#.


9.2$7

9.2$7

+


48/138

JDBCChange

Request

Number


d In

Fixed

In

'(00--2

&he Aracle &hin /B' driver has not been certified with /H.). #n internal testing, B! has noted test failures with the

/'#$!L data type calls until

the non=standard set batch number is reached.


Aracle=specific code was added in the pool to reset standardbehavior when caching any Aracle driver statement.

9. 9.2

'(2*)2

*

WebLogic Server does not create a cache structure if the

cache is defined to be 6ero=si6ed, but one internal routine

9. 9.2


49/138

refers to the structure without chec8ing for null first.

'(20)-+9

&here is a performance degradation in the WebLogic &ype -/B' /river for Aracle get!sciiStream


50/138

vendors.


B! continues to recommend that the /B be highly available,

as the availability of the Singleton Servers directly dependson the availability of the database.

'(2*-5+2

&he +. version of the B!=branded driver from /ata/irectwas updated from version +..))+ to version +..))+0.

9.2 9.2

'(+))55

Averloaded state missing from the /B' /ata Sources$onitoring" Statistics 'onsole ;elp page and

the D"CData+ource&untimeM"eanof the WebLogic Server

$Bean (eference.

Averloaded = all resources in pool are in use.

9.) ).)

'(+)-950

&he /B2 driver used to return an error when a callablestatement execute stored procedure to retrieve BLAB

images.


0.S7

9.2$72

'(+)0++)

#f the user of the operating system that runs WebLogic didnot have permission to write to the default temporary

directory defined by $, the /B' driver used toraise 1mpt3+tacE1xception.


9.2 9.2$72

'(+2++

$ulti/ataSources were all being treated as participating intransactions even if individual /ataSources they contained

were not.


9.2 9.2$72

'(+0

&he manifest in weblogic.jarused to fail to list Sybase@'onnect *.)


51/138

incorrect. ven if there were no connections waiting, Waiting1or 'onnection Success &otal count used to be increased.


$7 $72

'(+--5

/B' connection lea8 was not detected if all statements wereclosed but the connection was not released.


9.2$7

9.2$72

'(+9)

)

&he B!=branded driver from /ata/irect was updated to

version +.*.

9.2

$72

9.2

$72

'(+-9

9

&he B!=branded driver from /ata/irect was updated to

version +.5.

9.2

$7+

9.2

$7+

'(+20+2-

When nitial Capacit3and Maximum Capacit3was not

e4ual, /B' pool used to shrin8 after 9)) seconds even

when +hrinE


52/138


'(++5*59

When you shutdown a /ataSource from the !dministration'onsole, the operation used to fail

with javax.transaction.+3stem1xception. &his behaviorused to occur when using an 3! driver.


se untargetCtarget instead of shutdownCstart operation.


9.2$7

9.2$7+

JMSChan

ge

Requ

est

Num

ber

Description and Workaround or Solution Fo

un

d

In

Fi

xe

d

In

'(2-

909*

&he 7ersistent Store 'onnection runtime statistics was incorrectlyreporting a negative ob@ect count after recovery.


9.

9.

2

'(2

)00*

&he $S wrappers do not correctly handle cases in which the caller isusing the $S . Message5ro8ucer.sen8>methods.


&he $S wrappers were changed to chec8 the values

of )+en8eror t5ublisherin the sen8>method and then call whicheverone is not null.

9.

)

9.

2

'(

2)

5

&he persistent store in WebLogic Server 9. can encounter a thread=safety

problem in some timing scenarios. &he symptom can


53/138

mpl.next>2.

'(2

29*

&he validation of the targeting of a niform /istributed /estination, aswell as the validation of the list of members of a Weighted /istributed

/estination, is not sufficient to prevent a user from mista8enly targeting a/istributed /estination to more than one cluster


54/138

9- connection creation.


'(2*9

-5

#n WebLogic Server 9.), niform /istributed /estination members werenot migrating properly when their parent $S Server was migrated fromone server to another server.


9.)

9.2

'(

2*5-

++

WebLogic Server 9.x $essage=/riven Beans !7# on a newly created

message causes a $S'lientxception.

&he $S :0Message5ro8ucer forwar8>!7# can only be used on

unmodified received messages.

9

.2

'(

252-

When the path service is associated with a single WebLogic Server

instance in a cluster and that server is down during the upgrade process,the $S client cannot send unit=of=order


55/138

'(25

255*

'(+)

*)-

When using the WebLogic Scripting &ool


56/138

resourceT

Wor8around or solution"

When using multiple $S S!1 client producers, try introducing a small

delay between the creation of each new client.

'(

250*

--

(econnecting transacte8+ession.commit>or transacte8+ession.roll

bacE> calls may throw exceptions more than once when reconnecting.

When a transacted session allows reconnect == that is, when

a :0Connection.get&econnect5olic3>is not none== the first call

to session.commit>orsession.rollbacE>will throw an exception

after the server WL'onnection has reconnected after a failure. &his isexpected behavior. nfortunately, the second call

to.commit> or.rollbacE>may also throw an exception.

!fterwards the reconnected transacted session will wor8 normally.

9

.2

'(

2509

*)

&here is no support for multi=byte characters in WebLogic Store file and

directory names. 1or instance, when the WebLogic Server name has multi=byte characters, the default store cannot be created, and the WebLogic

Server will not boot.


'reate WebLogic Servers without multi=byte characters in the path nameand use that path name rather than the default store. /o not use multi=

byte characters in the Weblogic Server name.

9

.2

'(25

99*

M++ession5ool!esterre4uires temporary destinations to test and

validate pooled connections used by $S wrappers. &he exception listener

on the pooled connections is created by the M++ession5ool!ester@ it

was not getting created if temporary destinations were disabled.

&his problem has been resolved. $S wrapper pooled connections utili6e a

connection exception listener even when temporary destinations on the

$S

Server hosting the connections have been disabled. &his allows proper

clean=up of pooled connections even when the session pool tester hasbeen disabled.

:ote that this resolution wor8s only for $S providers thattrigger on1xceptionon a connection failure even when an asynchronous

receiver is not running. #f the onxception is not triggered on connectionfailure then the pooled connections will not be properly closed unless the

9.

9.

2

$

7


57/138

$S Session

7ool &ester for wrapped connections is active. &he $S Session 7ool &esteris automatically created on wrapped connections as long as temporary

destinations have not been disabled on the $S server.

'(

20))

-

When the :0Connection.get&econnect5olic3>method is set to all,

$S C01;!ACR;:01D1sessions may sometimes throw an

extra0ost+erver1xceptionwhen session.acEnowle8ge>is called. &his

occurs after the $S session has been reconnected to the server.

9

.2

'(20

))*-

/eploying $S standalone application modules to a cluster using the!dministration 'onsole succeed, but no subdeployments are targeted.


1or WebLogic Server 9.2, you must either"

se the !dministration 'onsole to target the $S standalone

application module at a single server instance, then reopen the

module and configure the targetting for individual subdeployments.

se the weblogic./eployer tool to target the $S standalone

application module.

9.

2

9.

2

'(

20

))

When the :0Connection.get&econnect5olic3>method is set to all,

$S C01;!ACR;:01D1sessions do not always throw

a 0ost+erver1xceptionwhen session.acEnowle8ge>is called and thereare unac8nowledged, non=persistent topic messages.

9

.

2

'(

2025

2

$essage=/riven Beans and asynchronous bridges listening on secure

WebLogic Server 4ueues were encountering the Isecurity has lapsed forthis consumerJ errors.


9

.

9

.2

$7

'(

20-

-2

$essage=sorting in $S ueue is slow.

&his problem has been resolved. $essage=sorting performance has been

enhanced. ;owever, memory re4uirements for sorted messages mightincrease.

9

.

9

.2

$

7


58/138


59/138

*

'(+

0*

+-


$7

2

'(29

*0

5-

#f there was a delay on the re4uest completion between client and serverdue to an unexpected peeroneor networ8 latency, a temporary halt used

to happen when receiving messages even though the topic property -

Dweblogic.jms.DisableMulti+en8eris set to true.


9.

9.

2

$

72

'(

2950

+0

!ny failure detected by a distributed topic used to stop the forwarder and

would not resume until the $SServer was restarted.


9

.

9

.2

$7

2

'(+)

-)9-

While the compactcommand in WebLogic Store administration tool was

run all non=store files were removed from the file store directory.


9.

9.

2

$72

'(

+)+

5)

#n a Solaris environment, an $/B deployed to a cluster was unable to

connect to a non=distributed topic on a different cluster in the samedomain.


9

.2

9

.2

$

72

'(+)

0)0

#f any of the servers in the receiver domain went down, the store=and=forward


60/138


'(+)

0*0

When sending messages from a WebLogic $S source 4ueue to a third=party $S provider such as Sonic$, the following exception was raised"

javax.jms.M+1xception@ Message 5ropert3 cannot be set b3 aM+ client


9.

2

9.

2

$

72

'(

+)9*

*+

When messages are sent to a destination, which was configured with a

$S 4uota and if that 4uota was met then messages were inadvertentlygetting added to the list of 7ageable messages. &his used to result in a

memory lea8age because the messages were retained on the list of7ageable messages until the server was restarted.


9

.

9

.2

$

7

2

'(+)

9925

! failure used to occur while performing 7aging #CA if many threads werewaiting for 7aging #CA to complete and these threads were bloc8ed.


9.

9.

2

$

72

'(+

)2

When the $S producer was repeatedly created and closed during asession, it used to cause a memory lea8.


9.

2

9.

2

$7

2

'(+

)-)+

&he store=and=forward


61/138

*0 &his problem has been resolved.

$7

$7

2

'(+

20-

$/B thread used to deadloc8at weblogic.messaging.util.Deliver30ist.wait'ntil8le> when

using WebLogic Server 0. &hreading $odel -

Dweblogic.'se(#+t3le1xecutePueues=true .


9.

9.

2

$

72

'(

29

)

++

'reating and closing $S producer or $S consumer on temporary

destinations was resulting in a memory lea8.


9

.

)

9

.

2

$7

2

'(+)

0)2+

!n error was being raised when $/B deployed on WebLogic Serverattempted to connect to a foreign $S provider using $S . 'onnection

1actory.


9.

2

9.

2

$

7

2

'(

292

+2

$S /B' store was not getting recovered after database failure and re=

connection.


9

.2

9

.2

$7

2

'(

+)*2--

;ull5ointer1xceptionwas being raised during '/S debugging

from weblogic.jms.common.CD+.getDestination;ame> if destination

name was absent in the 1oreign $S server :/# registry.


9

.2

9

.2

$7

2


62/138

'(+

+9)

B$& and non=transacted '$& $/Bs used to stop processing messagesand messages were left in a pending state when &un!ime1xceptionwas

raised from the onMessagemethod.


9.

2

9.

2

$

72

'(

+5-

+-

$/B used to stop processing the message after &untime1xceptionwas

raised in the onMessage>method.


9

.2

$7

9

.2

$7

2

'(++

50-

$essage headers of messages in the server were getting altered after yourestarted the server. &his was happening because the ;amefield of

theM+&epl3!oproperty was nullified when the server was restarted.


9.

2

$

7

9.

2

$

7+

'(

+-)5

$/B was not getting connected to a remote WebLogic Server distributed

4ueue through 1oreign$SServer.


9

.2

$7

2

9

.2

$7

+

'(+2

9++

/eadloc8s were detected in $S when using (oc8it $ build ..)O)*=b).


9.

2

$

7

2

9.

2

$

7

+

'(

+-

0

&here was no option to prevent the delivery counts from being reset when

forwarding messages to a new 4ueue.

&his problem has been resolved by providing a chec8 box named (eset

/elivery 'ount An 1orward in the 'onfiguration % Keneral page for the/istributed and niform /istributed 4ueues.

9

.2

$7

9

.2

$7


63/138

+

'(+

-*2

!utomatic reconnect for asynchronous consumers was not resetting themessage listener and this resulted in the failure of automatic reconnect on

consumers and an increase in the connection counters on continuedretries.


9.

2

$

7

9.

2

$

7+

'(

+22

-

&he S!1 agent sometimes used to stop forwarding messages when any of

the receiving servers was restarted.


9

.2

9

.2

$

7

+

'(+2

09+*

$emory lea8 used to occur in '/S code after continuous redeployment ofan $/B in a two=domain environment.


9.

9.

2

$

7+

'(+2

9*)5

'(

+2*

+

$emory lea8 used to occur in '/S code after connection failure betweenan $/B and a /istributedueue.


9.

9.

2

$7

+

'(++

5202

&he $S wrapper code was not using the supplied initial context factoryfrom a 1oreign$SServer and it was always defaulting to weblogic initial

context.


9.

2

$

72

9.

2

$

7+

'( ClassCast1xceptionused to raise from the compare>method of 9 9


64/138

+++9

2

B$essage'omparator and this resulted in stuc8 messages.


.2

.2

$

7

+

'(+-

+-++

&he $S client was hanging in a $SSessionC$S'onnection deadloc8 onasynchronous consumer disconnect due to a peerone1xception.


9.

2

$

7

9.

2

$

7+

'(

+-+

0)

#t was not possible to deploy an $/B while connecting to a foreign $S

provider through WebLogic Server foreign server resources configured in a$S module.


9

.2

$7

2

9

.2

$7

+

'(+-

-5

&he messaging bridge used to throw ClassCast1xceptionwhen $S .

!7# was used by foreign $S providers whose ueue'onnection1actory

ob@ect did not implement 'onnection1actory.


9.

2

9.

2

$7+

JNDIChange

Request

Number


d In

Fixed

In

'(2**0*

2

When a 1oreign :/# connection between two Weblogic

Server domains in a cluster is attempted, the server in thecalling domain fails to start because the 1oreign :/#

9. 9.2


65/138

$anager service is started prior to cluster services starting.


&he 1oreign :/# $anager service is separated from the

other :/# remote naming services, and a new 1oreign :/#$anager service is started after the cluster is started.

'(2*-5-

$S message consumers will not always reconnect after aservice migration when an

applicationMs :0Connection.get&econnect5olic3>attribute

is set to all. #f the consumers do not get migrated, either an

exception is thrown or on1xceptionwill occur to inform the

application that the consumer is no longer valid.


&he application can refresh the consumer either in theexception handler or through on1xception.

9.2

'(205*-

1oreign :/# provider lin8s were being replicated over thecluster. &his caused :/# lin8s to clash on clustered servers.


9. 9.2$7

JS and ServletChange

Request

Number


d In

Fixe

d In

'(902-9

WebLogic Server needs a way for users to pass in custom ob@ectswhen doing strong authentication.


! new method assert8entit3was added

to weblogic.servlet.securit3.

+ervletAuthenticationso that users can pass in a custom

ob@ect via the AppContextargument for this method.

&he AppContextis passed onto the security providers.#ts the

responsibility of the caller to add the re4uest and response

9.) 9.


66/138

ob@ects to the AppContextif re4uired.

'(200)

&he weblogic.servlet.prox3.eneric5rox3+ervlet class uses

the SSL identity WebLogic Server establishes for its SSL

connections. Because the application programming interfaces

server @i8entifierBK

9. 9.2

'(2-*0

2

When using #SA=2)22=7, encoding characters written

via +ervlet&esponse.getutput+tream>.print> are not

9. 9.

2


67/138

properly encoded.


&he encoder for #SA=2)22=7 maintains internal state which is

not getting flushed. /oing an explicit flush on the encoderresolves the issue.

'(25*2)

#f a Web applicationGs context=root is, redeployment in a

production environment does not wor8 as expected.


9.) 9.2

'(25**-

Some headers are s8ipped during processing of proxy headers.!fter removing an entry from the array list, the counter is not

decremented and WebLogic Server s8ips the entry following the

removed entry.

9.) 9.2

'(255

When in=memory session replication is used during failover thereis a possibility for a session loss.&his session loss happens

because when the primary server goes down, the secondaryserver detects this event and attempts to promote the session to

become primary. ;owever the thread does not have the correct

context classloader and therefore the session is lost.


Set the proper context classloader on the thread.

9. 9.2

'(20)5+

&he xtended Log 1ormat log file is rotated on server startupeven when the 7rotate-log-on-startup9element

in config.xmlis not set.

9.) 9.2

'(2020

When reading sessions from the :0+1&/01!+1++;+table, if

WebLogic Server gets a deseriali6ation exception due to the

version conflict, the old session ob@ect is not removed andcontinues to exist in the database.

9.) 9.2

'(2*)-

+)

#f the :'( charactersUO#%and UO#Bare present in the

xpression Language


68/138

feed as valid characters.

'(2*2+90

Because of the method si6e limit of *-H imposed by the $specification, large S7s with many tag handler calls


69/138


&he bug has been fixed in Sun /H..)O)*.

'(25-229 When the access.log file was rotated, header information wasmissing if ;&&7 logging was set to 1xten8e8.

&his problem has been resolved. ;eader information is now

added to the access.log during log=file rotation if ;&&7 logging is

set to xtended.

9. 9.2$7

'(25-

90

I-)- :ot 1oundJ error used to occur after deploying and starting

a new version of an application or response.enco8e&e8irect'&

9. 9.

2$7


70/138

0>in S7.

&his problem has been resolved. 5ath!rimis applied only

if 5ath5repen8is undefined or 5ath5repen8has been applied to

the (L on the bac8end server while

calling response.enco8e&e8irect'&0url>or response.re8irect'&0url>.

'(20)5

+

S7 compiler does not find boolean accessor methods prefixed

with IisJ when parsing the 7jsp@get5ropert39tag.

&his problem has been resolved. #f a avaBean class contains

boolean accessor methods prefixed with IisJ, the S7 getscompiled successfully when calling the 7jsp@get5ropert39tag

for this boolean property.

9. 9.

2$7

'(20552

/isabling resource=reload=chec8=secs was resultingin 1xception.

&his problem has been resolved. #f the static resource file isrenamed or moved to another location and resource=reload=

chec8=secs is set to = in the deployment descriptor, the browserdisplays the -)- = 7age :ot 1ound error when users attempt to

access this page.

9. 9.2

$7

'(202)

S7 would fail to compile if a scriptlet included two consecutivepercent characters


71/138

:ote that 7jsp-propert3-group9ta8es precedence

over 7servlet-mapping9.

'(20+9

2-

xpression language variables exposed by the &!K3 caused S73

compilation to fail.


9. 9.

2$7

'(200-2

S7 tag file directive, the name=from=attribute variable was notwor8ing with the alias attribute.


9. 9.2

$7

'(20*-

5

ven when url-rewriting-enable8was set to falsein

weblogic.xml, (L (ewriting was not getting disabled.

&his problem has been resolved. #f url-rewriting-enable8is

set to falsein weblogic.xml, it is disabled.

9. 9.

2

$7

'(205)29

WebLogic Server start=up used to fail and raise an exceptionwhen a custom ;&am

Documents

Administration Console