November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1358) StrictMaxPool for SFSB does not decrease Pool-Usage on bean-removal

by Stephan Pelikan (JIRA)

StrictMaxPool for SFSB does not decrease Pool-Usage on bean-removal ------------------------------------------------------------------- Key: EJBTHREE-1358 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1358 Project: EJB 3.0 Issue Type: Bug Components: pool Affects Versions: AS 4.2.1.GA Environment: Java 1.5.0_11 @Stateful(name="Lektorat") @PoolClass(value=org.jboss.ejb3.StrictMaxPool.class, maxSize=1000, timeout=10000) @Cache(org.jboss.ejb3.cache.NoPassivationCache.class) public class LektoratImpl implements Lektorat { .... Reporter: Stephan Pelikan Priority: Minor When using SFSB in the old fasioned way for long life operations - not as substitution for SLSB for accessing an extended EntityManager within a short-life-period (http-request) - we mentioned several side-effects (not covered in this JIRA-entry) which we could be trace back to the default-poolclass "ThreadLocalPool". So we decided to use instead the "StrictMaxPool"-class. Now - and this is the bug we found - we could see that the StrictMaxPool's semaphore is not decreased on SFSB-removal which leads to errors upon 1000 (our limit) SFSB has been created. We have mentioned that SFSB's removal does not call the pool's method "release" (The bean should not be reused) but the method "remove" isn't overwritten by StrictMaxPool so the semaphore is never decreased. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1425) Ensure good test coverage

by Tim Fox (JIRA)

Ensure good test coverage ------------------------- Key: JBMESSAGING-1425 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1425 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta We must ensure all functionality is fully tested. Perhaps not so concentrating on unit tests but using functional tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-6142) Include a more user friendly management and monitoring tool.

by Francisco Jose Peredo Noguez (JIRA)

Include a more user friendly management and monitoring tool. ------------------------------------------------------------ Key: JBAS-6142 URL: https://jira.jboss.org/jira/browse/JBAS-6142 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX/Web Console Reporter: Francisco Jose Peredo Noguez Assignee: Darran Lofthouse Please include a more user friendly management and monitoring tool, like the one Glassfish or Geronimo provide or even consider helping create a tight integratoin between the Lambda Probe project and JBoss AS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1186) maxBatchTime stops working after the connection between source and target servers is lost

by Maurice Zeijen (JIRA)

maxBatchTime stops working after the connection between source and target servers is lost ----------------------------------------------------------------------------------------- Key: JBMESSAGING-1186 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1186 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP1 Environment: Windows XP 64 Java 6 JBoss 4.2.2 Reporter: Maurice Zeijen Assigned To: Tim Fox We have the following Situation: A bridge MBean is setup to bridge between a local source and a remote target. The MaxBatchSize attribute is set to 5 and the MaxBatchTime is set to 10000. So the configuration looks like this: <mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=wai_sync_customer_bridge" xmbean-dd="xmdesc/Bridge-xmbean.xml"> <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends> <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends> <attribute name="SourceDestinationLookup">/queue/local</attribute> <attribute name="TargetDestinationLookup">/queue/remote</attribute> <attribute name="QualityOfServiceMode">0</attribute> <attribute name="MaxBatchSize">5</attribute> <attribute name="MaxBatchTime">10000</attribute> <attribute name="FailureRetryInterval">5000</attribute> <attribute name="MaxRetries">-1</attribute> <attribute name="AddMessageIDInHeader">false</attribute> <depends>jboss.messaging.destination:name=local,service=Queue</depends> </mbean> If the connection between the two servers is available then the MaxBatchTime works fine. After 10 seconds all messages are moved from local queue to remote queue if there are less then 5 messages in the queue. But when for some reason the connection is lost and after a while restored again then the MaxBatchTime doesn't work any more. Luckily the MaxBatchSize still works. Also the MaxBatchSize doesn't work when the remote server isn't available when the bridge on the local server is started. Restarting the bridge makes the MaxBatchTime work 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1415) remoting-bisocket-service.xml refers to obsolete numberOfCallRetries jboss-remoting param

