PK45366: WITH CONTROL_REGION_DREG_ON_NO_SRS=1ÿSET, THE MESSAGE 'BBOO0257IÿCURRENTÿEJBÿREQUESTS' VALUE MAY B | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description With a test run using 'control_region_dreg_on_no_srs=1'set, the message 'BBOO0257ICURRENTEJBREQUESTS' value was incorrect. Here's the test scenario: 1.control_region_dreg_on_no_srs=1isset. 2.run8EJBrequestsviaIIOPorServlet. EJBonlytoissuesleep. 3.outputofDISPLAYWORKcommandisasfollows FKY01,DISPLAY,WORK,ALL BBOO0255ITIMEOFLASTWORKDISPLAYFriNov2411:09:582006 BBOO0256ITOTALEJBREQUESTS16(DELTA4) BBOO0257ICURRENTEJBREQUESTS8 BBOO0258IEJBREQUESTSINDISPATCH6 BBOO0267ITOTALEJBTIMEOUTS0(DELTA0) <<thenumberofworkerthreadsis6,soEJBrequestsin dispatch shows 6, despite that the number of total EJB requests is 8. Thatmean2requestswereoutstanding>> 4.When CANCELing theServantregionbyMVScancelcommand, the followingerrormesssagewasissuedduetoSRabend org.omg.CORBA.INTERNAL:vmcid:0xc9c21000minorcode:123 completed:No 5.BBOO0299Iwasissuedbecause control_region_dreg_on_no_srs=1is set. <<BBOO0299ISERVERxyzHASNOSERVANTS. WORKISBEINGREJECTED.>> 6.BBOO0300IwasissuedwhenSRwasrecycled. <<BBOO0300ISERVERxyzHASDETECTEDSERVANT(S). WORKISNOLONGERBEINGREJECTED.>> 7.AfterrecyclingSR,the DISPLAYWORKcommandshowsEJBREQUESTSIN DISPATCHbeing2. FKY01,DISPLAY,WORK,EJB BBOO0255ITIMEOFLASTWORKDISPLAYFriNov2411:11:162006 BBOO0256ITOTALEJBREQUESTS16(DELTA0) BBOO0257ICURRENTEJBREQUESTS2 BBOO0258IEJBREQUESTSINDISPATCH0 BBOO0267ITOTALEJBTIMEOUTS0(DELTA0) <<TherewerenoEnclavebecauseofSRrecycle.So,EJB REQUESTSIN DISPATCH shouldbe0,butitshows2,whichisthesamenumber as outstandingrequestsatstep3.Inthemeantime,thenumber ofSR is 1. >>Local fix This is a very rare condition error, and it has no impact on the healthy function of the server. Thus this apar is marked as FIN.Problem summary **************************************************************** * USERS AFFECTED: All users of Websphere Application Server * * V6.1.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The work counts displayed by the * * "f <server>,display,work" command may * * include incorrect values. The count * * displayed in the BBOO0257I message may * * * * be larger than the actual number of * * requests. Also, the "DELTA" value, in * * message BBOO0267I, may be larger then * * the actual number of timeouts. * **************************************************************** * RECOMMENDATION: * **************************************************************** The counts kept in the controller for the display work command didn't get decremented when a piece of work was cleaned up while on the WLM queue (perhaps from a timeout). Also, the calculation for the "DELTA" value for message BBOO0267I incorrectly added in the MDB Timeout Request count.Problem conclusion The code for the management of the work counts was corrected to properly decrement in the error scenarios involving Requests cleaned up while currently on the WLM Queue. Also, the calculation for the "DELTA" value for message BBOO0267I was corrected. APAR PK45366 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.11 of WebSphere Application Server V6.1 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Document Information |
Current web document: swg1PK45366.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK45366
IBM Group: Software Group
Modified date: Oct 2, 2007
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.