• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

Stylesheets problem

 
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Hi,

I have a web application Development and Production running on the same Websphere application server.
Production runs on HTTPS where as Development runs on HTTP.

The issue is: everything works absolutely perfect on Production where as in Development - the stylesheets do not load/apply properly most of the times but they do work fine sometimes like in the weekend when very few people login...

Is the problem because of some proxy setting or proxy firewall or Apache (web server) setting??

I really appreciate your help.
Thanks
 
Rancher
Posts: 1093
29
Netbeans IDE Oracle MySQL Database Tomcat Server C++ Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

prasad agarwal wrote:
but they do work fine sometimes like in the weekend when very few people login


As you point out they seem to work ok when there are not very many people on. Is that people on either side, or just the dev side of the world?

In any case it shows a resource problem. I'd get with the Admin for the box and take a look at configurations for each environment, dev and prod, and what happens as people login. It sounds like you do not have a problem in production, so your dev side is being throttled down as a sacrifice to ensure production. There may not be a good solution to this as long as both have to run on the same box. Characteristically, it is the RAM available that is the problem causing culprit.

But without seeing what you have, I am guessing and overlaying what I've had happen in my own situations. Get with the box Admin and check to see what is happening, it's the only way you may come to a solution.
 
prasad agarwal
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Les Morgan, Thanks a lot for your response.

When I said "not very many people on" it means on either side. I mean development is only for a very few people who access it.
I would say, when traffic at proxy is less, then development works fine...

I do all the config too (of course along with coding). On our Apache/Websphere set up, in case of production, since it is running on SSL, it is running on a specific IP address (IP based virtual host) where as development along with 3 more applications run on a different IP address (Name based virtual hosts).
All applications run fine regarding stylesheets except development !

Now since we are planning to move to new Websphere 8.x, I need to give access to the development for more people to test which is the reason why I am now trying to find and fix the problem.

Any help would be appreciated.
My idea is: if I can fix the stylesheets load problem then I will give access to development for testing otherwise I need to create production version along with SSL for testing on new Websphere 8.x.

One main point though is: In both Apache/Websphere 6.x (on one system - present Production) and Apache/Websphere 8.x (on another system - plan to migrate to), all applications run fine expect Development of the application which has a Production version run on SSL. I mean on 2 different systems, same thing happening ?? Something definitely is common in both cases...
Is it because, the browser caches the css files from production and when development tries to access, it fails? 3 other applications running don't have any development versions and they work fine.

Thanks again.
 
prasad agarwal
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


I am doing a little bit more research using Chrome browser and network monitoring...
You know in Production, I mostly get status=200 (from cache) where as in development sometimes status=200 where as sometimes it is 304 (from cache).
Maybe is it because of this, there is a problem?
 
I’m tired of walking, and will rest for a minute and grow some wheels. This is the promise of this tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic