[JBoss Messaging] - Re: Message priority does not seem to work
by ydzsidemiik
I have succeeded in creating a stand-alone example of the behavior in my original post. This download is a ready to go EAR with source included. Simply drop it in the deploy directory of a JBM configuration (mine was built from `all`) to run.
http://www.mediafire.com/?2y3w3gy2xic
This example has two producers, one sending priority 4s into a queue at a rate of 50 messages per second and the other priority 9s at a rate of one every five seconds. An MDB consumes from the queue at a rate of 15 messages per second. Watch (you may have to look at the logs afterwards) how the high priority messages, represented by the letter 'H', are sent into the queue but not processed in a timely manner. Use jboss.j2ee:ear=test-prio.ear,jar=test-prio-mdb.jar,name=BootstrapImpl,service=EJB3,type=ManagementInterface in your JMX console to start and stop the senders. You can let them run for a minute or so and then stop them to watch the MDB clear the queue; the 'H' messages appear only intermittently in between large numbers of 'L' messages, even after the producers are stopped.
I will investigate the pure JMS solution as per your suggestion, but my application was planned, designed, implemented, tested, and placed into production using MDBs -- whatever the outcome, it is the MDB stuff I ultimately have to get working.
I would be enormously appreciative of any further insight you may have.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126265#4126265
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126265
18 years, 2 months
[JBoss Seam] - Re: Trinidad SelectManyShuttle with seam ?
by gjeudy
I tought trinidad SelectManyShuttle was working. Actually I always get the same value in my selected list which is always the first value of the available list no matter what I put in my selected list(on the client side). This happens when executing the action on the command button on the server side.
In the code example below, it's the first value in
#{refDomainSearch.refDomains}, how come #{refDomainSearch.selectedRefDomains} always contain this first value ?
Could this be a bug in trinidad component library or a problem with trinidad/seam integration ?
refDomainSearch is a stateful bean/seam managed component with session scope and getters/setters for refDomains & selectedRefDomains. I don't use @In/@Out annotation in my example.
<tr:selectManyShuttle id="existitemshuttle2"
| leadingHeader="Domain Objects Found" trailingHeader="Domain Objects Selected"
| value="#{refDomainSearch.selectedRefDomains}" size="#{refDomainSearch.pageSize}" rendered="#{not empty refDomainSearch.refDomains}">
| <s:selectItems var="refDomain" label="#{refDomain.domainName}" value="#{refDomainSearch.refDomains}">
| </s:selectItems>
| <s:convertEntity />
| </tr:selectManyShuttle>
The commandButton triggering the action is part of the same form.
<h:commandButton type="submit" value="Add selection to package"
| action="#{refDomainSearch.updatePackageItems}" />
Thanks,
-Guillaume
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126264#4126264
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126264
18 years, 2 months
[Microcontainer] - Deployer sequencing
by gcompienne
Hello, I am trying to understand JBoss MC and there is a thing on deployer sequencing that I don't understand:
When JBoss MC is used in the context of JBoss AS I can see that the HackClassloaderMetaDataDeployer class is only being triggered by the deployment of "console-mgr.sar". Now I must admit I don't understand why is that happening as the HackClassloaderMetaDataDeployer does not seem to be setting any input ("setInputs") or output ("setOutput").
When I tried to write my own deployer I was able to ensure that it was always called ("setAllInputs(true); ") but I really don't understand why HackClassloaderMetaDataDeployer behaves as it currently do...
Thanks for your help.
Gilles.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126262#4126262
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126262
18 years, 2 months
[JBoss Seam] - Re: Problem with: seam-gen deploy
by pete007
"pete.muir(a)jboss.org" wrote : Just correct the generated code.
Okay, thank you for the hint. I already tried to correct it with several approaches, but didn't find the correct.
The first one, just to delete the two extra references, which is obviously false, leads to Routings which always have 3 pointers to the same Node.
Second one was to rename the references to nodeHome1, nodeHome2, nodeHome3, change the names in the wire()-method.
Compilation worked, deployment also, but when selecting a routing or creating a new one, I always get an exception saying:
"@In attribute requires non-null value: routingHome.nodeHome1"
Changing the names in the view components also didn't help.
Can you or someone else please tell me, which files I have to edit or where I can get an explanation, what is going wrong?
Thank you so far, Peter
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126250#4126250
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126250
18 years, 2 months