But maybe that's because one of them was stolen.

That's right, the alleged first Segway theft took place right here in Good ol New York. A New York City college student was caught with it, hanging outside a Queens Starbucks, waiting for a "Segway expert" to show up and help him figure out how to start it. Apparently he was having problems getting it rolling without the key (the expert tipped off the cops). The young scamp says he didn't steal it though -- he bought it from a homeless man for $75.

Right.

Given his interest in Segways, I'm sure he won't mind the "segue" from campus dorm to prison cell. They're both about the same size.

Man, sometimes I just kill myself!

Well, the fixes are not fixing things.

I've been able to confirm with IBM that the specific problem that has cropped up is indemic to WebSphere 3.5 and 4.0.1.

WebSphere 5.0 does not have this problem, so we'll be migrating as soon as possible to WAS 5.0. I've been playing with WebSphere Studio and running our code base on a test 5.0 server with success, so I don't foresee any huge issues.

Stay tuned to see if I'm psychic or not.

The site v4.windowsupdate.microsoft.com is running Microsoft-IIS/6.0 on Linux .

"One strategy for cushioning the blow was to extinguish the Windowsupdate.com. We have no plans to ever restore that to be an active site."

Well, it's still freaky.

So now we're using WebSphere's clustering to see if we can keep consistently alive.

What a week.

• Blackout CameraPhone Blog -- because someone had to do it.
• Car Ships Collide at Sea -- somehow it was inevitable
• Amazon Light v2.0 beta -- 5 mill items...on one page? oh the humanity!
• SCO posts profit from Linux licensing? -- Proving Nietzsche's point.

I just had to laugh at your "Top 11 Signs times are tough in your IT department." Specifically, item # 4, because, uhmm, that's the reality where I work (Nevada Dept. of Corrections). We just got rid of the last ARCnet segment a couple of months ago. What keeps me going? The fact that we are getting some new things, so I get to work on W2K and Linux.

When WebSphere freaks out, it's because of an exception caused by: com.ibm.ejs.sm.active.ActiveEJBServerProcess.

Apparently it's unable to ping the default server and decides it's time to restart it.

I've got two different machines installed with WebSphere and both exhibit the same behavior. Research on the web shows at least two other people have had this exact same issue crop out of nowhere, one on WAS 3.5 and one on WAS 4.0.2. We're running WAS 4.0.1.

Unfortunately, neither questions have answers.

I've adjusted the ping/default time out settings for both servers and will continue to watch them to see if this solves the problem. One post seemed to indicate that this had worked for them on one server, but not another. We'll see what happens.

Well, I think. The control database in DB2 had tablespaces in an inconsistent state. A shutdown and reboot caused it to sync up and it's happy again. For now.

Time to do some reading and figure out why DB2 is not happy. So we're up.

For now.

Or maybe Bruce's testing broke it. Or maybe a network gremlin came along and decided to be mean and break it cause they thought we needed even more excitement.

Regardless of who's to blame, NWC Inc. is broken. Not everything, just the app server. It's been acting weird for a while and we haven't been able to diagnose the problem. I started a fresh install on a nice shiny clean OS and guess what - same error. Apparently I need to tell WebSphere to pretend that the local DB2 database used as a repository is a remote instance, otherwise no more than 10 connections to the database can be made.

That sounds funky, but that's what the error represents, according to IBM's web site.

Unfortunately, following the directions to fix it isn't working either.

So while I'm trying to figure it out, NWC Inc. transactions aren't working. The web services are working, but nothing that involves WebSphere is working right.

I have forever had problems getting a TCP/IP connection to DB2 to work correctly. It just never works so I've been using named pipes for remote connectivity.

Today I was configuring remote access to DB2 for some product testing and happened to notice that there was an extra 0 in the TCP/IP port.

Instead of 5000, it was running on 50,000. Gee, when you use the right port, things work better.

If you've seen visited our Axis Network Camera lately you may notice that we've cleaned up a bit. We had visitors to NWC Inc. to show off what we've been doing and, of course, had to make things look nice for our auspicious guests.

Steven's finally finished with his last big review and we've had our lab rat shipping out products for a week. Now that Steve has some time, he's been working on our NAS and getting our automated backup systems in place.

The scary part - testing those backups - is still to come....

Kuwan.net SCO Anti Protest

• Reviews--Evaluate products with our sneak previews and head-to-head comparisons.
• Know-How--Learn how to manage your network with tutorials, primers, training materials and the like.
• Talk--Read and respond to editor opinions, blog posts and forum entries.
• Technologies--Find all content according to technologies like wireless, security, infrastructure, etc.

Each summer, our crack team of editors sojourns across the globe in search of a faraway destination, where they can put their collective brain cells to the task of setting down our editorial calendar for the following year. This time, our editors found their way north to the sunny town of Syracuse, New York. Here are a few photos cataloging their efforts.

	While Bruce Boardman is busy downloading new ring tones, Mike DeMaria works on his laptop monitor rotation resistance test.
	Peter Morrissey, obviously cheating off of Dave Molta's unprotected laptop as Rob Preston (standing) and Kevin Cooke investigate strange sounds coming from beneath the table.
	Lorna Garey, prepping for the afternoon session.
	This is what happens when someone forgets to bring the wireless access point.

If you don't know who these folks are, just check out our Masthead, where you can find short bios and hopefully more flatting photos.

It's a sure fire bet that everyone who gets this annoying email promptly relegates it to their trash bin, right? Right?

Wrong.

This may come as a shock, but there's a large number of people replying to this type of email, and ORDERING the pills that it offers -- despite the fact that there is no real company information, let alone any standard security encryption for protecting their credit card information.

Read more about this at Wired.

But bottom line, this is probably proof positive that the SPAM business is not going to go out of business anytime soon.

More and more people are dumping their regular phones in favor of going cellular full time. In fact, the number of folks saying bye bye to ATT, MCI, Verizon et al has reached somewhere around 7.5 million.

Continue reading "Cutting the Cord"

Posted here at 11:50 AM in

Comment on this blog entry

Posted here at 11:54 PM in

Comment on this blog entry