[JBoss Messaging] - Manchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier League
by KOll MICK
KOll MICK [https://community.jboss.org/people/hirstsauxq33] created the discussion
"Manchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier League"
To view the discussion, visit: https://community.jboss.org/message/773771#773771
--------------------------------------------------------------
Manchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier LeagueManchester United vs Arsenal Live S-t-r-e-a-m Barclays Premier League
LINK Here to live ((( copy & paste )) below link
bit.ly/VJsKYT
bit.ly/VJsKYT
bit.ly/VJsKYT
LINK Here to live ((( copy & paste )) below link
bit.ly/VJsKYT
bit.ly/VJsKYT
bit.ly/VJsKYT
LINK Here to live ((( copy & paste )) below link
bit.ly/VJsKYT
bit.ly/VJsKYT
bit.ly/VJsKYT
LINK Here to live ((( copy & paste )) below link
bit.ly/VJsKYT
bit.ly/VJsKYT
bit.ly/VJsKYT
LINK Here to live ((( copy & paste )) below link
bit.ly/VJsKYT
bit.ly/VJsKYT
bit.ly/VJsKYT
LINK Here to live ((( copy & paste )) below link
bit.ly/VJsKYT
bit.ly/VJsKYT
bit.ly/VJsKYT
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/773771#773771]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
[JBoss Remoting] - JBoss 4 to JBoss 6 - remoting client invocation - Exception due to not being connected to server
by Volker Biermann
Volker Biermann [https://community.jboss.org/people/katerchen0815] created the discussion
"JBoss 4 to JBoss 6 - remoting client invocation - Exception due to not being connected to server"
To view the discussion, visit: https://community.jboss.org/message/772371#772371
--------------------------------------------------------------
Hello,
we have an Web Start application using JBoss. The client application works fine with JBoss 4.2.3.GA but throws Exception using JBoss 6. We use a code sniplet to invoke a bean home interface:
try
{
writeLog("connectionStr:", connectionStr);
writeLog("jndiName:", jndiName);
EJBHome home = getHome(connectionStr, jndiName, homeClass);
writeLog("Home", "ok");
writeLog("Home", home.toString());
Method createMethod = homeClass.getMethod("create", (Class[])null);
writeLog("createMethod", "ok");
writeLog("createdMethod ", createMethod.toString());
Object bean = createMethod.invoke(home, (Object[])null);
writeLog("bean", "ok");
// sessionCache.put(jndiName, bean);
return bean;
// }
// return sessionCache.get(jndiName);
}
catch (ILServiceLocatorException e)
{
writeLog("bean", e.getMessage());
throw e;
}
catch (Exception ex)
{
writeLog("Exception type", ex.toString());
PrintWriter pw = null;
try
{
pw = new PrintWriter(new FileWriter("c:\\test\\properties.txt", true));
ex.printStackTrace(pw);
pw.flush();
pw.close();
}
catch (IOException e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
throw new ILServiceLocatorException(
getMessageString("ErrorCreateBusinessDelegate.001"), ex);
}
As a result we will get:
--- JBoss 4.2.3.GA ---
Okt 25,2012 15:26 - connectionStr:: jnp://192.168.16.220:10000
Okt 25,2012 15:26 - jndiName:: ILUserAuthentication
Okt 25,2012 15:26 - Home: ok
Okt 25,2012 15:26 - Home: ILUserAuthenticationHome
Okt 25,2012 15:26 - createMethod: ok
Okt 25,2012 15:26 - createdMethod : public abstract com.identalink.bpauth.ILUserAuthentication com.identalink.bpauth.ILUserAuthenticationHome.create() throws java.rmi.RemoteException,javax.ejb.CreateException
Okt 25,2012 15:26 - bean: ok
--- JBoss 6.1.Final ---
Okt 25,2012 15:50 - connectionStr:: jnp://192.168.16.220:10000
Okt 25,2012 15:50 - jndiName:: ILUserAuthentication
Okt 25,2012 15:51 - Home: ok
Okt 25,2012 15:51 - Home: ILUserAuthenticationHome
Okt 25,2012 15:51 - createMethod: ok
Okt 25,2012 15:51 - createdMethod : public abstract com.identalink.bpauth.ILUserAuthentication com.identalink.bpauth.ILUserAuthenticationHome.create() throws java.rmi.RemoteException,javax.ejb.CreateException
Okt 25,2012 15:51 - Exception type: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.identalink.utils.ILServiceLocator.getSessionBean(ILServiceLocator.java:283)
... 43 more
Caused by: java.lang.Exception: Can not make remoting client invocation due to not being connected to server.
at org.jboss.remoting.Client.invoke(Client.java:2075)
at org.jboss.remoting.Client.invoke(Client.java:879)
at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:184)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.proxy.ejb.SecurityContextInterceptor.invoke(SecurityContextInterceptor.java:64)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
... 44 more
We think it has something to do of changes on jboss-remoting.jar.
How can we solve the problem?
Thank you for your help
Volker
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/772371#772371]
Start a new discussion in JBoss Remoting at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
[JBoss Messaging] - Running inot a deadlock because of messageListener handling
by sameer saurabh
sameer saurabh [https://community.jboss.org/people/nomind] created the discussion
"Running inot a deadlock because of messageListener handling"
To view the discussion, visit: https://community.jboss.org/message/773764#773764
--------------------------------------------------------------
The scenario for deadlock in JMS MessageListener while closing resources in onException() method of ExceptionListener:
• When an exception occurs in a MessageListener thread, it calls the asynchFailure() method of Session class which in turns calls the asynchFailure() method of Connection class. In the Connection class, a lock is taken on ‘elLock’ object and if there is no ExceptionListenerRunnable thread running, a ExceptionListenerRunnable thread is created and started. In the run() method of ExceptionListenerRunnable, a lock is again taken on ‘elLock’ object and the onException() method of ExceptionListener class is invoked.
• In onException() method of ExceptionListener class we try to recreate the JMS Connection. Before reconnecting we close all existing resources (Consumer, Session and Connection). In the close() API of SpyMessageConsumer class, the Message Consumer checks for any MessageListener thread and if there is any listener thread it calls the join() API of Thread class and wait for the listener thread to die.
• In the meanwhile if one more exception occurs in MessageListener thread, it again invokes asynchFailure() method of Connection class. If the earlier ExceptionListenerRunnable thread has not released the lock on the ‘elLock’ object, the MessageListener thread waits outside the synchronized block in asynchFailure() method of Connection class.
This leads to a deadlock situation where ExceptionListener thread is waiting for the MessageListener thread to die and MessageListener thread is waiting for the ExceptionListener class to release lock on ‘elLock’ object.
Though in asynchFailure() method of Connection class, a check is there to verify and log a warning message (“Connection failure, already in the exception listener”) if the ExceptionListenerRunnable thread is already running but this check is also inside the synchronized block. So even if ExceptionListenerRunnable thread is already running, the other thread will not be able to take the lock on ‘elLock’ object and the warning message will never be displayed. This seems to be a bug in JMS code as the check to verify an already running ExceptionListenerRunnable thread should be outside the synchronized block and if the ExceptionListenerRunnable thread is already running, the method should return from there.
Following is my thread dump -
"ExceptionListener Connection@206865307[token=ConnectionToken:ID:44/ee177c7bd4386f174c32bc563cb9b67a rcvstate=STARTED]"Id=331 in WAITING on lock=java.lang.Thread@13f1442e
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1258)
at java.lang.Thread.join(Thread.java:1332)
at org.jboss.mq.SpyMessageConsumer.close(SpyMessageConsumer.java:554)
at com.tribalfusion.jms.JMSReceiver.closeResources(JMSReceiver.java:88)
at com.tribalfusion.jms.JMSTopicReceiver.setJMSConfig(JMSTopicReceiver.java:32)
- locked com.tribalfusion.jms.JMSTopicNonDurableSubscriber@600877d4
at com.tribalfusion.jms.JMSReceiver.reconfigureJMS(JMSReceiver.java:140)
at com.tribalfusion.jms.JMSReceiver.reconnect(JMSReceiver.java:128)
at com.tribalfusion.jms.JMSReceiver$2.onException(JMSReceiver.java:77)
at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1320)
- locked java.lang.Object@4bf3308d
at java.lang.Thread.run(Thread.java:722)
| MessageListenerThread - dbSaveAckTopic"Id=45 in BLOCKED on lock=java.lang.Object@4bf3308d | owned by ExceptionListener Connection@206865307[token=ConnectionToken:ID:44/ee177c7bd4386f174c32bc563cb9b67a rcvstate=STARTED] Id=331 |
| | at org.jboss.mq.Connection.asynchFailure(Connection.java:424) |
| | at org.jboss.mq.SpySession.asynchFailure(SpySession.java:1063) |
| | at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:731) |
| | at java.lang.Thread.run(Thread.java:722) |
Full thread dump is attached.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/773764#773764]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months
[jBPM] - XOR split error - sequenceFlow condition not evaluating
by Jason J
Jason J [https://community.jboss.org/people/jasonjho] created the discussion
"XOR split error - sequenceFlow condition not evaluating"
To view the discussion, visit: https://community.jboss.org/message/773762#773762
--------------------------------------------------------------
I just upgraded to Drools 5.5.0.CR1 and jBPM 5.4.0.CR1.
I have a workflow that has been working just fine on Drools 5.3.1.Final and jBPM 5.2.Final, but is breaking on the new version.
*Problem*
I have a diverging XOR gateway that is failing to evaluate on either branch.
<sequenceFlow id="_31-_43" sourceRef="_31" targetRef="_43" name="Saved" tns:priority="2" >
<conditionExpression xsi:type="tFormalExpression" language="http://www.java.com/java" >
QueryResults queryResults = kcontext.getKnowledgeRuntime().getQueryResults("Saved");
Iterator iter = queryResults.iterator();
if(!iter.hasNext()) {
return false;
}
QueryResultsRow qResult = (QueryResultsRow)iter.next();
SaveEvent se = (SaveEvent) qResult.get( "$saveEvent" );
return se != null;
</conditionExpression>
</sequenceFlow>
<sequenceFlow id="_31-_45" sourceRef="_31" targetRef="_45" name="Published" tns:priority="2" >
<conditionExpression xsi:type="tFormalExpression" language="http://www.java.com/java" >
QueryResults queryResults = kcontext.getKnowledgeRuntime().getQueryResults("Published");
Iterator iter = queryResults.iterator();
if(!iter.hasNext()) {
return false;
}
QueryResultsRow qResult = (QueryResultsRow)iter.next();
PublishEvent pe = (PublishEvent) qResult.get( "$publishEvent" );
return pe != null;
</conditionExpression>
</sequenceFlow>
Here's an example of one of the rule queries that is being invoked:
query "Save"
$processInstance : WorkflowProcessInstance()
$saveEvent : SaveEvent()
end
The condition for either branch is based on the existence of a Fact in the working memory (thus, the need to use a rule query), and not a process variable which most conditions seem to be based on.
Is this a known regression? I don't see why this would start failing on an upgraded deployment.
Thanks to anyone who can help.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/773762#773762]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 5 months