[
https://issues.apache.org/jira/browse/CXF-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed CXF-4416.
---------------------------
Resolution: Invalid
Again, please ask your questions on the CXF user's list, which has a healthy
number of WebLogic users who can quite possibly help you. (Blocked on External
is for CXF internal use only, and does not help you with your problem by
reducing the number of people reading it.) We can return to JIRA upon finding
a CXF bug. I would update to the latest CXF (2.6.1) if you can. I don't
personally have any more knowledge on WebLogic beyond my blog entry; someone
had mentioned to me that you might be using an obsolete (2.3.x) version of CXF,
which could be part of the problem.
> Compatability with weblogic 9.1
> -------------------------------
>
> Key: CXF-4416
> URL: https://issues.apache.org/jira/browse/CXF-4416
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5
> Environment: Java 1.5, Weblogic 9.1, CXF WS 2.5, Solaris 10 Webserver
> Reporter: sravan
> Priority: Critical
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> Is weblogic9.1 is compatible with CXF WS?
> Getting below exceptions continuously for certain time. I have deployed the
> app on 7001 port even though cxf is accepting requests on port 80[default
> port] which is not expected. Due to this it is reaching maximum heap
> utilization and application is timed out. Please suggest a way to resolve
> this.
> org.apache.cxf.transport.http.WSDLQueryException: Exception occurred while
> trying to process http://<IP>:80/extension?wsdl
> at
> org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:237)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:169)
> at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
> at
> weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
> at
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
> at
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
> at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
> at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
> at
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
> at
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
> at
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
