November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBVFS-75) Make VFS configurable per instance

by Ales Justin (JIRA)

Make VFS configurable per instance ---------------------------------- Key: JBVFS-75 URL: https://jira.jboss.org/jira/browse/JBVFS-75 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Ales Justin We should be able to configure VFS per instance. e.g. instead of plain static usage: VFS::getRoot user should be able to configure VFS instance: - vfs cache - nested jar handling - encoding - reaper - case sensitivity - memory optimization - ... Current static usage should be backcompatible, e.g. static singleton configured as it is currently -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default

by Galder Zamarreno (JIRA)

boot.log should print command line options ($JAVA_OPTS) by default ------------------------------------------------------------------ Key: JBAS-5240 URL: http://jira.jboss.com/jira/browse/JBAS-5240 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor To help remote support, AS should by default log command line options within boot.log as explained in " Logging command line options in boot.log" section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging Thoughts? -- 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

14 years, 11 months

6
28
0 / 0

[JBoss JIRA] Created: (JBAS-3768) Define initial persistent format of the profile repository

by Scott M Stark (JIRA)

Define initial persistent format of the profile repository ---------------------------------------------------------- Key: JBAS-3768 URL: http://jira.jboss.com/jira/browse/JBAS-3768 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta We need to define the initial profile repository format with consideration of future migrations, jsr88, admin tools. -- 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

14 years, 11 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-4585) Properties not being correctly parsed on JCA

by Clebert Suconic (JIRA)

Properties not being correctly parsed on JCA -------------------------------------------- Key: JBAS-4585 URL: http://jira.jboss.com/jira/browse/JBAS-4585 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Clebert Suconic Fix For: JBossAS-5.0.0.Beta3 -- 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

14 years, 11 months

9
18
0 / 0

[JBoss JIRA] Created: (JBAS-3417) SocketException during minimal tests

by Jaroslaw Kijanowski (JIRA)

SocketException during minimal tests ------------------------------------ Key: JBAS-3417 URL: http://jira.jboss.com/jira/browse/JBAS-3417 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta Environment: win xp, fedora core 5 Reporter: Jaroslaw Kijanowski while running the first test of the testsuite (jboss-minimal-tests), get a java.net.SocketException. server.log: 2006-07-22 17:05:55,046 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml 2006-07-22 17:05:55,046 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/D:/jboss3/jboss-head/build/output/jboss-5.0.0.Beta/server/minimal/conf/jboss-service.xml 2006-07-22 17:05:55,046 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [5.0.0.Beta (build: CVSTag=HEAD date=200607220701)] Started in 3s:359ms 2006-07-22 17:05:55,281 DEBUG [org.jboss.naming.NamingService] Error writing response to /127.0.0.1 java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1676) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1585) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1167) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1121) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1278) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:294) at org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:476) at org.jboss.util.threadpool.RunnableTaskWrapper.run(Unknown Source) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743) at java.lang.Thread.run(Thread.java:595) -- 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

14 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1287) enabling prepare-statement-cache throws error during startup

by Prabhat Jha (JIRA)

enabling prepare-statement-cache throws error during startup ------------------------------------------------------------ Key: JBPORTAL-1287 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1287 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Environment: QA: jboss running on cluster01, mysql5 running on cluster08, jdk1.4, jboss-portal.sar as of 2007 Feb, 21. Reporter: Prabhat Jha This happens on my end when prepared-statement-cache is on. Here is my portal-mysql5-ds.xml: <datasources> <local-tx-datasource> <jndi-name>PortalDS</jndi-name> <connection-url>jdbc:mysql://10.16.0.103:3306/portal?jdbcCompliantTruncation=false</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>portal</user-name> <password></password> <min-pool-size>20</min-pool-size> <max-pool-size>40</max-pool-size> <prepared-statement-cache-size>100</prepared-statement-cache-size> </local-tx-datasource> </datasources> Once I comment out the prepared-statement-cache-size, then it starts fine. Given that Julien has not been able to reproduced on his end, he probably needs to have access to this environment or I have to see if I can reproduce in his environment. -- 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

14 years, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6001) JNDIView.list() in jmx-console does not show the java:comp namespace for WAR files

by jaikiran pai (JIRA)