by Dimitris Andreadis (JIRA)

remoting-bisocket-service.xml refers to obsolete numberOfCallRetries jboss-remoting param ----------------------------------------------------------------------------------------- Key: JBMESSAGING-1415 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1415 Project: JBoss Messaging Issue Type: Task Components: AS Integration Affects Versions: 1.4.1.CR1 Reporter: Dimitris Andreadis Assignee: Tim Fox Fix For: 1.4.1.CR2 With the upgrade of jboss remoting to 2.4.0.SP1 we see a warning in the AS console: 21:13:15,625 WARN [MicroSocketClientInvoker] numberOfRetries is no longer used This is coming from setting numberOfRetries in remoting-bisocket-service.xml: ... <invoker transport="bisocket">  <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute> <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute> <attribute name="dataType" isParam="true">jms</attribute> <attribute name="socket.check_connection" isParam="true">false</attribute> <attribute name="serverBindAddress">${jboss.bind.address}</attribute> <attribute name="serverBindPort">4457</attribute> <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute> <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute> <attribute name="numberOfCallRetries" isParam="true">1</attribute> <attribute name="pingFrequency" isParam="true">214748364</attribute> <attribute name="pingWindowFactor" isParam="true">10</attribute> <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute> ... It should be removed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

6
17
0 / 0

[JBoss JIRA] Created: (JBAS-6027) Upgrade jboss-metadata to 1.0.0.GA

by Dimitris Andreadis (JIRA)

Upgrade jboss-metadata to 1.0.0.GA ---------------------------------- Key: JBAS-6027 URL: https://jira.jboss.org/jira/browse/JBAS-6027 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assignee: Alexey Loubyansky Priority: Critical Fix For: JBossAS-5.0.0.GA Upgrade to a final release for jboss-metatada. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
15
0 / 0

[JBoss JIRA] Created: (JBAS-5834) Make JBoss-AS-4.2.x-TestSuite-openjdk6 pass

by Dimitris Andreadis (JIRA)

Make JBoss-AS-4.2.x-TestSuite-openjdk6 pass ------------------------------------------- Key: JBAS-5834 URL: https://jira.jboss.org/jira/browse/JBAS-5834 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assignee: Shelly McGowan Fix For: JBossAS-4.2.4.GA Make sure JBoss-AS-4.2.x-TestSuite-openjdk6 passes as expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-6052) Upgrade jboss-profiler-jvmti to a final release

by Dimitris Andreadis (JIRA)

Upgrade jboss-profiler-jvmti to a final release ----------------------------------------------- Key: JBAS-6052 URL: https://jira.jboss.org/jira/browse/JBAS-6052 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assignee: Clebert Suconic Fix For: JBossAS-5.0.0.GA Clebert, the dependency on jboss-profiler has been on a CR release for some time now. jboss.profiler.jvmti:jboss-profiler-jvmti:jar:1.0.0.CR5:compile Are you planning to go GA on that so we can reference it in the AS build? It needs to happens soon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1219) Using DSL and accumulate in Drools BRMS leads to unexpected results

by Cristiano Giuffrida (JIRA)

Using DSL and accumulate in Drools BRMS leads to unexpected results ------------------------------------------------------------------- Key: JBRULES-1219 URL: http://jira.jboss.com/jira/browse/JBRULES-1219 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Environment: HP-UX java version "1.5.0.05" Reporter: Cristiano Giuffrida Assigned To: Mark Proctor Details of this problem are described in the following thread: http://www.nabble.com/Using-DSL-and-accumulate-in-Drools-BRMS-leads-to-un... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-5992) Add a ManagedDeployment/ManagedComponent status servlet

by Scott M Stark (JIRA)

Add a ManagedDeployment/ManagedComponent status servlet -------------------------------------------------------- Key: JBAS-5992 URL: https://jira.jboss.org/jira/browse/JBAS-5992 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA We need a simple status servlet tha developers can use to view what their deployment ManagedDeployment/ManagedComponent object graphs look like to help validate development of their management interfaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008