WLS 6.0 sp2 Apache fail to proxy request

Hi
IHAC who is going live soon and I am involved in configuring
apache plug-in for them.
The thing is that the plug-in is proxying request to admin server instead of
the
managed server. When I turn debug on, the request has admin server in the
preferred list
of server.
I do not have any admin server ip or port in apache config and I am not
using 8001 for admin port.
I have also clear all cookies on my browsers. Does anybody has any clues.
regards
Eng Guan

Similar Messages

WLS 6.1 SP2 Cluster fails

 Hi All.
 we have migrated to WLS 6.1 SP2, now we have a serious problem with the cluster
 wihch die after several minutes. Our architecture is several front-ends servers
 (concretely servelts, without cluster) make request to back-end (starteles EJB,
 DB access). This back-end is compuond by four WLS instances running into 2 Sun
 Solaris Machines. The system reports the nexts messages in the weblogic.log.
 * backendPlatformA instance
 for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
 '#|platformA|129.1027407260379', bound: 'false', dead: 'false'" because
 of soft disconnect timeout.>
 ####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
 <platformA> <ExecuteThread: '117' for queue: 'default'> <system> <>
 <000000> <Tried to renew lease on lost reference: '257'>
 * backendPlatformB instance
 for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
 '#|platformB|118.1027407423933', bound: 'false', dead: 'false'" because
 of soft disconnect timeout.>
 ####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
 <platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
 <Removing "ClientContext - id: '#|platformB|119.1027407423933', bound:
 'false', dead: 'false'" because of soft disconnect timeout.>
 * ioboxPlatfromC instance
 for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
 '#|platformC|139.1027407286958', bound: 'false', dead: 'false'" because
 of soft disconnect timeout.>
 ####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
 <platformC> <ExecuteThread: '119' for queue: 'default'> <system> <>
 <000000> <Tried to renew lease on lost reference: '257'>
 * Instancia ioboxPlatfromD
 for queue: 'default'> <> <> <000274> <Removing "ClientContext - id:
 '#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
 of soft disconnect timeout.>
 ####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
 <platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
 <Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
 'false', dead: 'false'" because of soft disconnect timeout.>
 ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
 <ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
 platformA
 jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
 from cluster view due to PeerGone>
 ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
 <ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
 7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
 to the cluster>
 ####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
 <platformD> <ExecuteThread: '102' fo
 r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
 anaydidos>
 ####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
 <platformD> <ExecuteThread: '119' for queue: 'default'> <system> <>
 <000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because of:
 'Server received a message over an uninitialized connection: 'JVMMessage
 from: 'null' to:
 '1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
 cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
 flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
 Any idea?
 Thanks for all


 Hi,
 We are using Weblogic 6.1 SP2, NT 4.0 and java 1.3.1. We have also encountered
 the same error message. We have 1 admin and 2 managed servers. We have tried connecting
 in using weblogic.admin to check the idle thread and we are able to connect. However,
 when we connect from IIS to Weblogic, the application failed to response. We have
 tried connect direct to weblogic but it does not response as well. We have seen
 that the idle thread left has been reduced but there is no activites from the
 weblogic console. The thread is used but not releasing and the console is not
 moving. When we shutdown one of the managed server, the application is able to
 process as seen from the console.
 We have turned off native io and this behavior is not seen. When we turn on native
 io, it appear. So we can conclude that it is related to native io.
 Is there any solution or intermediate patch without upgrading to the later SP
 Thanks
 Rajesh Mirchandani <[email protected]> wrote:
 >We are shipping the Jdriver for oracle 816 with SP3. Use the driver
 >from .\bin\oci816_8
 >
 >Manuel wrote:
 >
 >> Thanks Rajesh,
 >>
 >> we have another problem since our database is Oracle 8.1.6 and SP3
 >jDriver doesn´t
 >> support this version.
 >>
 >> Best Regards
 >>
 >> Rajesh Mirchandani <[email protected]> wrote:
 >> >Upgrade to SP3, if possible.
 >> >
 >> >Manuel wrote:
 >> >
 >> >> Hi All.
 >> >>
 >> >> we have migrated to WLS 6.1 SP2, now we have a serious problem with
 >> >the cluster
 >> >> wihch die after several minutes. Our architecture is several front-ends
 >> >servers
 >> >> (concretely servelts, without cluster) make request to back-end
 >(starteles
 >> >EJB,
 >> >> DB access). This back-end is compuond by four WLS instances running
 >> >into 2 Sun
 >> >> Solaris Machines. The system reports the nexts messages in the weblogic.log.
 >> >>
 >> >> * backendPlatformA instance
 >> >>
 >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
 >id:
 >> >> '#|platformA|129.1027407260379', bound: 'false', dead: 'false'"
 >because
 >> >> of soft disconnect timeout.>
 >> >> ####<Jul 23, 2002 10:02:24 AM GMT> <Info> <DGCserver> <wls00>
 >> >> <platformA> <ExecuteThread: '117' for queue: 'default'> <system>
 ><>
 >> >> <000000> <Tried to renew lease on lost reference: '257'>
 >> >>
 >> >> * backendPlatformB instance
 >> >>
 >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
 >id:
 >> >> '#|platformB|118.1027407423933', bound: 'false', dead: 'false'"
 >because
 >> >> of soft disconnect timeout.>
 >> >> ####<Jul 23, 2002 10:03:52 AM GMT> <Info> <WebLogicServer> <wls00>
 >> >> <platformB> <ExecuteThread: '114' for queue: 'default'> <> <> <000274>
 >> >> <Removing "ClientContext - id: '#|platformB|119.1027407423933',
 >bound:
 >> >> 'false', dead: 'false'" because of soft disconnect timeout.>
 >> >>
 >> >> * ioboxPlatfromC instance
 >> >>
 >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
 >id:
 >> >> '#|platformC|139.1027407286958', bound: 'false', dead: 'false'"
 >because
 >> >> of soft disconnect timeout.>
 >> >> ####<Jul 23, 2002 10:04:24 AM GMT> <Info> <DGCserver> <wls01>
 >> >> <platformC> <ExecuteThread: '119' for queue: 'default'> <system>
 ><>
 >> >> <000000> <Tried to renew lease on lost reference: '257'>
 >> >>
 >> >> * Instancia ioboxPlatfromD
 >> >>
 >> >> for queue: 'default'> <> <> <000274> <Removing "ClientContext -
 >id:
 >> >> '#|platformD|58.1027415900956', bound: 'false', dead: 'false'" because
 >> >> of soft disconnect timeout.>
 >> >> ####<Jul 23, 2002 10:05:54 AM GMT> <Info> <WebLogicServer> <wls01>
 >> >> <platformD> <ExecuteThread: '107' for queue: 'default'> <> <> <000274>
 >> >> <Removing "ClientContext - id: '#|platformD|59.1027415900956', bound:
 >> >> 'false', dead: 'false'" because of soft disconnect timeout.>
 >> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
 >> >> <ExecuteThread: '107' for queue: 'default'> <> <> <000113> <Removing
 >> >> platformA
 >> >> jvmid:7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
 >> >> from cluster view due to PeerGone>
 >> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Info> <Cluster> <wls01> <platformD>
 >> >> <ExecuteThread: '116' for queue: 'default'> <> <> <000129> <Removing
 >> >> 7148145370197743783S:10.2.1.1:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformA
 >> >> to the cluster>
 >> >> ####<Jul 23, 2002 10:06:22 AM GMT> <Error> <T3Services> <wls01>
 >> >> <platformD> <ExecuteThread: '102' fo
 >> >> r queue: 'default'> <> <5577:04d703f24ce814ba> <000000> < Parametros
 >> >> anaydidos>
 >> >> ####<Jul 23, 2002 10:06:33 AM GMT> <Error> <ConnectionManager> <wls01>
 >> >> <platformD> <ExecuteThread: '119' for queue: 'default'> <system>
 ><>
 >> >> <000000> <Closing: 'weblogic.rjvm.t3.T3JVMConnection@63718b' because
 >> >of:
 >> >> 'Server received a message over an uninitialized connection: 'JVMMessage
 >> >> Wrom: HJEXXIMQZU
 >> >> '1615014391094985181S:10.2.1.4:[17001,17001,7002,7002,17001,7002,-1]:backendPlatform:platformD'
 >> >> cmd: 'CMD_REQUEST', QOS: '101', responseId: '1', invokableId: '454',
 >> >> flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev offset: '38'''
 >> >>
 >> >> Any idea?
 >> >>
 >> >> Thanks for all
 >> >
 >> >--
 >> >Rajesh Mirchandani
 >> >Developer Relations Engineer
 >> >BEA Support
 >> >
 >> >
 >
 >--
 >Rajesh Mirchandani
 >Developer Relations Engineer
 >BEA Support
 >
 >

