Win a copy of Penetration Testing Basics this week in the Security forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

IllegalArgumentException when invoking web service over https

Arun Narayanan
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
Im having some trouble figuring out this issue and I couldnt get much from google either. So wondering if its something really weird on my part or if there's something else going on. Here's the situation. I have a stateless session bean deployed as a webservice and I have BOTH .NET client and a java client invoking that. Everything works like a charm so far. But as soon as I turn on the Single Sign-On agent, weblogic throws this error when I try to access the same webservice method which worked fine w/o the Single Sign-On!

Root cause of ServletException>
java.lang.IllegalArgumentException: Illegal MimeHeader name or value
at javax.xml.soap.MimeHeaders.addHeader(Unknown Source)
at weblogic.webservice.binding.soap.HttpServerBinding.createMimeHeaders(
at weblogic.webservice.binding.soap.HttpServerBinding.receive(
at weblogic.webservice.core.DefaultWebService.invoke(
at weblogic.webservice.server.servlet.ServletBase.serverSideInvoke(
at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(
at weblogic.webservice.server.servlet.ServletBase.doPost(
at weblogic.webservice.server.servlet.WebServiceServlet.doPost(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at weblogic.servlet.internal.ServletStubImpl$
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(
at weblogic.servlet.internal.WebAppServletContext$
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(
at weblogic.servlet.internal.ServletRequestImpl.execute(
at weblogic.kernel.ExecuteThread.execute(
And I see an Internal Server Error (status code 500) in the response.
I did see one thing in the weblogic service pack updates though...
Calling a method in Web Service through the ISAPI filter causes this exception. And there it says that its been fixed in the WL 8.1 sp3 pack. But Im quite sure that there MUST be a WL 7.0 server using webservices and being called over HTTPS and SSO. Im not sure about the ISAPI part. But we DO have an apache http server filtering requests to weblogic.
Could anyone please throw some light into this? Again...another thing to note here. With SSO turned on, if I directly call the web service using IP address and weblogic port...that works fine too. But what I want is to be able to call the web service over SSO AND load-balanced url. Please help!!!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic