We help IT Professionals succeed at work.

org.xml.sax.SAXException: Bad envelope tag:  html

Manish
Manish asked
on
8,728 Views
Last Modified: 2012-08-13
Hi,
  I am getting following exception in our application.
What would be reason? How to solve this?
Only change we did was we changed server url of actuate report.
It is giving exception when it is going through login flow.

 AxisFault
 faultCode: {http://xml.apache.org/axis/}Server.userException
 faultString: org.xml.sax.SAXException: Bad envelope tag:  html
 faultActor: null
 faultDetail:
      stackTrace: org.xml.sax.SAXException: Bad envelope tag:  html
      at org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:106)
      at org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:870)
      at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
      at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(Unknown Source)
      at org.apache.xerces.impl.XMLNamespaceBinder.startElement(Unknown Source)
      at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
      at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
      at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
      at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
      at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
      at javax.xml.parsers.SAXParser.parse(Unknown Source)
      at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:213)
      at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:457)
      at org.apache.axis.Message.getSOAPEnvelope(Message.java:362)
      at org.apache.axis.client.Call.invokeEngine(Call.java:2046)
      at org.apache.axis.client.Call.invoke(Call.java:2016)
      at org.apache.axis.client.Call.invoke(Call.java:1786)
      at org.apache.axis.client.Call.invoke(Call.java:1711)
      at org.apache.axis.client.Call.invoke(Call.java:1251)
Comment
Watch Question

Mick BarryJava Developer
CERTIFIED EXPERT
Top Expert 2010
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
ManishLead
CERTIFIED EXPERT

Author

Commented:
But we are providing him correct user id and password,
Mick BarryJava Developer
CERTIFIED EXPERT
Top Expert 2010

Commented:
could be something else causing it to return html.
you need to have a look at the details of the response, that should hopefully tell you the cause.

Lead
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Mick BarryJava Developer
CERTIFIED EXPERT
Top Expert 2010

Commented:
which may result in you getting html back, wouldn't it ;)

ManishLead
CERTIFIED EXPERT

Author

Commented:
ya object,
  But that is not 100 correct solution that y I am dividing it.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.