August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-496) The remoting snapshot breaks ConnectionFactoryTest.testAdministrativelyConfiguredConnectors() in-vm and remote

by Ovidiu Feodorov (JIRA)

The remoting snapshot breaks ConnectionFactoryTest.testAdministrativelyConfiguredConnectors() in-vm and remote --------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-496 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-496 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Tim Fox Priority: Blocker Fix For: 1.0.1.CR4 testAdministrativelyConfiguredConnectors Failure junit.framework.AssertionFailedError at org.jboss.test.messaging.jms.ConnectionFactoryTest.testAdministrativelyConfiguredConnectors(ConnectionFactoryTest.java:157) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-476) Reoccuring Consumer endpoint activation failed Error

by Joel Lindheimer (JIRA)

Reoccuring Consumer endpoint activation failed Error ---------------------------------------------------- Key: JBMESSAGING-476 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-476 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.0 Environment: Windows XP Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov Ovidiu, I left my server running for a while with the test consumer running. I noticed that it started printing the following ERROR every so often: "ERROR [MessageCallbackHandler] Consumer endpoint activation failed javax.jms.JMSSecurityException: User guest is NOT authenticated" I here is the bulk of what the test consumer does: public class TestConsumer implements Runnable { public void run() { (...) while (true) { log.warn("whileloop+"); ut = (UserTransaction) getInitialContext().lookup("UserTransaction"); ut.begin(); conn = (QueueConnection) this.getQueueFactory().createQueueConnection(); conn.start(); session = conn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); receiver = session.createReceiver(getQueue()); TextMessage msg = (TextMessage) receiver.receive(5000); receiver.close(); session.close(); conn.close(); log.warn("msg: " + msg); if(msg!=null) { log.warn("msg.text: " +msg.getText()); } if(ConfigHelper.getBoolean("test.jms.consumer.commit")) { ut.commit(); } else { ut.rollback(); } log.warn("whileloop-"); (...) } } You will need to add the following to your startup servlet init() method: TestConsumer tc = new TestConsumer(); Thread thread = new Thread(tc); thread.setDaemon(true); thread.start(); Here is the ERROR/stacktrace: 14:01:50,755 ERROR [MessageCallbackHandler] Consumer endpoint activation failed javax.jms.JMSSecurityException: User guest is NOT authenticated at org.jboss.jms.server.security.SecurityMetadataStore.authenticate(SecurityMetadataStore.java:181) at org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.java:252) at org.jboss.jms.server.container.SecurityAspect.checkConsumerAccess(SecurityAspect.java:174) at org.jboss.jms.server.container.SecurityAspect.handleGetMessageNow(SecurityAspect.java:155) at sun.reflect.GeneratedMethodAccessor212.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:130) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aop.Advisor.dynamicInvoke(Advisor.java:723) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:101) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:126) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:842) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:82) at org.jboss.remoting.Client.invoke(Client.java:610) at org.jboss.remoting.Client.invoke(Client.java:602) at org.jboss.jms.client.delegate.DelegateSupport.invoke(DelegateSupport.java:112) at org.jboss.jms.client.delegate.ClientConsumerDelegate$getMessageNow_5405025797982928611.invokeNext(C lientConsumerDelegate$getMessageNow_5405025797982928611.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:134) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117) at org.jboss.jms.client.delegate.ClientConsumerDelegate$getMessageNow_5405025797982928611.invokeNext(C lientConsumerDelegate$getMessageNow_5405025797982928611.java) at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69) at org.jboss.jms.client.delegate.ClientConsumerDelegate$getMessageNow_5405025797982928611.invokeNext(C lientConsumerDelegate$getMessageNow_5405025797982928611.java) at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) at org.jboss.jms.client.delegate.ClientConsumerDelegate$getMessageNow_5405025797982928611.invokeNext(C lientConsumerDelegate$getMessageNow_5405025797982928611.java) at org.jboss.jms.client.delegate.ClientConsumerDelegate.getMessageNow(ClientConsumerDelegate.java) at org.jboss.jms.client.remoting.MessageCallbackHandler$ConsumerActivationRunnable.run(MessageCallback Handler.java:781) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) at java.lang.Thread.run(Thread.java:595) (etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

4
9
0 / 0

[JBoss JIRA] Updated: (JGRP-193) RpcDispatcher.callRemoteMethod(s) should add "throws Exception" to signature

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-193?page=all ] Bela Ban updated JGRP-193: -------------------------- Fix Version/s: 3.0 (was: 2.4) Affects Version/s: 2.4 2.5 2.x Complexity: Low Need to move this to 3.0, as this will break API compatibility > RpcDispatcher.callRemoteMethod(s) should add "throws Exception" to signature > ---------------------------------------------------------------------------- > > Key: JGRP-193 > URL: http://jira.jboss.com/jira/browse/JGRP-193 > Project: JGroups > Issue Type: Task > Affects Versions: 2.4, 2.2.9.1, 2.2.9, 2.3, 2.2.8, 2.5, 2.x > Reporter: Bela Ban > Assigned To: Bela Ban > Priority: Minor > Fix For: 3.0 > > > This will requirec code changes to callers of these methods, so this will make it not API compatible with previous versions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JGRP-111) Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-111?page=all ] Bela Ban resolved JGRP-111. --------------------------- Resolution: Done Performance is fine (2400 methods/sec) > Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall > ----------------------------------------------------------------------------------- > > Key: JGRP-111 > URL: http://jira.jboss.com/jira/browse/JGRP-111 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9, 2.3, 2.4, 2.2.9.1, 2.2.9.2, 2.2.9 SP3 (2.2.9.3), 2.3 SP1 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JGRP-111) Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-111?page=comments#action_12340815 ] Bela Ban commented on JGRP-111: ------------------------------- $ jt RpcDispatcherSpeedTest -mode id -num 100000 -props ./fc-fast-minimalthreads.xml ------------------------------------------------------- GMS: address is 192.168.5.2:3529 ------------------------------------------------------- -- new view: [192.168.5.2:3524|1] [192.168.5.2:3524, 192.168.5.2:3529] -- invoking 100000 methods using mode=ID 10000 20000 30000 40000 50000 60000 70000 80000 90000 100000 time for 100000 remote calls was 40406, avg=0.40406ms/invocation, 2474 calls/sec > Improve performance of RpcDispatcher/MessageDispatcher/RequestCorrelator/MethodCall > ----------------------------------------------------------------------------------- > > Key: JGRP-111 > URL: http://jira.jboss.com/jira/browse/JGRP-111 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9, 2.3, 2.4, 2.2.9.1, 2.2.9.2, 2.2.9 SP3 (2.2.9.3), 2.3 SP1 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-268) Util.objectFromByteBuffer() is inefficient

by Bela Ban (JIRA)

Util.objectFromByteBuffer() is inefficient ------------------------------------------ Key: JGRP-268 URL: http://jira.jboss.com/jira/browse/JGRP-268 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1, 2.3, 2.2.9 SP3 (2.2.9.3), 2.2.9.2 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.4 The implementation tries to unmarshal as an Externalizable/Serializable, when an exception is thrown, we try for Streamable. This is inefficient when we send a lot of Streamable types, because we always run into the exception. Fix: add an additional byte in objectToByteBuffer() which marks the object as Streamable or Externalizable/Serializable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-709) Out of memory problem

by Sudhakar Pandey (JIRA)

Out of memory problem --------------------- Key: JBCACHE-709 URL: http://jira.jboss.com/jira/browse/JBCACHE-709 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.2.4SP2 Environment: Windows NT, Ecliplse IDE and Pentium 4 processor. Reporter: Sudhakar Pandey Assigned To: Manik Surtani Priority: Critical Problem: ~~~~~~~ While running the following testcase after entering 66666 records my system program is getting hang. Following is the description of program: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I am putting some String object in TreeCache, accessing it and then removing it from the cache. I am doing this in a infinite loop. Following is the eviction policy: ~~~~~~~~~~~~~~~~~~~~~~~ <attribute name="EvictionPolicyConfig"> <config> <attribute name="wakeUpIntervalSeconds">72000</attribute>  <region name="/_default_"> <attribute name="maxNodes">500</attribute> <attribute name="timeToLiveSeconds">180</attribute>  <attribute name="maxAgeSeconds">7200</attribute> </region>  <region name="/com/yodlee"> <attribute name="maxNodes">500</attribute> <attribute name="timeToLiveSeconds">180</attribute>  <attribute name="maxAgeSeconds">7200</attribute> </region> </config> </attribute> *IMPORTENT*: If I reduce the 'wakeUpIntervalSeconds' then there is no leak. However, I can reduce this time coz it eats up lots of CPU. I have attached the Tree Cache Configuration xml file also. Program: ~~~~~~~ public void testTreeCache(){ TreeCache treeCache; try { treeCache = new TreeCache(); treeCache.setCacheMode(TreeCache.LOCAL); // configure TreeCache PropertyConfigurator config = new PropertyConfigurator(); config.configure(treeCache, "com/yodlee/core/system/services/cacheservice/TreeCache.xml"); treeCache.startService(); String identifier = "Test/MemoryLeak/"; String key = "key"; String value = "JBoss Cache is a product designed to cache frequently accessed Java objects in order to dramatically improve the performance of e-business applications. By eliminating unnecessary database access, JBoss Cache decreases network traffic and increases the scalability of applications."; for(int i=0;;i++) { System.out.println("Putting key=" + (key +i)); treeCache.put(identifier, key +i, value); System.out.println(treeCache.get(identifier, key + i)); System.out.println("Removing key=" + (key+i)); treeCache.remove(identifier, key + i); } //treeCache.stopService(); } catch (Exception e) { MessageController.log(JBossCacheServiceImpl.class.getName(), 1, ExceptionHelper.getExceptionStackTrace(e), MessageController.FATAL); throw new CoreException(ExceptionHelper.getExceptionStackTrace(e)); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

