[JBoss Messaging] - Re: Getting javax.jms.InvalidClientIDException when using 1.
by sathish_06
Hi Ovidiu,
After setting CLIENTID to null in JMS_USER table, now its giving error msg - "Cannot create durable subscriber without a valid client ID"
Here is the complete exception stack trace:-
23:50:38,276 INFO [EjbModule] Deploying MigrationManagerMDB
| 23:50:41,995 ERROR [ExceptionUtil] SessionEndpoint[-2147483630] createConsumerDelegate [5c4o5s4p-1pplvj-eyens72c-1-eyeny0zv-i]
|
| javax.jms.JMSException: Cannot create durable subscriber without a valid client ID
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:191)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createCon
| sumerDelegate$aop(SessionAdvised.java:90)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:118)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:130)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aop.Advisor.dynamicInvoke(Advisor.java:723)
| at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:101)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:127)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:715)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:552)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
| 23:50:41,995 ERROR [ServerThread] SocketServerInvoker[0.0.0.0:4457].invoke() call failed: Cannot create durable subscriber wit
| hout a valid client ID
| 23:50:42,042 WARN [JMSContainerInvoker] JMS provider failure detected for BankAccountHistoryMDB
| org.jboss.deployment.DeploymentException: Error during topic setup; - nested throwable: (javax.jms.JMSException: Cannot create
| durable subscriber without a valid client ID)
| at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:720)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:839)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
The SP4 release notes mentioned about following bug,
JBMESSAGING-791] - Duplicates clientIDs are not throwing InvalidClientIDException
Do we need to make anykind of configuration changes while using this SP4 ? Can you suggest us the ideal way of configuring clientids, roles in JMS_USER, JMS_ROLE and mapping them with desitnations(Topics) .
Thx, Sathish
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019491#4019491
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019491
19Â years, 2Â months
[JBoss jBPM] - Task timer and TaskInstance.dueDate field
by p4elka
Hello
JBPM allow to use timers with task instance, where timer has it's own due date not related to task due date. Timer's due date cannot be changed after timer is created (at least using API provided i.e SchedulerService or JobSession).
Sometimes it is required to change due date for timer associated with task instance after task instance is created, and I haven't found standard way of doing this in JBPM.
Here is how I think this could be implemented and I would be glad to get your opinion on this.
I believe that link between task instance due date and task timer due date is missing in current JBPM implementation.
Task due date should be ignored when timer is associated with task, and task instance should be initialized with timer due date.
Upon change of task due date, we should look whether task has timer associated and if yes, timer instance should be found and updated with new due date value.
Another approach could be not to change dates in existing timers but cancel timer and create new one using existing timer declaration.
What do you think ?
Thanks a lot !
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019486#4019486
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019486
19Â years, 2Â months