Apache configuration for proxying requests to Weblogic SSL port

Hello Everyone,
I want to proxy requests from Apache to Weblogic server on its SSL Port 7002. I am using the default SSL demo version provided by Oracle/BEA.
Both my Apache and Weblogic instances are running on same machine.
This is the procedure I followed. I enabled SSL port on Weblogic. Added below configuration to Apache conf file. I am passing trusted.crt file inside WL_HOME/server/lib as parameter to TrustedCAFile .
<Location "/">
SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
SetHandler weblogic-handler
WebLogicHost ServerHostMame
WebLogicPort WLInstanceSSLPort
SecureProxy ON
TrustedCAFile "C:/trusted.crt"
RequireSSLHostMatch false
Debug ALL
WLLogFile "C:/wl_proxy.log"
</IfModule>
When I start the Apache instance and try to access the webpage I see below exception in proxy log.
Thu Apr 09 10:38:05 2009 <735212392878852> Hdrs to WLS:[WL-Proxy-Client-IP]=[10.149.181.55]
Thu Apr 09 10:38:05 2009 <735212392878852> Hdrs to WLS:[Proxy-Client-IP]=[10.149.181.55]
Thu Apr 09 10:38:05 2009 <735212392878852> Hdrs to WLS:[X-Forwarded-For]=[10.149.181.55]
Thu Apr 09 10:38:05 2009 <735212392878852> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]
Thu Apr 09 10:38:05 2009 <735212392878852> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
Thu Apr 09 10:38:05 2009 <735212392878761> INFO: No session match found
Thu Apr 09 10:38:05 2009 <735212392878852> INFO: SSL certificate chain validation failed: 3015
Thu Apr 09 10:38:05 2009 <735212392878852> trusted certs = 0
Thu Apr 09 10:38:05 2009 <735212392878852> dumping cert chain
Thu Apr 09 10:38:05 2009 <735212392878852> commonName is testmachine-us
Thu Apr 09 10:38:05 2009 <735212392878761> INFO: DeleteSessionCallback
Thu Apr 09 10:38:05 2009 <735212392878852> ERROR: SSLWrite failed
Thu Apr 09 10:38:05 2009 <735212392878852> SEND failed (ret=-1) at 789 of file ../nsapi/URL.cpp
Thu Apr 09 10:38:05 2009 <735212392878852> *******Exception type [WRITE_ERROR_TO_SERVER] raised at line 790 of ../nsapi/URL.cpp
Thu Apr 09 10:38:05 2009 <735212392878852> Marking 10.149.181.55:40011 as bad
Thu Apr 09 10:38:05 2009 <735212392878852> got exception in sendRequest phase: WRITE_ERROR_TO_SERVER [os error=0, line 790 of ../nsapi/URL.cpp]: at line 2994
Thu Apr 09 10:38:05 2009 <735212392878852> INFO: Closing SSL context
Thu Apr 09 10:38:05 2009 <735212392878852> INFO: Error after SSLClose, socket may already have been closed by peer
Thu Apr 09 10:38:05 2009 <735212392878852> Failing over after WRITE_ERROR_TO_SERVER exception in sendRequest()
Thu Apr 09 10:38:05 2009 <735212392878852> attempt #1 out of a max of 5
Thu Apr 09 10:38:05 2009 <735212392878852> general list: trying connect to '10.149.181.55'/40011/40011 at line 2619 for '/'
Thu Apr 09 10:38:05 2009 <735212392878852> New SSL URL: match = 0 oid = 22
Thu Apr 09 10:38:05 2009 <735212392878852> Connect returns -1, and error no set to 10035, msg 'Unknown error'
Thu Apr 09 10:38:05 2009 <735212392878852> EINPROGRESS in connect() - selecting
Thu Apr 09 10:38:05 2009 <735212392878852> Setting peerID for new SSL connection
Please advice if I am missing anything here?
- - Tarun

I'm using WL9 and Apache2.2
I had exact same issue as above (which I solved with these directions) in additiion to another issue, that only showed once I enabled full logging, since it shows as warning/info, not as error
First to enable full logging, add this
Debug ALL
WLLogFile "C:/wl_proxy.log"
Then after a failure (even after fixing the above), look at the log, and if you see this INFO/WARN:
Thu Apr 23 00:48:27 2009 <235612404369072> INFO: Host (comp1) doesn't match (192.168.0.229), validation failed
Thu Apr 23 00:48:27 2009 <235612404368911> WARN: DeleteSessionCallback: No match found!!
Thu Apr 23 00:48:27 2009 <235612404369072> ERROR: SSLWrite failed
Thu Apr 23 00:48:27 2009 <235612404369072> SEND failed (ret=-1) at 795 of file ../nsapi/URL.cpp
Thu Apr 23 00:48:27 2009 <235612404369072> *******Exception type [WRITE_ERROR_TO_SERVER] raised at line 796 of ../nsapi/URL.cpp
Thu Apr 23 00:48:27 2009 <235612404369072> Marking 192.168.0.229:7002 as bad
that means you have same problem as I do. The WeblogicHost inside the Location descriptor should match the actual host name for the machine. I believe it's easer because the certificate created by weblogic during its installation will encapsulate the machine host name, or because the SSL validation mechanism expects the machine host name, nothing else.
Here's how the config would like (my hostname is comp1)
<IfModule mod_weblogic.c>
SecureProxy on
TrustedCAFile "C:/tools/bea9/weblogic92/server/lib/CertGenCA.pem"
Debug ALL
WLLogFile "C:/wl_proxy.log"
EnforceBasicConstraints off
</IfModule>
<Location /EnterpriseCMP>
SetHandler weblogic-handler
WebLogicHost comp1
WebLogicPort 7002
ConnectTimeoutSecs 1000
ConnectRetrySecs 1000
</Location>
I believe the

WLS 6.1 SP2 proxy server timeout

