Presentation is loading. Please wait.

Presentation is loading. Please wait.

B7: Caring for an Ailing AppServer™

Similar presentations


Presentation on theme: "B7: Caring for an Ailing AppServer™"— Presentation transcript:

1 B7: Caring for an Ailing AppServer™
Diego Canziani Senior Technical Support Engineer

2 Agenda Anatomy of the AppServer Diagnosing Problems
Help Treating your AppServer AppServer Broker Agent client Listening Port Cl ients Agents

3 Anatomy of the AppServer
What is the OpenEdge® AppServer?

4 Anatomy of the AppServer
Or What is the Progress® AppServer? Broker JavaTM process Handles communication from clients to agents Manages client and agent pools Writes to <brokername>.broker.log <brokername>.broker.log

5 Anatomy of the AppServer
Or What is the Progress AppServer? Agent “C” process Handles requests and replies to the clients Communicates “STATUS” to broker Writes to <brokername>.server.log <brokername>.server.log

6 Anatomy of the AppServer
4 Operating Modes State-aware State-reset Stateless State-free One to one - Default Many to few

7 Anatomy of the AppServer
2 Connection Models Client to Broker gets redirected to Agent State-aware State-reset Client to Agent through the Broker Stateless State-free

8 Anatomy of the AppServer
2 Connection Models State-aware State-reset 2 Connection Models Stateless State-free Agent Agent Agent Agent client AppServer Broker Agent

9 Anatomy of the AppServer
AppServer Broker Thread Pools Listening Thread L-3090 Client Threads C-0001 C-0002 C-0003 C-0004 C-0005 C-0006 AppServer Broker Server Threads S-0001 S-0002 S-0003 S-0004 S-0005

10 Anatomy of the AppServer
Broker communication with Agents Broker starts agent and waits for agent to respond, status set to: STARTING Once started the agent reports to broker and broker sets status to: AVAILABLE Client request agent, is redirected to agent port, broker sets status to: CONNECTING Client connects to agent, agent reports to broker, broker sets status to: CONNECTED Agent completes request, notifies broker, broker sets status to:

11 Anatomy of the AppServer
Reading Log Files P T AS AS P T AS AS Application Server connected with connection id: ::asbroker1::3090::b0d80cae72::1191a17d1f0:-7ffc. (8358) P T AS 4GLTRACE Run performCardAuth "John Doe Visa -H localhost -S 6789" [Main Block - authcard.p] P T AS 4GLTRACE Run connectAuthSvc "-H localhost -S 6789 " [performCardAuth - authcard.p] P T AS 4GLTRACE Run createAuthMsg "John Doe Visa " [performCardAuth - authcard.p] P T AS 4GLTRACE Run sendAuthMsg "1000 Name=John Doe;Number= ;Type=Visa " [performCardAuth - authcard.p] P T AS 4GLTRACE Run disconnectAuthSvc "1000" [performCardAuth - authcard.p] P T AS AS Application Server disconnected. (8360) Application Server connected with connection id: : :asbroker1::3090::b0d80cae72::1191a17d1f0:-7ffc. (8358) AS 4GLTRACE Run connectAuthSvc “-H localhost -S 6789” [performCardAuth - authcard.p]

12 Anatomy of the AppServer
Supporting Processes AdminServer - Required JAVA process Manages all OpenEdge Brokers and Servers Writes to admserv.log NameServer - Optional Traffic manager from clients to AppServers Writes to <nameservername>.ns.log

13 Agenda Anatomy of the AppServer Diagnosing Problems
Help Treating your AppServer

14 Diagnosing Problems Startup Problems
$DLC/bin/asbman -name asbroker1 -start OpenEdge Release 10.1C01 as of Fri May 9 21:58:30 EDT 2008 Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280) Searching for asbroker1 (8288) Connecting to asbroker1 (8276) Unable to start asbroker1 (8297)

