I've gotten in the habit of putting in my web.xml deployment descriptors, even when not deploying into a cluster.

I found some odd behavior when I did this using JBoss 3.0.6 and JBossWeb (i.e. Jetty 4.2.6).

My application ran properly, and negotiated HttpSessions properly (i.e., I saw the jsessionid cookie and my URLs were rewritten with the jsessionid), but my HttpSession didn't persist from request to request.

Attachments don't seem to be working, here's the relevant portion:



600
<!-- NYI
node1
-->


<!--

-->








<!-- Put this back in for distributable support under 'all' configuration


604800
3600
900
UDP(mcast_addr=228.8.8.8;mcast_port=45566;ip_ttl=32;ucast_recv_buf_size=16000;ucast_send_buf_size=16000;mcast_send_buf_size=32000;mcast_recv_buf_size=64000;loopback=true):PING(timeout=2000;num_initial_members=3):MERGE2(min_interval=5000;max_interval=10000):FD_SOCK:VERIFY_SUSPECT(timeout=1500):pbcast.STABLE(desired_avg_gossip=20000):pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800;max_xmit_size=8192):UNICAST(timeout=2000):FRAG(frag_size=8192;down_thread=false;up_thread=false):pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;print_local_addr=true):pbcast.STATE_TRANSFER
DefaultSubCluster
20000
5000
GET_ALL


-->




I saw a few errors in my log:

11:46:25,180 INFO [MainDeployer] Starting deployment of package: file:/C:/Work/jboss-3.0.6/server/tapestry/deploy/vlib.ear
11:46:25,210 INFO [EARDeployer] Init J2EE application: file:/C:/Work/jboss-3.0.6/server/tapestry/deploy/vlib.ear
11:46:25,751 INFO [EjbModule] Creating
11:46:25,781 INFO [EjbModule] Deploying Person
11:46:25,951 INFO [EjbModule] Deploying Book
11:46:25,981 INFO [EjbModule] Deploying Publisher
11:46:26,001 INFO [EjbModule] Deploying KeyAllocator
11:46:26,031 INFO [EjbModule] Deploying BookQuery
11:46:26,101 INFO [EjbModule] Deploying Operations
11:46:26,281 INFO [EjbModule] Created
11:46:26,281 INFO [EjbModule] Starting
11:46:29,075 INFO [Publisher] Table 'PUBLISHER' already exists
11:46:29,346 INFO [Person] Table 'PERSON' already exists
11:46:29,406 INFO [Book] Table 'BOOK' already exists
11:46:29,406 INFO [EjbModule] Started
11:46:29,486 INFO [Manager] cloning Manager: org.mortbay.j2ee.session.Manager@81a197
11:46:29,486 INFO [JBossWebApplicationContext] setDistributableSessionManager org.mortbay.j2ee.session.Manager@7bbfb8
11:46:29,716 INFO [jbossweb] Registered jboss.web:Jetty=0,JBossWebApplicationContext=3,context=/
11:46:30,037 INFO [jbossweb] Extract jar:file:/C:/Work/jboss-3.0.6/server/tapestry/tmp/deploy/server/tapestry/deploy/vlib.ear/26.vlib.ear-contents/vlib.war!/ to C:\DOCUME~1\H
oward\LOCALS~1\Temp\Jetty_0_0_0_0_80__\webapp
11:46:30,558 INFO [JBossWebApplicationContext] setDistributable true
11:46:30,658 INFO [JBossWebApplicationContext#] using Distributable HttpSession Manager: org.mortbay.j2ee.session.Manager@7bbfb8
11:46:30,668 WARN [Manager] No Store. Falling back to a local session implementation - NO HTTPSESSION DISTRIBUTION
11:46:30,678 INFO [jbossweb] Started WebApplicationContext[/,Tapestry Virtual Library Demo]
11:46:30,808 INFO [jbossweb] successfully deployed file:/C:/Work/jboss-3.0.6/server/tapestry/tmp/deploy/server/tapestry/deploy/vlib.ear/26.vlib.ear-contents/vlib.war to
11:46:30,808 INFO [MainDeployer] Deployed package: file:/C:/Work/jboss-3.0.6/server/tapestry/deploy/vlib.ear
11:46:30,818 INFO [URLDeploymentScanner] Started
11:46:30,818 INFO [MainDeployer] Deployed package: file:/C:/Work/jboss-3.0.6/server/tapestry/conf/jboss-service.xml
11:46:30,818 INFO [Server] JBoss (MX MicroKernel) [3.0.6 (CVSTag=JBoss_3_0_6 Date=200301260037)] Started in 0m:23s:554ms
11:47:44,995 ERROR [SubscribingInterceptor] could not get AbstractReplicatedStore
11:47:48,249 ERROR [SubscribingInterceptor] could not get AbstractReplicatedStore

My jboss-service.xml is enclosed. It is pretty generic, and not set up for distributable (since I'm not running a cluster).

My complaint is that the tag in a web.xml should work properly, even in a non-cluster. Instead, because the app is distributable but the server is not in a cluster, my app fails because of some internal problem with the HttpSession.