The DuplicateIDCache will not work:
- The MessageID lookup could fail in two circunstances:
I - on deliverReplicated, where we need to temporarily remove the messages from the Queue and place it on deliveringRefs.
II - On replicating acknoledgement... as I could fail
On I, we can't really add anything to duplicateIDCache, as the ID wasn't even delivered yet.
I have created a Branch with my current changes:
https://svn.jboss.org/repos/messaging/branches/Branch_Failover_Page
And PagingfailoverTest will pass with this Hack on QueueImpl:
// This is a temporary hack, for the temporary branch only
| for (int i = 0; i < 10; i++)
| {
| System.out.println("Retry " + i);
| Thread.sleep(100);
|
| ref = removeReferenceWithID(id, false);
|
| if (ref != null)
| {
| System.out.println("Finally found it:");
| break;
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200477#4200477
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200477
So far I've split the project as follows:
1) Transporters are in https://svn.jboss.org/repos/jbossremoting/remoting3-transporter/trunk. After the main GA release of Remoting, I'll release a Beta of transporters that can be used with it.
2) As per the standard for Microcontainer integration projects, the Remoting Microcontainer project (such as it is) has been moved to https://svn.jboss.org/repos/jbossremoting/remoting-mc-int/trunk.
I'm considering also moving the protocols each to their own projects. What do you guys think? This would probably mean that the R3 api & core would have a somewhat longer release cycle, just because new features probably won't be frequently added to the core. Instead, we'd see more frequent releases of the various supporting modules - transporters, protocols, and the supporting marshallers. This would also help prevent dead code from hanging around by hiding inside of another project - something I really hate.
On the other hand, it means a little more release work overall, which I don't mind but others might.
Opinions?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200475#4200475
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200475
I've run this unit test against both revisions of EJBContainer (using the latest ejb trunk and as Branch_5_0) and get the same results:
[junit] Running org.jboss.ejb3.test.service.unit.ServiceUnitTestCase
[junit] Tests run: 20, Failures: 0, Errors: 1, Time elapsed: 39.25 sec
[junit] Test org.jboss.ejb3.test.service.unit.ServiceUnitTestCase FAILED
Unless I'm missing something, from my perspective, it doesn't appear that the changes to EJBContainer for EJBTHREE-1653 caused any regressions. Can you email me that hudson link?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200449#4200449
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200449
I am on a government project. Our solution must deploy to a machine that has JBOSS AS on it. Anything "new" must go through a lengthy approval process, which is unfeasible to our deadline.
JBOSS ESB would be approved, as it can be deployed within JBOSS AS.
We need to write an application that functions as a multicast receiver... to a multicast group IP that is external. Does anyone know if JBOSS ESB could help us fulfill this functional goal?
Thanks in advance.
Jim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200435#4200435
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200435
"wolfc" wrote : All in all this thing should never communicate with SBM in the first place.
| It's not some network service which AS provides. It's a hack around a JVM limitation.
I'm not convinced. The argument you make that it's not a network service is true enough; using the SBM for this is conceptually a bit unclean.
But if I'm an admin who starts the AS and looks at what sockets it's opened and want to know where to configure the ports, I'd much prefer to be told to go to one location than be told to go to one place except for X which uses a dynamic port. I don't care that it's not a network service.
Generally dynamic ports are used for client sockets or short lived ones. This one is a "nothing socket" :) But the fact it lives as long as the server makes it IMHO a lot closer to a server socket than anything.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200432#4200432
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200432
just to clear it up. its weakclasscache that cache the ctclasses, the methodinfos are also cached if they have been fetched earlier from what i can tell.
one thing we could do is to add a compare(CtClass,CtClass) method and check if there has been any changes after we've fetched the ClassInfo from cache.
since we cant do any changes to JavassistTypeInfo, ill add a simple compare(JavassistTypeInfo,CtClass) in JavassistTypeInfoFactoryImpl when we fetch the object from cache and just compare number of methods/fields. - it should be more thorough, but this would do for now i think.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200422#4200422
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200422