January 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Non connected remoting clients throwing java.lang.Except

by clebert.suconic＠jboss.com

http://jira.jboss.org/jira/browse/JBMESSAGING-762 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003971#4003971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003971

19 years, 2 months

1
0
0 / 0

[Design of JBossCache] - JBCACHE-941 discussion

by genman

http://jira.jboss.com/jira/browse/JBCACHE-941 >From the issue: anonymous wrote : The java.util.Collections utility class supplies useful methods for dealing with legacy interfaces and wrapping collection classes for concurrency, type safety, read-only, etc. | | In a simiilar vein, I wrote a "Caches" class that returns java.util.Map instances for a Node, which allow data to be modified through the standard Map interface. | | This I expect to be extremely useful for allowing uses to integrate their existing application with JBoss Cache, and will eliminate some of the confusion of using a new API and they can use the API they know best. Users also often demand an API which is "generic" so that their code is not tied to a particular vendor. | | There are basically two methods in Caches, one looks like this: | | Cache cache = DefaultCacheFactory.getInstance().createCache(); | Map m = Caches.asMap(cache); | m.put("foo", "bar"); | | The API and examples explain themselves. | | "Caches" could also include other useful methods for printing or reporting. | | Note that this functionality could be considered duplicated from PojoCache... | Here is one method: /** | * Returns a {@link Map}, where map keys are named children of the given Node, | * and values are kept under a single key for this node. | * The map may be safely concurrently modified through this Map or externally, | * and its contents reflect the cache state and | * existing data of the Node. | * This means that {@link ConcurrentModificationException} is never thrown | * and all methods are thread safe. | * <p/> | * The map is not serializable. | * <p/> | * Usage note: As a single node is used for every key, it is most efficient to store | * data for a single entity (e.g. Person) in a single object. | * <p/> | * Also, when using a {@link CacheLoader} for storage, keys used must be valid as | * part of the {@link Fqn} used in calls. Generally speaking, simple string values are | * preferred. | */ Manik suggests also an adaptor for JCache (JSR-107). Actually, it might also be nifty if JBoss Cache could supply adaptors for competing Cache APIs. I'm not sure of the legality of this for commercially published interfaces. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003959#4003959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003959

19 years, 2 months

1
0
0 / 0

[Design of JBossCache] - Re: Last minute 2.0 API suggestions

by genman

1. It would be nice if it returned a boolean not a Node 2. Actually, I'm not sure "size" is a good idea. It still has to hit the interceptor chain to return the correct value, and for this I assume requires some non-trivial thought. I'm creating a thread for the Cache->Map thing View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003956#4003956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003956

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Non connected remoting clients throwing java.lang.Except

by ovidiu.feodorov＠jboss.com

Clebert: Please create a JIRA issue about this, schedule it with Beta2 and assign it to me, as I want to clear all Remoting issues by the end of this week. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003947#4003947 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003947

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Non connected remoting clients throwing java.lang.Except

by clebert.suconic＠jboss.com

"clebert.suconic(a)jboss.com" wrote : Ron... this is just personal preference... | | but do you have a better name than quickRemove... quickWhatever? What about cancelConnection, cancelLease..... ??? Or... clearConnection... clearLease... The idea would be to disable the socket (or clearing it... cancelling it) without performing a server communication. And... just to reinforce... can you guys remove those throw java.lang.Exception from the code? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003946#4003946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003946

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Non connected remoting clients throwing java.lang.Except

by clebert.suconic＠jboss.com

Another place where remoting is throwing java.lang.Exception: java.lang.Exception: Error setting up client lease. | at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:388) | at org.jboss.remoting.Client.setupClientLease(Client.java:521) | at org.jboss.remoting.Client.connect(Client.java:430) | at org.jboss.remoting.Client.connect(Client.java:420) | at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:99) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.invoke(ClientConnectionFactoryDelegate.java:200) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) | at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:86) | at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) | at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003941#4003941 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003941

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: serializable KernelDeployment

by bill.burke＠jboss.com

Well, I found one problem. org.jboss.dependency.spi.ControllerState is being compared with identity ==. When it is deserialized, you a readResolve isn't done. Lets see if this fixes the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003928#4003928 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003928

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: New Rule: each thirdparty dependency bug should have a t

by ovidiu.feodorov＠jboss.com

Yes. All I want to make sure is that after they fix a bug that affects Messaging, they don't break that code again. Normally, it is the thirdparty module's responsibility to add functional tests after a bug is identified and fixed, but recent events taught us that this is something cannot be relied upon. I am not happy about it, I know it's a pain in the rear end. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003925#4003925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003925

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: serializable KernelDeployment

by bill.burke＠jboss.com

Very simple testcase to reproduce: | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <bean name="Two" class="org.jboss.embedded.test.SimpleBean"> | <property name="kernel"> | <inject bean="jboss.kernel:service=Kernel"/> | </property> | </bean> | </deployment> | | Upon validation I get: | Exception in thread "main" java.lang.IllegalStateException: Incompletely deployed: | | *** DEPLOYMENTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} | Two -> jboss.kernel:service=Kernel{Configured:**ERROR**} | | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:252) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:163) | at org.jboss.embedded.test.BeanCompilerTester.deploy(BeanCompilerTester.java:65) | at org.jboss.embedded.test.BeanCompilerTester.main(BeanCompilerTester.java:101) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003915#4003915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003915

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by clebert.suconic＠jboss.com

anonymous wrote : | 6. ClusterViewUpdateTest.testUpdateConnectionFactory() fails. | | | I executed the whole testsuite about two times between yesterday and today.. and didn't get any failures. Maybe you have a local problem? I thought you meant the testupdate I wrote... I will take a look View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003912#4003912 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003912

19 years, 2 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-dev-forums January 2007