[JBoss Web Services] New message: "Re: Endpoint not registering"
by Peter Johnson
User development,
A new message was posted in the thread "Endpoint not registering":
http://community.jboss.org/message/520142#520142
Author : Peter Johnson
Profile : http://community.jboss.org/people/peterj
Message:
--------------------------------------------------------------
Well, I am stumped. I used your code (with my suggested changes) and deployed it:
09:41:38,210 INFO [DefaultEndpointRegistry] register: jboss.ws:context=foo,endpoint=foobar
09:41:38,283 INFO [TomcatDeployment] deploy, ctxPath=/foo
09:41:39,458 INFO [WSDLFilePublisher] WSDL published to: file:/C:/opt/jboss/as/jboss-5.0.1.GA/serve
r/foo/data/wsdl/foo.war/TestServiceService504811253484387295.wsdl
Which version of the JDK are you using? Did you download the version of JBoss AS that matches the JDK version (the one with -jdk6- in it is for JDK 6, the other is for JDK 5)?
Did you try going to http://localhost:8080/jbossws/services to see if the web service was really registered?
Here's the web.xml (the source file matches yours exactly, with the addition of the "package com.foo.services;" line which you did not post):
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/520142#520142
16 years, 3 months
[jBPM] New message: "jbpm 4 task problem"
by m p
User development,
A new message was posted in the thread "jbpm 4 task problem":
http://community.jboss.org/message/520140#520140
Author : m p
Profile : http://community.jboss.org/people/supermp
Message:
--------------------------------------------------------------
Hi everybody,
i'm trying to migrate my process from 3.2.1 to 4.3;
In jbpm 3.1.2 i had an action on a transition that send an email with the current task ID in its body;
now in jbpm 4.3 i have this task:
<task assignee="peter" form="review.ftl" g="241,85,80,40" name="readyToStart">
<on event="start">
<event-listener class="com.jbpm.utils.test">
</event-listener>
</on>
<transition g="-43,-18" name="to fork1" to="task1"/>
</task>
and in the class test:
public class test implements EventListener{
public void notify(EventListenerExecution execution) throws Exception {
ProcessEngine eng= Configuration.getProcessEngine();
String process=execution.getProcessInstance().getId();
Task t=eng.getTaskService().createTaskQuery().processInstanceId(process).uniqueResult();
t.getId();
System.err.println(t.getAssignee());
System.err.println(t.getId());
System.err.println(t.getExecutionId());
}
}
but the task-id is not the "current task"-id but the previous task-id.
It seems that the eventlistener is fired before that in the database the current Task is updated ,
so i get the previous task-id.
There is a way to get the task-id of the current task?
Massimo
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/520140#520140
16 years, 3 months
[JBoss Messaging] New message: "Slow dequeue for singleton MDB"
by Mohit Anchlia
User development,
A new message was posted in the thread "Slow dequeue for singleton MDB":
http://community.jboss.org/message/520126#520126
Author : Mohit Anchlia
Profile : http://community.jboss.org/people/mohitanchlia
Message:
--------------------------------------------------------------
We use tibco ems and Jboss 4.2 CP 6. For the queues in question:
1. Every onMessage calls take around 10-20ms.
2. According to the stats we should be able to process around 50 messages per sec. worst case.
3. But we are only able to do 15 messages per sec.
So there is a delay and messages are not being sent. It gets worse as load increases. CPU on tibco ems server is only 96% idle and no iowaits. CPU on Jboss server is around 90% idle. It looks like a performance issue with Jboss fetching the messages. I have also tried setting "prefetch" in tibco ems. It looks like Jboss is slow when dequeing messages for singletons. Even though MDB is available it doesn't get message fast enough.
Could someone please help me performance tuning or where the issue might be.
We tried using JBossJMSMessageEndpointFactory and have followed what's in http://community.jboss.org/docs/DOC-10104 with no success.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/520126#520126
16 years, 3 months