"Companies have gotten comfortable with Linux, and they're scratching their heads and saying, 'The argument for Linux was total cost of ownership and skills, and our developers like it and applications are supporting it,'" says Pierre Fricke, an analyst at D.H. Brown Associates. "Then they start thinking, 'What about this thing called JBoss. Doesn't it offer some of the same things?' And it does."

Network World Fusion article, Open source products grab corporate attention, explains why National Leisure Group moved their J2EE infrastructure from BEA Weblogic to JBoss. The broader Open Source topic is discussed with some interesting insights into corporate backing as well as appropriate cautions....

A recent article in CIO Magazine, raises a valid point about the communicated purpose of Enterprise Architecture. Enterprise Architecture can be an overwhelmingly complex undertaking if approached comprehensively from the top down. In order to avoid getting lost in the matrix of the Zachman Framework, EA should be attached to solving business problems, and according to GM CTO Tony Scott, business peers shouldn't even know its called "enterprise architecture".

The goal of EA is to Reduce Complexity, not increase it. EA is described simply as the mapping of business requirements and processes to IT systems which support them. But its not a technology platform, or a one time mapping. It is a discipline. We don't sell disciplines, we practice them.

The EA discipline is practiced when key problem areas, inefficient processes, legacy systems, those things which can no longer be directly connected with the business need are re-evaluated. The goal is to provide agility, reduce complexity, so that the organization can "change the business rules" when need dictates without reinventing the IT systems that support them.

Often IT is viewed as slowing down the advancement of the organization, rather than enabling it. Strategic alignment has been thwarted by the increasing complexity of ad hoc computing solutions. IT is too busy just keeping the plethora of individual PC's, components, and nich products running. It seems like products are always being added, never removed. Clearly re-alignment is necessary, discipline is the key.

It appears as though more of the industry is waking up to Presence Being the Killer App. With Jabber Inc. being a leader in this space. Jabber, Inc., which develops real-time communication server platforms for developing IM and presence-enabled applications, is fashioning its XCP platform into an application server of sorts not only for presence, but also for messaging, routing and XML-application development. In September, it will release a publish-and-subscribe technology called Information Broker for pushing content out to users.

Interesting too, is the increase in adoption of Enterprise IM (EIM) and consequent integration of presence in business applications. A recent Osterman Research study shows 44% of companies use IM with business applications, up from 21% just three years ago. Furthermore, 34% of users have standardized on an internally run IM platform, up from 24% just two years ago.

Jabber Inc. is has announced new versions of its commercial Jabber server and client.

About the same time as students came back to campus this year, I noticed that my internet connection speed was extremely slow on my gentoo linux notebook. Some websites wouldn't load, and ftp and http downloads never exceded 5KB/s and often were in a measurement not often seen anymore, bits/s. I thought, I know this is a heavy usage period on campus, but this is rediculous.

Well, after our network administrator reported that utilization was was not maxed on our campus partial ds3, I thought perhaps it was a router issue. I started trying different locations, other hosts on campus did not have this problem. I switched to wired, same problem. When others in the building also running linux, were not having the problem I began to suspect by box. But I get full speed at home? Whats the problem?

I did a dslreports speed test which came out rather bizarre, 3434 kbps up and 36 kbps down. :-? Thats two T1's upload speed and a pre 56K modem download speed folks. To which dslreports stated "Your upload speed is much faster than down.. have you tweaked?"

Since the problem was occuring regardless of interface, I began to suspect my kernel. I rebooted with an older 2.6.7 and whamo, the same file that was downloading at 5K/s completed at 200K/s. After the latest gentoo development-sources linux-2.6.8.1, didn't solve the problem I decided to google and found the answer.

The recent 2.6.8 kernels have enabled TCP Window Scaling by default. Window Scaling has been a technique used by cat burglars and the IETF since 1992, see RFC 1323. Basically, it allows for the dynamic setting of tcp window sizes beyond their early fixed limit of 64K to increase performance on the Internet with modern equipment. So why doesn't it work with Linux? Well the problem is not with Linux at all, other than the fact that they turned it on by default. Apparently many routers and packet firewalls are rewriting the window scaling factor during a transmission, instead of only during the initial handshake (SYN). This means that the sending and receiving side are assuming a different TCP window size. The result of this misnegotiation of protocol, is very slow successful traffic if at all.

This also explains why the problem is visible on some sending and receiving sites, because only devices behind the path of broken routers are affected. For instance, why my notebook worked fine from my house, or why I was able to get to some sites from on campus at full speed. Also apparently some routers are only mangling in one direction, which would explain that crazy speed test above.

The solution? Well, some of the linux developers are hoping that leaving the option enabled will force the issue, so that vendors will fix their routers. As for me, I was able to follow David S. Miller's suggestion to turn off the feature dynamically in the kernel.

The following command will disable the win scaling feature for the running kernel:

sysctl -w net.ipv4.tcp_default_win_scale=0

And the following command will make sure it gets set next reboot:

echo "net.ipv4.tcp_default_win_scale=0" >> /etc/sysctl.conf

In case you hadn't picked up on it, this is not a gentoo specific issue. Redhat fedora users, you might be affected as well, along with any other distribution using the recent stock 2.6.8 kernels. This LWN article is the only press I have seen about the problem. For a more complete discussion of the topic, here's the start of the thread on the Linux Kernel Mailing List. It would be nice if someone had a complete list of affected routers, some have mentioned openbsd and cisco.