We are using WLS 6.1 SP2 server as a proxy server. When accessing a
page that has a long running process, the server times out in 5
minutes and throws an internal server error on the browser. Is there a
way to prevent this from happening or increase the timeout period?

We are using WLS 6.1 SP2 server as a proxy server. When accessing a
page that has a long running process, the server times out in 5
minutes and throws an internal server error on the browser. Is there a
way to prevent this from happening or increase the timeout period?

Wls 7.0 sp2 proxy plugin issue with iplanet6.x and wls 6.1 sp3 app server

Hi,
I've a setup with iplanet 6.x webserver using the wls 7.0 sp2 proxy plugin to
route requests to the clustered app server instances (2 of them) that are in wls
6.1 sp3.
The issue is, I'm noticing that the session is not sticky and is getting routed
onto the other app server instance. The error that I see in the wlproxy.log is
as follows:
*******Exception type [PROTOCOL_ERROR] raised
at line 654 of URL.cpp
Thu Nov 13 11:30:08 2003 failure on sendRequest() w/ recycled connection
to Instance1:7001, numfailures=1
Thu Nov 13 11:30:08 2003 Marking Instance1:7001 as bad
Thu Nov 13 11:30:08 2003 got exception in sendRequest phase:
PROTOCOL_ERROR [line 654 of URL.cpp]: unexpected EOF
reading HTTP status at line 1010
Thu Nov 13 11:30:08 2003 Failing over after sendRequest exception
Thu Nov 13 11:30:08 2003 attempt #1 out of a max of 5
Has anyone seen this issue? Can anyone explain why this issue is occuring.?
Thanks.

Did you find a solution for this problem?
I have somthing very similar going on where I am currently working.
Thanks!
Andy.
"Simple Guy" <[email protected]> wrote:
>
Hi,
I've a setup with iplanet 6.x webserver using the wls 7.0 sp2 proxy plugin
to
route requests to the clustered app server instances (2 of them) that
are in wls
6.1 sp3.
The issue is, I'm noticing that the session is not sticky and is getting
routed
onto the other app server instance. The error that I see in the wlproxy.log
is
as follows:
*******Exception type [PROTOCOL_ERROR] raised
at line 654 of URL.cpp
Thu Nov 13 11:30:08 2003 failure on sendRequest() w/ recycled connection
to Instance1:7001, numfailures=1
Thu Nov 13 11:30:08 2003 Marking Instance1:7001 as bad
Thu Nov 13 11:30:08 2003 got exception in sendRequest phase:
PROTOCOL_ERROR [line 654 of URL.cpp]: unexpected EOF
reading HTTP status at line 1010
Thu Nov 13 11:30:08 2003 Failing over after sendRequest exception
Thu Nov 13 11:30:08 2003 attempt #1 out of a max of 5
Has anyone seen this issue? Can anyone explain why this issue is occuring.?
Thanks.

WLS 6.1 SP2 and Apache 1.3.26 Windows NT/2000

Hi,
Is there an Apache plugin available for WLS 6.1 (SP2) and Apache 1.3.26 running
on Windows NT/2000?
thanks

I've solved my own problem. I learned that there was a sp4 (let alone a
sp3) for WLS. Installed that and the problem went away. Sorry for the
noise.
-Phil
Philip Bower <[email protected]> wrote in
news:[email protected]:
When I try to deploy the struts-example.war or if I add the struts.jar
to any other web app I've created, I get this error when I start WLS
and it tries to deploy that war.
java.lang.StringIndexOutOfBoundsException
at weblogic.servlet.internal.WebAppHelper.resolveManifestName
(WebAppHelper.java:469)
I'm using version 1.1b3 of struts. I'm having no problems with
version 1.0.2 of struts.
I'm guessing its complaining about the manifest file in struts.jar,
but I don't understand why.
Here's my version info and the stack trace (my web app is called
findme in this example). Thanks in advance.
-Phil
Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
#154529
<Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
application findme: Could not load findme>
<Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
starting Config caught throwable
java.lang.reflect.UndeclaredThrowableException:
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1
at java.lang.String.substring(String.java:1525)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
.jav a:469)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
ava: 234)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
Serv letContext.java:3407)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
Cont ext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
t.ja va:862)

Wls 8.1 sp2: weblogic.jspc complains about struts-html tags

 Hi,
 I am trying to compile jsps with weblogic.jspc, which use struts' html tags. However,
 the compilation fails with the following message:
 [java] Translation of /views/viewPageBody.jsp failed: (line 3): Error in using
 tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
 has no setter method corresponding to TLD declared attribute 'server', (JSP 1.1
 spec, 5.4.1)
 I opened the BaseTag class from the struts jar and found the setter exists for
 the attribute 'server' of html tld. So does the property 'server'. The property
 'server' is a string and the parameter in the setter is a string. I read about
 the jspc errors in wls 8.1 about the setter parameter being of different type
 than the property. However, that is not the case here. I tried using both Sun's
 and BEA's jdk. None of them help. Btw, there is another attribute mentioned in
 the html tld, which is 'target'. The compiler doesn't complain yet about this.:(
 Also, I happened to compile other apps which have struts logic tags.
 My environment:
 OS: Win2k sp3
 WLS: 8.1 sp2
 JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
 Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
 without any mention supports only ant 1.5.3.)
 I would appreciate any help in this regard.
 Thanks,
 Abbas


 What version of Struts are you trying to use?
 Are you certain you're not encountering a different instance of that class in
 an unexpected location in your classpath?
 "Abbas" <[email protected]> wrote:
 >
 >Hi,
 >I am trying to compile jsps with weblogic.jspc, which use struts' html
 >tags. However,
 >the compilation fails with the following message:
 >
 >[java] Translation of /views/viewPageBody.jsp failed: (line 3): Error
 >in using
 >tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
 >has no setter method corresponding to TLD declared attribute 'server',
 >(JSP 1.1
 >spec, 5.4.1)
 >
 >I opened the BaseTag class from the struts jar and found the setter exists
 >for
 >the attribute 'server' of html tld. So does the property 'server'. The
 >property
 >'server' is a string and the parameter in the setter is a string. I read
 >about
 >the jspc errors in wls 8.1 about the setter parameter being of different
 >type
 >than the property. However, that is not the case here. I tried using
 >both Sun's
 >and BEA's jdk. None of them help. Btw, there is another attribute mentioned
 >in
 >the html tld, which is 'target'. The compiler doesn't complain yet about
 >this.:(
 >Also, I happened to compile other apps which have struts logic tags.
 >
 >
 >My environment:
 >OS: Win2k sp3
 >WLS: 8.1 sp2
 >JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
 >Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
 >without any mention supports only ant 1.5.3.)
 >
 >I would appreciate any help in this regard.
 >
 >Thanks,
 >
 >Abbas

