[JBoss Seam] - EL enhancements and EntityQuery
by hispeedsurfer
Hi,
I use a rich:datatabel component to display data from an class extending the EntityQuery class
| @Name("recipientsList")
| public class RecipientsList extends EntityQuery {
|
from datatable i use method expression
| <h:form>
| <rich:dataTable id="searchresults"
| onRowMouseOver="this.style.backgroundColor='#F1F1F1'"
| onRowMouseOut="this.style.backgroundColor='#{a4jSkin.tableBackgroundColor}'"
| var="addrlist"
| value="#{addresslist}">
| <f:facet name="header">
| <rich:columnGroup>
| <rich:column>
| <h:outputText value="Surname"></h:outputText>
| </rich:column>
| </rich:columnGroup>
| </f:facet>
| <rich:column>
| <h:outputText value="#{addrlist.surname}"></h:outputText>
| </rich:column>
| <a:support id="support1" event="onRowClick" action="#{recipientsList.selectedRecipient(addrlist)}"/>
| </rich:dataTable>
| </h:form>
|
to call selectedRecipient on above class and set the selected recipient from table in the class.
In firebug I can see that the ajax-request works, but the method in class is never called (debug). There is nothing to see, no error or whatever.
I also have used <a:support> and <richt:dataTable> in the same way with an other app and there the correspondending method is called.
Is there a limitation using EL enhancement or why method is not called in this case?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081665#4081665
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081665
18 years, 7 months
[JBoss Messaging] - Bridge under load throws IllegalStateException
by mclu
Hi again!
I have my bridge up and running.
2 servers (A and B) and a middleware server (M).
on both servers there are 3 queues. The middlewareserver bridges them to its local queues. I am using QOS 2 (Transacted)
Messageflow is like
-A send to lokal.
-Bridged from A to M
-M processing and send processed to lokalQueue(M)
-Message bridged from M to B
-B processing message and send result to localQueue(B)
-Bridged to M
-result stored.
When I send a lot of messages I receive a stack traces is like:
| 14:41:44,250 ERROR [ClientConsumer] Failed to deliver message
| java.lang.IllegalStateException: There is already a delivery set for auto ack
| at org.jboss.jms.client.state.SessionState.setAutoAckInfo(SessionState.java:371)
| at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:258)
| at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect18.invoke(SessionAspect18.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java)
| at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:150)
| at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:941)
| at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
| at java.lang.Thread.run(Thread.java:619)
|
Its caused by the Bridge. My breakpoint stops on 3 threads related
my 3 queues. One example is listed below:
Variables of ClientConsumer.callOnMessage(SessionDelegate, MessageListener, String, String, boolean, MessageProxy, int, int, SessionDelegate, boolean):
| sess ClientSessionDelegate (id=315)
| listener Bridge$SourceListener (id=508)
| consumerID "a1-tcoi696f-1-l3lf696f-nkdb51-q4z24a"
| queueName "local_incomingSyncRequests"
| isConnectionConsumer false
| m TextMessageProxy (id=507)
| ackMode 0
| maxDeliveries 10
| connectionConsumerSession null
| shouldAck true
| deliveryInfo DeliveryInfo (id=367)
|
And SessionState Vars:
| this SessionState (id=310)
| acknowledgeMode 0
| asfMessages LinkedList<E> (id=395)
| autoAckInfo DeliveryInfo (id=399)
| callbackHandlers HashMap<K,V> (id=403)
| children HashSet<E> (id=408)
| clientAckList ArrayList<E> (id=396)
| currentTxId MessagingXid (id=419)
| delegate ClientSessionDelegate (id=315)
| dupsOKBatchSize 1000
| executor ClearableQueuedExecutor (id=423)
| parent ConnectionState (id=425)
| recoverCalled false
| sessionID "91-3hmi696f-1-l3lf696f-nkdb51-q4z24a"
| sessionListener null
| transacted true
| xa true
| xaResource MessagingXAResource (id=445)
| info DeliveryInfo (id=367)
| connectionConsumerSession null
| consumerId "a1-tcoi696f-1-l3lf696f-nkdb51-q4z24a"
| msg TextMessageProxy (id=507)
| queueName "local_incomingSyncRequests"
| shouldAck true
|
I have seen some references in the Design forum and version 1.2.
Do you have an Idea?
Oh forgot: I am using 1.4 cr2 and jboss 4.2.1GA..
Greets
Markus Lutum
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081656#4081656
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081656
18 years, 7 months
[JBossCache] - Re: Write lock is not released
by vitamin-c
"manik.surtani(a)jboss.com" wrote :
| It looks like the current WL holder and the RL requestor are not the same:
|
| | ... could not be acquired by <zzz:4256>:162303 ...
| |
| and
|
| | ... Write lock owner: Thread[ReportDataTaskRunner-20521017-1,5,jboss] ...
| |
|
Is it OK that RL requestor thread uses a GlobalTransaction, whereas WL owner thread doesn't?
Here's the code, where a GlobalTransaction is assigned to a thread requesting a lock (either RL or WL):
| package org.jboss.cache.interceptors;
| ...
| public class LockInterceptor extends Interceptor {
| ...
| public Object invoke(MethodCall m) throws Throwable {
| ...
| GlobalTransaction gtx=null;
| ...
| if(tx_mgr != null && (tx=tx_mgr.getTransaction()) != null && isValid(tx)) { // ACTIVE or PREPARING
| if(!transactions.contains(tx)) {
| gtx=cache.getCurrentTransaction(tx);
| if(gtx == null)
| throw new Exception("failed to get global transaction");
| ...
| else {
| gtx=cache.getTransactionTable().get(tx);
| }
| ...
|
Assuming that transaction manager presents, it is still unclear will a thread receive a non-null gtx, since cache.getTransactionTable().get(tx) doesn't check for null return value. According to metastaz's observations a thread may or may not receive a gtx, which looks like a bug, doesn't it?
Thanks,
Alexey
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081653#4081653
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081653
18 years, 7 months