August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-3260) JNDI-View.list() throws NPE

by Ortwin Glück (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3260?page=comments#action_12341185 ] Ortwin Glück commented on JBAS-3260: ------------------------------------ Workaround: in conf/jboss-services.xml remove HAJNDI from JNDIView: <mbean code="org.jboss.naming.JNDIView" name="jboss:service=JNDIView" xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">   </mbean> > JNDI-View.list() throws NPE > --------------------------- > > Key: JBAS-3260 > URL: http://jira.jboss.com/jira/browse/JBAS-3260 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: JBossAS-5.0.0.Beta, JBossAS-4.0.4.GA > Environment: 4.0.4.GA-patch1 from installer, "ejb3"-config. Stock install without modifications. JDK 1.5.0._06 on WinXP > Reporter: Heiko W. Rupp > Assigned To: Heiko W. Rupp > Priority: Minor > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > When using the JNDIView-MBean list() operation, the console shows: > 11:37:09,024 ERROR [JNDIView] JNDIView.getHAJndiAttributes() failed > java.lang.NullPointerException: name cannot be null > at javax.management.ObjectName.construct(ObjectName.java:342) > at javax.management.ObjectName.<init>(ObjectName.java:1304) > at org.jboss.naming.JNDIView.getHAJndiAttributes(JNDIView.java:836) > at org.jboss.naming.JNDIView.getHAUrl(JNDIView.java:811) > at org.jboss.naming.JNDIView.list(JNDIView.java:193) > 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:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > 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:262) > 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:717) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java > :664) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:595) > There is output on the web page, but I can not tell, if this is all valid. > In java:comp it shows: > +- timedCacheFactory (class: javax.naming.Context) > Failed to lookup: timedCacheFactory, errmsg=org.jboss.util.TimedCachePolicy > +- TransactionPropagationContextExporter (class: org.jboss.tm.TransactionPropagationContextFactory) > +- StdJMSPool (class: org.jboss.jms.asf.StdServerSessionPoolFactory) > +- Mail (class: javax.mail.Session) > +- comp.ejb3 (class: javax.naming.Context) > | NonContext: null > This might come from the comp.ejb3 subcontext, which is not in the FR of the ejb3 spec. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-418) RHS Action Langauge

by Mark Proctor (JIRA)

RHS Action Langauge ------------------- Key: JBRULES-418 URL: http://jira.jboss.com/jira/browse/JBRULES-418 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Mark Proctor Assigned To: Bob McWhirter Fix For: 3.1-m2 We need a RHS declarative language that is a subset of groovy. This language should only allow method and function calls along with object instantiation and foreach iteration. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3358) Work directory shouldn't be deleted

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3358?page=all ] Anil Saldhana reassigned JBAS-3358: ----------------------------------- Assignee: Anil Saldhana (was: Remy Maucherat) > Work directory shouldn't be deleted > ----------------------------------- > > Key: JBAS-3358 > URL: http://jira.jboss.com/jira/browse/JBAS-3358 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Javid Jamae > Assigned To: Anil Saldhana > Fix For: JBossAS-4.0.5.GA > > > I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down. > Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted). -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-391) SVN access request for bentruitt

by Michael Neale (JIRA)

SVN access request for bentruitt -------------------------------- Key: JBRULES-391 URL: http://jira.jboss.com/jira/browse/JBRULES-391 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: All Reporter: Michael Neale Assigned To: Damon Sicore Damon, need Ben Truitt (jboss.com user name is bentruitt) to be setup as a committer in SVN. -- 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

