Weblogic.apache.xalan.xpath.dtm.DTMException:

Hi,
I got two different behaviors when trying to the XSLT processor:
1) When running the XSLT processor using the XSLT JSP tag, everything works
fine.
2) When running the XSLT process from a Java program, got the following
error:
weblogic.apache.xalan.xpath.dtm.DTMException:
at
weblogic.apache.xalan.xpath.dtm.DTMProxy.getChildNodes(DTMProxy.java:
255)
at com.agilesoft.common.BOMRollUp.getRollupPrice(BOMRollUp.java:42)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.apache.xalan.xpath.XSLTJavaClassEngine.callJava(XSLTJavaClas
sEngine.java:397)
at
weblogic.apache.xalan.xpath.XSLTJavaClassEngine.callFunction(XSLTJava
ClassEngine.java:668)
at
weblogic.apache.xalan.xpath.ExtensionFunctionHandler.callFunction(Ext
ensionFunctionHandler.java:282)
at
weblogic.apache.xalan.xpath.xml.XMLParserLiaisonDefault.extFunction(X
My XSL file contains Java extension to call a Java program where it needs to
call Element.getElementsByTagName() method,
which causes the DTMException.
I am using WebLogic 6.0sp2 on NT. Do I need to configure the default XSLT
parser when running
the processor from a Java program? Is it possible to get info. about the
XSLT JSP tags are executing
the XSLT processor?
Thanks,
Hien

Similar Messages

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

Apache/Xalan

I need to use the library org.apache.xalan.xpath for programming Xpath and XLS but the compiler dosen�t recognize the files. I have the jar Files but I'm not sure where to put then.

I'm not quite sure what you mean by "doesn't recognize them", but I'll toss in something that might help.
I have been working with Apache's Xerces package (XML SAX parsing), and had considerable trouble getting it working initially. I finally solved my problems by adjusting the order of my ClassPath. The problem was that Xerces jar files needed to be seen before the J2EE jar files.
Try putting the Xalan jar files in the front of your classpath, and see if that helps at all.
Good luck!

Memory leak in org.apache.xalan.trasnformer.TransformerImpl

I am using Xalan library, I notice there is a memory leak in org.apache.xalan.trasnformer.TransformerImpl class.
Every time I call transform(), the size of the instances grows and it won't reduce after garbage collection.
Does anyone experience the same thing? or do I miss anything when I use this class?

I just found out the transformer objects are supposed to be used for single transformation only.
If multiple transformations with same stylesheet is needed, we should create a Templates object and then for each transformation, create a transformer object by Templates.newTransformer().

WL10.3.3 Console Provider org.apache.xalan.processor.TransformerFactoryImp

Getting the following error:
An error occurred during activation of changes, please see the log for details.
[Management:141191]The prepare phase of the configuration update failed with an exception:
Provider org.apache.xalan.processor.TransformerFactoryImpl not found
Note: we have the FOP added to the domain as a shared library with the following libraries:
avalon-framework-cvs-20020806.jar
batik.jar
fop.jar
xalan-2.4.1.jar
xercesImpl-2.2.1.jar
xml-apis.jar
Note: Also, the shared libraries are not displaying referencing applications
Edited by: SK Jennings on Nov 9, 2010 10:25 AM
Added more info.

Hi,
I'm getting the same ClassCastException when I try to activate the changes of my EJB application. Were you able to resolve the error you were getting? Please let me know.
Thanks

WL 10.3.3 Console org.apache.xalan.processor.TransformerFactoryImpl not fou

Getting the following error:
An error occurred during activation of changes, please see the log for details.
[Management:141191]The prepare phase of the configuration update failed with an exception:
Provider org.apache.xalan.processor.TransformerFactoryImpl not found
Note: we have the FOP added to the domain as a shared library with the following libraries:
avalon-framework-cvs-20020806.jar
batik.jar
fop.jar
xalan-2.4.1.jar
xercesImpl-2.2.1.jar
xml-apis.jar
Note: Also, the shared libraries are not displaying referencing applications

Getting the following error:
An error occurred during activation of changes, please see the log for details.
[Management:141191]The prepare phase of the configuration update failed with an exception:
Provider org.apache.xalan.processor.TransformerFactoryImpl not found
Note: we have the FOP added to the domain as a shared library with the following libraries:
avalon-framework-cvs-20020806.jar
batik.jar
fop.jar
xalan-2.4.1.jar
xercesImpl-2.2.1.jar
xml-apis.jar
Note: Also, the shared libraries are not displaying referencing applications

Org.apache.xalan.transformer.TransformerImpl

I have an ecr.index servlet which is run on Tomcat, here is the part of it's code:
           javax.xml.transform.sax.SAXTransformerFactory factory = ( javax.xml.transform.sax.SAXTransformerFactory ) javax.xml.transform.TransformerFactory.newInstance();
           Source ss = new StreamSource( new FileInputStream( context.getRealPath( xsl_file ) ) );
           ss.setSystemId( context.getRealPath( xsl_file ) );
           javax.xml.transform.sax.TransformerHandler handler = factory.newTransformerHandler( ss );
       131:handler.setResult( new StreamResult( response.getOutputStream() ) );When I access the page the exception is thrown:
org.apache.xml.utils.WrappedRuntimeException: The output format must have a '{http://xml.apache.org/xalan}content-handler' property!
     at org.apache.xalan.serialize.SerializerFactory.getSerializer(SerializerFactory.java:142)
     at org.apache.xalan.transformer.TransformerImpl.createResultContentHandler(TransformerImpl.java:1048)
     at org.apache.xalan.transformer.TransformerImpl.createResultContentHandler(TransformerImpl.java:975)
     at org.apache.xalan.transformer.TransformerHandlerImpl.setResult(TransformerHandlerImpl.java:209)
     at ecr.index.service(index.java:131)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206)
     at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:339)
     at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:415)
     at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:716)
     at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:650)
     at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688)
     at java.lang.Thread.run(Thread.java:534)But I don't use org.apache.xalan.transformer.TransformerImpl, even the package org.apache.xalan.transformer isn't imported, but this package is present in classpath, where is the error?