WLS 7.0 sp2 - Servlet Problems with SOAP messages

 I'm using Weblogic 7.0 SP2 and trying to create a Servlet to receive SOAP wrapped
 XML messages. I'm getting the following error. Is this a problem with WLS7.0sp2's
 support of JAXM? The System.out.println's indicate I have successfully received
 the incoming SOAP request and then successfully formatted the SOAP response, but
 upon returning saving the response it appears to blow up. Does anyone have any
 suggestions?
 I need to do the following in a servlet:
 - receive an incoming SOAP request with an embedded XML message
 - perform some processing
 - return a SOAP response with an embedded XML message
 Should I be using JAXM? Or can I do this same task easily with JAX-RPC?
 <Feb 24, 2004 4:10:42 PM AST> <Error> <HTTP> <101017> <[ServletContext(id=260434
 7,name=isd.war,context-path=)] Root cause of ServletException
 java.lang.Error: NYI
 at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessag
 eImpl.java:360)
 at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
 (ServletStubImpl.java:1058)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
 pl.java:401)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
 pl.java:306)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
 n.run(WebAppServletContext.java:5445)
 at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
 eManager.java:780)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
 rvletContext.java:3105)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
 pl.java:2588)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
 >
 I've stripped the code down so that all it does is verifies the incoming SOAP/XML
 request and creates a hard-coded response... be gentle... I'm a novice at this
 import javax.xml.soap.*;
 import javax.servlet.*;
 import javax.servlet.http.*;
 // import javax.xml.transform.*;
 import java.util.*;
 import java.io.*;
 public class RegisterServlet extends HttpServlet
 static MessageFactory fac = null;
 static
 try
 fac = MessageFactory.newInstance();
 catch (Exception ex)
 ex.printStackTrace();
 public void init(ServletConfig servletConfig) throws ServletException
 super.init(servletConfig);
 public void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException,
 IOException
 try
 System.out.println("** Note: doPost() Entering req = " + req);
 // Get all the headers from the HTTP request
 MimeHeaders headers = getHeaders(req);
 // Get the body of the HTTP request
 InputStream is = req.getInputStream();
 // Now internalize the contents of a HTTP request
 // and create a SOAPMessage
 SOAPMessage msg = fac.createMessage(headers, is);
 System.out.println("** Note: doPost() Step A");
 SOAPMessage reply = null;
 reply = onMessage(msg);
 System.out.println("** Note: doPost() Step B reply = " + reply);
 if (reply != null)
 * Need to call saveChanges because we're
 * going to use the MimeHeaders to set HTTP
 * response information. These MimeHeaders
 * are generated as part of the save.
 if (reply.saveRequired())
 System.out.println("** Note: doPost() Step C reply.saveRequired()");
 reply.saveChanges();
 resp.setStatus(HttpServletResponse.SC_OK);
 putHeaders(reply.getMimeHeaders(), resp);
 // Write out the message on the response stream
 OutputStream os = resp.getOutputStream();
 System.out.println("** Note: doPost() Step D os = " + os);
 reply.writeTo(os);
 os.flush();
 else
 resp.setStatus(HttpServletResponse.SC_NO_CONTENT);
 catch (Exception ex)
 throw new ServletException("** Error: SAAJ POST failed: " + ex.getMessage());
 static MimeHeaders getHeaders(HttpServletRequest req)
 Enumeration enum = req.getHeaderNames();
 MimeHeaders headers = new MimeHeaders();
 while (enum.hasMoreElements())
 String headerName = (String)enum.nextElement();
 String headerValue = req.getHeader(headerName);
 StringTokenizer values =
 new StringTokenizer(headerValue, ",");
 while (values.hasMoreTokens())
 headers.addHeader(headerName,
 values.nextToken().trim());
 return headers;
 static void putHeaders(MimeHeaders headers, HttpServletResponse res)
 Iterator it = headers.getAllHeaders();
 while (it.hasNext())
 MimeHeader header = (MimeHeader)it.next();
 String[] values = headers.getHeader(header.getName());
 if (values.length == 1)
 res.setHeader(header.getName(),
 header.getValue());
 else
 StringBuffer concat = new StringBuffer();
 int i = 0;
 while (i < values.length)
 if (i != 0)
 concat.append(',');
 concat.append(values[i++]);
 res.setHeader(header.getName(), concat.toString());
 // This is the application code for handling the message.
 public SOAPMessage onMessage(SOAPMessage message)
 SOAPMessage replymsg = null;
 try
 System.out.println("** Note: OnMessage() Entering msg = " + message);
 //Extract the ComputerPart element from request message and add to reply SOAP
 message.
 SOAPEnvelope reqse = message.getSOAPPart().getEnvelope();
 SOAPBody reqsb = reqse.getBody();
 //System.out.println("** Note: OnMessage() Step B");
 System.out.println("** Note: OnMessage () Step A Soap Request Message Body = "
 + reqsb);
 //Create a reply mesage from the msgFactory of JAXMServlet
 System.out.println("** Note: OnMessage () Step B");
 replymsg = fac.createMessage();
 SOAPPart sp = replymsg.getSOAPPart();
 SOAPEnvelope se = sp.getEnvelope();
 SOAPBody sb = se.getBody();
 System.out.println("** Note: OnMessage () Step C Soap Reply Before Message Body
 = " + sb);
 se.getBody().addBodyElement(se.createName("RegisterResponse")).addChildElement(se.createName("ErrorCode")).addTextNode("000");
 System.out.println("** Note: OnMessage () Step D Soap Reply After Message Body
 = " + sb);
 replymsg.saveChanges();
 System.out.println("** Note: OnMessage() Exiting replymsg = " + (replymsg));
 catch (Exception ex)
 ex.printStackTrace();
 return replymsg;


Michael,
I got the same error on WLS8.1/Win2K professional and apache FOP (old version).
After digging into the WLS code and FOP(old version). i found the conflict happens
on
the "org.xml.sax.parser" system property. In WLS code, they hard coded like the
following when startup weblogic server:
System.setProperty("org.xml.sax.parser", "weblogic.xml.jaxp.RegistryParser");
But the FOP code try to use the "org.xml.sax.parser" system property to find the
sax parser then conlict happens.
Here is the response from BEA support :
"I consulted with our developers regarding the question of whether we can change
the hard-coded value for the java system property: org.xml.sax.parser by using
a configuration parameter and I found that unfortunately there is no specific
setting to change the value. As you had mentioned in your note the org.xml.sax.parser
system property can be changed programmatically in your application code."
I solve my problem by using newer apache FOP (it never use the system property:org.xml.sax.parser
any more) and XML Registy for WLS8.1.
Good luck.
David Liu
Point2 Technologies Inc.
"p_michael" <[email protected]> wrote:
>
Help.
When we migrated from WLS 6.1 to WLS 7.0 SP2 when encountered a problem
with XML
parsing that did not previously exist.
We get the error "weblogic.xml.jaxp.RegistryParser is not a SAX driver".
What does this mean? And, what should we do about it.
p_michael

Re: WLS 6.0 SP2 hangs due to many sockets in CLOSE_WAIT state

We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000 platform.
Currently we are using running some stablity tests and noticing that there are
lot of sockets in close_wait state and handle count keeps going up and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay as suggested
in this newsgroup, and we are still noticing this problem. Does any body have
the same issue?. is this a know problem with weblogic http server?. and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N

BEA acknowledges this problem in 6.0 SP2 with iPlanet plug-in.
Solution that they recommend is to use 6.1 SP2 plug-in (they claim
full compatibility). Also, you may have to set KeepAliveEnabled to
false in obj.conf (the problem is in wrong pooling).
Hope it helps,
Bala
Robert Patrick <[email protected]> wrote in message news:<[email protected]>...
There are a couple of issues.
1.) You need to tune the machine running the web server and the machine
running WebLogic to make sure that it is configured appropriately for a
high-volume HTTP server. See
http://e-docs.bea.com/wls/platforms/sun/index.html for details on tuning
Solaris.
2.) I believe that there is a bug in the plugins in 6.0 where it is not
properly closing sockets. Try using the plugin from WLS 6.1 SP2...
Hope this helps,
Robert
Kevin Phillips wrote:
Tim Funk <[email protected]> wrote:
I am experiencing similar problems with WL 6.0 SP2 on Solaris 2.6.
We are already proxying all HTTP traffic through a
cluster of apache servers. Unfortuantely, the apache-WL
bridge seems to work so efficiently that our servers are
still flooded with open sockets in the TCP_CLOSE_WAIT state.
It seems to be bound by WebLogic's capacity to respond to
the requests in a speedy enough fashion.
Anybody have any suggestions?
Kevin
We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because
it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000
platform.
Currently we are using running some stablity tests and noticing that
there are
lot of sockets in close_wait state and handle count keeps going up
and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay
as suggested
in this newsgroup, and we are still noticing this problem. Does any
body have
the same issue?. is this a know problem with weblogic http server?.
and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N

