Re: [GSOC][CXF-2736] Proposal for "Simple and lightweight Atom HTML-based browser for CXF logs"
Hi Tomasz On Fri, Apr 2, 2010 at 10:18 AM, Tomasz Oponowicz < tomasz.oponow...@gmail.com> wrote: > Hi Sergey, > > I have prepared sample project using AtomPullServer (base on CXF > 2.3.0-SNAPSHOT). I successful published Atom feed with CXF logs. Now I > understand clearly your requirments. > it's good you've independently verified that the publication works, thanks. > > I have updated my proporsal (at ASF wiki and GSOC 2010 website), changes: > - Noted about AtomPullServer; > - Added requirement with respect to implementation of > ReadWriteLogStorage interface; > I think it is something that an AtomPullServer demo could do, that is, show how a custom ReadWriteLogStorage can be used to persist records across the restarts. When reading (only) from the external file, a custom ReadableLogStorage can be used instead. I'm not sure if we can come up with production-quality default implementation, perhaps a file-based ReadWriteLogStorage can be provided OTB, but there's no way we can have a default ReadableOnlyStorage, perhaps the abstract helper only, given that users's code can log into external files using log4j, jul, sl4j, using various formats. So perhaps you can have an optional task to do with adding a demo showing how a user could start a browser, point it to an AtomPullServer endpoint, and view the logs from some external file (using ReadableStorage), and then point to another endpoint which uses ReadWriteLogStorage - Added Atom authentication requirement; > I've been thinking for a while of adding some cxf jaxrs code for handling WSSE UserName HTTP headers (as opposed to SOAP headers) so that the regular JAXRS endpoints could do such authentication over plain HTTP too (using digest), so AtomPullServer will reuse that code (as opposed to bringing an extra abdera dependency for handling wsse username headers). > - Fixed language mistakes; > > I hope everything is fine now. > It all looks very good. A couple of comments: - IMHO using links as opposed to buttons will be better (for browsing to first/last/etc feeds) - The browser should offer users an option to do the search (ex, get all the records with level INFO logged by a given component between 12.10.2010 14.50 and 12.10.2010 15.00). After collecting a requirement from a user, the browser will convert it into a FIQL query and issue a request (please see http://sberyozkin.blogspot.com/2010/03/cxf-jaxrs-search-extensions.html). This probably can be captured by your 'filtering' task. I'll actually need to enhance AtomPullServer too for such queries be supported... thanks, Sergey > Best Regards, > Tomasz Oponowicz > > On Wed, Mar 31, 2010 at 2:15 PM, Sergey Beryozkin > wrote: > > Hi Tomasz > > > > thanks for your interest. I'd be happy to be a mentor. > > > > Just a couple of clarifications with respect to your proposal : > > > > - CXF JAXRS endpoint acting as an Atom Pull server has already been added > to > > a rt/management component, I've briefly described it here : > > > http://sberyozkin.blogspot.com/2010/02/use-your-favorite-atom-reader-to-view.html > . > > I'll make sure that by the time you start working on this project the > > documentation will be up-to-date. To my knowledge, no existing atom > readers > > support the paged/archived feeds well, thus the idea for the OTB browser > has > > come up. Indeed, as you mentioned in your proposal, the same browser may > be > > extended later on to support the viewing of the CXF exchanges, it is for > > this latter task when a dedicated CXF JAXRS endpoint will have to be > added. > > > > - The question of security will need to be addressed as well. Most likely > > we'll need to use a WSSE UserToken for the Atom authentication, basic > > authentication over HTTPs may not be a practical solution for viewing the > > logs... > > > > Please post your ideas/questions to this thread when you start working > and > > we'll be glad to help > > cheers, Sergey > > > > > > > > On Tue, Mar 30, 2010 at 11:40 PM, Tomasz Oponowicz < > > tomasz.oponow...@gmail.com> wrote: > > > >> Hi, > >> > >> I want to attend the GSOC, and get involved into open source. I chose > >> project called "Simple and lightweight Atom HTML-based browser for CXF > >> logs" (CXF-2736) from suggestions in JIRA . Finally I create my > >> proposal. I guess that Sergey Beryozkin will be mentor for this > >> project. > >> > >> - Proposal in ASF wiki: > >> http://wiki.apache.org/general/soc2010-cxf2736-proposal > >> > >> - Proposal in GSOC: > >> > >> > http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/tomekopo/t126998466755 > >> > >> Any comments and suggestions are welcome. > >> Thanks in advance for your feedback. > >> > >> Best Regards, > >> Tomasz Oponowicz > >> > > > > > > -- > Pozdrawiam, > Tomasz Oponowicz >
Re: [jira] Commented: (CXF-2741) JAXB hang on JBoss 5.1.0
Hi Jeffrey
thanks for resolving this issue, it's been a tricky one :-). It would be
interesting to know which JVM parameter is 'to blame'...
cheers, Sergey
On Fri, Apr 2, 2010 at 3:12 PM, Jeffrey Poore (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/CXF-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852827#action_12852827]
>
> Jeffrey Poore commented on CXF-2741:
>
>
> It appears that this is some kind of subtle JVM bug. I took a grass roots
> JBoss and put the war on it containing a minimal hello world service and it
> runs fine without hanging. Then put our normal war on it, still runs fine.
> We have some JNDI's that we add and some database connections, and it still
> worked after adding those. Then I added in the extra JVM parameters we pass
> in, and it hangs. I'm working on figuring out which one it is, but this is
> not a CXF issue, so I'm resolving.
>
> Thanks for your help gentlemen.
>
> > JAXB hang on JBoss 5.1.0
> >
> >
> > Key: CXF-2741
> > URL: https://issues.apache.org/jira/browse/CXF-2741
> > Project: CXF
> > Issue Type: Bug
> > Components: JAXB Databinding
> >Affects Versions: 2.2.6
> > Environment: JBoss 5.1.0.GA, Spring 2.5.6,
> javax.ws.rs.jsr311-api 1.1
> >Reporter: Jeffrey Poore
> >
> > We have been using CXF RESTFul services for a long time on jboss-4.2.3
> with no issues. When we switched to JBoss 5.1.0.GA, things worked fine at
> first, but we noticed that after a short period of uptime, requests began to
> hang and time out. Debugging this issue, we tracked it to the synchronized
> block in AbstractJAXBProvider.java:
> > {code}
> > JAXBElementProvider(AbstractJAXBProvider).getPackageContext(Class)
> line: 377
> > JAXBElementProvider(AbstractJAXBProvider).getJAXBContext(Class, Type)
> line: 354
> > JAXBElementProvider(AbstractJAXBProvider).createMarshaller(Object,
> Class, Type, String) line: 453
> > JAXBElementProvider.marshal(Object, Class, Type, String, OutputStream,
> MediaType) line: 296
> > JAXBElementProvider.writeTo(Object, Class, Type, Annotation[],
> MediaType, MultivaluedMap, OutputStream) line: 219
> > JAXRSOutInterceptor.serializeMessage(Message, Response,
> OperationResourceInfo, boolean) line: 241
> > JAXRSOutInterceptor.processResponse(Message) line: 138
> > JAXRSOutInterceptor.handleMessage(Message) line: 77
> > PhaseInterceptorChain.doIntercept(Message) line: 243
> > OutgoingChainInterceptor.handleMessage(Message) line: 76
> > PhaseInterceptorChain.doIntercept(Message) line: 243
> > ChainInitiationObserver.onMessage(Message) line: 109
> > ServletDestination.invoke(ServletConfig, ServletContext,
> HttpServletRequest, HttpServletResponse) line: 98
> > ServletController.invokeDestination(HttpServletRequest,
> HttpServletResponse, ServletDestination) line: 406
> > ServletController.invoke(HttpServletRequest, HttpServletResponse) line:
> 139
> > CXFServlet(AbstractCXFServlet).invoke(HttpServletRequest,
> HttpServletResponse) line: 142
> > CXFServlet(AbstractHTTPServlet).handleRequest(HttpServletRequest,
> HttpServletResponse) line: 179
> > CXFServlet(AbstractHTTPServlet).doGet(HttpServletRequest,
> HttpServletResponse) line: 108
> > CXFServlet(HttpServlet).service(HttpServletRequest, HttpServletResponse)
> line: 617
> > CXFServlet(AbstractHTTPServlet).service(ServletRequest, ServletResponse)
> line: 159
> > ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse)
> line: 290
> > ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line:
> 206
> > ReplyHeaderFilter.doFilter(ServletRequest, ServletResponse, FilterChain)
> line: 96
> > ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse)
> line: 235
> > ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line:
> 206
> > StandardWrapperValve.invoke(Request, Response) line: 235
> > StandardContextValve.invoke(Request, Response) line: 191
> > SecurityAssociationValve.invoke(Request, Response) line: 190
> > JaccContextValve.invoke(Request, Response) line: 92
> > SecurityContextEstablishmentValve.process(Request, Response, HttpEvent)
> line: 126
> > SecurityContextEstablishmentValve.invoke(Request, Response) line: 70
> > StandardHostValve.invoke(Request, Response) line: 127
> > ErrorReportValve.invoke(Request, Response) line: 102
> > CachedConnectionValve.invoke(Request, Response) line: 158
> > StandardEngineValve.invoke(Request, Response) line: 109
> > CoyoteAdapter.service(Request, Response) line: 330
> > Http11Processor.process(Socket) line: 829
> > Http11Protocol$Http11ConnectionHandler.process(Socket) line: 598
> > JIoEndpoint$Worker.run() line: 447
> > Thread.run() line: 619
> > {code}
> > Specifically, this method:
> > {code}
> > public JAXBContext getPackageContext(Class type) {
> > if (type == null || type == JAXBElement.class) {
> >
Re: [GSOC][CXF-2736] Proposal for "Simple and lightweight Atom HTML-based browser for CXF logs"
Hi Sergey, I have prepared sample project using AtomPullServer (base on CXF 2.3.0-SNAPSHOT). I successful published Atom feed with CXF logs. Now I understand clearly your requirments. I have updated my proporsal (at ASF wiki and GSOC 2010 website), changes: - Noted about AtomPullServer; - Added requirement with respect to implementation of ReadWriteLogStorage interface; - Added Atom authentication requirement; - Fixed language mistakes; I hope everything is fine now. Best Regards, Tomasz Oponowicz On Wed, Mar 31, 2010 at 2:15 PM, Sergey Beryozkin wrote: > Hi Tomasz > > thanks for your interest. I'd be happy to be a mentor. > > Just a couple of clarifications with respect to your proposal : > > - CXF JAXRS endpoint acting as an Atom Pull server has already been added to > a rt/management component, I've briefly described it here : > http://sberyozkin.blogspot.com/2010/02/use-your-favorite-atom-reader-to-view.html. > I'll make sure that by the time you start working on this project the > documentation will be up-to-date. To my knowledge, no existing atom readers > support the paged/archived feeds well, thus the idea for the OTB browser has > come up. Indeed, as you mentioned in your proposal, the same browser may be > extended later on to support the viewing of the CXF exchanges, it is for > this latter task when a dedicated CXF JAXRS endpoint will have to be added. > > - The question of security will need to be addressed as well. Most likely > we'll need to use a WSSE UserToken for the Atom authentication, basic > authentication over HTTPs may not be a practical solution for viewing the > logs... > > Please post your ideas/questions to this thread when you start working and > we'll be glad to help > cheers, Sergey > > > > On Tue, Mar 30, 2010 at 11:40 PM, Tomasz Oponowicz < > tomasz.oponow...@gmail.com> wrote: > >> Hi, >> >> I want to attend the GSOC, and get involved into open source. I chose >> project called "Simple and lightweight Atom HTML-based browser for CXF >> logs" (CXF-2736) from suggestions in JIRA . Finally I create my >> proposal. I guess that Sergey Beryozkin will be mentor for this >> project. >> >> - Proposal in ASF wiki: >> http://wiki.apache.org/general/soc2010-cxf2736-proposal >> >> - Proposal in GSOC: >> >> http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/tomekopo/t126998466755 >> >> Any comments and suggestions are welcome. >> Thanks in advance for your feedback. >> >> Best Regards, >> Tomasz Oponowicz >> > -- Pozdrawiam, Tomasz Oponowicz