JNDIView.list() in jmx-console does not show the java:comp namespace for WAR files ---------------------------------------------------------------------------------- Key: JBAS-6001 URL: https://jira.jboss.org/jira/browse/JBAS-6001 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.0.0.CR2 Environment: JBoss-5 CR2, Sun Java 1.5, Windows 2003 Operating System Reporter: jaikiran pai Assignee: Darran Lofthouse In JBoss-5 CR2 (Sun Java 1.5 and Windows 2003 OS), when i invoke the list() method on the JNDIView MBean through the jmx-console, i see this exception being logged at DEBUG level, in the server.log: 2008-09-28 17:30:03,510 DEBUG [org.jboss.naming.JNDIView] (http-0.0.0.0-8080-2) Unable to list web a pplications ENC javax.management.AttributeNotFoundException: not found: DeployedApplications at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:335) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:565) at org.jboss.naming.JNDIView.list(JNDIView.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.ja va:140) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258) at org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:281) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290 ) 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:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:91) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishm entValve.java:92) 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:325) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) The JNDI tree UI page is missing the java:comp namespace for various WAR files. For example the "java:comp namespace of the jboss-web.deployer/ROOT.war application" is missing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2223) create a hudson build for windows/IE testing

by Prabhat Jha (JIRA)

create a hudson build for windows/IE testing -------------------------------------------- Key: JBPORTAL-2223 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2223 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Prabhat Jha Assignee: Viliam Rockai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1002) EJB3-based version of the RetryInterceptor

by Brian Stansberry (JIRA)

EJB3-based version of the RetryInterceptor ------------------------------------------ Key: EJBTHREE-1002 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1002 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Looking for a conceptual equivalent to the EJB2 RetryInterceptor -- ability to reestablish a valid remoting client when the current FamilyClusterInfo does not contain any valid targets. If the approach is analogous to the RetryInterceptor case, what would be registered in JNDI is the FamilyClusterInfo itself (rather than the EJB2 Invoker). Looking this up in JNDI would provide the current list of targets. -- 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

15 years

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2040) Portal Admin very slow

by frontline frontline (JIRA)

Portal Admin very slow ---------------------- Key: JBPORTAL-2040 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2040 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.5 Final Reporter: frontline frontline Attachments: jamon1.gif, jamon2.gif, jamon3.gif, server.zip We are noticing that the portal admin interface is starting to get very slow. It apparently has to do with the amount of "portal objects" in the database. The portal seems to create a dashboard for each user so if there are 10000 users there are also at least that many portal objects. In my tests I noticed that the database access takes about half of the time and the method refresh() in PortalObjectManagerBean is also very slow. This part is the slow part in that method (the iterator is probably the culprit, there seems to be some "custom" implementation for it). === Collection portals = getSelectedObject().getChildren(PortalObject.PORTAL_MASK); ArrayList portalList = new ArrayList(portals.size() + 1); for (Iterator iterator = portals.iterator(); iterator.hasNext();) { PortalObject o = (PortalObject)iterator.next(); SelectItem item = new SelectItem(o.getName()); portalList.add(item); } portalList.add(new SelectItem("", "no selection")); portalItems = (SelectItem[])portalList.toArray(new SelectItem[portalList.size()]); === This of course loops through all the "portal" type objects including all the user's dashboards. An easy optimization would be to discard the dashboard object looping when using the admin interface because the dashboards are naturally not needed there (maybe a new type of mask or something?). Other problems that would be good to check is the iterator (eg. hasNext() and getting the next object), and also why is there generated such a huge amount of SQL SELECTs (at least one per portal object). (The following assumes that I can add attachments to this issue) I have attached a zip file that can be extracted into a freshly installed (ie. extracted zip) portal installation (the AS bundled version of 2.6.5) The zip contains the "server" folder so extract it at the root of the portal installation and overwrite all files. After the portal is started you can go to the timing report page at: http://localhost:8080/test/jamon/jamonadmin.jsp There you can reset the counters, access a page in the admin console, and click refresh. After that you can sort the results by eg. the "total" column to see where time is spent. Currently it logs the sql-statements and the refresh method in PortlaObjectManagerBean. The timings for PortlaObjectManagerBean are split in three different parts with "*refresh" being the time for the whole method, "*portals" the time for iterating through the portals and "*pages" the time for looping through the pages. Now at this stage everything is OK and the response times are good. I have included a servlet that generates 10000 dashboards. Go to http://localhost:8080/test/create and wait (it takes a while, the console printsthe progress.) Load this page only once. After the dashboards have been created you can again test the admin console and check the JAmon report page for results. I have also included some screenshots from my testruns. The first (jamon1.gif) is from a newly installed instance listing the portals in the admin console. The second (jamon2.gif) is the same portal list after the dashboards have been created. The third (jamon3.gif) is after clicking "portlet instances" page. Notice how here is generated 40000 sql selects. Note that the included java db is quite fast at these selects. A mysql installation usually takes about 10 seconds for 10000 selects of this type. -- 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

15 years

5
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008