Ignoring Http basic authentication header in wls 7.0.sp2 web service servlet (weblogic.webservice.server.servlet.WebServiceServlet)

Hi!
We need to implement authentication using our own methods, and the authentication
information is provided to the web service implementation in a basic authentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles web services
in
wls 7.0.sp2, always attempts to perform authentication, if the header is present.
Is there any way to circumvent this, because we want to implement authentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for our own
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet, which
would
remove the basic authentication header, and put the authentication info in custom
headers, such as x-auth: <user:password>, or smthng similar, and after successful
authentication, make a call to bea's servlet weblogic.webservice.server.servlet.WebServiceServlet.
But still, I'd like to know if there is any way to tell bea's servlet to ignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Currently there is no option to turn off security check.
I think you can use a servlet filter mapped to the URL
of your service, instead of a proxy servlet?
Regards,
-manoj
http://manojc.com
"Toni Nykanen" <[email protected]> wrote in message
news:3ef1577b$[email protected]..
>
Hi!
We need to implement authentication using our own methods, and theauthentication
information is provided to the web service implementation in a basicauthentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
in
wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
Is there any way to circumvent this, because we want to implementauthentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for ourown
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet,which
would
remove the basic authentication header, and put the authentication info incustom
headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
>
But still, I'd like to know if there is any way to tell bea's servlet toignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Apache as reverse proxy - 400 Bad request

Hi all,
I'm configured apache as reverse proxy according to this blog:
The Reverse Proxy Series -- Part 3: Apache as a reverse-proxy
When I try to navigate http://testcomp/irj I get "400 - Bad request"
See exception;
Message : User Guest, IP address
Cannot parse the http request. Http error response [400 Bad Request] will be returned. Request is [Host: sapportal:50000
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
Accept-Language: en,he;q=0.5
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
Max-Forwards: 10
Via: 1.1 localhost
X-Forwarded-For: 10.0.0.4
X-Forwarded-Host: 10.0.0.6
X-Forwarded-Server: localhost
Connection: Keep-Alive
GET /irj HTTP/1.1
Host: sapportal:50000
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
Accept-Language: en,he;q=0.5
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
Max-Forwards: 10
Via: 1.1 localhost
X-Forwarded-For: 10.0.0.4
X-Forwarded-Host: 10.0.0.6
X-Forwarded-Server: localhost
Connection: Keep-Alive
com.sap.engine.services.httpserver.exceptions.HttpIllegalArgumentException: Incompatible field content in the MIME header.
 at com.sap.engine.services.httpserver.lib.headers.MimeHeaderField.parse(MimeHeaderField.java:364)
 at com.sap.engine.services.httpserver.lib.headers.MimeHeaders.init(MimeHeaders.java:504)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.initialize(RequestAnalizer.java:196)
 at com.sap.engine.services.httpserver.server.Client.initialize(Client.java:84)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:143)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Severity : Error
Category :
Location : com.sap.engine.services.httpserver
Application :
Thread : SAPEngine_Application_Thread[impl:3]_32
Datasource : 9332850:C:usrsapPD9JC00j2eeclusterserver0logdefaultTrace.trc
Message ID : 000C29EFE9A300570000002D00000B9000043A81D3311894
Source Name : com.sap.engine.services.httpserver
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : 5359e85066e411dcbf6b000c29efe9a3
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 2
Source : com.sap.engine.services.httpserver
ThreadObject : SAPEngine_Application_Thread[impl:3]_32
Transaction :
User : Guest
The lines I added to http.conf
#Enable reverse-proxying
ProxyVia on
ProxyTimeout 600
#disable forward-proxying
ProxyRequests Off
#proxy /irj both ways
ProxyPass /irj http://sapportal:50000/irj
ProxyPassReverse /irj http://testcomp/irj
#proxy /logon both ways
ProxyPass /logon http://sapportal:50000/logon
ProxyPassReverse /logon http://testcomp/logon
I tried with apache version 2.2.3 & 2.0.59 with no success.
My J2EE/Portal version is 6.17.
Since this is a testing environment the two computers are under the same workgroup (no domain).
If I naviagte directly to the portal (without the reverse proxy) everything is working.
How can I solve it?
Regards,
Omri

Hi Jakub,
Thanks for the answer.
It's not working for me...
I'm attaching my httpd.conf file.
Also, what apache version do you use?
Can you send me your post your httpd.conf file?
Thanks,
Omri
httpd.conf
This is the main Apache HTTP server configuration file. It contains the
configuration directives that give the server its instructions.
See <URL:http://httpd.apache.org/docs/2.2/> for detailed information.
In particular, see
<URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
for a discussion of each configuration directive.
Do NOT simply read the instructions in here without understanding
what they do. They're here only as hints or reminders. If you are unsure
consult the online docs. You have been warned.
Configuration and logfile names: If the filenames you specify for many
of the server's control files begin with "/" (or "drive:/" for Win32), the
server will use that explicit path. If the filenames do not begin
with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
with ServerRoot set to "c:/apache" will be interpreted by the
server as "c:/apache/logs/foo.log".
NOTE: Where filenames are specified, you must use forward slashes
instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
If a drive letter is omitted, the drive on which Apache.exe is located
will be used by default. It is recommended that you always supply
an explicit drive letter in absolute paths, however, to avoid
confusion.
ThreadsPerChild: constant number of worker threads in the server process
MaxRequestsPerChild: maximum number of requests a server process serves
ThreadsPerChild 250
MaxRequestsPerChild 0
ServerRoot: The top of the directory tree under which the server's
configuration, error, and log files are kept.
Do not add a slash at the end of the directory path. If you point
ServerRoot at a non-local disk, be sure to point the LockFile directive
at a local disk. If you wish to share the same ServerRoot for multiple
httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "c:/apache"
Listen: Allows you to bind Apache to specific IP addresses and/or
ports, instead of the default. See also the <VirtualHost>
directive.
Change this to Listen on specific IP addresses as shown below to
prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#Listen 12.34.56.78:80
Listen 80
Dynamic Shared Object (DSO) Support
To be able to use the functionality of a module which was built as a DSO you
have to place corresponding `LoadModule' lines at this location so the
directives contained in it are actually available before they are used.
Statically compiled modules (those listed by `httpd -l') do not need
to be loaded here.
Example:
LoadModule foo_module modules/mod_foo.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
'Main' server configuration
The directives in this section set up the values used by the 'main'
server, which responds to any requests that aren't handled by a
<VirtualHost> definition. These values also provide defaults for
any <VirtualHost> containers you may define later in the file.
All of these directives may appear inside <VirtualHost> containers,
in which case these default settings will be overridden for the
virtual host being defined.
ServerAdmin: Your address, where problems with the server should be
e-mailed. This address appears on some server-generated pages, such
as error documents. e.g. [email protected]
ServerAdmin @@ServerAdmin@@
ServerName gives the name and port that the server uses to identify itself.
This can often be determined automatically, but we recommend you specify
it explicitly to prevent problems during startup.
If your host doesn't have a registered DNS name, enter its IP address here.
ServerName localhost:80
DocumentRoot: The directory out of which you will serve your
documents. By default, all requests are taken from this directory, but
symbolic links and aliases may be used to point to other locations.
DocumentRoot "c:/apache/htdocs"
Each directory to which Apache has access can be configured with respect
to which services and features are allowed and/or disabled in that
directory (and its subdirectories).
First, we configure the "default" to be a very restrictive set of
features.
<Directory />
 Options FollowSymLinks
 AllowOverride None
 Order deny,allow
 Deny from all
 Satisfy all
</Directory>
Note that from this point forward you must specifically allow
particular features to be enabled - so if something's not working as
you might expect, make sure that you have specifically enabled it
below.
This should be changed to whatever you set DocumentRoot to.
<Directory "c:/apache/htdocs">
Possible values for the Options directive are "None", "All",
or any combination of:
Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
Note that "MultiViews" must be named explicitly --- "Options All"
doesn't give it to you.
The Options directive is both complicated and important. Please see
http://httpd.apache.org/docs/2.2/mod/core.html#options
for more information.
 Options Indexes FollowSymLinks
AllowOverride controls what directives may be placed in .htaccess files.
It can be "All", "None", or any combination of the keywords:
Options FileInfo AuthConfig Limit
 AllowOverride None
Controls who can get stuff from this server.
 Order allow,deny
 Allow from all
</Directory>
DirectoryIndex: sets the file that Apache will serve if a directory
is requested.
<IfModule dir_module>
 DirectoryIndex index.html
</IfModule>
The following lines prevent .htaccess and .htpasswd files from being
viewed by Web clients.
<FilesMatch "^\.ht">
 Order allow,deny
 Deny from all
</FilesMatch>
ErrorLog: The location of the error log file.
If you do not specify an ErrorLog directive within a <VirtualHost>
container, error messages relating to that virtual host will be
logged here. If you do define an error logfile for a <VirtualHost>
container, that host's errors will be logged there and not here.
ErrorLog logs/error.log
LogLevel: Control the number of messages logged to the error_log.
Possible values include: debug, info, notice, warn, error, crit,
alert, emerg.
LogLevel warn
<IfModule log_config_module>
The following directives define some format nicknames for use with
a CustomLog directive (see below).
 LogFormat "%h %l %u %t \"%r\" %>s %b \"%You need to enable mod_logio.c to use %I and %Oi\" \"%{User-Agent}i\"" combined
 LogFormat "%h %l %u %t \"%r\" %>s %b" common
 <IfModule logio_module>
 LogFormat "%h %l %u %t \"%r\" %>s %b \"%i\" \"%{User-Agent}i\" %I %O" combinedio
 </IfModule>
The location and format of the access logfile (Common Logfile Format).
If you do not define any access logfiles within a <VirtualHost>
container, they will be logged here. Contrariwise, if you do
define per-<VirtualHost> access logfiles, transactions will be
logged therein and not in this file.
 CustomLog logs/access.log common
If you prefer a logfile with access, agent, and referer information
(Combined Logfile Format) you can use the following directive.
 #CustomLog logs/access.log combined
</IfModule>
<IfModule alias_module>
Redirect: Allows you to tell clients about documents that used to
exist in your server's namespace, but do not anymore. The client
will make a new request for the document at its new location.
Example:
Redirect permanent /foo http://www.example.com/bar
Alias: Maps web paths into filesystem paths and is used to
access content that does not live under the DocumentRoot.
Example:
Alias /webpath /full/filesystem/path
If you include a trailing / on /webpath then the server will
require it to be present in the URL. You will also likely
need to provide a <Directory> section to allow access to
the filesystem path.
ScriptAlias: This controls which directories contain server scripts.
ScriptAliases are essentially the same as Aliases, except that
documents in the target directory are treated as applications and
run by the server when requested rather than as documents sent to the
client. The same rules about trailing "/" apply to ScriptAlias
directives as to Alias.
 ScriptAlias /cgi-bin/ "c:/apache/cgi-bin/"
</IfModule>
"c:/apache/cgi-bin" should be changed to whatever your ScriptAliased
CGI directory exists, if you have that configured.
<Directory "c:/apache/cgi-bin">
 AllowOverride None
 Options None
 Order allow,deny
 Allow from all
</Directory>
Apache parses all CGI scripts for the shebang line by default.
This comment line, the first line of the script, consists of the symbols
pound (#) and exclamation followed by the path of the program that
can execute this specific script. For a perl script, with perl.exe in
the C:\Program Files\Perl directory, the shebang line should be:
 #!c:/program files/perl/perl
Note you mustnot_ indent the actual shebang line, and it must be the
first line of the file. Of course, CGI processing must be enabled by
the appropriate ScriptAlias or Options ExecCGI directives for the files
or directory in question.
However, Apache on Windows allows either the Unix behavior above, or can
use the Registry to match files by extention. The command to execute
a file of this type is retrieved from the registry by the same method as
the Windows Explorer would use to handle double-clicking on a file.
These script actions can be configured from the Windows Explorer View menu,
'Folder Options', and reviewing the 'File Types' tab. Clicking the Edit
button allows you to modify the Actions, of which Apache 1.3 attempts to
perform the 'Open' Action, and failing that it will try the shebang line.
This behavior is subject to change in Apache release 2.0.
Each mechanism has it's own specific security weaknesses, from the means
to run a program you didn't intend the website owner to invoke, and the
best method is a matter of great debate.
To enable the this Windows specific behavior (and therefore -disable- the
equivilant Unix behavior), uncomment the following directive:
#ScriptInterpreterSource registry
The directive above can be placed in individual <Directory> blocks or the
.htaccess file, with either the 'registry' (Windows behavior) or 'script'
(Unix behavior) option, and will override this server default option.
DefaultType: the default MIME type the server will use for a document
if it cannot otherwise determine one, such as from filename extensions.
If your server contains mostly text or HTML documents, "text/plain" is
a good value. If most of your content is binary, such as applications
or images, you may want to use "application/octet-stream" instead to
keep browsers from trying to display binary files as though they are
text.
DefaultType text/plain
<IfModule mime_module>
TypesConfig points to the file containing the list of mappings from
filename extension to MIME-type.
 TypesConfig conf/mime.types
AddType allows you to add to or override the MIME configuration
file specified in TypesConfig for specific file types.
 #AddType application/x-gzip .tgz
AddEncoding allows you to have certain browsers uncompress
information on the fly. Note: Not all browsers support this.
 #AddEncoding x-compress .Z
 #AddEncoding x-gzip .gz .tgz
If the AddEncoding directives above are commented-out, then you
probably should define those extensions to indicate media types:
 AddType application/x-compress .Z
 AddType application/x-gzip .gz .tgz
AddHandler allows you to map certain file extensions to "handlers":
actions unrelated to filetype. These can be either built into the server
or added with the Action directive (see below)
To use CGI scripts outside of ScriptAliased directories:
(You will also need to add "ExecCGI" to the "Options" directive.)
 #AddHandler cgi-script .cgi
For type maps (negotiated resources):
 #AddHandler type-map var
Filters allow you to process content before it is sent to the client.
To parse .shtml files for server-side includes (SSI):
(You will also need to add "Includes" to the "Options" directive.)
 #AddType text/html .shtml
 #AddOutputFilter INCLUDES .shtml
</IfModule>
The mod_mime_magic module allows the server to use various hints from the
contents of the file itself to determine its type. The MIMEMagicFile
directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
Customizable error responses come in three flavors:
1) plain text 2) local redirects 3) external redirects
Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
EnableMMAP and EnableSendfile: On systems that support it,
memory-mapping or the sendfile syscall is used to deliver
files. This usually improves server performance, but must
be turned off when serving from networked-mounted
filesystems or if support for these functions is otherwise
broken on your system.
#EnableMMAP off
#EnableSendfile off
Supplemental configuration
The configuration files in the conf/extra/ directory can be
included to add extra features or to modify the default configuration of
the server, or you may simply copy their contents here and change as
necessary.
Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
Language settings
#Include conf/extra/httpd-languages.conf
User home directories
#Include conf/extra/httpd-userdir.conf
Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
Virtual hosts
#Include conf/extra/httpd-vhosts.conf
Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
Various default settings
#Include conf/extra/httpd-default.conf
Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
Note: The following must must be present to support
 starting without SSL on platforms with no /dev/random equivalent
 but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
ProxyPreserveHost On
ProxyVia on
ProxyTimeout 600
#disable forward-proxying
ProxyRequests Off
#proxy /irj both ways
ProxyPass /irj http://sapportal:50000/irj
ProxyPassReverse /irj http://sapportal:50000/irj
#ProxyPassReverse /irj http://testcomp/irj
#proxy /logon both ways
ProxyPass /logon http://sapportal:50000/logon
ProxyPassReverse /logon http://sapportal:50000/logon
#ProxyPassReverse /logon http://testcomp/logon

Apache and weblogic proxying not happening properly

Hi,
I am trying to proxy my request from my apache installation to weblogic installation.
I am able to proxy request to the default page of my application in weblogic.
But when trying to browse through that page I am getting error.
Basically, It tries to listen at 7501 port of my machine(apache machine) only
and is not trying to listen at 80 port of my machineso that it can be proxied
to the 7501 port of weblogic machine.
I am unable to figure out the issue. Maybe u can help me from ur experience.
I get an exception saying:
###<Apr 28, 2003 9:53:47 PM IST> <Warning> <Entitlements> <blrkec09630a> <portalServer>
<ExecuteThread: '10' for queue: 'default'> <kernel identity> <16:b7687ce40e05e9a9>
<402716> <Missing entitlments configuration asset.>
Exception[com.bea.p13n.rules.manager.RuleSetNotFoundException: The rule set with
URI /entitlements/GlobalEntitlements.rls could not be located by the class named
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.]
at com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.getRuleSet(RuleSetPersistenceManager.java:385)
at com.bea.p13n.rules.manager.internal.ContextPool.<init>(ContextPool.java:156)
at com.bea.p13n.rules.manager.internal.ContextPoolFactory.createContextPool(ContextPoolFactory.java:164)
at com.bea.p13n.rules.manager.internal.ContextPoolFactory.getContextPool(ContextPoolFactory.java:223)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.getContext(RulesManagerImpl.java:469)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.evaluate(RulesManagerImpl.java:350)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.evaluateRuleSet(RulesManagerImpl.java:148)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl_mcr6qe_EOImpl.evaluateRuleSet(RulesManagerImpl_mcr6qe_EOImpl.java:448)
at com.bea.p13n.entitlements.rolemapper.RoleMapper.mapRoles(RoleMapper.java:179)
at com.bea.p13n.entitlements.accesscontroller.AccessController.isAccessAllowed(AccessController.java:143)
at com.bea.portal.entitlement.util.EntitlementHelper.isAccessAllowed(EntitlementHelper.java:285)
at com.bea.portal.entitlement.util.EntitlementHelper.checkEntitlementInternal(EntitlementHelper.java:231)
at com.bea.portal.entitlement.util.EntitlementHelper.checkEntitlement(EntitlementHelper.java:144)
at com.bea.portal.manager.internal.UserPortalStatePolicy.checkPortletEntitlement(UserPortalStatePolicy.java:636)
at com.bea.portal.manager.internal.UserPortalStatePolicy.generateUserPageState(UserPortalStatePolicy.java:567)
at com.bea.portal.manager.internal.UserPortalStatePolicy.generateUserPortalState(UserPortalStatePolicy.java:293)
at com.bea.portal.manager.internal.PortalManagerDelegateImpl.getUserPortalState(PortalManagerDelegateImpl.java:179)
at com.bea.portal.manager.ejb.internal.PortalManagerBean.getUserPortalState(PortalManagerBean.java:70)
at com.bea.portal.manager.ejb.internal.PortalManagerBean_w6xny9_EOImpl.getUserPortalState(PortalManagerBean_w6xny9_EOImpl.java:370)
at com.bea.portal.appflow.internal.PortalRequestImpl.getPortalState(PortalRequestImpl.java:148)
at com.bea.portal.render.servlets.jsp.PortalRenderHelper.getSelectedSkin(PortalRenderHelper.java:167)
at jsp_servlet._framework._security.__login._jspService(login.inc:11)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:445)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:20)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.RequestDispatcherImpl$ForwardAction.run(RequestDispatcherImpl.java:345)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:252)
at com.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doGet(WebflowServlet.java:178)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWebflowServlet.java:235)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:20)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.tracking.clickthrough.ClickThroughEventFilter.doFilter(ClickThroughEventFilter.java:156)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5451)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
Regards,
Vinod Thapliyal

The WebLogic Server (WLS) is a Java container similar to OC4J in Application Server 10g release 2. If you want to use WLS, you will have to upgrade your Application Server 10g installation to Fusion Middleware 11g. The upgrade path typically depends on the products which you are using in 10g, e.g. the upgrade path for SOA is different than the upgrade path for Forms/Reports or Oracle Portal. The [url http://docs.oracle.com/cd/E23943_01/upgrade.1111/e10125/before_you_begin.htm]Upgrade Planning Guide is a good start.
Thanks,
EJ

IIS Plug for WLS 6.1 SP2: The specified procedure could not be found.

I get an the following error message "The specified procedure could not be
found." in my browser when trying to use the IIS-proxy plugin on WLS 6.1 sp2
Windows 2000
Has anyone else encountered this message? Any solutions?
Regards,
Jonas Klemming

Thank you for posting your answer, and then solution! :> I was fighting
with my IIS/WLS installation last night when I was about to give up, I came
across your posting. Although I'm playing with 7, I thought I would try
reading your posting anyways, and thankfully I did. What I saw, reminded me
to look at the steps one more time and I found I wasn't forwarding the
.wlforward piece on! So thank you veyr much! :>>>>
"Jonas Klemming" <[email protected]> wrote in message
news:[email protected]..
Fixed it.
I had mapped .wlforward to iisforward.dll instead of iisproxy.dll
/Jonas
"Jonas Klemming" <[email protected]> wrote in message
news:[email protected]..
I get an the following error message "The specified procedure could not
be
found." in my browser when trying to use the IIS-proxy plugin on WLS 6.1sp2
Windows 2000
Has anyone else encountered this message? Any solutions?
Regards,
Jonas Klemming

ERROR: Error from ejbc: in WLS 6.1 sp2 Win2K

Never had this problem before. Started new project using WLS 6.1 sp2 under Windows
2K Prof., using ANT & get;
ERROR: Error from ejbc:
In EJB NOTiFYEJB, method createUser defined in the remote interface either does
not exist in the bean class, or it is not a public method. Each method in the
remote interface must have a corresponding public method in the bean class.
BUILD FAILED
I saw a posting which referred to a problem with Win2K & an old (1.2) JDK in the
path. I have put C:\bea\jdk131 at the front of my class path but still get this
error.

The problem was nothing to do with classpaths etc.
CMP does not support "Date" types and in my EJB I had Date types, I changed these
to "long" and converted all Dates to number of milleseconds from 1970 and persisted
them to a number column in Oracle.
It was the entries in the weblogic-cmp-rdbms.xml which was the root of the problem.
"Roger Lee" <[email protected]> wrote:
>
Matthew,
Thanks for yor suggestions.
My classpath is set in the ANT.BAT & only points to the tools.jar, weblogic_sp.jar
& weblogic.jar.
I have my JARs in a manfest file in each directory with the "Class-Path:"
entry.
I have also added a new Bean with compiles & ejbcs fine. But I still
get an error
with my "createUser" method, saying the interface does not exist in the
bean class
or is not a public method.
I have even changed it's name to "createUserCandidate" just in case it
was clashing
with an existing method.
Any other ideas for investigation?
Thanks.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Roger Lee wrote:
The "warnings saying classes are being loaded from your classpath"are, I believe
just warning from Ant. I searched the newsgroups and it appears thatthis is not
a problem.These warnings are from ejbc. They are there to let you know that classes\interfaces
needed by your EJB are being loaded from your classpath and not your
jar. They
should be taken seriously. This could definitely be the cause of your
problem. As I
said in my previous posting, ejbc could be loading an old version of
your bean class
from your classpath. This old class may not contain the createUsermethod
with the
same signature as the method in your remote interface.
Is this an issue with WLS 6.1 sp2?I don't believe so.
I've wasted so much time on this any help would be appreciated.You essentially have three options.
1. Take my advice and make sure your classes are being loaded fromyour
jar and not
the classpath.
2. Post your entire jar so we can try to reproduce the problem.
3. Contact support.
- Matt
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Your bean and interface look fine. One thing you might try is explicitly
declaring
your createUser method to be public in your remote interface. I
don't
think this
will change the outcome but it's worth a try. When you run ejbcdo
you
get any
warnings saying classes are being loaded from your classpath ratherthan
your jar?
If this were the case, you could have an old copy of your bean inyour
classpath
that ejbc is picking up. If this doesn't help, I think the next
step
is to send me
or post your entire jar.
- Matt
Roger Lee wrote:
Typo that should have been "path", I had added "C:\bea\jdk131"
to
the
front of
my path & was getting the error.
Enclose my two classes in the attached file.
Thanks for you help.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Make sure you put C:\bea\jdk131 in front of your path (not classpath).
:) Assuming
this isn't the problem, can you please post any createUser method
declarations
in your
remote interface and the corresponding createUser methods in yourbean
class?
- Matt
Name: NOTiFY_&_NOTiFYBean.java
NOTiFY_&_NOTiFYBean.java Type: java/*
Encoding: base64

WLS 6.0 and Iplanet 4.1 proxy problems

Could someone confirm what is the latest version of IPlanet webserver
that is supported under WLS 6.0 SP2.
We are running under AIX 4.3.3 and have a Iplanet 4.0 sp4 webserver
running a connection to a backend WLS 6.0 sp2 instance also on AIX.
We are also running the libproxy_4x.so wl proxy file which allows us
to specify which IP in the obj.conf to have WLS 6.0 respond to vs. the
default ip on the server. The webserver runs on an aliased IP address
and due to firewall restrictions we must have WLS 6.0 talk back to the
IP that called the wl proxy. This does work correctly.
We have tried to duplicate this configuration under IPlanet 4.1 sp8
and we are getting the following errors with the wl proxy file:
[13/Oct/2001:03:42:15] failure (20564): for host x.x.x.x trying to GET
/testpath, wl-proxy reports: exception occurred for backend host
'x.x.x.x/6100': 'CONNECTION_REFUSED [os error=78, line 1282 of
URL.cpp]: x.x.x.x:6100'
This leads me to believe that it is the version of IPlanet server that
is causing the problem when it is calling the wl proxy. If someone is
running Iplanet 4.1 on AIX and using the wl proxy could you reply with
which service pack for Iplanet 4.1 works. We need to upgrade our
IPlanet to the latest version that will work with this configuration.
Any help would be appreciated.
Thanks,
Jamin Kumelski
Internet System Administrator
AdvancePCS

I have a question. Will WebLogic only listen to connections being
established from NES on the aliased IP? From what it looks like, with the
version of NES that you have, the NSAPI plugin is trying to establish a
connection to Weblogic on the primary IP, not the aliased IP.
There was a new feature added to the NES Plugin that allows you to bind the
plugin to a certain IP address in the case that you are using an IP Alias.
When the plugin makes a connection to WebLogic, it will first bind to the
specified IP address in the obj.conf.
The new parameter is: WLLocalIP.
I do believe the latest service pack for 6.1 (SP01) has the AIX plugin that
has this new parameter.
Regards,
Eric
BEA WebLogic
"Jamin Kumelski" <[email protected]> wrote in message
news:[email protected]...
Could someone confirm what is the latest version of IPlanet webserver
that is supported under WLS 6.0 SP2.
We are running under AIX 4.3.3 and have a Iplanet 4.0 sp4 webserver
running a connection to a backend WLS 6.0 sp2 instance also on AIX.
We are also running the libproxy_4x.so wl proxy file which allows us
to specify which IP in the obj.conf to have WLS 6.0 respond to vs. the
default ip on the server. The webserver runs on an aliased IP address
and due to firewall restrictions we must have WLS 6.0 talk back to the
IP that called the wl proxy. This does work correctly.
We have tried to duplicate this configuration under IPlanet 4.1 sp8
and we are getting the following errors with the wl proxy file:
[13/Oct/2001:03:42:15] failure (20564): for host x.x.x.x trying to GET
/testpath, wl-proxy reports: exception occurred for backend host
'x.x.x.x/6100': 'CONNECTION_REFUSED [os error=78, line 1282 of
URL.cpp]: x.x.x.x:6100'
This leads me to believe that it is the version of IPlanet server that
is causing the problem when it is calling the wl proxy. If someone is
running Iplanet 4.1 on AIX and using the wl proxy could you reply with
which service pack for Iplanet 4.1 works. We need to upgrade our
IPlanet to the latest version that will work with this configuration.
Any help would be appreciated.
Thanks,
Jamin Kumelski
Internet System Administrator
AdvancePCS

WLS 6.0 sp2 Apache fail to proxy request

Similar Messages

Maybe you are looking for