[
https://jira.jboss.org/browse/JBRULES-2711?page=com.atlassian.jira.plugin...
]
Kris Verlaenen commented on JBRULES-2711:
-----------------------------------------
As the exception kinda describes, the console fails to load as it cannot access the human
task service. Part of the console is showing user tasks lists etc., and the console needs
to have access to the human task service to show that part. See
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/t...
how to start the task service. If you use the installer, you can use that to
automatically start a human task service for you as well.
I do agree that we should not show a large stack trace like that, a smaller, more elegant
error box with a good explanation should be sufficient., so I'll leave this JIRA to
address this issue.
Could not connect task client
-----------------------------
Key: JBRULES-2711
URL:
https://jira.jboss.org/browse/JBRULES-2711
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-process-task
Affects Versions: 5.1.1.FINAL
Environment: JBoss 4.2.3-GA
JDK 6u14
Windows XP SP3
Reporter: José Manuel García Rivas
Assignee: Mark Proctor
Fix For: 5.2.0.M1
Just after logging in the BPM console, it sends me to
http://localhost:8080/gwt-console/app.html#errai_ToolSet_Tasks;none and shows a
"Could not connect task client" error and a stacktrace.
* URL: 'http://localhost:8080/gwt-console-server/rs/tasks/admin'
* Action: 'org.jboss.bpm.console.client.task.LoadTasksAction'
* Exception: 'class com.google.gwt.http.client.RequestException'
HTTP 500:
Estado HTTP 500 -
type Informe de Excepción
mensaje
descripción El servidor encontró un error interno () que hizo que no pudiera rellenar
este requerimiento. (The server encountered an internal error that prevented it to
fulfiill this requirement)
excepción
org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalArgumentException: Could not
connect task client
org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319)
org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230)
org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
causa raíz
java.lang.IllegalArgumentException: Could not connect task client
org.drools.integration.console.DroolsFlowTaskManagement.connect(DroolsFlowTaskManagement.java:59)
org.drools.integration.console.DroolsFlowTaskManagement.getAssignedTasks(DroolsFlowTaskManagement.java:128)
org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskListFacade.java:99)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117)
org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira