-
1. Re: sessions conflict for same app on two different AS instances on different ports -
Ian, the issue isn't related to Seam. It's because Tomcat/JBoss AS generate a JSESSIONID cookie for the domain excluding the port. If this is a development environment, then an easy solution is to add a local DNS entry that points to your local machine e.g. map myotherapp to 127.0.0.1. that way you have different domains and will get different JSESSIONID's for each