Weblogic running on HP Oracle DB Server

[Tracey]

I would like some feedback from those of you who are running Weblogic on the same HP box that your Oracle DB is running on. Pro's? Con's?

[Alexander M. Ermes]

Hi there.
We have installed the WebLogic server.
If i were you, i would take Apache.
We have been forced by a software vendor,
which would not work without WebLogic, to use it.
Apache, if you download it from HP, is free.
You also get some support, if you do not compile or change anything on that downloaded software. Apache runs without problems, while the config of WebLogic is a sheer horror, if you use it for several databases.
Hope, i have not confused you too much.
If you would like more info, contact me
under Alexander_Ermes@web.de
Rgds
Alexander M. Ermes

[Volker Borowski]

Hello Tracey,

we are running weblogic on solaris.

We have two environments.
One is distributed:
apache with plug-in on one host,
weblogic on the next
and seperate database host (3-tier).

The other one is running all on a single box.

Both are doing quite fine, but there is not so much load on both of these.

This is the typical scalabilaty discussion. Go on one box, as long as everything performs well. Have a seperate DB-Server when things become worse.
Use seperate Webserver when you have a good part of static documents, which can be serviced by apache directly, and use weblogic only for those components requiring application processing.

Just my 2 cent
Volker

[Brian Lin]

Here I have a question would like to ask Volker for your experience. Are you running for some Broken pipe message comes out from WL as:
java.io.IOException: Broken pipe at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:87)
at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:114)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:124)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:91)
at weblogic.servlet.internal.ServletOutputStreamImpl.checkForFlush(ServletOutputStreamImpl.java:482)
at weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamImpl.java:193)
at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:136)
at jsp_servlet._jsp._GeneralError._jspService(_GeneralError.java:74)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:253)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:172)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:113)
at jsp_servlet._SearchMemberList._jspService(_SearchMemberList.java:393)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:253)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:172)
at com.tbcn.servlet.SearchMemberServlet.performTask(SearchMemberServlet.java:372)
at com.tbcn.servlet.SearchMemberServlet.doPost(SearchMemberServlet.java:400)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
................

[DavidH_2]

I would suggest you have a look at weblogic log file to find out error details. I find weblogic will generate error if link or path is not properly setup in Servlet or JSP(Check web.xml).

Could you post more details?

[Brian Lin]

Actually those messages are generated from WL (weblogic.log). We're using WL 5.1 so that can't have web.xml.

[Volker Borowski]

Hello Tracey,

to be honest, I just administrate these servers technically, I have no idea of the development side.
Since this broken pipe seems to come from a java class, I would first go for weblogic website and check release requirements and dependencies.
Weblogic Service Packs up to date ?
Required JAVA-Runtime Patches installed ?

And then, most funny-> jsp_servlet
Be sure, esp. if you do a version-reset of your application, to delete the compiled code!
Otherwise your old version will find no need to re-compile the servlets, as they carry newer timestamps.

Hope this helps
Volker