[jBPM] - Human Task View and "Could not connect to task server, refresh first" problem.
by Francisco Barros
Francisco Barros [http://community.jboss.org/people/francisco_barros] created the discussion
"Human Task View and "Could not connect to task server, refresh first" problem."
To view the discussion, visit: http://community.jboss.org/message/590059#590059
--------------------------------------------------------------
Hi all!
I've been trying to reproduce the screencast ( http://people.redhat.com/kverlaen/install-eclipse-jbpm.swf http://people.redhat.com/kverlaen/install-eclipse-jbpm.swf) linked at section "2.4. Using Eclipse Tooling" of "jBPM User Guide". I was stuck at 1:05, when, at the Human Task View, krisv name is entered at UserId and the button Refresh is clicked. I was getting "Could not connect to task server, refresh first" message. I've discovered that what was causing the problem was the installation of JBoss Tools 3.2 (before the installation I was able to reproduce the screencast *). To confirm, I uninstalled just Drools related plugins of JBoss Tools and could, then, reproduce the screencast without errors *.
My environment:
Eclipse Java EE Helios SR1 Win32 (not the default eclipse Java Helios that is configured to be retrieved at build.xml)
jbpm-5.1-SNAPSHOT
JBoss Tools 3.2 (Helios) Final.
* After uninstalling Drools related plugins from JBoss Tools I was *almost* able to identically reproduce the screencast. The only diference is that I can't see the image that represents process ongoing at Process Instance view (1:18).
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/590059#590059]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[Beginner's Corner] - Struggling with injecting singleton in 6.0
by Robin Hughes
Robin Hughes [http://community.jboss.org/people/rhinmass] created the discussion
"Struggling with injecting singleton in 6.0"
To view the discussion, visit: http://community.jboss.org/message/597183#597183
--------------------------------------------------------------
Hello,
I am having trouble figuring out how to inject a singleton into another class - in this case a servlet.
My singleton looks like this:
package com.robin.ejb
import javax.ejb.Singleton;
import javax.ejb.Startup;
@Singleton
@Startup
public class HelloWorld
{
public HelloWorld()
{
System.out.println("constructing HelloWorld");
}
public String sayHello() {
return "Hello World !!!";
}
}
My servlet looks like this:
import ...
import com.robin.ejb.HelloWorld;
@WebServlet(name="helloServlet", urlPatterns={"/hello"},
initParams={ @WebInitParam(name="nameParam", value="world")})
public class HelloServlet extends HttpServlet {
private static final long serialVersionUID = 1L;
@Inject
private HelloWorld hw;
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
PrintWriter out = response.getWriter();
String nameParam = request.getParameter("nameParam");
if (nameParam == null)
nameParam = getServletConfig().getInitParameter("nameParam");
out.println("hello " + nameParam + " " + hw.sayHello());
out.flush();
out.close();
}
}
When I run this in JBoss AS 6.0.0.Final I get the following errors:
2011-04-01 10:23:43,299 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (Thread-2) Error installing to Start: name=vfs:///C:/jboss/jboss-6.0.0.Final/server/rbh/deploy/myapp-0.0.1.ear_WeldBootstrapBean state=Create: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [HelloWorld] with qualifiers [@Default] at injection point [[field] @Inject private com.robin.webapp.HelloServlet.hw]. Possible dependencies [[Session bean [class com.robin.ejb.HelloWorld with qualifiers [@Any @Default]; local interfaces are [HelloWorld], Session bean [class com.robin.ejb.HelloWorld with qualifiers [@Any @Default]; local interfaces are [HelloWorld]]]
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:309) [:6.0.0.Final]
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139) [:6.0.0.Final]
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162) [:6.0.0.Final]
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:377) [:6.0.0.Final]
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:363) [:6.0.0.Final]
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:388) [:6.0.0.Final]
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/597183#597183]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss Tools] - Re: Adding JBoss AS source to a project
by henk de boer
henk de boer [http://community.jboss.org/people/henk53] created the discussion
"Re: Adding JBoss AS source to a project"
To view the discussion, visit: http://community.jboss.org/message/569958#569958
--------------------------------------------------------------
Just wondering, have the runtime guys ever been convinced of this?
In other words, with JBoss AS 6 and JBoss Tools 3.2, can I attach all source with one click now?
I'm now moving to Eclipse 3.6, which is of course a brand new install and it's really painful to attach all the literally hundreds of jars again that I attached to my old setup over the last year. Since quite often I have to attach the same jar twice (both for the editor and for the debugger), this really adds up.
If I upgrade my installation at work I have to attach the same couple of hundred jars there as well. This is really painful. I'm not sure how others cope with this, or maybe I'm the only nut who wants to have every last bit of source there is available in Eclipse ;)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/569958#569958]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss Messaging] - Failed to replay transaction
by John Heijm
John Heijm [http://community.jboss.org/people/jheijm] created the discussion
"Failed to replay transaction"
To view the discussion, visit: http://community.jboss.org/message/594927#594927
--------------------------------------------------------------
JBoss is attempting to recover existing prepared transactions by redelivering unhandled messages and acknowledgements on the appropriate channels (from TransactionRepository#recoverPreparedTransactions javadocs). The queue that was bound to the channel id specified is no longer defined.
I have two questions:
1) How can this happen? There are three nodes in this cluster.
2) How can I remove these transactions or force them to recover? This same message keeps repeating for the same 3 ids over and over and over again).
Thanks a lot.
Here is my stack trace:
2011-03-21 11:23:47,285 WARN -> (Thread-6) [TransactionRepository] Failed to replay transaction (XID: MessagingXid (24348582 bq:45.55.52.99.102.55.49.52.57.58.99.52.53.51.58.52.100.55.54.56.55.52.98.58.51.51.48.101.57.49 fo
rmatID:131075 gtxid:49.45.45.55.52.99.102.55.49.52.57.58.99.52.53.51.58.52.100.55.54.56.55.52.98.58.51.51.48.101.57.48, LocalID: 21293346538722831) during recovery.
java.lang.IllegalStateException: Cannot find binding for channel id 751
at org.jboss.messaging.core.impl.tx.TransactionRepository.handleAcks(TransactionRepository.java:377)
at org.jboss.messaging.core.impl.tx.Transaction.loadState(Transaction.java:357)
at org.jboss.messaging.core.impl.tx.TransactionRepository.recoverPreparedTransactions(TransactionRepository.java:149)
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.getPreparedTransactions(ServerConnectionEndpoint.java:539)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$getPreparedTransactions$aop(ConnectionAdvised.java:106)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$getPreparedTransactions_8083036720366990761.invokeNext(ConnectionAdvised$getPreparedTransactions_8083036720366990761.java)
at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$getPreparedTransactions_8083036720366990761.invokeNext(ConnectionAdvised$getPreparedTransactions_8083036720366990761.java)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.getPreparedTransactions(ConnectionAdvised.java)
at org.jboss.jms.wireformat.ConnectionGetPreparedTransactionsRequest.serverInvoke(ConnectionGetPreparedTransactionsRequest.java:67)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
at org.jboss.remoting.Client.invoke(Client.java:1640)
at org.jboss.remoting.Client.invoke(Client.java:554)
at org.jboss.remoting.Client.invoke(Client.java:542)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$getPreparedTransactions$aop(ClientConnectionDelegate.java:265)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$getPreparedTransactions_8083036720366990761.invokeNext(ClientConnectionDelegate$getPreparedTransactions_8083036720366990761.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$getPreparedTransactions_8083036720366990761.invokeNext(ClientConnectionDelegate$getPreparedTransactions_8083036720366990761.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.ClientConnectionDelegate$getPreparedTransactions_8083036720366990761.invokeNext(ClientConnectionDelegate$getPreparedTransactions_8083036720366990761.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.getPreparedTransactions(ClientConnectionDelegate.java)
at org.jboss.jms.tx.ResourceManager.recover(ResourceManager.java:575)
at org.jboss.jms.tx.MessagingXAResource.recover(MessagingXAResource.java:281)
at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.recover(MessagingXAResourceWrapper.java:110)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecovery(XARecoveryModule.java:746)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecovery(XARecoveryModule.java:685)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:179)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWork(PeriodicRecovery.java:237)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:163)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/594927#594927]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months