Weblogic - apache connector

          I am configuring Apache 2.0 - Weblogic server 8.1 on Linux. In this setup, Apache
          is the Web Server and Weblogic is the App Server. We are using the library "mod_wl_20.so"
          to connect Apache and Weblogic.
          Weblogic default port : 7001 Apache default port : 80
          After configuring this setup, the request are getting correctly routed through
          the apache server port. i.e. the URL http://localhost:80/gepam/jsp/test.jsp gets
          the proper request from weblogic.
          But at the sane time , we are also able to hit the site using the weblogic server
          port i.e. http://localhost:7001/gepam/jsp/test.jsp . We want to disable this weblogic
          web server port.
          Any clue on how to go about. Your valuable suggestion is highly appreciated.

Similar Messages

BEA Apache connector bug

I'd like to open a bug regarding the Apache connector. We first ran into it back in 7.0 and I just confirmed today it still exists in 8.1 (at least Apache 2.0/win32).
The bug is that the connector only forwards bodies for a subset of HTTP methods, so Webdav, for instance, is unusable via the connector.
For instance, the ACL method, RFC 3744, when sent to apache looks similar to
--- snip --
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: close
<?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:">
<D:ace>
<D:principal>
<D:href>xxx</D:href>
</D:principal>
<D:grant>
<D:privilege> <D:read/> </D:privilege>
</D:grant>
</D:ace>
</D:acl>
but the BEA connector forwards this to BEA as:
-- snip---
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: Keep-Alive
WL-Proxy-SSL: false
WL-PATH-TRIM: /
WL-Proxy-Client-IP: 127.0.0.1
Proxy-Client-IP: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-WebLogic-Force-JVMID: unset
... which of course times out since the body is not sent but CL is (correctly) specified.
We have to ship our product with a separate apache module which changes all methods to a POST, then stuffs the real method in a header. Then in our special servlet that we ship just for BEA, we extract the real method from the header and use it instead of the POST in the ServletRequest.
Can someone with karma at BEA file this bug? Other methods with bodies that I suspect will probably fail include OPTIONS, PROPPATCH, & PROPFIND. I also verified that arbitrary (ie non-RFC'd) http methods will fail to transmit a body as well.
Our last customer who used our application with BEA was supposed to open a bug about this via standard support means but I don't have any record of it ever being done.
Thanks,
Keith

Hi. Please send me an email address and I'll do what I can.
j
o
e
b
e
a
c
o
m
Keith Wannamaker wrote:
I'd like to open a bug regarding the Apache connector. We first ran into it back in 7.0 and I just confirmed today it still exists in 8.1 (at least Apache 2.0/win32).
The bug is that the connector only forwards bodies for a subset of HTTP methods, so Webdav, for instance, is unusable via the connector.
For instance, the ACL method, RFC 3744, when sent to apache looks similar to
--- snip --
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: close
<?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:">
<D:ace>
<D:principal>
<D:href>xxx</D:href>
</D:principal>
<D:grant>
<D:privilege> <D:read/> </D:privilege>
</D:grant>
</D:ace>
</D:acl>
but the BEA connector forwards this to BEA as:
-- snip---
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: Keep-Alive
WL-Proxy-SSL: false
WL-PATH-TRIM: /
WL-Proxy-Client-IP: 127.0.0.1
Proxy-Client-IP: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-WebLogic-Force-JVMID: unset
... which of course times out since the body is not sent but CL is (correctly) specified.
We have to ship our product with a separate apache module which changes all methods to a POST, then stuffs the real method in a header. Then in our special servlet that we ship just for BEA, we extract the real method from the header and use it instead of the POST in the ServletRequest.
Can someone with karma at BEA file this bug? Other methods with bodies that I suspect will probably fail include OPTIONS, PROPPATCH, & PROPFIND. I also verified that arbitrary (ie non-RFC'd) http methods will fail to transmit a body as well.
Our last customer who used our application with BEA was supposed to open a bug about this via standard support means but I don't have any record of it ever being done.
Thanks,
Keith

WebLogic Apache bridge problems on uploading large files via HTTP post

I have a problem uploading files larger than quarter a mega, the jsp
page does a POST
to a servlet which reads the input stream and writes to a file.
Configuration: Apache webserver 1.3.12 connected to the Weblogic 5.1
application server
via the bridge(mod_wl_ssl.so) from WebLogic Service pack 4.
The upload goes on for about 30 secs and throws the following error.
"Failure of WebLogic APACHE bridge:
IO error writing POST data to 100.12.1.2:7001; sys err#: [32] sys err
msg [Broken pipe]
Build date/time: Jul 10 2000 12:29:18 "
The same upload(in fact I uploaded a 8 MEG file) using the
Netscape(NSAPI) WebLogic
connector.
Any answers would be deeply appreciated.

I have a problem uploading files larger than quarter a mega, the jsp
page does a POST
to a servlet which reads the input stream and writes to a file.
Configuration: Apache webserver 1.3.12 connected to the Weblogic 5.1
application server
via the bridge(mod_wl_ssl.so) from WebLogic Service pack 4.
The upload goes on for about 30 secs and throws the following error.
"Failure of WebLogic APACHE bridge:
IO error writing POST data to 100.12.1.2:7001; sys err#: [32] sys err
msg [Broken pipe]
Build date/time: Jul 10 2000 12:29:18 "
The same upload(in fact I uploaded a 8 MEG file) using the
Netscape(NSAPI) WebLogic
connector.
Any answers would be deeply appreciated.

TransformerException -- possible bug in weblogic.apache.xalan.transformer.TransformerImpl

Using WebLogic Server 6.1 SP2. Am using xslt to transform xml into html. After
repeatedly
using the same Transformer object to transform different xml documents, the Transformer
eventually becomes corrupt – sometimes after 20 or so transforms, sometimes only
after
thousands.
Once the Transformer object becomes corrupt, any additional attempt to call the
transform
method results in the following exception:
=============================
javax.xml.transform.TransformerException: -1
at weblogic.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1248)
at weblogic.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:483)
at weblogic.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1153)
at … <snip>
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at weblogic.apache.xml.utils.NodeVector.popQuick(NodeVector.java:247)
at weblogic.apache.xpath.XPathContext.popCurrentNode(XPathContext.java:552)
at weblogic.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2100)
at weblogic.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1225)
at … <snip>
=============================
Using cavaj to decompile weblogic.apache.xalan.transformer.TransformerImpl yields:
Method: applyTemplateToNode:
try
pushElemTemplateElement(elemtemplateelement1);
m_xcontext.pushCurrentNode(node);
     <snip>
