Home > Articles > Programming > Windows Programming

This chapter is from the book

SOAP in the Real World

Let's take a case in which a user says she can't run a particular Web applet that she needs for her job. In particular, we'll take a case in which the problem seems to be intermittent—again, those tend to be among the toughest problems. Figure 7.1 shows a logical map of the site; her PC lives at point A on the map.

Figure 7.1 Troubleshooting a time-related problem.

You visit the user's PC and can run the applet just fine. She frowns at you and says, "Well, it doesn't work for me." She tries right after you, and it works, but she reports the problem again the next day. You decide to use SOAP on this one:

S: Web applet does not run when user tries it.
O: Web applet runs when I try it.
A: Perhaps the time of day has something to do with it?
P: Come back during the time she usually tries the applet.

Your analysis of the problem is a good one, and your plan to gather new information works. You visit her when she usually tries her Web applet, and, sure enough, it won't work for you. What's going on? This time through, you're the one supplying the subjective data; it's your guess:

S: I bet that the time of day has something to do with the applet not working.
O: Web applet does not run at 8:00 a.m.
A: Could it be related to another network activity on that segment happening at the same time?
P: Try using a different network segment (point B on the map).

An okay plan, but it doesn't work out, as shown from your notes:

S: Network activity might be different on her segment at 8:00 a.m.
O: Web applet still fails on a different segment.
A: My head hurts. What else could be different at this time of day?
P: Investigate what goes on at 8:00 a.m. on the network as a whole.

She still has problems at 8:00 a.m. on a different network segment. That's fine. You've now ruled out her network segment, and that's very important to do. You've made a deduction, and it's wrong. Don't sweat it.

Is It a Virus, Doc?

After getting a cup of coffee, you briefly think about the possibility of one of those viruses that "go off" at 8:00 a.m. on a certain day, but you dismiss it—you have pretty good virus protection. What's more, you used a different workstation that you're sure is virus free when you tested the different segment. That's a good guess because things like this have happened—even viruses that don't do anything until a certain day at a certain time in the morning can interfere with system operations every day while it checks to see if it's the right day to ruin you.

So, it's back to the drawing board.

Getting a Consultation

This is the crucial part because you're frustrated, and you think you can't possibly solve this problem. It's tempting to give up. Guess what? Pros feel that way, too. The difference, however, is that the successful troubleshooter takes a break and looks at the facts again. Then, much like a doctor, the troubleshooter might "get a consultation" and go right back at it.

Do you have to get a consultation from a pro? Not necessarily. You get a consultation because you're too close to the problem, and you already have preconceptions as to what's going on. Let's say that you ask somebody—anybody—what goes on at 8:00 a.m. every day. The answer is going to be "everybody turns their PCs on" or "everybody gets in to work" or some variation on this. That turns on a lightbulb for you—because everybody is turning their PCs on and logging in at 8:00, might this be the computer equivalent of rush hour on the network?

The answer, of course, is yes, there is a network rush hour. How do you verify this? Well, it's sort of tough. There are two ways:

  • Actual measurement (relatively difficult unless you've already read Hour 23, "Network Management Tools")

  • Changing the situation (moving the workstation to a place where traffic will be quieter)

Even though you've already moved the workstation to a different segment, you hadn't considered that the segment you were moving to might also be problematic. You can think of this as the equivalent of moving from the Long Island Expressway to the Grand Central Parkway—it doesn't do you a lot of good at rush hour. (You've been treating the situation as though there was construction or an accident on one but not the other.) Now, your SOAP looks like this:

S: The problem might be network congestion.
O: The problem occurs at the same time on different major network segments.
A: Login congestion is likely on major segments, but not as likely on a segment with fewer users.
P: Check maps and try the applet on a "low traffic" network segment (perhaps nearer to the Internet segment and away from segments with server login traffic on them).

You deploy your plan: You temporarily set up a workstation at point C on the map. When you try the applet at 8:00, it works. You have now pointed the finger squarely at network congestion. The next question is, whose problem is this? In other words, is this something that the applet vendor is responsible for, or is this your problem for having a network that's too busy?

Your response to this problem might vary. On one hand, it might be practical to move this person to a less busy segment. However, this might not work because you can see from your physical maps that the network segments near PCs tend to have a lot of PCs on them and are smack in the middle of the servers. In other words, physical constraints might prevent you from putting this person on a segment without other PCs because the only hubs near her probably are being used for other users. Note here that if you were using switches that supported VLANs instead of hubs, you could switch her effective segment (the virtual data link domain) without physically moving her workstation—that's what VLANs are for. But in this case, we're dealing with hubs, so no such luck. Worse, we discover that all low-population segments are either in your data center or in another building, outside of her physical reach. (The smart aleck might ask, "Why not ask this person to stop doing her work process at 8:00 in the morning?" Not a great solution—the network is supposed to work, darn it!)

At this point, if you really needed to have this person's workstation stay where it was on the busy segment, you have to start application troubleshooting. Why is it that this person doesn't have any other problems, say, with local applications? As you'll see in Hour 19, "Intranet and Internet Troubleshooting: TCP/IP at Work," comparing a local application to an Internet application isn't a good idea; using Internet applications is like taking an international flight versus hopping in your car to go to the store. A lot of things can happen between here and Paris. You write down your SOAP again:

S: Applet is not working; other applications are.
O: The applet is the only Internet application in the mix.
A: Internet applications are not local applications.
P: Try a different Internet application during peak hours.

You've now done five SOAP lists. Long and tedious, isn't it? Yet, as you can see, SOAP is a powerful process for refining what you know, as well as a way to take guesses and turn them into fact and a way to keep you moving forward.

You try a different Internet application at 8:00 the next morning, and it works like a champ. Even though it doesn't do exactly the same thing, at least you're now comparing apples to apples—that is, a firewall-dependent, wide-area application to another firewall-dependent, wide-area application. You try yet another Internet application, just to make sure, and it, too, works just dandy. Here's your latest SOAP:

S: The application itself seems to be at fault.
O: Only have tried two other Internet applications.
A: Measurement of congestion and delay might help but would still lead to vendor.
P: Contact supplier of the applet and relate all notes that led to this conclusion.

Fortunately, this is not a free applet, and the supplier is eager to make it work for you. The supplier talks you through taking a network trace, and you email it off to him. He responds that you have quite a lot of traffic, but not an unreasonable amount. Because you've gathered a lot of notes and have sent them to him, he has a good idea of what's going on and understands that it's probably his problem. Because he wants you as a customer, before too long, you've got a patched program emailed to your desk, which you install to your user's PC—problem solved.

TIP

In a situation such as this, you want to make sure that you document the problem—either informally (via email to your colleagues) or formally (say, as an addendum to the product documentation in your library). You might write something like this:

10/20/98, JF: Applet has problems running on a busy network, use Patch 1.2, located on the 'Barbarian' server's 'FIXES' share.

Sound crazy? A software supplier fixing something you reported? Not really. Our shop has reported many bugs to suppliers over the years using this procedure with great success. When you follow careful SOAP note-taking procedures, you're likely to convince your technical support people that you have a bona fide problem that needs to be addressed. However, it's even more likely that you'll come up with the answer yourself—which is really the objective.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020