DFS 6.5 SP1 remote access issue with Weblogic 10.3.

I got a requirement where in my client application reside on Oracle Weblogic 10.3 server. Need to make DFS web service call from my application. I tried loading DFS on Weblogic, it fails later found that weblogic 10.3 does not support DFS 6.5 SP1. This was wrongly documented in release notes. I am now trying to access DFS service hosted on method server, the call fails. Whereas the same code is working when I tried to access the service from tomcat server and Jboss server hosted on a different machine. Please let me know whether remote accessing of service from weblogic 10.3 is also not supported?

Given below is the error that occurs in weblogic when trying to remotely access service(DFS) hosted on jboss method server..

####<Aug 24, 2009 11:14:17 AM UTC> <Error> <HTTP> <HDHCBSDTDL0259> <AdminServer> <[ACTIVE] ExecuteThread: '5'for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1251112457908> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@a13ea6 - appName: 'dfsWebApp', name: 'dfsWebApp.war', context-path: '/dfsWebApp', spec-version: '2.5', request: weblogic.servlet.internal.ServletRequestImpl@1d2af80[

POST /dfsWebApp/DfsDeleteSubmittal HTTP/1.1

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.13) Gecko/2009073022 Firefox/3.0.13

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Accept-Language: en-us,en;q=0.5

Accept-Encoding: gzip,deflate

Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7

Keep-Alive: 300

Connection: keep-alive

Referer: http://**.**.**.**:7001/dfsWebApp/deleteObject.html

Cookie: JSESSIONID=pSMfKSxLwTnQtpV8qCGNV5L0JL6GwVFXyhmVCDQpBMHfgY1VggrT!-626903137; ADMINCONSOLESESSION=52hsKSnKvthSTw17CnBHkqRBZCJfCwTm2vRLLxt3pDPWGYtLJWC7!-626903137

Content-Type: application/x-www-form-urlencoded

Content-Length: 26

]] Root cause of ServletException.

com.emc.documentum.fs.rt.AuthenticationException: Authorization failed, could not find identities in service context with token "temporary/127.0.0.1-1251109390214-6943403846894395327"

at com.emc.documentum.fs.rt.impl.handler.AuthorizationHandler.handleMessage(AuthorizationHandler.java:51)

at com.emc.documentum.fs.rt.impl.handler.AuthorizationHandler.handleMessage(AuthorizationHandler.java:1)

at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:284)

at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:135)

at com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:133)

at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:116)

at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)

at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)

at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)

at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)

at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)

at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)

at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)

at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)

at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129)

at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160)

at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)

at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)

at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

at java.lang.Thread.run(Thread.java:595)

Find more posts tagged with

Comments

zhou_simonq

Yes, there is a documentation issue in DFS 6.5 SP1 that Weblogic 10.3 isn't supported. Pls try another application server. You can find these info from the document of DFS 6.5 SP2.

if authrization failed, no service can be consumed because all services will go through this step.

- simon

mszurap

Hi,

This is an interesting issue, which we faced also... Weblogic 10.3 uses JDK6 as I know. In the DFS_65_SP2_release_notes.pdf on page 34 it says that JAX-WS in JDK6 conflicts with JAX-WS in DFS. I assume this is the problem with your authentication problem as well.

Is the problem caused by the different JAX-WS jars or there is other differences of because EMC does not support Weblogic 10.3? I ask this because there was a workaround written down right there, so it may work even in Weblogic 10.3? So it can be run with JDK 6 as well, based on the "Java version support" table. This all applies to the web services layer (.ear)

The other side is when you consume DFS services from a standalon application or from a web application. In the same documentation there is a statement (end of Page 26):

For Documentum Foundation Services in standalone mode, Java J2SE 5.0.x is supported. For Documentum Foundation Services running in a web application server environment, all Java 5.0.x versions supported by each web application server configuration are supported.

No mention of JDK6...

By the way, what was your direction? Have you moved your webapp into BEA Weblogic 9.2?

One more question to dear EMC employees... If we use wsdl-based clients, then there is no limitation on which application server we use, right? I mean we won't get a "NotSupportedEnvironmentException" message from EMC support, will we?

Mike

zhou_simonq

yes, WS related jars in JDK 6 confict with the ones in DFS. Weblogic 10.3 may be supported in later versions.

RKG

hi Zhou -

we are calling the DFS 6.7 SP1 (hosted on Jboss 5.1.1 JMS) from weblogic 10.3 and are still running into this issue. is it not supported in weblogic 10.3 also ? is there some workaorund that we can use, we are desperately trying to use this for a transformation service

thanks,

Raj

mszurap

Hi,

Have you tried to specify this in your EAR/META-INF/weblogic-application.xml?

<?xml version="1.0" encoding="UTF-8"?><weblogic-application xmlns="http://www.bea.com/ns/weblogic/90">     <prefer-application-resources>        <resource-name>META-INF/services/*</resource-name>    </prefer-application-resources></weblogic-application>

It is needed on 10.3.3 maybe it works with 10.3.0 also.

mszurap

Or look at https://community.emc.com/message/608843#608843

RKG

hi Miklos -

this configuration does not run and is not supported by EMC. we hence abandoned this approach and finally ended up deploying the methods (the transformation methods that call the core services) on JMS and were able to get this working finally. if anyone needs assistance let me know

thanks,

Raj