catch(SAXException saxexception)
throw new TransformerException(saxexception);
finally
m_xcontext.popCurrentNode();
     <snip>
So what appears to be happening is that one of the two push calls at the beginning
of the try
block is throwing an Exception, causing the pop method to be called in the finally
block without
first having had a successful call to push. The corresponding NodeVector inside
m_xcontext
thereupon becomes corrupt, and it is only a matter of time before the above
ArrayIndexOutOfBoundsException appears.
Unfortunately, we are unable to consistently reproduce this Transformer corruption
and
currently have no idea how it happens in the first place. We figure there’s probably
some sort
of error in our xsl stylesheet which is at the root of all this, but have had
no luck in finding it.
So, two questions:
1.) Has anyone encountered this problem of having a bad xsl stylesheet which,
when applied
repeatedly on certain xml documents, can cause the Transformer to become corrupt
as a result
of calling NodeVector.pop without a corresponding call to NodeVector.push? If
so, do you have
a simple example of the type of xsl template and/or xml document which might reproduce
the
scenario.
2.) Would not the above code snippet in TransformerImpl be considered buggy in
any case,
since it should not be possible for an invalid xsl stylesheet to permanently corrupt
the
Transformer? If there’s agreement that this represents a bug in TransformerImpl,
has it been
fixed in 6.1 SP3 or higher, or in subsequent versions of the Weblogic Server?
Thanks,
John

hi,
I've just recently started getting this error too. It's completely random as
to when it occurs. My system can process hundreds of translations with no problems
and then once and awhile I get this exact error.
I'm using WebLogic v7.0 sp2. I've noticed however that this only happens on my
Windows system - I've got it running on a solairs box with no problems.
Has anyone else seen this ?
Thanks.
Jerry
"John Lame" <[email protected]> wrote:
>
Using WebLogic Server 6.1 SP2. Am using xslt to transform xml into html.
After
repeatedly
using the same Transformer object to transform different xml documents,
the Transformer
eventually becomes corrupt – sometimes after 20 or so transforms, sometimes
only
after
thousands.
Once the Transformer object becomes corrupt, any additional attempt to
call the
transform
method results in the following exception:
=============================
javax.xml.transform.TransformerException: -1
at weblogic.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1248)
at weblogic.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:483)
at weblogic.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1153)
at … <snip>
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at weblogic.apache.xml.utils.NodeVector.popQuick(NodeVector.java:247)
at weblogic.apache.xpath.XPathContext.popCurrentNode(XPathContext.java:552)
at weblogic.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2100)
at weblogic.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1225)
at … <snip>
=============================
Using cavaj to decompile weblogic.apache.xalan.transformer.TransformerImpl
yields:
Method: applyTemplateToNode:
try
pushElemTemplateElement(elemtemplateelement1);
m_xcontext.pushCurrentNode(node);
     <snip>
catch(SAXException saxexception)
throw new TransformerException(saxexception);
finally
m_xcontext.popCurrentNode();
     <snip>
So what appears to be happening is that one of the two push calls at
the beginning
of the try
block is throwing an Exception, causing the pop method to be called in
the finally
block without
first having had a successful call to push. The corresponding NodeVector
inside
m_xcontext
thereupon becomes corrupt, and it is only a matter of time before the
above
ArrayIndexOutOfBoundsException appears.
Unfortunately, we are unable to consistently reproduce this Transformer
corruption
and
currently have no idea how it happens in the first place. We figure
there’s probably
some sort
of error in our xsl stylesheet which is at the root of all this, but
have had
no luck in finding it.
So, two questions:
1.) Has anyone encountered this problem of having a bad xsl stylesheet
which,
when applied
repeatedly on certain xml documents, can cause the Transformer to become
corrupt
as a result
of calling NodeVector.pop without a corresponding call to NodeVector.push?
If
so, do you have
a simple example of the type of xsl template and/or xml document which
might reproduce
the
scenario.
2.) Would not the above code snippet in TransformerImpl be considered
buggy in
any case,
since it should not be possible for an invalid xsl stylesheet to permanently
corrupt
the
Transformer? If there’s agreement that this represents a bug in TransformerImpl,
has it been
fixed in 6.1 SP3 or higher, or in subsequent versions of the Weblogic
Server?
Thanks,
John

Java.lang.NoSuchMethodError at at weblogic.apache.xpath.DOM2Helper.getNamespaceOfNode(DOM2Helper.java:356)

I am getting this xml parser error after migrating to weblogic7.0 from wl 6.1
I am using the sax parser. I am using the jaxp.jar and xalan.jar for compilation
as well as running the application. However I am also using the weblogic.jar for
compilation and runtime in the classpath. I am wandering if there are any changes
to the version of SAX parser which weblogic 7.0 is using. Does anybody has any
idea..
Thanks,
This is the error which I am getting on the server.
java.lang.NoSuchMethodError
at weblogic.apache.xpath.DOM2Helper.getNamespaceOfNode(DOM2Helper.java:356)
at weblogic.apache.xml.utils.TreeWalker.startNode(TreeWalker.java:366)
at weblogic.apache.xml.utils.TreeWalker.traverse(TreeWalker.java:190)
at weblogic.apache.xalan.processor.TransformerFactoryImpl.processFromNode(TransformerFactory
Impl.java:232)
at weblogic.apache.xalan.processor.TransformerFactoryImpl.processFromNode(TransformerFactory
Impl.java:331)
at weblogic.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImp
l.java:875)
at weblogic.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryI
mpl.java:757)
at weblogic.xml.jaxp.WebLogicTransformerFactory.newTransformer(WebLogicTransformerFactory.ja
va:195)
at weblogic.xml.jaxp.RegistryTransformerFactory.newTransformer(RegistryTransformerFactory.ja

The version of the xalan in weblogic7.0 is 2.2 transformer.
You can refer to the following upgrade guide.
Ajay
"sameer" <[email protected]> wrote in message
news:3e78d50e$[email protected]..
>
I am getting this xml parser error after migrating to weblogic7.0 from wl6.1
I am using the sax parser. I am using the jaxp.jar and xalan.jar forcompilation
as well as running the application. However I am also using theweblogic.jar for
compilation and runtime in the classpath. I am wandering if there are anychanges
to the version of SAX parser which weblogic 7.0 is using. Does anybody hasany
idea..
Thanks,
This is the error which I am getting on the server.
java.lang.NoSuchMethodError
atweblogic.apache.xpath.DOM2Helper.getNamespaceOfNode(DOM2Helper.java:356)
atweblogic.apache.xml.utils.TreeWalker.startNode(TreeWalker.java:366)
atweblogic.apache.xml.utils.TreeWalker.traverse(TreeWalker.java:190)
atweblogic.apache.xalan.processor.TransformerFactoryImpl.processFromNode(Trans
formerFactory
Impl.java:232)
atweblogic.apache.xalan.processor.TransformerFactoryImpl.processFromNode(Trans
formerFactory
Impl.java:331)
atweblogic.apache.xalan.processor.TransformerFactoryImpl.newTemplates(Transfor
merFactoryImp
l.java:875)
atweblogic.apache.xalan.processor.TransformerFactoryImpl.newTransformer(Transf
ormerFactoryI
mpl.java:757)
atweblogic.xml.jaxp.WebLogicTransformerFactory.newTransformer(WebLogicTransfor
merFactory.ja
va:195)
atweblogic.xml.jaxp.RegistryTransformerFactory.newTransformer(RegistryTransfor
merFactory.ja

CF10 64bit Apache connector (mod_jk.so) does not work for Apache2.4.3 (windows)

CF10 64bit Apache connector (mod_jk.so) does not work for Apache2.4.3 (win64), where can I get a module that works?
I get this error from Apache :
C:\www\Apache2.4\bin>httpd -t
httpd: Syntax error on line 741 of C:/www/Apache2.4/conf/httpd.conf: Syntax error on line 2 of C:/www/Apache2.4/conf/mod_jk.conf: Cannot load C:\\ColdFusion10\\config\\wsconfig\\1\\mod_jk.so into server: The specified procedure could not be found.
I have already tried manually extracting the pre-built mod_jk22.so from the wsconfig.jar with same results.
If I switch to Apache 2.2.22 64bit, it does work. what I need is to be able to run on Apache 2.4.

Please check out this link.
http://rob.brooks-bilson.com/index.cfm/2012/2/21/Installing-ColdFusion-10-with-Apache-on-W indows
In this link, they are configuring with Apache 2.2 only.
When we were working colfusion 9 with Linux and apache, we had the same problem, it will work when it connect to Apache 2.0 but not with Apache 2.2 version.

WebLogic Apache Plug-in

I've just read about the WebLogic Apache plug-in that's new in 5.1 :-)
          Am I right to assume that this plug-in only works for Apache running on
          Solaris? :-(
          I'm running Apache (Stronghold actually) on Linux and I need to use this to
          proxy JSP request to my Weblogic Servers running on Solaris - any thoughts?
          Ken


          We will be making a port of the plug-in in the future. You should contact
          your account manager who can supply the full details.
          Thanks,
          Michael Girdley
          WLS Product Manager
          Ken <kenw{noSpam]@lostwax.com> wrote in message
          news:8cej50$dsu$[email protected]..
          > I've just read about the WebLogic Apache plug-in that's new in 5.1 :-)
          >
          > Am I right to assume that this plug-in only works for Apache running on
          > Solaris? :-(
          >
          > I'm running Apache (Stronghold actually) on Linux and I need to use this
          to
          > proxy JSP request to my Weblogic Servers running on Solaris - any
          thoughts?
          >
          > Ken
          >
          >

JRUN Apache connector not timing out despite setting recvTimeout

Hi,
       I have set a recvTimeout for the JRUN apache connector using the
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480]     ap_escape_uri(TimeoutTest.cfm) = TimeoutTest.cfm
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480] jrun_trans: sub-request so DECLINED
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480]     getRealPath(TimeoutTest.cfm) = TimeoutTest.cfm
[Thu Dec 15 15:29:48 2011] [notice] jrApache[3068: 20480] sent/avail/result 79/79/79
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] PROXY_GET_HEADER <- [11]
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] read/len/total 21/21/21
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480]     HTTP_X_REQUESTED_WITH: <null>
[Thu Dec 15 15:29:53 2011] [notice] jrApache[3068: 20480] sent/avail/result 4/4/4
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 jrConnect [9]
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] sent/avail/result 4/4/4
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 is reachable
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] sent/avail/result 4/4/4
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 is reachable
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] 67.206.10.197:51050 returned socket [9] to pool
[Thu Dec 15 15:34:53 2011] [notice] jrApache[3068: 20480] jrRecv [11] timeout but server reachable so recv again
[Thu Dec 15 15:36:33 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
[Thu Dec 15 15:36:33 2011] [notice] jrApache[3068: 20480] PROXY_GET_REALPATH <- [11]
[Thu Dec 15 15:36:33 2011] [notice] jrApache[3068: 20480] read/len/total 4/4/4
What does this error mean: jrRecv [11] timeout but server reachable so recv again
Is the jrun apache connector retrying or waiting some more for the page response ? I dont want it to retry / wait beyond the recvTimeout that I have set. What can I do in the config or elsewhere so that the recvTimeout returns as a timeout to apache and cleint without recv again attempt that it appears to be doing?
Thanks in advance for any help on this.
JRunConfig RecvTimeout 300
        I want this setting so long running pages will time out and return after 300 s with a timeout error and return the error back to the client.
However, I see that the timeout is not working and long running cfm pages continue to cycle without returning. Upon enabling the verbose option I see the following error logged for the long running page after the timeout occurs, but the page does not return anything and continues to wait on the client side.

sunilr1 wrote:
Hi,
       I have set a recvTimeout for the JRUN apache connector using the
JRunConfig RecvTimeout 300
        I want this setting so long running pages will time out and return after 300 s with a timeout error and return the error back to the client.
That is not the setting to time out long-running pages and then return a message. Why would you want to control request timeouts from JRun anyway? I don't think it's a good idea.
RecvTimeout determines how long to wait before timing out a socket receive call on a JRun server. The receive call is generally a synchronous call on a socket on a JRun server. It will throw an exception if the time out period is exceeded. In other words, a long-running page does not necessarily imply a long wait on a socket receive call.

Can't configure Apache connector

I've tried this on Fedora Core 9 with no success and now I'm
trying it on FC8 with the same error. After installing CF and
configuring it to work with Apache, I go to start it and I get
quote:
[root@ns1 ~]# /opt/coldfusion8/bin/coldfusion start
Starting ColdFusion 8...
The ColdFusion 8 server is starting up and will be available
shortly.
======================================================================
Running the ColdFusion 8 connector wizard
======================================================================
Configuring the web server connector (Launched on the first
run of the ColdFusion 8 start script)
Running apache connector wizard...
=======================================
There was an error while running the connector wizard
Connector installation was not successful
=======================================
======================================================================
ColdFusion 8 has been started.
ColdFusion 8 will write logs to
/opt/coldfusion8/logs/cfserver.log
======================================================================
I changed the paths in the 'apache-connector.sh' file, but I
still can't get it to work. Any ideas?

Ok, this is from this morning when trying:
07/25 09:05:39 info Macromedia JRun 4.0 (Build 108487)
07/25 09:05:40 debug Found JRun server coldfusion at
127.0.0.1:2930
07/25 09:05:40 debug Deleted directory
/opt/coldfusion8/runtime/lib/wsconfig/1/.libs
07/25 09:05:40 debug Deleted directory
/opt/coldfusion8/runtime/lib/wsconfig/1
07/25 09:05:40 info Fedora release 9 (Sulphur)
07/25 09:05:40 debug Using Apache binary /usr/sbin/httpd
07/25 09:05:40 info Server's Module Magic Number:
20051115:11. Supported major magic numbers on this platform are
20020628 and 20020903.
07/25 09:05:40 info Attempting to build connector from
sources
07/25 09:05:40 info Server version: Apache/2.2.8 (Unix)
07/25 09:05:40 debug Using Apache control script
/usr/sbin/httpd
07/25 09:05:40 debug Parsing Apache configuration file
/etc/httpd/conf/httpd.conf
07/25 09:05:40 debug Exec'ing chmod 777
/opt/coldfusion8/runtime/lib/wsconfig/1
07/25 09:05:40 debug Set permission to 777 on
/opt/coldfusion8/runtime/lib/wsconfig/1
07/25 09:05:40 debug Exec'ing chmod +x
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22
07/25 09:05:40 debug Set permission to execute on
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22
07/25 09:05:40 debug Exec'ing
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22
07/25 09:05:41 error Error running
"/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22": exit code
was 1
07/25 09:05:41 error Could not build Apache2 web server
connector from source. Use build script /opt/coldfusion8/
runtime/lib/wsconfig/1/build_jrun22.
jrunx.connectorinstaller.ConnectorInstallerException: Could
not build Apache2 web server connector from source. U
se build script
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22.
at
jrunx.connectorinstaller.ApacheInstaller.buildModuleFromSource(ApacheInstaller.java:1234)
at
jrunx.connectorinstaller.ApacheInstaller.copyFiles(ApacheInstaller.java:1126)
at
jrunx.connectorinstaller.ApacheInstaller.installConnector(ApacheInstaller.java:223)
at
jrunx.connectorinstaller.ConnectorInstaller.installConnector(ConnectorInstaller.java:337)
at
jrunx.connectorinstaller.ConnectorInstaller.doIt(ConnectorInstaller.java:271)
at
jrunx.connectorinstaller.ConnectorInstaller.main(ConnectorInstaller.java:759)

Apache connector

Does anyone know where I can get the gxapache connector DLL for win32?
This is getting kind of urgent as we really need to switch from the
(dangerous) IIS4 as the web server.
I find information on it in release notes, but I can't find the actual file
anyway.
PS I am using NAS4.0 at present, but I think the connector is pretty much
unchanged since then.

There is no Apache connector for NAS4. Apache is a new connector with sp3.
(I'd recommend iWS anyway.)
David
Michael Neale wrote:
Does anyone know where I can get the gxapache connector DLL for win32?
This is getting kind of urgent as we really need to switch from the
(dangerous) IIS4 as the web server.
I find information on it in release notes, but I can't find the actual file
anyway.
PS I am using NAS4.0 at present, but I think the connector is pretty much
unchanged since then.

How to configure Weblogic Tuxedo Connector ?

Hi:
I have 2 machines. One machine "A" installed with BEA TUXEDO 8.0 software.
The other machine "B" doesn't have BEA TUXEDO 8.0 software but it has BEA WebLogic
Server 6.1
installed.
My desire is to be able to make a successful application using WebLogic Tuxedo
Connector from the machine "B" to machine "A".
I have tried to follow the instruction for the WebLogic Tuxedo Connector example.
However, I wasn't able to make the application work. I am suspecting that
I must have BEA TUXEDO 8.0 software installed into machine "B" in order to make
it work. Am I right or wrong?

Khanh,
You don't need Tuxedo installed on the same machine as WLS to use WTC.
Your problem must be caused by some error in your configuration, either
in the dmconfig on the Tuxedo side, or the xml config on the WTC side.
I think you will need to post more detail to get any further help.
Regards,
Peter.
Khanh Mai wrote:
Hi:
I have 2 machines. One machine "A" installed with BEA TUXEDO 8.0 software.
The other machine "B" doesn't have BEA TUXEDO 8.0 software but it has BEA WebLogic
Server 6.1
installed.
My desire is to be able to make a successful application using WebLogic Tuxedo
Connector from the machine "B" to machine "A".
I have tried to follow the instruction for the WebLogic Tuxedo Connector example.
However, I wasn't able to make the application work. I am suspecting that
I must have BEA TUXEDO 8.0 software installed into machine "B" in order to make
it work. Am I right or wrong?

Error loading weblogic apache plug-in

HPUX11i
Apache 2.0.55
WebLogic 8.13
I am following the instructions on how to configure the Weblogic Apache plug-in:
http://e-docs.bea.com/wls/docs81/plugins/apache.html#119517
When I attempt to verify the syntax of the http.conf or attempt to start apache, I get the following error:
/usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage:
/usr/lib/libcl.2
/usr/lib/dld.sl: Exec format error
Syntax error on line 247 of /usr/local/apache2/conf/httpd.conf:
Cannot load /usr/local/apache2/modules/mod_wl_20.so into server: Exec format error
Any ideas on how to fix this?
Thanks.

          We will be making a port of the plug-in in the future. You should contact
          your account manager who can supply the full details.
          Thanks,
          Michael Girdley
          WLS Product Manager
          Ken <kenw{noSpam]@lostwax.com> wrote in message
          news:8cej50$dsu$[email protected]..
          > I've just read about the WebLogic Apache plug-in that's new in 5.1 :-)
          >
          > Am I right to assume that this plug-in only works for Apache running on
          > Solaris? :-(
          >
          > I'm running Apache (Stronghold actually) on Linux and I need to use this
          to
          > proxy JSP request to my Weblogic Servers running on Solaris - any
          thoughts?
          >
          > Ken
          >
          >

Coldfusion 8 /Apache Connector Bug??????

I have wasted almost 3 weeks now on this problem. It will
cost us $500 to get a answer if this is a bug on Coldfusion 8.
Almost ready to jump this ship and go to the Open source camp!
Install went fine.
Running Red Hat 4AES
Apache 2.0
ColdFusion 8
I rebuilt the connector about 10 times now....using
the following document
http://kb.adobe.com/selfservice/viewContent.do?externalId=121a0b29&sliceId=2
when I try to start Coldfusion I get the following error....
The ColdFusion 8 server is starting up and will be available
shortly.
======================================================================
Running the ColdFusion 8 connector wizard
======================================================================
Configuring the web server connector (Launched on the first
run of the ColdFusion 8 start script)
Running apache connector wizard...
=======================================
There was an error while running the connector wizard
Connector installation was not successful
=======================================
======================================================================
ColdFusion 8 has been started.
ColdFusion 8 will write logs to
/usr/coldfusion8/logs/cfserver.log

Could use similar assistance with our CF8 Standard upgrade.
I have spent a week trying to upgrade our dedicated server
from CFMX7 to CF8 with no success. I submitted an Adobe support
request ticket (Case #0180044098) about five days ago, but am still
waiting for them to help me resolve the problem. Thought I would
post this in case someone can offer assistance while I am waiting
for the Adobe school solution.
Our server configuration is as follows:
-- LINUX version: REDHAT Enterprise 4 i686 on standard - WHM
X v3.1.0
-- Apache version: 2.0.63
-- MySQL version: 5.0.45-community
-- PHP version: 5.2.5
-- WebHost Manager: version 11.15.0
-- cPanel Version: 11.18.1-RELEASE, cPanel Build: 20683
Here is what I have done most recently:
(1) Uninstalled CF8 (for about the fourth time).
(2) Deleted /opt/coldfusionmx7 and /opt/coldfusion8
directories.
(3) Restarted Apache, ensured the httpd-devel version of
Apache was installed.
(4) Reinstalled CF8 (for about the 5th time); it is running
and appears to have installed successfully (except for Apache
connectors).
(5) Modified
/opt/coldfusion8/bin/connectors/apache_connector.sh as follows:
../../runtime/bin/wsconfig \
-server coldfusion \
-ws apache \
-dir /etc/httpd/conf \
-bin /usr/local/apache/bin/httpd \
-script /usr/local/apache/bin/apachectl \
-coldfusion
(6) Ran ./wsconfig -uninstall to remove old/incorrect
connectors.
(7) Ran ./wsconfig per the information below which indicated
that JRun Apache connector install was successful.
Here are the results of running the ./wsconfig ...
[root@_______ bin]# ./wsconfig -uninstall
[Wed Mar 05 01:15:06 2008] [warn] NameVirtualHost *:80 has no
VirtualHosts
Restarted Apache server
The Apache connector was removed from /etc/httpd/conf
[root@_______ bin]# ./wsconfig -server coldfusion -ws Apache
-dir /etc/httpd/conf -bin /usr/local/apache/bin/httpd -script
/usr/local/apache/bin/apachectl -coldfusion -v
Found JRun server coldfusion at 127.0.0.1:2930
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using Apache binary /usr/local/apache/bin/httpd
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Using Apache control script /usr/local/apache/bin/apachectl
Parsing Apache configuration file /etc/httpd/conf/httpd.conf
Exec'ing chmod 777 /opt/coldfusion8/runtime/lib/wsconfig/1
Set permission to 777 on
/opt/coldfusion8/runtime/lib/wsconfig/1
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Exec'ing chmod +x
/opt/coldfusion8/runtime/lib/wsconfig/1/mod_jrun20.so
Set permission to execute on
/opt/coldfusion8/runtime/lib/wsconfig/1/mod_jrun20.so
Created file
/opt/coldfusion8/runtime/lib/wsconfig/1/mod_jrun20.so
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Wrote file /etc/httpd/conf/httpd.conf
Added JRun configuration to Apache configuration file
/etc/httpd/conf/httpd.conf
Created file
/opt/coldfusion8/runtime/lib/wsconfig/1/README.txt
Wrote file
/opt/coldfusion8/runtime/lib/wsconfig/wsconfig.properties
Exec'ing /usr/local/apache/bin/apachectl restart
[Wed Mar 05 01:21:18 2008] [warn] NameVirtualHost *:80 has no
VirtualHosts
Restarted Apache server
The Apache connector was installed to /etc/httpd/conf
[root@_______ bin]#
Although everything appears to have installed correctly, our
server and website will still not recognize or process .cfm files.
So I am still unable to even access CF8 Administrator and our site
will not process Coldfusion files, just asks me, "Do you want to
save this file, or find a program online to open it?"
Never had any problems with CFMX7 install or operation, so
this is most disconcerting.
I am not a happy camper.
Any suggestions while I am waiting for my Adobe customer
support ticket to be answered will be most appreciated.
Thanks.

About Weblogic-Apache plugin for windows NT

Is there windows NT version of WEBLOGIC-APACHE Plugin? If so where can we get the details about the product?

Last time I checked, the NT version of Apache was still an alpha (or
beta???) release. I believe that we have plans to support this once the NT
version is no longer in alpha/beta status...
Mike Reiche wrote:
I am 93% sure there is no such plug-in available.
Mike
Sairam Krishnaswamy <[email protected]> wrote:
Is there windows NT version of WEBLOGIC-APACHE Plugin? If so where can
we get the details about the product?

Different error messages for Weblogic-Apache bridge

We are running WLS 5.1 sp5 with Apache as Webserver.
I want to know how could I display more user freindly error messages when
weblogic is down and apache is working. Currently we get the default
Weblogic-Apache down page.
Thanks,
Rakesh

We used this but it did not work. Now the default does not show up but it is
not able to find the url that we specify which is reachable if I directly
use in the brower.
"Vinod Mehra" <[email protected]> wrote in message
news:[email protected]..
Checkout the plugin param "ErrorPage" in our documentation.
--Vinod.
Rakesh Gupta wrote:
We are running WLS 5.1 sp5 with Apache as Webserver.
I want to know how could I display more user freindly error messages
when
weblogic is down and apache is working. Currently we get the default
Weblogic-Apache down page.
Thanks,
Rakesh

Weblogic - apache connector

Similar Messages

Maybe you are looking for