RE: Facing error on Weblogic 11g with Apache CXF |u sing POST IN REST |Need help
Support for wauth and whr is supported as a callbackhandler in the fediz plugin for the relying party (application). Also metadata support is provided in the plugin. It's not yet supported for the fediz idp. -- Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://www.talend.com From: Cabrera Juan Manuel [juan-manuel.cabr...@atos.net] Sent: 04 September 2012 16:47 To: dev@cxf.apache.org Subject: RE: Facing error on Weblogic 11g with Apache CXF |u sing POST IN REST |Need help Hello everyone. I just dug out an old email about the Fediz roadmap (March, 29th 2012): http://mail-archives.apache.org/mod_mbox/cxf-dev/201203.mbox/%3c79ab4452999c844d9920e03635332731120...@s10be002.sh10.lan%3E#archives Roadmap - 1st release (end of april): - Move configuration code to fediz-core - Publish WS-Federation Metadata document - Move SignIn request creation to fediz-core - support callback handlers for federation parameters: wauth, whr, 2nd release (end of june): - Create CXF plugin for JAX-RS - Create Websphere plugin based on TAI - Support encrypted token - Support the role of relying party IDP in mock - Support SAML HoK: either use UseKey element in RST or collocate STS in IDP thus STS has access to underlying transport - add layer to support other protocols like SAML-P, OAuth 3rd release (end of september): - create JBoss plugin - create Jetty plugin Just to know if it is still correct (excepting the dates, obviously); I am very interested in the features about federation (wauth, whr, metadata, ...) Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité d'Atos ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Re: Facing error on Weblogic 11g with Apache CXF |u sing POST IN REST |Need help
Hi On 03/09/12 11:11, himanshu wrote: Hi everyone, We are facing a a issue in weblogic with Apche CXF,(Have been looking for a solution since long) We are using weblogic 11g(OCCAS) on linux machine. Its in cluster ,application gets deployed through the admin server on engines. We are using APACHE CXF for the REST based request processing in the application. The issue which we are facing is : If we stop and then start the deployed application from the console, It shows active on the Page.Now if we hit the REST web service using REST client it gives 500 -internal server error. But only the POST REST requests are giving this error however the GET requests works fine.But if we wait for some time(ranging from 15 sec to 12 min) the POST request also start responding successfully. The application is deployed in a cluster ,we have noted this issue on the Envoirnments where the admin-server is on another machine and the engines are on differnet machines.Its works fine on the ENV where the both the admin server and engine are on the same machine. We have enabled the CXF logging as well but have not been able to notice any exception/error in the logs. I honestly do not think it is anything do to with POST, it appears that the actual service endpoint has not been initialized after a restart, in cases when the admin server is not collocated. I'd try to isolate the issue somehow but I'm afraid I've nothing to suggest :-), it's a complex case... Cheers, Sergey I tried one thing which worked was I packaged the CXF.jar into the EAR itself( instead of domain/lib) and set prefer-web-inf-classes Element.Then the application started behaving perfectly fine.This seems that the classes with POST functionality are taking time to load. Anyone who has experienced it before or have an ifdea how CXF library will be loaded in this scenario. This is very urgent if someone can give pointers. Exception trace is : 2012-08-22 01:54:44,812 WARN [org.apache.cxf.phase.PhaseInterceptorChain] Application has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: argument type mismatch while invoking public com.nsn.see.application.callerid.Registration com.nsn.see.application.callerid.CallerIdService.registration(com.nsn.see.application.callerid.Register) with params [com.nsn.see.application.callerid.Register@1d03015d]. at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:159) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:133) at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:130) at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:82) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:109) at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:98) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:394) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:133) at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3692) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3656) 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:2268) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174) at
RE: Facing error on Weblogic 11g with Apache CXF |u sing POST IN REST |Need help
Hello everyone. I just dug out an old email about the Fediz roadmap (March, 29th 2012): http://mail-archives.apache.org/mod_mbox/cxf-dev/201203.mbox/%3c79ab4452999c844d9920e03635332731120...@s10be002.sh10.lan%3E#archives Roadmap - 1st release (end of april): - Move configuration code to fediz-core - Publish WS-Federation Metadata document - Move SignIn request creation to fediz-core - support callback handlers for federation parameters: wauth, whr, 2nd release (end of june): - Create CXF plugin for JAX-RS - Create Websphere plugin based on TAI - Support encrypted token - Support the role of relying party IDP in mock - Support SAML HoK: either use UseKey element in RST or collocate STS in IDP thus STS has access to underlying transport - add layer to support other protocols like SAML-P, OAuth 3rd release (end of september): - create JBoss plugin - create Jetty plugin Just to know if it is still correct (excepting the dates, obviously); I am very interested in the features about federation (wauth, whr, metadata, ...) Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité d'Atos ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.