3
14
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-487) ssh smoke test fails on 4.0.4.GA

by Ovidiu Feodorov (JIRA)

ssh smoke test fails on 4.0.4.GA -------------------------------- Key: JBMESSAGING-487 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-487 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.0.1.CR4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
4
0 / 0

[JBoss JIRA] Updated: (JBAS-3203) Delegate for Authorization Interceptor for RMIAdaptor should have roles configurable

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3203?page=all ] Anil Saldhana updated JBAS-3203: -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta Affects Version/s: JBossAS-4.0.3 SP1 > Delegate for Authorization Interceptor for RMIAdaptor should have roles configurable > ------------------------------------------------------------------------------------ > > Key: JBAS-3203 > URL: http://jira.jboss.com/jira/browse/JBAS-3203 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Anil Saldhana > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.4.GA > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureTheInvokers > The AuthorizationInterceptor can have an authorization delegate to perform the authorization. The current implementation of > RolesAuthorization (http://tinyurl.com/kglsl) cannot be configured for the roles. > We need an extension of RolesAuthorization delegate that can accept roles from a properties file. > Conveyed about this feature request to Dimitris. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBMESSAGING-495) Remoting 2.0.0.CR1 breaks existing org.jboss.remoting.security.SSLSocketBuilder deployments

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-495?page=all ] Ovidiu Feodorov deleted JBMESSAGING-495: ---------------------------------------- > Remoting 2.0.0.CR1 breaks existing org.jboss.remoting.security.SSLSocketBuilder deployments > ------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-495 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-495 > Project: JBoss Messaging > Issue Type: Sub-task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Blocker > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006