[Beginners Corner] - Error parsing taglibs.
by cdiggins
I am attempting to add ajax4jsf support to my project and am getting errors parsing rich.taglib.xml, richfaces.taglib.xml, and a4j.taglib.xml.
| java.io.IOException: Error parsing [jar:file:/C:/jboss-4.2.2.GA/server/default/tmp/deploy/tmp26011richfaces-ui-3.1.3.GA.jar!/META-INF/ajax4jsf.taglib.xml]:
| at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:410)
| at com.sun.facelets.compiler.TagLibraryConfig.loadImplicit(TagLibraryConfig.java:431)
| at com.sun.facelets.compiler.Compiler.initialize(Compiler.java:87)
| at com.sun.facelets.compiler.Compiler.compile(Compiler.java:104)
| at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197)
| at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144)
| at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95)
| at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:517)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
| at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
| at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216)
| at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
| at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:307)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
| at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
| at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
| at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| 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:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| 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:262)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Unknown Source)
| Caused by: org.xml.sax.SAXException: Error Handling [jar:file:/C:/jboss-4.2.2.GA/server/default/tmp/deploy/tmp26011richfaces-ui-3.1.3.GA.jar!/META-INF/ajax4jsf.taglib.xml@12,20] <handler-class>
| at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:271)
| at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
| at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source)
| at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
| at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at javax.xml.parsers.SAXParser.parse(Unknown Source)
| at javax.xml.parsers.SAXParser.parse(Unknown Source)
| at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:407)
| ... 53 more
| Caused by: java.lang.Exception: org.ajax4jsf.taglib.html.facelets.AjaxListenerHandler must be an instance of com.sun.facelets.tag.TagHandler
| at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.createClass(TagLibraryConfig.java:293)
| at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:210)
| ... 68 more
|
They are all along the same lines as that one, but with different classes needing to 'be an instance of com.sun.facelets.tag.TagHandler'
Trying to get it to work with JBoss AS 4.2.2 and Seam 2.
Here is my web.xml, if it would help at all: http://pastebin.com/d4d71d4dd
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121396#4121396
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121396
18 years, 5 months
[Messaging, JMS & JBossMQ] - JMS - NoRouteToHostException and ping timeouts
by nbirch
Hi,
Running JBossAS 4.x, and JBossMQ on RH-Linux. Our application is a multi-process app, where processes interact over JMS topics and Queues.
I am seeing the following exceptions thrown from the JBoss process in some of our installations, very occasionally:
Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
...and...
org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.net.NoRouteToHostException: No route to host)
I have seen other postings describing similar situations, but never describing a specific cause/solution. One posting stated that they could reproduce the "NoRouteToHostException" if they disconnected their server from the network. Why would connectivity to the network cause JMS to throw exceptions when supporting inter-process comm within the same host?
Does JBossMQ get impacted by the server-OS DHCP/DNS operation/configuration?
The "java.io.IOException: ping timeout" is described in http://wiki.jboss.org/wiki/Wiki.jsp?page=IGetIOExceptionPingTimeoutHowDoI...
Here is says that large JMS messages and/or heavy paging could cause this. I have been able to create a ping timeout by changing the Linux date/time via the shell!
Any insights would be greatly appreciated.
Thanks,
NBirch
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121395#4121395
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121395
18 years, 5 months