[JBoss Seam] - Re: Is Seam compatible with JBoss 4.2.1?
by wise_guybg
Yesterday I ported my seam application to JBoss AS 4.2.1GA. I have setup the libraries. I forgot to place my datasource (*-ds.xml) file in the deploy folder but that was easily fixed. So, no problems with me either...
Here an excerpt from the log that I think matches yours:
anonymous wrote :
| 14:50:38,624 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=AuthApplication.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3 with dependencies:
| 14:50:38,802 INFO [EJBContainer] STARTED EJB: org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
| 14:50:38,876 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateful.StatefulContainer
| 14:50:38,876 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=AuthApplication.ear,jar=jboss-seam.jar,name=EjbTransaction,service=EJB3 with dependencies:
| 14:50:38,950 INFO [EJBContainer] STARTED EJB: org.jboss.seam.transaction.EjbTransaction ejbName: EjbTransaction
| 14:50:38,994 INFO [EJB3Deployer] Deployed: file:/D:/AuthApplication.ear/jboss-seam.jar
| 14:50:38,994 INFO [TomcatDeployer] deploy, ctxPath=/AuthWebApp, warUrl=file:/D:/AuthApplication.ear/AuthWebApp.war/
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066965#4066965
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066965
18Â years, 9Â months
[JBoss Seam] - Seam + Richfaces, java.lang.IllegalArgumentException
by Stateless Bean
I get this exception when I call http://localhost:8080/rf/home.seam
SEVERE: Error Rendering View[/home.xhtml]
| java.lang.IllegalArgumentException: Component j_id11:amm not instance of org.richfaces.component.UIDataTable
| at org.ajax4jsf.framework.renderer.RendererBase.encodeBegin(RendererBase.java:94)
| at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:788)
| at javax.faces.component.UIData.encodeBegin(UIData.java:879)
| at org.ajax4jsf.ajax.repeat.UIDataAdaptor.encodeBegin(UIDataAdaptor.java:989)
| at org.ajax4jsf.framework.renderer.RendererBase.renderChild(RendererBase.java:280)
| at org.ajax4jsf.framework.renderer.RendererBase.renderChildren(RendererBase.java:262)
| at org.richfaces.renderkit.html.PanelRenderer.doEncodeChildren(PanelRenderer.java:189)
| at org.richfaces.renderkit.html.PanelRenderer.doEncodeChildren(PanelRenderer.java:184)
| at org.ajax4jsf.framework.renderer.RendererBase.encodeChildren(RendererBase.java:121)
| at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812)
| at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886)
| at javax.faces.render.Renderer.encodeChildren(Renderer.java:137)
| at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812)
| at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886)
| at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577)
| at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
| at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:233)
| 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.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:87)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:63)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:46)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
| at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:40)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:63)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:140)
| 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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
| 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(Unknown Source)
home.xhtml:
| (...)
| <rich:dataTable id="amm" value="#{stringi}" var="s">
| <rich:column>
| <f:facet name="header">
| <h:outputText id="ot2" value="Header"/>
| </f:facet>
| <h:outputText id="ot1" value="#{s}">
|
| </h:outputText>
|
| </rich:column>
| <a4j:support event="onclick" reRender="panel" oncomplete="javascript:Richfaces.showModalPanel('panel');"></a4j:support>
| </rich:dataTable>
|
I know that it is problem with class loaders, but I can't resolve that issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066964#4066964
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066964
18Â years, 9Â months
[JBoss jBPM] - Re: JBPM - concurrent process execution fails
by estaub
efip10,
Sorry, I used too broad a brush.
At least in some cases, the behavior I described is dependent on the isolation level selected. If at least level 2 ("read-committed") is selected, then I think it works as I described, if the database supports it. I believe that row-locking is used internally to the database to prevent concurrent access during the commit. Everything is written first, and then everything is unlocked. Thus if the race goes the wrong way, the early reader will block until the late writer has finished. I don't know about MySQL's behavior in this area.
While I think that JBPM is supposed to work
with any isolation level, its default isolation level is 1 ("read-uncommitted"), and so there's much more experience with that level. The level for JBPM is set as hibernate property hibernate.connection.isolation. I don't know where isolation level for a database-persisted queue is dealt with for JMS - AFAICT, it's either vendor-specific, or it's automatically set to "read-committed" if this isolation level is supported. For JBoss messaging, I haven't found where it's set, but see http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone... for more info. I don't know how current it is.
Please share back whatever you find out!
-Ed Staub
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066963#4066963
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066963
18Â years, 9Â months