15 Diagnosing Problems Startup Problems - <brokername>.broker.log
===================================================================== P T-Main /usr1/stat/progress/101c/wrk/asbroker1.broker.log opened. P T-Main Logging level set to =2 P T-Main Log entry types activated: P T-Main 2 UB Basic ubroker version: v101c (07-May-08) (8038) P T-L UB Basic Started listenerthread: L-9090 (8043) P T-L UB Could not listen on port: 9090 (8044) P T-L UB java.net.BindException: Address already in use (errno:226) P T-L UB at java.net.PlainSocketImpl.socketBind(Native Method) P T-L UB at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) P T-L UB at java.net.ServerSocket.bind(ServerSocket.java:325) P T-L UB at java.net.ServerSocket.<init>(ServerSocket.java:186)

16 Diagnosing Problems Startup Problems
$DLC/bin/asbman -name asbroker1 -start Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280) Searching for asbroker1 (8288) Connecting to asbroker1 (8276) Starting asbroker1. Check status. (8296) $DLC/bin/asbman -name asbroker1 -query Broker: asbroker1 not running (8313)

17 Diagnosing Problems Startup Problems - <brokername>.broker.log
P T-S UB Basic Started server: /usr1/stat/progress/101c/dlc/bin/_proapsv -logginglevel 2 -logfile /usr1/stat/progress/101c/wrk/asbroker1.server.log -ubpid 435 -Ms 1 -logname asbroker1 -logentrytypes ASPlumbing,DB.Connects -logthreshold 0 -numlogfiles 3 -ASID 4 –ubpropfile /usr1/stat/progress/101c/dlc/properties/ubroker.properties -svrefresh -ipver IPv4 -db mydatabase (8108) P T-S UB Message from server : Startup Procedure Failed (8113) P T-S UB IOException reading message from server : java.io.EOFException: pipe to server broken (8117) P T-S UB Basic ERROR: cannot start server. (8100)

18 Diagnosing Problems Startup Problems - <brokername>.server.log
P T AS -- ** There is no server active for database mydatabase on -H cruz -S (704) P T AS -- Error initializing the application server. (5479) P T AS AS Application Server Shutdown. (5476) P T AS -- ** There is no server active for database mydatabase on -H cruz -S (704) P T AS -- Error initializing the application server. (5479) P T AS AS Application Server Shutdown. (5476)

19 Diagnosing Problems Startup Problems - <brokername>.server.log
P T AS AS Starting application server for asbroker1. (5560) P T AS AS Application Server Startup. (5473) P T AS -- C:\tmp\ex08\roy\eg1\asstart.r Database sports2000 not connected. (1006) P T AS -- C:\tmp\ex08\roy\eg1\asstart.r startup procedure ended with an ERROR condition. (8025) P T AS AS Application Server Shutdown. (5476)

20 Diagnosing Problems Startup Problems All “INITIAL” agents must start or the AppServer will fail to start Set initial agents to start to zero “initialSrvrInstance=0” in ubroker.properties (IPv6 enabled on a machine can cause agents not to communicate with broker) Add “–Djvmstart.debug=1” to the “jvmargs=“ in AdminServerPlugins.properties View $WRKDIR/jvmStart.log file

21 Diagnosing Problems Phantom Agents Broker Name : asbroker1
Operating Mode : State-reset Broker Status : ACTIVE Broker Port : 3090 Broker PID : 25319 Active Servers : 5 Busy Servers : 0 Locked Servers : 0 Available Servers : 5 Active Clients (now, peak) : (0, 6) Client Queue Depth (cur, max) : (0, 11) Total Requests : 124 Rq Wait (max, avg) : (259 ms, 11 ms) Rq Duration (max, avg) : (5543 ms, 24 ms) PID State Port nRq nRcvd nSent Started Last Change 25320 CONNECTED May 19, :28 May 19, :28 25321 AVAILABLE May 19, :28 May 19, :28 25323 AVAILABLE May 19, :28 May 19, :28 25322 CONNECTED May 19, :28 May 19, :28 25324 AVAILABLE May 19, :28 May 19, :28

22 Diagnosing Problems Phantom Agents protrace.25320 protrace.25322
ps -ef | grep _proapsv statqa :28:47 ? :24 /usr1/stat/progress/101c/dlc/bin/_proapsv -logginglevel 2 -logf statqa :28:46 ? :56 /usr1/stat/progress/101c/dlc/bin/_proapsv -logginglevel 2 -logf statqa :28:45 ? :55 /usr1/stat/progress/101c/dlc/bin/_proapsv -logginglevel 2 –log protrace.25320 protrace.25322

23 Diagnosing Problems Look at log files Increase logging levels
Diagnosing Application problems Look at log files <brokername>.broker.log <brokername>.server.log Database log files where agent is connected Increase logging levels srvrLoggingLevel=4 (extended) srvrLogEntryTypes=4GLTrace UBNet - New for 10.1C

24 Diagnosing Problems Hanging Agents Broker Name : asbroker1
Operating Mode : Stateless Broker Status : ACTIVE Broker Port : 3090 Broker PID : 25319 Active Servers : 1 Busy Servers : 0 Locked Servers : 0 Available Servers : 1 Active Clients (now, peak) : (0, 1) Client Queue Depth (cur, max) : (0, 1) Total Requests : 11 Rq Wait (max, avg) : (11 ms, 11 ms) Rq Duration (max, avg) : (24 ms, 11 ms) PID State Port nRq nRcvd nSent Started Last Change SENDING Apr 4, :40 Apr 4, :41

25 Diagnosing Problems Diagnosing Agent problems
P T AS AS Application Server connected with connection id: ::asbroker1::3090::b0d80cae72::1191a17d1f0:-7ffc. (8358) P T AS 4GLTRACE Run performCardAuth "John Doe Visa -H localhost -S 6789" [Main Block - authcard.p] P T AS 4GLTRACE Run connectAuthSvc "-H localhost -S 6789 " [performCardAuth - authcard.p] P T AS 4GLTRACE Run createAuthMsg "John Doe Visa " [performCardAuth - authcard.p] P T AS 4GLTRACE Run sendAuthMsg "1000 Name=John Doe;Number= ;Type=Visa " [performCardAuth - authcard.p] P T AS 4GLTRACE Run disconnectAuthSvc "1000" [performCardAuth - authcard.p] P T AS AS Application Server disconnected. (8360)

26 Agenda Anatomy of the AppServer Diagnosing Problems
Help Treating your AppServer

27 Help Treating your AppServer
asbman -query Get status and history of AppServer broker and agents -kill Shutdown an AppServer with busy or hanging agents May need to run twice in a row

28 Help Treating your AppServer
LogRead Available on PSDN ABL source code available Read and Sort multiple log files Unsupported

29 Help Treating your AppServer
Database Connections Don’t connect using the startup parameters Any database down to a single database will cause your AppServer agents to be unresponsive Connect using the “CONNECT” call in the srvrStartupProc= srvrConnectProc= srvrActivateProc= Use “IF CONNECTED” ABL

30 Help Treating your AppServer
Lifespan New in 10.1B Described in ubroker.properties.README Read the CAUTION! Use only when directed by Tech Support Periodically force the shutdown of all agents and allow new agents to start when requested

31 Help Treating your AppServer
OpenEdge Management

32 Under Development D I S C L A I M E R
The next slide includes information about potential future products and/or product enhancements. What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here. D I S C L A I M E R

33 Help Treating your AppServer
List AppServer Connections New in 10.2A Described in ubroker.properties.README List of all clients known to the AppServer, includes: Host/IP Port Connected Agent More!

34 Help Treating your AppServer
Help from Progress Technical Support Knowledge Base (kbase) PSDN

35 In Summary Understand your AppServer Diagnose your Problem
Care for your Ailing AppServer AppServer Broker Agent client Listening Port Cl ients Agents

36 ? Questions

37 Thank You

38


Download ppt "B7: Caring for an Ailing AppServer™"

Similar presentations


Ads by Google