[JBoss Portal] - Problem starting jBoss Portal 2.6.4
by isaquexavier
Hello Guys....
I've just installed the jBoss Portal 2.6.4 om my PC (Win XP) and it's works. But when I call the index page (http://localhost:8080/portal/) of the Portal and after click on the register tab, I get the error below.......Can some one help me ?
11:04:16,872 ERROR [STDERR] 13/02/2008 11:04:16 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/programs/jboss-portal-2.6.4/server/default/./deploy/jboss-portal.sar/portal-identity.sar/portal-identity.war/WEB-INF/lib2/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
11:04:16,887 ERROR [STDERR] 13/02/2008 11:04:16 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/programs/jboss-portal-2.6.4/server/default/./deploy/jboss-portal.sar/portal-identity.sar/portal-identity.war/WEB-INF/lib2/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
11:04:16,919 ERROR [STDERR] 13/02/2008 11:04:16 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/programs/jboss-portal-2.6.4/server/default/./deploy/jboss-portal.sar/portal-identity.sar/portal-identity.war/WEB-INF/lib2/portal-faces-lib.jar!/META-INF/portal.taglib.xml
11:04:16,997 ERROR [STDERR] 13/02/2008 11:04:16 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/programs/jboss-portal-2.6.4/server/default/./deploy/jboss-portal.sar/portal-identity.sar/portal-identity.war/WEB-INF/lib2/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
11:04:17,122 ERROR [STDERR] 13/02/2008 11:04:17 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/programs/jboss-portal-2.6.4/server/default/./deploy/jboss-portal.sar/portal-identity.sar/portal-identity.war/WEB-INF/lib2/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
11:04:17,200 ERROR [STDERR] 13/02/2008 11:04:17 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/D:/programs/jboss-portal-2.6.4/server/default/./deploy/jboss-portal.sar/portal-identity.sar/portal-identity.war/WEB-INF/lib2/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
11:04:18,700 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using default value true
11:04:18,700 INFO [MyfacesConfig] Tomahawk jar not available. Autoscrolling, DetectJavascript, AddResourceClass and CheckExtensionsFilter are disabled now.
11:04:18,700 INFO [MyfacesConfig] Starting up Tomahawk on the RI-JSF-Implementation.
11:04:18,700 INFO [MyfacesConfig] Starting up Tomahawk on the MyFaces-JSF-Implementation
11:04:18,700 ERROR [MyfacesConfig] Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations.
11:04:38,559 ERROR [IOTools] Error while closing outstream
ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:358)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309)
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:273)
at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104)
at org.jboss.portal.common.io.IOTools.safeClose(IOTools.java:133)
at org.jboss.portal.core.controller.handler.HTTPResponse$2.sendResponse(HTTPResponse.java:81)
at org.jboss.portal.core.controller.Controller.sendResponse(Controller.java:319)
at org.jboss.portal.core.controller.Controller.processHandlerResponse(Controller.java:305)
at org.jboss.portal.core.controller.Controller.processCommandResponse(Controller.java:285)
at org.jboss.portal.core.controller.Controller.processCommand(Controller.java:259)
at org.jboss.portal.core.controller.Controller.handle(Controller.java:217)
at org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
at org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.aspects.server.PortalContextPathInterceptor.invoke(PortalContextPathInterceptor.java:45)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:96)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:246)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.server.aspects.server.SignOutInterceptor.invoke(SignOutInterceptor.java:98)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.impl.api.user.UserEventBridgeTriggerInterceptor.invoke(UserEventBridgeTriggerInterceptor.java:65)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49)
at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129121#4129121
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129121
18 years, 2 months
[Installation, Configuration & DEPLOYMENT] - Starting an own Quartz Schedulerclass
by praenti
Hi,
I'm using here JBoss 4.0.5 GA and wanted to start an own implementation of a Quartz scheduler when I deploy the EAR file.
My software consists of 3 main modules which are deployed with the EAR file. 2 of them are webapplications based on struts and jsf and the big module is the database and facade module with the logic components which is also used by an Eclipse RCP application. As the scheduler also has to be logically in this big module I cannot use (or better I don't want to use) one of the web.xml's from the two webapps :-(.
In a Tomcat environment you would configure that over the web.xml in -tags, but how can I tell JBoss that there is a scheduler class which has to be loaded after deployment?
Because I need information from the database for the job creation (the configuration is done in the database), it was not possible to use the quartz-ra.rar :-(.
Anyone can help me?
Ragards,
Mike
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129120#4129120
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129120
18 years, 2 months
[JBoss Seam] - Why a STATIC RESTRICTIONS in Seam-gen EntityQuery?
by boevink
All sessionbean lists generated by seam-gen provide an implementation of an EntityQuery class.
Why is the String[] of RESTRICTIONS marked as Static? as shown below:
| package web.session;
|
| import web.entity.user.*;
| import org.jboss.seam.annotations.Name;
| import org.jboss.seam.framework.EntityQuery;
| import java.util.List;
| import java.util.Arrays;
|
| @Name("userList")
| public class UserList extends EntityQuery {
|
| private static final String[] RESTRICTIONS = {
| "lower(email) like concat(lower(#{userList.user.email}),'%')",
| "lower(password) like concat(lower(#{userList.user.password}),'%')",
| "lower(username) like concat(lower(#{userList.user.username}),'%')", };
|
| private User user = new User();
|
| @Override
| public String getEjbql() {
| return "select user from User user";
| }
|
| @Override
| public Integer getMaxResults() {
| return 25;
| }
|
| public User getUser() {
| return user;
| }
|
| @Override
| public List<String> getRestrictions() {
| return Arrays.asList(RESTRICTIONS);
| }
|
| }
|
The only place currently reffering to this attribute is within the class itself (getRestrictions).
Or am I missing something?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129116#4129116
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129116
18 years, 2 months
[JBossCache] - Re: Manual eviction not working
by mircea.markus
I've run the following test on 1.4.1SP3, works fine:
public void testIssues() throws Exception
| {
| TreeCache cache = new TreeCache();
| PropertyConfigurator conf = new PropertyConfigurator();
| conf.configure(cache, "..\\passivation-issues.xml");
| cache.startService();
| cache.put("/za_node", "key","value");
| cache.put("/za_node2", "key","value");
| cache.put("/za_node3", "key","value");
| cache.put("/za_node4", "key","value");
| cache.evict(Fqn.ROOT);
| assertEquals(0, cache.getNumberOfNodes());
| cache.stop();
|
| TreeCache cache2 = new TreeCache();
| PropertyConfigurator conf2 = new PropertyConfigurator();
| conf2.configure(cache2, "..\\passivation-issues.xml");
| cache2.startService();
| cache2.get("/za_node", "key");
| cache2.get("/za_node2", "key");
| cache2.get("/za_node3", "key");
| cache2.get("/za_node4", "key");
| assertEquals(4, cache2.getNumberOfNodes());
| cache2.stopService();
| }
I've used same config as one you posted.
Some comments on your code, though:
anonymous wrote : Fqn fqn = Fqn.fromString("/root/");
1. This will fetch you a node named 'root' (i.e. a child of root node), and not the root node which is '/'. Was this your intention?
2. You can evict all existing nodes this way: cache.evict(Fqn.ROOT);
If code was your issues hope this helps. Otherwise, Can you please create a UT (or change the one I've attached) to reproduce the issue, then a JIRA and attach code+config to it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129114#4129114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129114
18 years, 2 months
[Tomcat, HTTPD, Servlets & JSP] - lost session-cookies with jboss, iis, internet explorer
by kurt.spescha＠consor.ch
Hallo,
Problem with the combination on W2003 64bit, IIS, jboss-4.2.2.GA and IE. Session cookies get lost. Isapi_redirect.dll should be the correct one. There is no problem with Firefox and Opera. A similar installation, but on Linux 64bit Red Hat, Apache, jboss-4.2.2.GA, has no problem, even not with IE. Client is an Applet. The Webstart-Versions work well on all environments. Just not with IE 6.0 and 7.0.
Any idea? I don't understand the difference.
rgrds
Kurt
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129112#4129112
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129112
18 years, 2 months