[JBoss Portal] - Portlet Instance creation problem, when new portlet is deplo
by vijay2p
Take the scenario, I have created a portlet DemoPortlet with instance name DemoPortletInstance.
Now I decided to undeploy the DemoPortlet.war file and Again I created one more Portlet with name TestPortlet and here I created the Instance name as DemoPortletInstance. Which is same as above portlet which I already undeployed.
Now what is there on the admin screen. Portlet definition is created correctly but Portlet Instance is not displayed under Portlet Instances tab under Admin tab. Now If I try to create the instance name DemoPortletInstance manually then it is not creating that instance and in logs it says that instance already exists.
But I cann't use that instance in the application.
Please let me know if anyone has faced the same problem and got any solution for the same
I am using jboss-portal-2.7.0.
I tested this problem on Windows and Linux OS.
Thanks,
Vijay
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244107#4244107
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244107
17 years
[Clustering/JBoss] - Random clustering error on jboss 5.1 (seam apps in war deplo
by meetoblivion
I have a couple of seam apps that we're trying to migrate from tomcat deployments to jboss deployments. WAR makes the most sense in my opinion still, since the main thing we're using is hibernate's caching.
In general, everything works ok, but I see this in the logs.
2009-07-16 10:22:27,853 WARN [org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.CacheListener] (Incoming-13,172.17.11.16:33287) Possible concurrency problem: Replicated version id 100 is less than or equal to in-memory version for session KU99koDyou45fJcau9qcHA__
And every once in a while I'll get the generic error in seam/jsf about something went wrong.
The stack traces look typically like:
2009-07-16 10:00:26,538 WARN [org.jboss.web.tomcat.service.session.distributedcache.impl.jbc.CacheListener] (Incoming-11,172.17.11.16:33287) Possible concurrency problem: Replicated version id 3 is less than or equal to in-memory version for session KU99koDyou45fJcau9qcHA__
2009-07-16 10:00:28,073 ERROR [facelets.viewhandler] (http-172.17.11.16-8380-7) Error Rendering View[/viewShipment.xhtml]
com.sun.facelets.tag.TagAttributeException: /viewShipment.xhtml @28,238 timeZone="#{storeBean.currentStore.timeZone}" /viewShipment.xhtml @28,238 timeZone="#{storeBean.currentStore.timeZone}": Error reading 'currentStore' on type com.coat.web.wm.intransit.reports.CurrentStoreBean_$$_javassist_1
at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:235)
at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:166)
at com.sun.facelets.tag.jsf.core.ConvertDateTimeHandler.setAttributes(ConvertDateTimeHandler.java:107)
at com.sun.facelets.tag.jsf.ConvertHandler.apply(ConvertHandler.java:116)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:64)
at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:131)
at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:337)
at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:307)
at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:109)
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:140)
at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113)
at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:100)
at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:176)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:444)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310)
at org.jboss.seam.web.RewriteFilter.process(RewriteFilter.java:98)
at org.jboss.seam.web.RewriteFilter.doFilter(RewriteFilter.java:57)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
Any ideas?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244103#4244103
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244103
17 years
[Security & JAAS/JBoss] - Configuring Single Sign On (SSO) in JBoss
by SinghK
Hi All,
I am trying to configure SSO in JBoss . I have my custom LoginModules which I have configured in login-config.xml
| <application-policy name="LoginModule1">
| <authentication>
| <login-module code="com.MyLoginModule" flag="required">
| </login-module>
| </authentication>
| </application-policy>
|
| <application-policy name="LoginModule2">
| <authentication>
| <login-module code="com.MyLoginModule" flag="required">
| <module-option name="useSharedState">true</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
|
The name of my web applications are sso1 and sso2 . Both of them use the same instance of JBoss .
I have also configured auth.conf
| sso1 {
| com.MyLoginModule required;
| };
|
| sso2 {
| com.MyLoginModule required useSharedState=true;
| };
|
I am logging in to sso1 and their I am checking if user is logged in , if not then user is presented with login page . The username and passwords are checked and then user is forwaded to next page .
The MyLoginModule code is :
| if ("true".equalsIgnoreCase((String)this.options.get("useSharedState")))
| {
| userName = (String)this.sharedState.get("javax.security.auth.login.name");
| password = (String)this.sharedState.get("javax.security.auth.login.password");
| } else {
| userName = request.getParameter("userName");
| password = request.getParameter("password");
|
| //save the username and password into the shared state
| this.sharedState.put("javax.security.auth.login.name",userName);
| this.sharedState.put("javax.security.auth.login.password",password);
|
| }
when user logs in for the first time the username and password is put into sharedstate . Now when I fwd the user to sso2 application , MyLoginModule again comes into action , the 'if' part of the code is executed but the
this.sharedState.get("javax.security.auth.login.name") or this.sharedState.get("javax.security.auth.login.password") returns null .
I have configured the jboss-web.xml also in respective webapps.
| <jboss-web>
| <security-domain>java:/jaas/LoginModule1</security-domain>
| <context-root>/sso1</context-root>
| </jboss-web
|
| <jboss-web>
| <security-domain>java:/jaas/LoginModule2</security-domain>
| <context-root>/sso2</context-root>
| </jboss-web
Also server.xml is configured properly
| <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
Any idea whats failing ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244101#4244101
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244101
17 years
[Security & JAAS/JBoss] - Re: From Servlet Standalone Tomcat to EJB on JBoss
by GFEMajor
OK, i feel sorry that i did not mention my configuration.
I use (standalone) Tomcat 6.0.20 and JBoss 4.3.
I read the FAQ:
"FAQ" wrote :
| Q10: Why isn't my authentication info picked up from the JNDI InitialContext
|
| A10: Because there is no reason for it. You have to use an InitialContextFactory implementation that supports this. See the Available InitialContext Factories section, and LoginInitialContextFactory or JndiLoginInitialContextFactory in particular.
Because i am using JBoss 4.3 the "org.jboss.security.jndi.JndiLoginInitialContextFactory" should work, but this is not my Problem. When i use the code from my Post #1, i can log me in and use my EJB.
The Problem is, that i'm trying to authenticate against the standalone tomcat (servlet) and later, i try to call an EJB from that servlet, but tomcat does not populate the logged in user to JBoss, so i have to login a secound time to JBoss, with the code from post#1.
I try to avoid the secound login to JBoss, so that tomcat automaticly logs in into JBoss with the principal logged in on tomcat, and the question was, if this is possible (and how :-)).
"Wolfgang Knauf" wrote :
| See this forum thread for more details: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4198157
Sorry, but this thread does not help me, because alsways there must be the principal and password known, but i only get the principals name from the tomcat session.
(@Wolfgang Knauf: if you do not understand my problem (or i don't understand your solution ;-)), maybe you can send me an email to gfemajor2 [at] gmx.de and we could talk in german :-))
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244089#4244089
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244089
17 years