November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-4780) J2EE duke's bank example missing javax.servlet.jar dependency

by Ely Schoenfeld (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4780?page=comments#action_12388625 ] Ely Schoenfeld commented on JBAS-4780: -------------------------------------- Hi I managed to compile examples thanks to this link: http://joewong.blogspot.com/2007/08/eclipse-322-with-jboss-server-421.html that points to this one http://www.informatik.fh-wiesbaden.de/%7Eknauf/public/ The problem is that using JBoss 4.2.0, the javax.servlet.jar is packed in a different jar. I just added a line to the build.xml in order to add servlet-api.jar to the classpath: <path id="jboss.classpath"> ... <pathelement path="${jboss.dir}/server/default/lib/servlet-api.jar"/> ... </path> Hope it helps someone Ely > J2EE duke's bank example missing javax.servlet.jar dependency > ------------------------------------------------------------- > > Key: JBAS-4780 > URL: http://jira.jboss.com/jira/browse/JBAS-4780 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Environment: JBoss AS 4.2.0.GA > Reporter: James Shaw > > Trying to compile the example results in compilation errors due to javax.servlet.jar not being present in ${jboss.home}/server/default/lib/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBXB-107) Merge jbossxb and jbossxb-builder

by Scott M Stark (JIRA)

Merge jbossxb and jbossxb-builder --------------------------------- Key: JBXB-107 URL: http://jira.jboss.com/jira/browse/JBXB-107 Project: JBoss XML Binding (JBossXB) Issue Type: Task Affects Versions: JBossXB-2.0.0.CR4 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossXB-2.0.0.CR5 The https://svn.jboss.org/repos/common/jbossxb-builder and https://svn.jboss.org/repos/common/jbossxb projects need to be merged. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1810) DTD of portlet-instances.xml is wrong for [preferences] element

by Sylvain FRANCOIS (JIRA)

DTD of portlet-instances.xml is wrong for [preferences] element ---------------------------------------------------------------- Key: JBPORTAL-1810 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1810 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.2 Final Reporter: Sylvain FRANCOIS Assigned To: Julien Viet Priority: Minor portal-object_2_6.dtd is wrong for [preferences] element, only one preference may be overidden : <!ELEMENT preferences (preference)> instead of <!ELEMENT preferences (preference+)> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-632) Ability to replace thread pools with custom thread pools

by Bela Ban (JIRA)

Ability to replace thread pools with custom thread pools -------------------------------------------------------- Key: JGRP-632 URL: http://jira.jboss.com/jira/browse/JGRP-632 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 In TP, we should be able to set a custom thread pool for the default *and* OOB thread pools. In the ProtocolStack, we should be able to replace the timer thread pool with a custom thread pool -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-218) Fix behaviour of AbstractMetaDataContext.isEmpty()

by Ales Justin (JIRA)

Fix behaviour of AbstractMetaDataContext.isEmpty() -------------------------------------------------- Key: JBMICROCONT-218 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-218 Project: JBoss MicroContainer Issue Type: Bug Affects Versions: JBossMC-2.0.0.Beta5 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.CR1 Fix the bug in AbstractMetaDataContext.isEmpty() implementation + add additional tests for this functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1809) Preferences names are not diplayed correcty

by Thomas Heute (JIRA)

Preferences names are not diplayed correcty ------------------------------------------- Key: JBPORTAL-1809 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1809 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.2 Final, 2.6.1 Final Reporter: Thomas Heute Fix For: 2.6.3 Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-187) Complete the single deployment api

by Adrian Brock (JIRA)

Complete the single deployment api ---------------------------------- Key: JBMICROCONT-187 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-187 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.GA The single deployment api needs finishing. 1) deploy()/undeploy() on the DeployerClient/MainDeployer need making threadsafe such that they only do work on the deployment passed a parameter 2) The incomplete checking for a single deployment needs to "know" look at only those microcontainer contexts that it created (+ those contexts/deployments referenced as dependencies). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-556) Consolidate thread pools

by Vladimir Blagojevic (JIRA)

