Re: [Stripes-users] Potential 1.5.4 Proxy Issue WAS [JIRA] Created: (STS-779) Release 1.5.4 (also to Maven Repo)]

2010-11-12 Thread gshegosh
Yeah, IIS is a piece of crap that I'd never choose, but I have no 
control over the environment used since we're integrating our e-commerce 
web piece with Microsoft Dynamics Navision (or whatever its name is) and 
IIS has to be used there for political reasons (our partners are MS 
gold certified, etc).

I have no idea if 1.5.3 works since I didn't manage to run my app on 
Glassfish 3 at all until I used 1.5.x branch's latest code. But I will 
try to apply Ben's patch (btw, thank You so much for the patch, Ben) and 
deploy the app using old layouts code to see if it is the case for my 
trouble. I'm hoping to be able to do so in the beginning of next week -- 
I'll keep You posted.

What I mean by strange problems is that when I access glassfish 
directly on :8080, whole page gets rendered nicely. But when I access it 
through the IIS proxy, the HTML code sent back seems to be cut in the 
middle. What is interesting is that it is completely repeatable -- I can 
set some user data up and it won't fail, then I change some small pieces 
(that aren't even rendered to the screen!) and it fails consistently, 
being cut in the same place. There's no stack trace, no IIS log entry, 
no nothing. There's no load balancer on the server yet, just IIS serving 
as a proxy to a single (not clustered) Glassfish 3 installation.

I too believe it's IIS fault, not Stripes. But since it all used to work 
for me with some older Stripes (1.5.3), old Glassfish 2.1, some older 
IIS and older version of my app -- and because of the particular way 
that pages are cut in the middle, I started thinking -- perhaps 
something isn't streamed from Glassfish to IIS quickly enough and IIS 
closes the stream prematurely and hence it returns to client half-baked 
HTML?

Best regards,
Grzegorz


--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users


[Stripes-users] Potential 1.5.4 Proxy Issue WAS [JIRA] Created: (STS-779) Release 1.5.4 (also to Maven Repo)]

2010-11-10 Thread Nikolaos Giannopoulos
Grzgorz,

Always makes me cringe to hear IIS used as a proxy for J2EE apps when 
there are so many great unix based RP's out there ;-) ;-) ;-)

In any event, you probably don't have much say in the matter OR perhaps 
you do... but regardless... you might want to try setting up something 
like Oracle Web Server (formerly Sun Web Server and since version 7.0 
has built-in RP capabilities) OR Squid OR Pound and do a side-by-side 
test.  Say install the RP on a another port and proxy to the same 
glassfish instance listening on port 8080.

I did pretty much the same thing when a client had a F5 load balancer 
that they weren't able to configure the load balancing sticky-session 
cookie on and to prove it was the F5 that was the issue I quickly setup 
a Sun RP as a software load balancer and proved that the F5 indeed was 
mis-configured b/c the Sun RP had no issues software load balancing to 
the GlassFish application (Sun OpenSSO / Access Manager).

In your case you might be able to prove whether or not IIS is causing 
you hardship in much the same way.
Also you may want to try setting up a more vanilla non-Stripes app and 
see if you can reproduce the issue.
Also you say I'm seeing strange problems... if you could be more 
descriptive on what is happening then that would help as well.

BTW do you have any load balancer software / hardware in the mix?  Did 
it work without issue w/ 1.5.3?

Personally - I doubt it that Stripes is the cause - and the only way to 
prove that is to rule things out one piece at a time.

--Nikolaos


Ben Gunter wrote:
 I use the trunk patched with the streaming layout modifications behind 
 Apache's mod_proxy in lots of different places and have never had a 
 problem with it. I've attached a patch you can apply to the 1.5.4 
 source code to revert the layouts to what they were in 1.5.3.

 You can check out 1.5.4 from here:
 https://stripes.svn.sourceforge.net/svnroot/stripes/tags/1.5.4

 You can build with maven or ant dist.

 -Ben

 2010/11/10 Grzegorz Krugły g...@karko.net mailto:g...@karko.net

 Ben, a quick question as I'm seeing some strange problems right now
 after overnight production deployment and because the discussion about
 layouts is fresh in my head, it naturally is the first candidate
 for my
 cause ;-)
 Have You (or anyone else for that matter) tried it all behind a
 proxy? I
 have a situation here where everything works when accessed on
 Glassfish
 directly (via 8080 port), but when accessed through IIS proxying to
 Glassfish, there are some connection resets or pages server are cut in
 the middle.

 Is there a simple way I can modify 1.5.x branch code to bring back old
 layout mechanisms? I have some other modifications so I cannot
 just drop
 in 1.5.3 back to test it :-(


 W dniu 10.11.2010 04:16, Ben Gunter pisze:
  My turn to join in the fun on this thread! As far as I'm concerned,
  the layout changes are solid. Everyone who reported problems while I
  was working on the changes is now reporting that everything
 works. All
  the zany tests I could come up with that used to break things no
  longer break things. I'm confident it's ready to ship.
 



--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users