April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2994) Event expiration offset

by Tomáš Schlosser (JIRA)

Event expiration offset ----------------------- Key: JBRULES-2994 URL: https://issues.jboss.org/browse/JBRULES-2994 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M2 Reporter: Tomáš Schlosser Assignee: Mark Proctor When inspecting KnowledgeBase through JConsole event always have expiration offset -1 although rule declares it to 10s: -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

5
14
0 / 0

[JBoss JIRA] Created: (JBAS-9351) Description Providers for OSGi subsystem

by Kabir Khan (JIRA)

Description Providers for OSGi subsystem ---------------------------------------- Key: JBAS-9351 URL: https://issues.jboss.org/browse/JBAS-9351 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Thomas Diesler Fix For: 7.0.0.Beta4 The OSGi subsystem needs to provide its descriptions, if I do this in the command line tool: :read-resource-description(recursive=1,operations=1,inherited=0) osgi currently does not give any meaningful descriptions of either its model or operations: ... "osgi" => {"operations" => {"add" => undefined}}, ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1137) ClusterChooserInterceptor does not support transaction failover authorisations

by Galder Zamarreno (JIRA)

ClusterChooserInterceptor does not support transaction failover authorisations ------------------------------------------------------------------------------ Key: EJBTHREE-1137 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1137 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3 Reporter: Galder Zamarreno org.jboss.aspects.remoting.ClusterChooserInterceptor does not contain logic to deal with transaction failover authorisations, contrary to legacy JRMP invoker or Unified invoker. The reason I'm entering this as a bug rather than as a feature request is because not having such logic is allowing failovers when they shouldn't happen. -- 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

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1141) LoadBalancePolicy that tries to pin all requests associated with a tx to one server

by Galder Zamarreno (JIRA)

LoadBalancePolicy that tries to pin all requests associated with a tx to one server ----------------------------------------------------------------------------------- Key: EJBTHREE-1141 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1141 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Create EJB3 transaction sticky load balance policies. -- 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

13 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-8548) Integrate SwitchBoard into AS

by jaikiran pai (JIRA)

Integrate SwitchBoard into AS ----------------------------- Key: JBAS-8548 URL: https://jira.jboss.org/browse/JBAS-8548 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 6.0.0.CR1 This JIRA will track the integration of the SwitchBoard component http://community.jboss.org/wiki/Switchboard into AS. Initially, the integration is being done on a separate branch https://svn.jboss.org/repos/jbossas/branches/switchboard-integration/ and finally will be merged to AS trunk. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-8671) ClassNotFoundException when a EJB Timer with custom info is deserialized

by Sipatha Shoko (JIRA)

ClassNotFoundException when a EJB Timer with custom info is deserialized ------------------------------------------------------------------------ Key: JBAS-8671 URL: https://jira.jboss.org/browse/JBAS-8671 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: WinXP 32 bit, Ubuntu 10.04 32 bit, SunOS 5.10 sparc Reporter: Sipatha Shoko Assignee: Carlo de Wolf When an EJB3 Timer is created, you can optionally specify information pertaining to the timer. The information object must be serializable. A TimerVo (packaged in the same jar as the EJB) object thats serializable is used as the information. The EJB is first deployed, the timer is correctly created. However if the server is restarted, a ClassNotFoundException for TimerVo is thrown when the previously saved timer is deserialised. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8814) Track EJB3 upgrades to AS trunk

by jaikiran pai (JIRA)

Track EJB3 upgrades to AS trunk ------------------------------- Key: JBAS-8814 URL: https://issues.jboss.org/browse/JBAS-8814 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 6.0.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8923) WAR with bundled Mojarra 2.1.0-b11

by Lukas Fryc (JIRA)

WAR with bundled Mojarra 2.1.0-b11 ---------------------------------- Key: JBAS-8923 URL: https://issues.jboss.org/browse/JBAS-8923 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: 6.0.0.Final Environment: RichFaces 4.0.0.20110227-CR1 r.21967 Mojarra 2.1.0-FCS JBoss AS 6.0.0.Final (default profile) OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux http://anonsvn.jboss.org/repos/richfaces/modules/tests/metamer/tags/metam... Reporter: Lukas Fryc Assignee: Stan Silvert When new profile Mojarra-2.1 (with 2.1.0-b11 libs) is created and WAR without jsf-libs is deployed, application works fine. But when JSF is bundled into WAR (and use WAR_BUNDLES_JSF_IMPL param) and deployed onto default Mojarra-2.0 profile, it doesn't work with exception bellow. Shortened stacktrace: 17:42:14,288 ERROR [[/metamer]] Error configuring application listener of class com.sun.faces.application.ServletContextSensitiveSingletonStore: java.lang.InstantiationException: com.sun.faces.application.ServletContextSensitiveSingletonStore at java.lang.Class.newInstance0(Class.java:357) [:1.6.0_20] at java.lang.Class.newInstance(Class.java:325) [:1.6.0_20] at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:280) [:6.0.0.Final] at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:264) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3319) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_20] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA] at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA] ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

5
9
0 / 0

[JBoss JIRA] Created: (JGRP-1309) Discovery: max_rank doesn't make any sense

by Bela Ban (JIRA)

Discovery: max_rank doesn't make any sense ------------------------------------------ Key: JGRP-1309 URL: https://issues.jboss.org/browse/JGRP-1309 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Discovery.max_rank was originally meant to reduce traffic in the discovery phase: rather than 100 members replying to a discovery request, only the coordinators (max_rank=1) would reply and this would be enough for a joiner to find the coordinator and send it a JOIN request. However, discovery responses also contain additional information, such as the logical name (if set) and the physical address of a member. This is needed by all members of a cluster, and so everyone should return this information to a new joiner. Seen under this aspect, max_rank is useless and even conter-productive ! If we have 100 members: - max_rank=0: we get 100 discovery responses - max_rank=1 (sets return_entire_cache to true): the coordinator return the entire cache to the joiner (1 unicast / cache entry: 100 unicasts) - max_rank=2: the coordinator plus the next in line return the entire cache: 200 unicasts - and so on The current problem is that ergonomics sets return_entire_cache which - in conjunction with max_rank > 0 - generates even more discovery responses than is max_rank is 0 ! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
7
0 / 0

[JBoss JIRA] Created: (JBAS-8551) tests.classpath length impacts running tests on Windows

by Shelly McGowan (JIRA)

tests.classpath length impacts running tests on Windows ------------------------------------------------------- Key: JBAS-8551 URL: https://jira.jboss.org/browse/JBAS-8551 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.0.CR1 http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-Wind... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011