[Design of JBoss jBPM] - Re: build failing ?
by tom.baeyens@jboss.com
i got those process archive tests working now also on jdk 6.
the problem was that i checked if the ProcessClassLoader found a certain class by loading the class in a process archive, then removing the class from the file system (cause there it is in the test classpath) and then deploying the archive and then using the class.
the 2 tests were somehow interfering. i don't know the cause. but it turned out that the test classloader already loaded the action handler before the test began. so the even though the actionhandler was loaded with the process classloader, it was already found previously by the parent of the process classloader before.
ps. kukeltje, are you already back awake ? well... in case your were, i'm sure that after reading the previous explanation you have been put back to sleep for another couple of days :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185038#4185038
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185038
15 years, 11 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Status of LargeMessages work
by timfox
"clebert.suconic(a)jboss.com" wrote : This is the status of my current work on MessageChunk and LargeMessages.
|
| It is committed on https://svn.jboss.org/repos/messaging/branches/Branch_Chunk_CRS2/ waiting revision before we add it to trunk. Branch_Chunk_CRS2 was just created today (r5188)
|
|
| I - I have added a method getPacketSize on the Packet interface. The abstract class is still returning (at this point at least) the DefaultPacketSize, but MessageSend, Chunk and Receive are calculating the packetSize accordingly.
| With that the InVM transport will also work for big messages, and we can avoid extra unecessary buffer creations.
|
What does "packetSize" represent?
* As soon as we merge it on trunk, we could have all the packets implementing this. But this is not a really high priority.
anonymous wrote :
| II - I have added a new interface called ServerLargeMessage which will be implemented by each storage-manager we have. We have JournalServerLargeMessageImpl and NullStorageManager. The StorageManager will be responsible for the instantiation of this class.
|
Confusing name. The journal is a large message?
anonymous wrote :
| III - I have separated the reference counting of references and durable references on Messages (that fix on paging discussed on this thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=144128)
|
| As soon as we remove the reference from the queue (ACKs) I decrement the refCount. I use that ref to delete large messages stored on files.
|
How is this different to how it was before?
anonymous wrote :
| IV - Paging could page largeMessages also. (On that case I don't take the bodySize in consideration, as that will be stored outside of the memory).
|
| V - The ChunkSize is configured on the ConnectionFactory, and the default is 100k
|
For everyone's benefit could you explain what chunkSize represents, and how it differs (or not) from minLargeMessageSize?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185019#4185019
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185019
15 years, 11 months