Here is the reason for this problem....
JDK 1.4 comes with a version of Xalan...
Somewhere around 1.4.2_03 the Xalan version that shipped with the JDK was upgraded because the XSLT spec was completed/revised or something like that.. When this happend the namespace identifier for xalan custom 'tags' changed. The content-handler tag used to be in the xslt name space.. now it is in the xalan namespace.
Problem is many stylesheets don't specifically set the output format so the defaults are used and the values are initialized from a properties file. However.... and this is where the problems comes in...
The Namespaces are used as prefixes to the keys in the file... AND... Tomcat''s WebappClassLoader is not safe about ensuring that a resource is loaded from the same Jar file as the classes that use it....
So what is happening is... the Xalan from your JVM is being used... but it is loading the formatting properties from a Xalan that is included in your Webapp.... which of course don't match....
All you need to do is remove the xalanXXX.jar from WEB-INF/lib and this problem will go away...
Matt Brozowski
The OpenNMS Group, Inc...

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
          >
          >

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
          >
          >

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 bridge

Folks,
I read in the instructions for installing the weblogic-apache plugin
where you can use the plug-in so apache can serve the static pages and
the servlets and ejbs are routed to the weblogic server. Can we use a
configuration where just the ejb's are mapped to the weblogic server and
the html, jsp's and servlets are served by the apache server? It seems
logical that the ejb's could be located by finding the JNDI compliant
server, and the rest served by apache. Are there any folks out there
using an architecture where weblogic is used only for ejbs and the rest
is served by apache? Or are there specific restrictions on what gets
served where using apache and weblogic? Thanks for listening,
Dan McGowan
Millennia Vision Corporation
[email protected]
509.585.1379
pager: 877.460.9073
cell: 509.544.8184
[dmcgowan.vcf]

The problem in using the JSPs and servlets on the servlet engine
of the web server is, they can not use clustering/faliover facilities
that come with WebLogic server.
-Selvan Rajan
Michael Girdley wrote:
Yes, a minority of customers use another servlet engine/JSP engine in front
of Weblogic. Then, they rely upon EJB's that reside in WLS possibly on
another machine.
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Dan McGowan" <[email protected]> wrote in message
news:[email protected]..
Folks,
I read in the instructions for installing the weblogic-apache plugin
where you can use the plug-in so apache can serve the static pages and
the servlets and ejbs are routed to the weblogic server. Can we use a
configuration where just the ejb's are mapped to the weblogic server and
the html, jsp's and servlets are served by the apache server? It seems
logical that the ejb's could be located by finding the JNDI compliant
server, and the rest served by apache. Are there any folks out there
using an architecture where weblogic is used only for ejbs and the rest
is served by apache? Or are there specific restrictions on what gets
served where using apache and weblogic? Thanks for listening,
Dan McGowan
Millennia Vision Corporation
[email protected]
509.585.1379
pager: 877.460.9073
cell: 509.544.8184

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.

How can I Serialize the Object of org.apache.xalan.transformer.TransformerI

Teachers:
How can I Serialize the Object of org.apache.xalan.transformer.TransformerImpl.

org.apache.xalan.transformer.TransformerImpl doesn't appear to be serializable... what do you try to achieve?

Weblogic.apache.xalan.xpath.dtm.DTMException:

Similar Messages

Maybe you are looking for