[JBoss-dev] [JBoss JIRA] Resolved: (JBPORTAL-180) Exception in JBossProfiler Forum
[ http://jira.jboss.com/jira/browse/JBPORTAL-180?page=history ] Thomas Heute resolved JBPORTAL-180: --- Assign To: Thomas Heute (was: Julien Viet) Resolution: Done > Exception in JBossProfiler Forum > > > Key: JBPORTAL-180 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-180 > Project: JBoss Portal > Type: Bug > Components: Forums > Environment: jboss.com > Reporter: Clebert Suconic > Assignee: Thomas Heute > > > Oftenly when replying messages into JbossProfiler forum I got a message > "Module threw an exception". > This might be something related to the configuration on JBossProfiler or > maybe some more generic bug. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Hibernate and JBossCache Mbean service in Weblogic 8.1
Have a look at http://www.jboss.org/wiki/Wiki.jsp?page=JBossCacheAndWebLogic first View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872118#3872118 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872118 --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316550 ] Bela Ban commented on JBCACHE-98: - done > Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases > > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Components: Clustering > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > Attachments: jboss-cache.jar > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. > In addition, there is 3.2.x release. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-98) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=history ] Bela Ban updated JBCACHE-98: Attachment: jboss-cache.jar attached JBossCache 1.2.2beta > Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases > > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Components: Clustering > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > Attachments: jboss-cache.jar > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. > In addition, there is 3.2.x release. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-88) Support primitive types
[ http://jira.jboss.com/jira/browse/JBJMX-88?page=comments#action_12316548 ] Michael Kopp commented on JBJMX-88: --- OK, sorry about that. But then this is actually a bug in the xml-console. A came about this, because I updated an attribute and got an exception. > Support primitive types > --- > > Key: JBJMX-88 > URL: http://jira.jboss.com/jira/browse/JBJMX-88 > Project: JBoss JMX > Type: Bug > Versions: JBossAS-4.0.1 > Reporter: Michael Kopp > > > If I have a property/parameter with type 'int' I have to pass it as Integer > into the setAttribute/invoke method. nevertheless, the correct method should > be found. > That does not happen right now! -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1319) redeploy causes OutOfMemoryError
[ http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316547 ] Clebert Suconic commented on JBAS-1319: --- Sorry... i meant no references through class loaders, not garbage collectors. > redeploy causes OutOfMemoryError > > > Key: JBAS-1319 > URL: http://jira.jboss.com/jira/browse/JBAS-1319 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.1 Final > Environment: JBoss 4.0.1 running on fedora core 3, using jdk 1.5.0 > Reporter: Matthew Todd > Assignee: Clebert Suconic > > > Constant redployment, even of a simple web application eventually causes an > OutOfMemoryError in JBoss. > To duplicate, keep on copying a .war package into a servers hot deploy > directory. Eventually an OutOfMemoryError occurs. > This is especially dangerous when running as a cluster, as when the node is > restarted, it is unable to join the cluster again. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1319) redeploy causes OutOfMemoryError
[ http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316546 ] Clebert Suconic commented on JBAS-1319: --- My understanding is that unused classes will be unloaded by the GC. I mean... no instances, on references through garbage collectors, next full GC=class release. So, why do we need additional features in the JVM unloading the class? (Sorry about my ignorance) I was trying to use JProfiler for this, but my JVM is crashing everytime I try to take a big snapshot of the memory. If it's not possible to use an already existent profiler for this, I was able to navigate in the HEAP using JVMTI (JVM 5), and I need to do the dirty job of analyze log files and show the heap through some simple front-end. Also... can this task be deferred to the next version? > redeploy causes OutOfMemoryError > > > Key: JBAS-1319 > URL: http://jira.jboss.com/jira/browse/JBAS-1319 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.1 Final > Environment: JBoss 4.0.1 running on fedora core 3, using jdk 1.5.0 > Reporter: Matthew Todd > Assignee: Clebert Suconic > > > Constant redployment, even of a simple web application eventually causes an > OutOfMemoryError in JBoss. > To duplicate, keep on copying a .war package into a servers hot deploy > directory. Eventually an OutOfMemoryError occurs. > This is especially dangerous when running as a cluster, as when the node is > restarted, it is unable to join the cluster again. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-89) Access the interface not the implementation
[ http://jira.jboss.com/jira/browse/JBJMX-89?page=comments#action_12316545 ] Michael Kopp commented on JBJMX-89: --- You are both right. The MBean I am talkig about is not part of a sar or -service.xml, but is registered by one of my components during startup. As such it can and is a private class. But as Adrian pointed out, the server should access the interface and not the implementation, thus it should not be a problem. unfortuantelly the mbean server is accessing the implementation. > Access the interface not the implementation > --- > > Key: JBJMX-89 > URL: http://jira.jboss.com/jira/browse/JBJMX-89 > Project: JBoss JMX > Type: Bug > Versions: JBossAS-4.0.1 > Reporter: Michael Kopp > Assignee: Dimitris Andreadis > > > I have a package private MBean class, the StandardMBean interface is public > though! > class WorkManager implements WorkManagerMBean > WorkManager is private > WorkManagerMBean is public > Unfortunatelly jboss jmx accesses the implementation directly, thus throwing > an IllegalAccessException. If it would access the mbean via the provided > interface this would not happen. (like jdk 5 is doing) -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-118) refactor all injectors to be constructor interceptors
refactor all injectors to be constructor interceptors - Key: EJBTHREE-118 URL: http://jira.jboss.com/jira/browse/EJBTHREE-118 Project: EJB 3.0 Type: Feature Request Reporter: Bill Burke Fix For: Preview 6 -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-168) Convert to AOP Project no longer showing..
Convert to AOP Project no longer showing.. -- Key: JBIDE-168 URL: http://jira.jboss.com/jira/browse/JBIDE-168 Project: JBoss IDE Type: Bug Components: AOP Plugin Reporter: Marshall Culpepper Assigned to: Marshall Culpepper Fix For: 1.5 Milestone 2 Right clicking on JBossAOP project no longer shows the "Convert to AOP Project" menu option. This is needed for users who have existing Java projects that want to utilize JBossAOP 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-102) Exception when Submitting Load into HttpSession
[ http://jira.jboss.com/jira/browse/JBCACHE-102?page=history ] Ben Wang resolved JBCACHE-102: -- Resolution: Done > Exception when Submitting Load into HttpSession > --- > > Key: JBCACHE-102 > URL: http://jira.jboss.com/jira/browse/JBCACHE-102 > Project: JBoss Cache > Type: Bug > Environment: jboss-4.0 Branch_4_0 > Reporter: Clebert Suconic > Assignee: Ben Wang > > > When submitting load using ou HttpStressTest application, using 10 threads in > the client and 1 session hold per thread, we have thrown these exceptions: > java.lang.IllegalStateException: standardSession.setAttribute.ise > at > org.jboss.web.tomcat.tc5.session.ClusteredSession.setAttribute(ClusteredSession.java:185) > at > org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:129) > at > org.jboss.test.weblayer.HttpStressTest.doGet(HttpStressTest.java:24) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) > 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:75) > 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.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) > at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:147) > at > org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:81) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) > 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:825) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) > 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:534) > And: > java.lang.IllegalArgumentException: You can only add ClusteredSessions to > this Manager > at > org.jboss.web.tomcat.tc5.session.JBossCacheManager.storeSession(JBossCacheManager.java:228) > at > org.jboss.web.tomcat.tc5.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:38) > at > org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) > 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:825) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) > 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:534) -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-120) Change the log level in ReplicationQueue to trace
[ http://jira.jboss.com/jira/browse/JBCACHE-120?page=history ] Ben Wang resolved JBCACHE-120: -- Resolution: Done > Change the log level in ReplicationQueue to trace > - > > Key: JBCACHE-120 > URL: http://jira.jboss.com/jira/browse/JBCACHE-120 > Project: JBoss Cache > Type: Task > Versions: 1.2.1 > Reporter: Ben Wang > Assignee: Ben Wang > Fix For: 1.2.2 > > Original Estimate: 1 hour > Remaining: 1 hour > > The current log level is info for replication queue. It is too verbose. Will > change it to trace. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1609) Backport latest JBossCache (1.2.1)
[ http://jira.jboss.com/jira/browse/JBAS-1609?page=history ] Ben Wang updated JBAS-1609: --- Original Estimate: 21600 (was: 7200) Remaining Estimate: 21600 (was: 7200) > Backport latest JBossCache (1.2.1) > -- > > Key: JBAS-1609 > URL: http://jira.jboss.com/jira/browse/JBAS-1609 > Project: JBoss Application Server > Type: Task > Components: JBoss Cache service > Versions: JBossAS-4.0.2RC1, JBossAS-3.2.7 Final > Reporter: Ben Wang > Assignee: Bela Ban > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 6 hours > Remaining: 6 hours > > We need to backport JBossCache1.2.1 to 4.0.2 release. However, there is one > or two bugs that Bela had to fix after the release in head though. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316540 ] Clebert Suconic commented on JBCACHE-98: Ok... It's 1.2.2 alpha. I guess this is the version that Ben has worked with. Can you upload the JAR at this JIRA task or send-me by e-mail, or instruction in how to get the file please? > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316538 ] Bela Ban commented on JBCACHE-98: - no, it is not: java -jar jboss-cache.jar will reveal the version # > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-227) Quote a Message
Quote a Message --- Key: JBPORTAL-227 URL: http://jira.jboss.com/jira/browse/JBPORTAL-227 Project: JBoss Portal Type: Bug Components: Forums Versions: 2.0 RC Reporter: Roy Russo Assigned to: Julien Viet Fix For: 2.0 RC Quoting a message in forums is not working. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.457 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050330093314Lbuild.457 BUILD COMPLETE - build.457Date of build: 03/30/2005 09:33:14Time to build: 364 minutes 53 secondsLast changed: 03/30/2005 08:43:23Last log entry: convert annoying System.out -> log.debug Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.2.6.1modifiedanddconsole/src/main/org/jboss/console/manager/DeploymentFileRepository.javaconvert annoying System.out -> log.debug
[JBoss-dev] [JBossCache] - Re: Error with nested transactions, but I'm not nesting tran
I am no longer seeing the nested transaction exceptions since adding the exception handling code with a setRollbackOnly() call. I have even removed the thread synchronization (as well as a new synchronization on a separate lock which I'd tried in the mean time). This appears to have solved my problems -- thanks so much Bela for the helpful suggestion. --James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872099#3872099 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872099 --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Portal under vhosts
I am trying to get jboss-portal to run under a number of vhosts. Currently, this involves: * deploying one complete jboss-portal.sar per vhost, each with its own UCL * modifying jboss-web in all the webapps to run under the vhost * changing the domain part of all the mbean names to reflect the vhost * modifying all hard-coded references to mbean names and jndi lookups * jakarta-slide (hmm, still thinking about this) I have a couple of questions. 1. Is anybody else doing (has done) this? Is there a better way to do it? 2. Why are the mbeans loaded in PortalContextListener, rather than just having jboss load them from the sar/META-INF/jboss-service.xml? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872097#3872097 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872097 --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - exception in LRUAlgorithm
Under some heavy load I get the following exception from the LRUAlgorithm.. | 2005-03-30 13:36:12,990 ERROR [org.jboss.cache.eviction.EvictionTimerTask] run(): error processing eviction with exception: org.jboss.cache.eviction.EvictionException: LRUAlgorithm.removeFromQueue(): internal error. Can't find fqn in NodeMap. fqn: /UserContext/user1 will reset the eviction queue list. | | 2005-03-30 13:36:12,990 INFO [org.jboss.cache.eviction.Region] reseteEvictionQueues(): node queue size: 439 region name: /_default_/ | 2005-03-30 13:36:12,990 ERROR [STDERR] org.jboss.cache.eviction.EvictionException: LRUAlgorithm.removeFromQueue(): internal error. Can't find fqn in nodeMap. fqn: /UserContext/user1 | | 2005-03-30 13:36:12,990 ERROR [STDERR] at org.jboss.cache.eviction.LRUAlgorithm.removeFromQueue(LRUAlgorithm.java:216) | | 2005-03-30 13:36:12,990 ERROR [STDERR] at org.jboss.cache.eviction.LRUAlgorithm.processRemovedNodes(LRUAlgorithm.java:108) | | 2005-03-30 13:36:12,990 ERROR [STDERR] at org.jboss.cache.eviction.LRUAlgorithm.processQueues(LRUAlgorithm.java:81) | | 2005-03-30 13:36:12,990 ERROR [STDERR] at org.jboss.cache.eviction.LRUAlgorithm.process(LRUAlgorithm.java:51) | | 2005-03-30 13:36:12,990 ERROR [STDERR] at org.jboss.cache.eviction.EvictionTimerTask.run(EvictionTimerTask.java:35) | | 2005-03-30 13:36:12,990 ERROR [STDERR] at java.util.TimerThread.mainLoop(Timer.java:432) | | 2005-03-30 13:36:12,990 ERROR [STDERR] at java.util.TimerThread.run(Timer.java:382) I saw that in the LRUAlgorithm itself, you catch and ignore this exception if it's called from evict(). If this exception happens from a call to processRemovedNodes, is is bubbled up to the exictionTimerTask and the nodeList is reset, which makes nothing timout ever. Should this exception be ignored from processRemovedNodes? If this exception should not be ignored, I can work on getting a better unit test to show this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872096#3872096 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872096 --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-48) build for security
[ http://jira.jboss.com/jira/browse/JBBUILD-48?page=history ] Ryan Campbell resolved JBBUILD-48: -- Resolution: Done All of the release artifacts for this module are now complete. > build for security > -- > > Key: JBBUILD-48 > URL: http://jira.jboss.com/jira/browse/JBBUILD-48 > Project: JBoss Build System > Type: Sub-task > Reporter: Ryan Campbell > Fix For: milestone-1 > > -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Re: can't open JSP -
that's fixed in Eclipse 3.0.1 M5 and jboss-ide 1.5M5 thanks to jboss-ide developers ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872092#3872092 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872092 --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1632) clustering unit test failure
[ http://jira.jboss.com/jira/browse/JBAS-1632?page=history ] Clebert Suconic reassigned JBAS-1632: - Assign To: Clebert Suconic (was: Ben Wang) > clustering unit test failure > > > Key: JBAS-1632 > URL: http://jira.jboss.com/jira/browse/JBAS-1632 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.2RC1, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha > Reporter: Ben Wang > Assignee: Clebert Suconic > Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.7 Final > Attachments: 2005-03-30.17-34.tgz, jboss-cache.jar > > Original Estimate: 4 hours > Remaining: 4 hours > > Currently, tests-clustering target has numerous failure. It was because that > the jboss-cache.jar is not the latest. In order for the test to success, we > will need it. > Clebert, you can verify this by copying /tmp/jboss-cache.jar in Atl machine > to all/lib directory. > This issue is therefore depends on backporting JBossCache release 1.2.2. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316532 ] Clebert Suconic commented on JBCACHE-98: I've already done this as part of JBAS-1632. Ben asked me to run it again (just in case), and it would be already done if our sourceforge-cvs wasn't so slw. :-) > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316531 ] Bela Ban commented on JBCACHE-98: - Looks like 4.0.2 might be delayed by 1 week, this gives me time to release 1.2.2 and create a thirdparty lib jboss-cache.jar that 4.0.2 will use. Clebert: I can already give you the jboss-cache.jar file for testing purposes, you'd simply replace server//all/lib/jboss-cache.jar with it, and could let me know whether the tests pass. This way, we could parallelize integration into 4.0.2 > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-2) Add targetdefs for build.bin and build.resources
[ http://jira.jboss.com/jira/browse/JBBUILD-2?page=history ] Ryan Campbell resolved JBBUILD-2: - Assign To: Ryan Campbell Resolution: Done Both build.bin and build.resoureces have been implemented. > Add targetdefs for build.bin and build.resources > > > Key: JBBUILD-2 > URL: http://jira.jboss.com/jira/browse/JBBUILD-2 > Project: JBoss Build System > Type: Task > Reporter: Ryan Campbell > Assignee: Ryan Campbell > Fix For: milestone-1 > > > Add targetdefs for build.bin and build.resources -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1632) clustering unit test failure
[ http://jira.jboss.com/jira/browse/JBAS-1632?page=history ] Clebert Suconic reassigned JBAS-1632: - Assign To: Ben Wang (was: Clebert Suconic) I executed the tests... see comments at this task. > clustering unit test failure > > > Key: JBAS-1632 > URL: http://jira.jboss.com/jira/browse/JBAS-1632 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.2RC1, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha > Reporter: Ben Wang > Assignee: Ben Wang > Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.7 Final > Attachments: 2005-03-30.17-34.tgz, jboss-cache.jar > > Original Estimate: 4 hours > Remaining: 4 hours > > Currently, tests-clustering target has numerous failure. It was because that > the jboss-cache.jar is not the latest. In order for the test to success, we > will need it. > Clebert, you can verify this by copying /tmp/jboss-cache.jar in Atl machine > to all/lib directory. > This issue is therefore depends on backporting JBossCache release 1.2.2. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1632) clustering unit test failure
[ http://jira.jboss.com/jira/browse/JBAS-1632?page=comments#action_12316528 ] Clebert Suconic commented on JBAS-1632: --- Even by changing the library we still have few errors. I've attached the results (2005-03-30.17-34.tgz) and I executed this test by: ant -Dnojars=true tests-clustering-all-stacks > clustering unit test failure > > > Key: JBAS-1632 > URL: http://jira.jboss.com/jira/browse/JBAS-1632 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.2RC1, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha > Reporter: Ben Wang > Assignee: Clebert Suconic > Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.7 Final > Attachments: 2005-03-30.17-34.tgz, jboss-cache.jar > > Original Estimate: 4 hours > Remaining: 4 hours > > Currently, tests-clustering target has numerous failure. It was because that > the jboss-cache.jar is not the latest. In order for the test to success, we > will need it. > Clebert, you can verify this by copying /tmp/jboss-cache.jar in Atl machine > to all/lib directory. > This issue is therefore depends on backporting JBossCache release 1.2.2. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBJMX-88) Support primitive types
[ http://jira.jboss.com/jira/browse/JBJMX-88?page=history ]
Adrian Brock closed JBJMX-88:
-
Resolution: Won't Fix
Use the class name not the string from the programming language:
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Class.html#getName()
server.invoke(,,, new String[] { Integer.TYPE.getName()) };
or
server.invoke(,,, new String[] { "I" };
NOT
server.invoke(,,, new String[] { Integer.class.getName()) };
NOT
server.invoke(,,, new String[] { "int" };
I don't know how many times I have answered this question in the forums,
but it is a lot
> Support primitive types
> ---
>
> Key: JBJMX-88
> URL: http://jira.jboss.com/jira/browse/JBJMX-88
> Project: JBoss JMX
> Type: Bug
> Versions: JBossAS-4.0.1
> Reporter: Michael Kopp
>
>
> If I have a property/parameter with type 'int' I have to pass it as Integer
> into the setAttribute/invoke method. nevertheless, the correct method should
> be found.
> That does not happen right now!
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1632) clustering unit test failure
[ http://jira.jboss.com/jira/browse/JBAS-1632?page=history ] Clebert Suconic updated JBAS-1632: -- Attachment: jboss-cache.jar I attached the mentioned file. > clustering unit test failure > > > Key: JBAS-1632 > URL: http://jira.jboss.com/jira/browse/JBAS-1632 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.2RC1, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha > Reporter: Ben Wang > Assignee: Clebert Suconic > Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.7 Final > Attachments: jboss-cache.jar > > Original Estimate: 4 hours > Remaining: 4 hours > > Currently, tests-clustering target has numerous failure. It was because that > the jboss-cache.jar is not the latest. In order for the test to success, we > will need it. > Clebert, you can verify this by copying /tmp/jboss-cache.jar in Atl machine > to all/lib directory. > This issue is therefore depends on backporting JBossCache release 1.2.2. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316522 ] Clebert Suconic commented on JBCACHE-98: It looks like it's mandatory to backport JBossCache to AS 4.0 due to the dependency on this JIRA task: JBAS-1632. Ben, can you confirm that please? Clebert > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-101) EntityManager not useable in PostConstruct callback of StatelessSessionBean.
[ http://jira.jboss.com/jira/browse/EJBTHREE-101?page=history ] Kabir Khan closed EJBTHREE-101: --- Resolution: Rejected I think it is fine. From spec: 3.4 Callbacks and Callback Listener Classes ... Callbacks can invoke JNDI, JDBC, JMS, and other EJBs, but not the EntityManager. [Note: This will be more closely defined for session beans and message-driven beans in synch with Tables 2, 4, 13 in the Enterprise JavaBeans Core Contracts and Requirements specification document.] ... 4.1.4 Callbacks for Stateless Session Beans The following lifecycle event callbacks are supported for stateless session beans: â PostConstruct â PreDestroy The PostConstruct callback occurs after any dependency injection has been performed by the container and before the first business method invocation on the bean.[3] The PostConstruct method is invoked in an unspecified transaction context and security context. The PreDestroy callback occurs at the time the bean instance is destroyed.[4] The PreDestroy method executes in an unspecified transaction and security context. > EntityManager not useable in PostConstruct callback of StatelessSessionBean. > > > Key: EJBTHREE-101 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-101 > Project: EJB 3.0 > Type: Bug > Versions: Preview 4 > Environment: JBoss-4.0.1sp1, EJB3-Preview4, Windows 2000. > Reporter: Shagoon > Assignee: Kabir Khan > Fix For: Preview 5 > > > When trying to use the entity manager for a query in a PostConstruct callback > in a StatelessSessionBean, execution fails with: > Caused by: java.lang.RuntimeException: EntityManager must be access within a > transaction > at > org.jboss.ejb3.entity.HibernateSessionFactory.getSession(HibernateSessionFactory.java:105) > at > org.jboss.ejb3.entity.EntityManagerImpl.getSession(EntityManagerImpl.java:146) > at > org.jboss.ejb3.entity.EntityManagerImpl.createQuery(EntityManagerImpl.java:39) > at some.package.postConstructCallback(SomeDAOBean.java:99) > ... 26 more -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - How I can get in AdminCMSPortlet???
Hello all, my problem is: I have installed JBoss Portal. It works. But i can't get results from AdminCMSPortlet. My steps are: 1.I login successfully 2.I go from "EntryPage" to "AdminControlPage" 3. In window "Permissions management" i click on AdminCSMPortlet Button 4. And i am in "Permissions management Distinkt". I think i should be in AdminCSMPortletControlPage. Pleas tell me any solutions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872048#3872048 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872048 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1632) clustering unit test failure
clustering unit test failure Key: JBAS-1632 URL: http://jira.jboss.com/jira/browse/JBAS-1632 Project: JBoss Application Server Type: Bug Components: Clustering Versions: JBossAS-4.0.2RC1, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha Reporter: Ben Wang Assigned to: Clebert Suconic Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.7 Final Currently, tests-clustering target has numerous failure. It was because that the jboss-cache.jar is not the latest. In order for the test to success, we will need it. Clebert, you can verify this by copying /tmp/jboss-cache.jar in Atl machine to all/lib directory. This issue is therefore depends on backporting JBossCache release 1.2.2. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1631) Cleanup System.out from console servlets and mbeans
[ http://jira.jboss.com/jira/browse/JBAS-1631?page=history ] Dimitris Andreadis closed JBAS-1631: Resolution: Done Done > Cleanup System.out from console servlets and mbeans > --- > > Key: JBAS-1631 > URL: http://jira.jboss.com/jira/browse/JBAS-1631 > Project: JBoss Application Server > Type: Task > Components: Management Service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Environment: console > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1631) Cleanup System.out from console servlets and mbeans
Cleanup System.out from console servlets and mbeans --- Key: JBAS-1631 URL: http://jira.jboss.com/jira/browse/JBAS-1631 Project: JBoss Application Server Type: Task Components: Management Service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Environment: console Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Error with nested transactions, but I'm not nesting tran
Thanks for your responses. Yes I realize that this has nothing to do with JBossCache, but there doesn't appear to be a JTA/Transactions specific forum so this one appears to be the most relevant. Plus I've had the best luck with getting my answers answered on this forum as opposed to other forums -- Ben and Bela appear to really be on the ball as far as focusing their attention to user problems posted here. The updateReceivedTime() may be called by several clients, and hence one invokation may start before another finishes. But I thought that I had prevented this from happening by marking the method as synchronized, which will prevent more than one thread from entering the method. Is this not the case ? If not then can someone suggest any other threading tricks I can use in order to prevent this transaction nesting ? I will add code to rollback the transaction if there's an exception, but my understanding is that there is no exception happening which requires a rollback, it's just the nested transaction which is causing the exception. So I need to isolate the updateReceivedTime() to a single thread and make sure it completes before allowing another thread to invoke it which opens the second/nested transaction. Apparently the synchronized keyword isn't sufficient for this and I need to do more with controlling the threads. At least that's me take on things at this point. Any further suggestions ? Thanks. --James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872043#3872043 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872043 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.910 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050330073525Lbuild.910 BUILD COMPLETE - build.910Date of build: 03/30/2005 07:35:25Time to build: 62 minutes 42 secondsLast changed: 03/30/2005 04:59:42Last log entry: create jar and rar for ha xa jdbc resource adapter Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (14)1.78modifiedloubyanskyconnector/build.xmlcreate jar and rar for ha xa jdbc resource adapter1.30modifiedloubyanskyconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslmodified to support ha-xa-datasource and moved url-delimeter to common properties1.1addedloubyanskyconnector/src/main/org/jboss/resource/adapter/jdbc/xa/HAXAManagedConnectionFactory.javafirst impl of HA XA managed connection factory1.17modifiedloubyanskyconnector/src/main/org/jboss/resource/adapter/jdbc/xa/XAManagedConnectionFactory.javamade xaProps protected1.1addedovidiufjms/src/main/org/jboss/jms/tools/Colocated.javaadded command line tool for colocated client/server1.4modifiedovidiufjms/src/main/org/jboss/jms/tools/Client.javaadded command line tool for colocated client/server1.2modifiedovidiufjms/src/main/org/jboss/jms/client/container/LocalInterceptor.javaadded command line tool for colocated client/server1.1addedovidiufjms/src/bin/runcolocatedadded command line tool for colocated client/server1.5modifiedovidiufjms/src/bin/runserveradded command line tool for colocated client/server1.1addedovidiufjms/docs/JBossMessagingConsumer.sxdadded command line tool for colocated client/server1.1addedovidiufjms/tests/src/org/jboss/test/messaging/util/RendezVousTest.java*** empty log message ***1.2modifiedovidiufjms/src/main/org/jboss/jms/server/remoting/JMSServerInvocationHandler.java*** empty log message ***1.3modifiedovidiufjms/src/main/org/jboss/jms/util/RendezVous.java*** empty log message ***1.10modifiedovidiufjms/src/bin/runtest*** empty log message ***
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1480) Web Console: Monitors: Errors in the log
[ http://jira.jboss.com/jira/browse/JBAS-1480?page=history ] Dimitris Andreadis reassigned JBAS-1480: Assign To: Dimitris Andreadis > Web Console: Monitors: Errors in the log > > > Key: JBAS-1480 > URL: http://jira.jboss.com/jira/browse/JBAS-1480 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.2 Final > Environment: JBoss 4.0.1 > Reporter: Anil Saldhana > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final > Attachments: FreeMemoryMonitor-service.xml > > > I see an error in the server log when using web console which is shown below. > Step 1: Create a monitor on Free Memory and call it "FreeMemoryMonitor". > Step 2: You will have a file called "FreeMemoryMonitor-service.xml" in > deploy/management/monitors. [Attached to the case]. > See error in the server log as follows: > 16:35:10,364 ERROR [MainDeployer] Could not make local copy for > file:/Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > java.io.FileNotFoundException: > /Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > at > org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:71) > at > org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:80) > at java.net.URL.openStream(URL.java:913) > at org.jboss.deployment.MainDeployer.copy(MainDeployer.java:1174) > at > org.jboss.deployment.MainDeployer.makeLocalCopy(MainDeployer.java:112 > No big deal. The error should not be thrown in a production environment with > multiple monitors. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1449) Update the ServerInfo memory ops to use the jdk 5 mbeans
[ http://jira.jboss.com/jira/browse/JBAS-1449?page=comments#action_12316514 ] Dimitris Andreadis commented on JBAS-1449: -- I had a look at the information provided by the jdk5 platform mbeans, wrt memory metrics, but I don't see how it is different from what the ServerInfo MBean already exposes. The reported metrics currently are: MaxMemory TotalMemory FreeMemory. I checked the above number with the numbers reported by the new MemoryMXBean and we have: Committed memory = TotalMemory MaxMemory = MaxMemory Finally MemoryMXBean reports "used" memory instead of "free" memory, but the values can be derived by subtracting from committed or total memory. What you get with the new platform mbeans is the detailed break down of memory into memory pools, plus some threhold notifications. > Update the ServerInfo memory ops to use the jdk 5 mbeans > > > Key: JBAS-1449 > URL: http://jira.jboss.com/jira/browse/JBAS-1449 > Project: JBoss Application Server > Type: Feature Request > Components: JMX, MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 4 hours > Remaining: 4 hours > > The memory related ops of the org.jboss.system.server.ServerInfo need to be > updated to use the jdk 5 memory mbeans. > http://java.sun.com/j2se/1.5.0/docs/guide/management/mxbeans.html -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBIDE-167) Hibernate Tools alpha3
[ http://jira.jboss.com/jira/browse/JBIDE-167?page=history ] Max Andersen updated JBIDE-167: --- Fix Version: 1.5 Milestone 2 > Hibernate Tools alpha3 > -- > > Key: JBIDE-167 > URL: http://jira.jboss.com/jira/browse/JBIDE-167 > Project: JBoss IDE > Type: Task > Versions: 1.5 Milestone 2 > Reporter: Max Andersen > Assignee: Marshall Culpepper > Fix For: 1.5 Milestone 2 > > > http://opensource.atlassian.com/projects/hibernate/secure/IssueNavigator.jspa?reset=true&pid=10030&fixfor=10232 -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-167) Hibernate Tools alpha3
Hibernate Tools alpha3 -- Key: JBIDE-167 URL: http://jira.jboss.com/jira/browse/JBIDE-167 Project: JBoss IDE Type: Task Versions: 1.5 Milestone 2 Reporter: Max Andersen Assigned to: Marshall Culpepper Fix For: 1.5 Milestone 2 http://opensource.atlassian.com/projects/hibernate/secure/IssueNavigator.jspa?reset=true&pid=10030&fixfor=10232 -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-jdk-matrix build.87 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050330051916Lbuild.87 BUILD COMPLETE - build.87Date of build: 03/30/2005 05:19:16Time to build: 45 minutes 16 secondsLast changed: 03/29/2005 01:05:09Last log entry: JBAS-1622 findSessions api is not correct Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (3)1.1.2.15modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api is not correct1.1.2.15modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api is not correct1.1.2.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString messages
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-119) Missing notification for remove() and addChild()
[ http://jira.jboss.com/jira/browse/JBCACHE-119?page=history ] Bela Ban resolved JBCACHE-119: -- Resolution: Done Testcase is TreeCacheListenerTest > Missing notification for remove() and addChild() > > > Key: JBCACHE-119 > URL: http://jira.jboss.com/jira/browse/JBCACHE-119 > Project: JBoss Cache > Type: Bug > Versions: 1.2.1 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 1.2.2 > > -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-119) Missing notification for remove() and addChild()
Missing notification for remove() and addChild() Key: JBCACHE-119 URL: http://jira.jboss.com/jira/browse/JBCACHE-119 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Priority: Minor Fix For: 1.2.2 -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite build.99 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050330025342Lbuild.99 BUILD COMPLETE - build.99Date of build: 03/30/2005 02:53:42Time to build: 92 minutes 18 secondsLast changed: 03/29/2005 01:05:09Last log entry: JBAS-1622 findSessions api is not correct Unit Tests: (1967) Total Errors and Failures: (8)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (3)1.1.2.15modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaJBAS-1622 findSessions api is not correct1.1.2.15modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1622 findSessions api is not correct1.1.2.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaFixed sm getString messages
[JBoss-dev] [JBossCache] - Re: Opinion: TreeCache/CacheLoader isomorphism
The TreeCache and CacheLoader class and interface are not the same. I intend to provide only an interface 'Cache' for TreeCache and TreeCacheAop in 1.3. CacheLoaders would then implement that interface as well, the idea being that a Cache can be either a real Cache or a CacheLoader. This would allow for hierarchies of caches. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872008#3872008 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872008 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: CacheLoader: exists() before get() inefficient - solutio
You're right. I have created a JIRA issue (http://jira.jboss.com/jira/browse/JBCACHE-118) that I already started working on. However, it broke the CacheLoader unit tests, so I commented my changes and moved to issue to 1.2.3. I don't want to retest 1.2.2 extensively, this is just the standalone module plus some minor changes View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872007#3872007 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872007 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-118) Inefficient CacheLoader.exists() followed by CacheLoader.get()
[ http://jira.jboss.com/jira/browse/JBCACHE-118?page=history ] Bela Ban updated JBCACHE-118: - Fix Version: 1.2.3 (was: 1.2.2) > Inefficient CacheLoader.exists() followed by CacheLoader.get() > -- > > Key: JBCACHE-118 > URL: http://jira.jboss.com/jira/browse/JBCACHE-118 > Project: JBoss Cache > Type: Task > Versions: 1.2.1 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 1.2.3 > > > I have a CacheLoader that I am using to allow a TreeCache to act as the > primary interface to a DAV/JDBC data model. Each access to the backend can be > quite expensive. I note that a CacheLoader.get() is always preceeded by a > CacheLoader.exists(), which seems redundant to me and has the unfortunate > effect of doubling the backend load. Am I missing something here? -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-118) Inefficient CacheLoader.exists() followed by CacheLoader.get()
Inefficient CacheLoader.exists() followed by CacheLoader.get() -- Key: JBCACHE-118 URL: http://jira.jboss.com/jira/browse/JBCACHE-118 Project: JBoss Cache Type: Task Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Priority: Minor Fix For: 1.2.2 I have a CacheLoader that I am using to allow a TreeCache to act as the primary interface to a DAV/JDBC data model. Each access to the backend can be quite expensive. I note that a CacheLoader.get() is always preceeded by a CacheLoader.exists(), which seems redundant to me and has the unfortunate effect of doubling the backend load. Am I missing something here? -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-117) Unnecessary lock acquisition with IsolationLevel.NONE
[ http://jira.jboss.com/jira/browse/JBCACHE-117?page=history ] Bela Ban resolved JBCACHE-117: -- Resolution: Done LockInterceptor.lock() does *not* acquire a lock if isolation level == NONE > Unnecessary lock acquisition with IsolationLevel.NONE > - > > Key: JBCACHE-117 > URL: http://jira.jboss.com/jira/browse/JBCACHE-117 > Project: JBoss Cache > Type: Bug > Versions: 1.2.1 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.2 > > > java.lang.IllegalStateException: addWriter(): owner already existed > at org.jboss.cache.lock.LockMap.addWriter(LockMap.java:112) > at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:175) > at org.jboss.cache.Node.acquireWriteLock(Node.java:483) > at org.jboss.cache.Node.acquire(Node.java:440) > at > org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:240) > at > org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:156) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at > org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) > > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at > org.jboss.cache.interceptors.ReplicationInterceptor.replicate(ReplicationInterceptor.java:217) > > at org.jboss.cache.TreeCache._replicate(TreeCache.java:2682) > 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:324) > at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236) > at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:220) > at > org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615) > > at > org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512) > > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326) > at > org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722) > > at > org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554) > > at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691) > at java.lang.Thread.run(Thread.java:534) -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-117) Unnecessary lock acquisition with IsolationLevel.NONE
[ http://jira.jboss.com/jira/browse/JBCACHE-117?page=comments#action_12316510 ] Bela Ban commented on JBCACHE-117: -- added test case IsolationLevelNoneTest > Unnecessary lock acquisition with IsolationLevel.NONE > - > > Key: JBCACHE-117 > URL: http://jira.jboss.com/jira/browse/JBCACHE-117 > Project: JBoss Cache > Type: Bug > Versions: 1.2.1 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.2 > > > java.lang.IllegalStateException: addWriter(): owner already existed > at org.jboss.cache.lock.LockMap.addWriter(LockMap.java:112) > at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:175) > at org.jboss.cache.Node.acquireWriteLock(Node.java:483) > at org.jboss.cache.Node.acquire(Node.java:440) > at > org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:240) > at > org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:156) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at > org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) > > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at > org.jboss.cache.interceptors.ReplicationInterceptor.replicate(ReplicationInterceptor.java:217) > > at org.jboss.cache.TreeCache._replicate(TreeCache.java:2682) > 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:324) > at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236) > at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:220) > at > org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615) > > at > org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512) > > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326) > at > org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722) > > at > org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554) > > at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691) > at java.lang.Thread.run(Thread.java:534) -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Lock Acquisition Timeouts In JBC 1.2.1
I fixed this (http://jira.jboss.com/jira/browse/JBCACHE-117). Will be available in JBossCache 1.2.2 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872000#3872000 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872000 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-117) Unnecessary lock acquisition with IsolationLevel.NONE
Unnecessary lock acquisition with IsolationLevel.NONE - Key: JBCACHE-117 URL: http://jira.jboss.com/jira/browse/JBCACHE-117 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.2 java.lang.IllegalStateException: addWriter(): owner already existed at org.jboss.cache.lock.LockMap.addWriter(LockMap.java:112) at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:175) at org.jboss.cache.Node.acquireWriteLock(Node.java:483) at org.jboss.cache.Node.acquire(Node.java:440) at org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:240) at org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:156) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) at org.jboss.cache.interceptors.ReplicationInterceptor.replicate(ReplicationInterceptor.java:217) at org.jboss.cache.TreeCache._replicate(TreeCache.java:2682) 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:324) at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236) at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:220) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615) at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512) at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554) at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691) at java.lang.Thread.run(Thread.java:534) -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1626) ClientReconnectInterceptor doesn't work
[ http://jira.jboss.com/jira/browse/JBAS-1626?page=comments#action_12316508 ] jens.schanz commented on JBAS-1626: --- Sorry, i can't provide a bugfix for this issue. I've read in the config file, that this is a violation against the specs, but this is at the moment the only solution we could choose. We use JMS over WAN and run sometimes into problems with disconnects. If the client would reconnect, he receives a exception with subscription allready in use. Our only solution at this time is a complete reboot of JBoss. > ClientReconnectInterceptor doesn't work > --- > > Key: JBAS-1626 > URL: http://jira.jboss.com/jira/browse/JBAS-1626 > Project: JBoss Application Server > Type: Bug > Components: JMS service > Versions: JBossAS-4.0.1 SP1 > Environment: SuSE Linux Enterprise Server 8, JBoss-4.0.1SP1 > Reporter: jens.schanz > Priority: Minor > > > File: jbossmq-service.xml > >name="jboss.mq:service=ClientReconnectInterceptor"> > name="InterceptorClass">org.jboss.mq.server.ClientReconnectInterceptor > optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager > > I have uncommented this feature, because our application has a bug with > unregistering and disconnecting. Until this bug is solved I want to enable > this feature in JBoss, but it doesn't work. I allready get the message > "reconnect failed : javax.jms.InvalidClientIDException: This client id > 'system1' is already registered!". > Maybee it's a bug. Could someone please check this? -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