19 years, 11 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-382) JDBC persistance with pojo cache and performance issue. Slow performance after Blob inserted

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-382?page=all ] Ben Wang resolved JBCACHE-382. ------------------------------ Resolution: Done > JDBC persistance with pojo cache and performance issue. Slow performance after Blob inserted > -------------------------------------------------------------------------------------------- > > Key: JBCACHE-382 > URL: http://jira.jboss.com/jira/browse/JBCACHE-382 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: POJOCache > Environment: JDk 1.4.2_06, Linux Pentium 4, Debian distribution, Informix Dynamic Server 9.3 back end(running on a server elsewhere) , > Reporter: John Lukar > Assigned To: Ben Wang > Fix For: POJOCache > > Attachments: JDBC2CacheLoader.java, JDBC2CacheLoaderTest.java, testJbossCache.tar.gz > > > I turned on JDBC persistance with Informix backend using TreeCacheAOP. > The performance numbers are horribly slow. > The "jbosscache" table created as part of service startup has the columns "fqn","node","parent" with types varchar(255), blob, varchar(255) respectively. > The inserts of my pojo business objects as they are serialized into byte stream by the cache, are taking on the average of 15 seconds for each row. The DB is on another server off of the subnet. > denormolizing the pojo object and writing a row out with all pojo fields to non-blob/byte columns as varchar, integers, etc. is a lot faster. > Is this going to be the expected behaviour where JDBC persistance of POJO objects using serialized byte stream as default mechanism by TreeCache/AOP is going to be magnitude slower ? > Can someone suggest a way to use JDBC persistance and yet make it fast or as fast as file persistance, etc. ? Maybe my own cacheLoader scheme ? > I have to use JDBC/informix(vs. sleepycat) in order to not worry about local disk failure issues on persistance and recovery. A remote DB seems to be way. > thanks -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCLUSTER-7) Http session replication using JBossCache

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-7?page=all ] Brian Stansberry resolved JBCLUSTER-7. -------------------------------------- Resolution: Done I'm resolving this as done; the benchmarking subtask is an ongoing effort. > Http session replication using JBossCache > ----------------------------------------- > > Key: JBCLUSTER-7 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-7 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q3Y6 > > > For HttpSession replication using JBossCache, we will need: > 1. Using plain cache > 2. Using cache aop for session attribute fine-grain replication > 3. Complete the automatic stress testing -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-77) Add script to ./bin directory of JBossAS which creates a cluster config

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-77?page=all ] Brian Stansberry updated JBCLUSTER-77: -------------------------------------- Fix Version/s: Q4Y6 (was: Q3Y6) Priority: Minor (was: Major) > Add script to ./bin directory of JBossAS which creates a cluster config > ----------------------------------------------------------------------- > > Key: JBCLUSTER-77 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-77 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Ben Wang > Priority: Minor > Fix For: Q4Y6 > > > Example: > ./create-cluster-config > This creates node1 and node2 under JBOSS_HOME/server. > The script can be copied from one of the labs in the Clustering training -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-654) Upgrade to JBoss AOP 2.0 to prevent classloader memory leakage during re-deployment

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-654?page=all ] Ben Wang updated JBCACHE-654: ----------------------------- Fix Version/s: 2.0.0 (was: POJOCache) > Upgrade to JBoss AOP 2.0 to prevent classloader memory leakage during re-deployment > ----------------------------------------------------------------------------------- > > Key: JBCACHE-654 > URL: http://jira.jboss.com/jira/browse/JBCACHE-654 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > > As titled. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-115) Major Clustering Features in JBoss 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-115?page=all ] Brian Stansberry updated JBCLUSTER-115: --------------------------------------- Priority: Blocker (was: Major) > Major Clustering Features in JBoss 5.0 > -------------------------------------- > > Key: JBCLUSTER-115 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-115 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Blocker > Fix For: Q3Y6 > > > Overall tracking issue for *major* clustering features/fixes to be included in JBoss AS 5.0.0. > There will of course be numerous minor issues; please track those with a filter on the issues in the JBAS project. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-583) add jms support for the messaging service

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-583?page=all ] Tom Baeyens updated JBPM-583: ----------------------------- Fix Version/s: jBPM 3.1.3 Priority: Critical (was: Major) promoted to highest feature request priority. it will be delivered on the 3.2, but also on the 3.1 branch. the actual versions of delivery are indicative. > add jms support for the messaging service > ----------------------------------------- > > Key: JBPM-583 > URL: http://jira.jboss.com/jira/browse/JBPM-583 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Jim Rigsbee > Priority: Critical > Fix For: jBPM 3.2 alpha 2, jBPM 3.1.3 > > -- 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

19 years, 11 months

1
0
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 August 2006