Consolidate thread pools ------------------------ Key: JGRP-556 URL: http://jira.jboss.com/jira/browse/JGRP-556 Project: JGroups Issue Type: Task Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 2.6 For JGroups 2.5 we have used numerous instances of ThreadPoolExecutor(s) as we needed them. For instance, STREAMING_STATE_TRANSFER, Multiplexer, TP, and ProtocolStack. Undoubtedly this lead to increased overhead and performance impact that we have not measured. First of all we should stop indiscriminately introducing new thread pools as we go further. Second, we should Investigate possibility to consolidate thread pools so they can be reused by various protocols and components of a channel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1720) Profile / enhance error message : DatePropertyAccessor

by Antoine Herzog (JIRA)

Profile / enhance error message : DatePropertyAccessor ------------------------------------------------------- Key: JBPORTAL-1720 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1720 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.1 Final Reporter: Antoine Herzog Priority: Optional Fix For: 2.6.2 Final Line 552 catch (ParseException e) { throw new IllegalArgumentException(); } Some more information on the error will be helpfull, espcially for integration of legacy user datasource. Like it is done for the boolean property accessor something like : catch (ParseException e) { throw new IllegalArgumentException("Can't convert the date in the user profile. value=[" + value + "].", e); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1782) CMS security checks using ldap causes "too many open files" error

by frontline frontline (JIRA)

CMS security checks using ldap causes "too many open files" error ----------------------------------------------------------------- Key: JBPORTAL-1782 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1782 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS, Portal Identity Affects Versions: 2.6.1 Final Environment: Linux Reporter: frontline frontline Assigned To: Sohil Shah I have configured the portal to use OpenDS as the "user store". I noticed that if I log in as some other user than admin and then perform many CMS operations I eventually get an "java.net.SocketException: Too many open files" error. Apparently the portal always opens a new connection when getting role info etc. for authorization? So there is no caching or even pooling of the ldap connections? Isn't this also potentially bad for performance (and for the poor ldap server)? If I wait a while the connections become usable again so there is no connection leak (the sockets are in TIME_WAIT for a while). Here is the error: java.net.SocketException: Too many open files java.net.Socket.createImpl(Socket.java:388) java.net.Socket.<init>(Socket.java:361) java.net.Socket.<init>(Socket.java:179) com.sun.jndi.ldap.Connection.createSocket(Connection.java:346) com.sun.jndi.ldap.Connection.<init>(Connection.java:181) com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118) com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1578) com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2596) com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283) com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175) com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193) com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136) com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66) javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) javax.naming.InitialContext.init(InitialContext.java:223) javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134) org.jboss.portal.identity.ldap.LDAPConnectionContext.createInitialContext(LDAPConnectionContext.java:99) org.jboss.portal.identity.ldap.LDAPUserModuleImpl.searchUsers(LDAPUserModuleImpl.java:353) org.jboss.portal.identity.ldap.LDAPUserModuleImpl.findUserByUserName(LDAPUserModuleImpl.java:81) org.jboss.portal.cms.security.AuthorizationProviderImpl.findPermissionsByUser(AuthorizationProviderImpl.java:365) org.jboss.portal.cms.security.AuthorizationProviderImpl.getSecurityBindings(AuthorizationProviderImpl.java:147) org.jboss.portal.cms.impl.jcr.command.ACLEnforcer.getPermissions(ACLEnforcer.java:573) org.jboss.portal.cms.impl.jcr.command.ACLEnforcer.computeAccess(ACLEnforcer.java:330) org.jboss.portal.cms.impl.jcr.command.ACLEnforcer.hasReadAccess(ACLEnforcer.java:209) org.jboss.portal.cms.impl.jcr.command.ACLEnforcer.hasAccess(ACLEnforcer.java:120) org.jboss.portal.cms.security.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:127) org.jboss.portal.cms.impl.interceptors.ACLInterceptor.invoke(ACLInterceptor.java:238) org.jboss.portal.cms.CMSInterceptor.invoke(CMSInterceptor.java:36) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007