Re: [jboss-user] [JBoss Remoting] - Unable to find Remoting services in Jboss 5.1.0
by dhaval joshi
dhaval joshi [http://community.jboss.org/people/dhaval0129] replied to the discussion
"Unable to find Remoting services in Jboss 5.1.0"
To view the discussion, visit: http://community.jboss.org/message/559906#559906
--------------------------------------------------------------
Hi,
I still do not understand how can make this work, In previous Jboss 4.2.2 I added code below to Jboss-service.xml to remoting section and everything worked for me. I really do not know how should I get it working on Jboss 5.1.0. This what i added to jboss-service.xml as below:
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:service=Connector,transport=SSLServlet"
display-name="SSL Servlet transport Connector">
<attribute name="InvokerLocator">
sslservlet://localhost:8443/servlet-invoker/ServerInvokerServlet
</attribute>
<attribute name="Configuration">
<config>
<handlers>
<handler subsystem="server-log-monitor">com.icrco.remoting.CallbackInvocationHandler</handler>
<handler subsystem="server-log-sender">com.icrco.remoting.CallbackInvocationHandler</handler>
</handlers>
</config>
</attribute>
</mbean>
Can any one tell me where do i need to add this in Jboss 5.1.0 and also to let you know this How my Web.xml looks like in servlet-invoker.war
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
" http://java.sun.com/dtd/web-app_2_3.dtd http://java.sun.com/dtd/web-app_2_3.dtd">
<!-- The the JBossRemoting server invoker servlet web.xml descriptor
$Id: web.xml,v 1.2 2009/06/03 17:42:47 jon Exp $
-->
<web-app>
<servlet>
<servlet-name>ServerInvokerServlet</servlet-name>
<description>The ServerInvokerServlet receives requests via HTTP
protocol from within a web container and passes it onto the
ServletServerInvoker for processing.
</description>
<servlet-class>org.jboss.remoting.transport.servlet.web.ServerInvokerServlet</servlet-class>
<init-param>
<!--
<param-name>invokerName</param-name>
<param-value>jboss.remoting:service=Connector,transport=SSLServlet</param-value>
<description>The servlet server invoker</description>
-->
<param-name>locatorUrl</param-name>
<param-value>sslservlet://localhost:8443/servlet-invoker/ServerInvokerServlet</param-value>
<description>The servlet server invoker locator url</description>
</init-param>
<load-on-startup>1</load-on-startup>
<depends>jboss.remoting:service=TransactionManager</depends>
</servlet>
<servlet-mapping>
<servlet-name>ServerInvokerServlet</servlet-name>
<url-pattern>/ServerInvokerServlet/*</url-pattern>
</servlet-mapping>
</web-app>
JBoss 5.1.0 also throws exception on depends tag can you please give me tips how to resolve this Jboss Remoting issues on 5.1.0
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559906#559906]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[Beginner's Corner] - Problem with Jax-WS Web service, Java 6 and JBoss 4.3
by Glauber Ribeiro
Glauber Ribeiro [http://community.jboss.org/people/theglauber] created the discussion
"Problem with Jax-WS Web service, Java 6 and JBoss 4.3"
To view the discussion, visit: http://community.jboss.org/message/559903#559903
--------------------------------------------------------------
I'm sorry if this has been discussed before. I googled for it and found a few references, but they're old.
I'm fairly new to JBoss. Trying to set up a simple Jax-ws web service undre JBoss AS 4.3 and Java 6. The choice of JBoss and Java version is because i want to match what we have in our production environment, so i'm limited to those versions.
I got it to work first with very basic code, but once i added more meat to the service, including a couple of exceptions, i can't get it to work anymore. When i try to access the service or the WSDL, i get nothing back. server.log contains the following exception:
2010-08-31 17:10:14,507 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] handleWSDLRequest: jboss.ws:context=CacheTest,endpoint=GetVehicleInfo
2010-08-31 17:10:14,507 ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] *Error processing web service request*
*java.lang.IllegalStateException: Cannot obtain endpoint meta data*
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:520)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:144)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:126)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
2010-08-31 17:10:14,507 ERROR [org.apache.catalina.core.ContainerBase] Servlet.service() for servlet GetVehicleInfo threw exception
java.lang.IllegalStateException: Cannot obtain endpoint meta data
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:520)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:144)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:126)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Here's the definition for the Web Service call:
@WebMethod(operationName = "getInfoFromVin")
public pojo.Vehicle getInfoFromVin(@WebParam(name = "vin")
final String vin) throws SQLException, NamingException {
pojo.Vehicle veh = db.Vehicle.fromVin(vin);
System.out.println(veh);
return veh;
}
I'm trying to keep this very simple... it's not production quality code, but a proof-of-concept app for caching data. At this point it's not caching anything yet, only doing database lookups. Once i get this to work, i'll add caching.
Should i catch those exceptions and throw some other kind, maybe?
The workarounds i was able to find in the Web had to do with copying jar files from the Metro distribution or from other places into lib/endorsed, but they didn't work for me.
I'm suspecting that my problem is coming from using Java 6.
If anyone can help me, i would be very grateful. Please let me know if you need more information.
Any ideas?
thank you.
glauber
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559903#559903]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[JNDI and Naming] - Session Bean not in JNDI
by Frank Langelage
Frank Langelage [http://community.jboss.org/people/lafr] created the discussion
"Session Bean not in JNDI"
To view the discussion, visit: http://community.jboss.org/message/559900#559900
--------------------------------------------------------------
I'm trying an upgrade from 4.24 to 6.00.M4.
I have a problem with class MessageEraser.
@Stateless
public class MessageEraser extends EraserBase implements TimedObject, MessageEraserLocal
{
...
}
MessageEraserLocal is:
@Local
public interface MessageEraserLocal extends EraserBaseLocal
{
...
}
Base class EraserBase implements some common methods:
public abstract class EraserBase implements EraserBaseLocal
{
...
}
MessageEraser is deployed:
22:15:16,300 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=fey2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MessageEraser,service=EJB3
22:15:16,300 INFO [JBossASKernel] with dependencies:
22:15:16,301 INFO [JBossASKernel] and demands:
22:15:16,301 INFO [JBossASKernel] jndi:fey2e-lafr-sb2000-ipc/ejb-session-core.jar/MessageEraser!biz.mbisoftware.fn.ejb.session.core.MessageEraserLocal; Required: Described
22:15:16,302 INFO [JBossASKernel] jndi:fey2e-lafr-sb2000-ipc/ejb-session-common.jar/Version!biz.mbisoftware.fn.ejb.session.common.VersionLocal; Required: Described
22:15:16,302 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService; Required: Described
22:15:16,302 INFO [JBossASKernel] jndi:fey2e-lafr-sb2000-ipc/ejb-session-core.jar/MessageSink!biz.mbisoftware.fn.ejb.session.core.MessageSinkLocal; Required: Described
22:15:16,303 INFO [JBossASKernel] jndi:fey2e-lafr-sb2000-ipc/ejb-session-core.jar/TaskHandler!biz.mbisoftware.fn.ejb.session.core.TaskHandlerLocal; Required: Described
22:15:16,303 INFO [JBossASKernel] jndi:fey2e-lafr-sb2000-ipc/ejb-session-common.jar/MbiFxtxtFacade!biz.mbisoftware.fn.ejb.session.common.MbiFxtxtFacadeLocal; Required: Described
22:15:16,303 INFO [JBossASKernel] persistence.unit:unitName=fey2e-lafr-sb2000-ipc.ear/ejb-entity.jar#fey2e-lafr-sb2000-ipc; Required: Described
22:15:16,304 INFO [JBossASKernel] and supplies:
22:15:16,304 INFO [JBossASKernel] jndi:fey2e-lafr-sb2000-ipc/ejb-session-core.jar/MessageEraser!biz.mbisoftware.fn.ejb.session.core.MessageEraserLocal
22:15:16,305 INFO [JBossASKernel] jndi:fey2e-lafr-sb2000-ipc/ejb-session-core.jar/MessageEraser!local
22:15:16,305 INFO [JBossASKernel] Class:biz.mbisoftware.fn.ejb.session.core.MessageEraserLocal
22:15:16,305 INFO [JBossASKernel] jndi:MessageEraser
22:15:16,306 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=fey2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MessageEraser,service=EJB3) to KernelDeployment of: ejb-session-core.jar
But looking at the global JNDI view afterwards it's not there.
The class StartupTimers want's to use MessageEraser through injection:
public class StartupTimers implements ServletContextListener
{
@EJB
private MessageEraserLocal messageEraser;
....
}
But the injection fails:
22:16:16,867 ERROR [[/mbi/fey2e-lafr-sb2000-ipc/web]] Error configuring application listener of class biz.mbisoftware.fn.web.StartupTimers: java.lang.RuntimeException: Unable to inject jndi dependency: env/biz.mbisoftware.fn.web.StartupTimers/messageEraser into property biz.mbisoftware.fn.web.StartupTimers.messageEraser: MessageEraser!biz.mbisoftware.fn.ejb.session.core.MessageEraserLocal not bound
at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:82) [:1.5.0]
at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:99) [:1.5.0]
at org.jboss.web.tomcat.service.TomcatInjectionContainer.processInjectors(TomcatInjectionContainer.java:395) [:6.0.0-SNAPSHOT]
at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:291) [:6.0.0-SNAPSHOT]
at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:285) [:6.0.0-SNAPSHOT]
at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:268) [:6.0.0-SNAPSHOT]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3319) [:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:299) [:6.0.0-SNAPSHOT]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:138) [:6.0.0-SNAPSHOT]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) [:6.0.0-SNAPSHOT]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0-SNAPSHOT]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_21]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_21]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_21]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_21]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.Beta5]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.Beta5]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.Beta5]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.Beta5]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.Beta5]
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.Alpha10]
at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.Alpha10]
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559900#559900]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[JBoss Messaging] - Changing jboss messaging login-module
by victor Kazakov
victor Kazakov [http://community.jboss.org/people/kazvictor] created the discussion
"Changing jboss messaging login-module"
To view the discussion, visit: http://community.jboss.org/message/559898#559898
--------------------------------------------------------------
Hi,
I need to change the jboss messaging login module so that it obtains the correct username and password. But when i do I get errors starting jboss. I think it is because my custom login module is deployed after jboss messaging beans, but I am not sure. Any help or advice would be great. Thanks.
I'm using JBOSS AS 5.1.0
Below is my messaging-jboss-beans.xml file, my-destinations-service.xml, and the jobb log.
<?xml version="1.0" encoding="UTF-8"?>
<!--
Messaging beans
$Id: messaging-jboss-beans.xml 88672 2009-05-11 20:49:47Z anil.saldhana(a)jboss.com (mailto:anil.saldhana@jboss.com) $
-->
<deployment xmlns="urn:jboss:bean-deployer:2.0">
<!-- messaging application-policy definition -->
<application-policy xmlns="urn:jboss:security-beans:1.0" name="messaging">
<authentication>
<login-module code = "path.to.my.jaas.LoginModule"
flag = "required">
<!-- user-role mapping -->
<module-option name = "unauthenticatedIdentity">admin(a)email.com (mailto:admin@email.com)</module-option>
<module-option name = "dsJndiName">java:/MyConfigurationDS</module-option>
<module-option name = "principalsQuery">select password from user u inner join user_role ur on u.id=ur.user_id inner join authorization_role r on ur.role_id=r.id where u.email=? and u.status=2 and r.id=5</module-option>
<module-option name = "rolesQuery">select r.name as role, 'Roles' as role_group from user u inner join user_role ur on u.id=ur.user_id inner join authorization_role r on ur.role_id=r.id where u.email=? and u.status=2 and r.id=5</module-option>
<!-- password hashing -->
<module-option name="hashAlgorithm">HashType</module-option>
<module-option name="hashEncoding">HashEncoding</module-option>
<module-option name="hashCharset">UTF-8</module-option>
</login-module>
</authentication>
</application-policy>
<bean name="SecurityStore">
<!-- default security configuration -->
<property name="defaultSecurityConfig">
<![CDATA[
<security>
<role name="guest" read="true" write="true" create="true"/>
</security>
]]>
</property>
<property name="suckerPassword">CHANGE ME!!</property>
<property name="securityDomain">messaging</property>
<property name="securityManagement"><inject bean="JNDIBasedSecurityManagement"/></property>
<!-- @JMX annotation to export the management view of this bean -->
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.messaging:service=SecurityStore",exposedInterface=org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStoreMBean.class)</annotation>
<!-- Password Annotation to inject the password from the common password utility
<annotation>@org.jboss.security.integration.password.Password(securityDomain="messaging",methodName="setSuckerPassword")</annotation>
-->
</bean>
<bean name="MessagingDeploymentTemplateInfoFactory"
/>
<bean name="QueueTemplate">
<property name="info"><inject bean="QueueTemplateInfo"/></property>
</bean>
<bean name="QueueTemplateInfo"
>
<constructor factoryMethod="createTemplateInfo">
<factory bean="DSDeploymentTemplateInfoFactory"/>
<parameter>org.jboss.profileservice.management.templates.JmsDestinationTemplateInfo</parameter>
<parameter>org.jboss.jms.server.destination.QueueServiceMO</parameter>
<parameter>QueueTemplate</parameter>
<parameter>A template for JMS queue *-service.xml deployments</parameter>
</constructor>
<property name="destinationType">QueueTemplate</property>
</bean>
<bean name="TopicTemplate">
<property name="info"><inject bean="TopicTemplateInfo"/></property>
</bean>
<bean name="TopicTemplateInfo"
>
<constructor factoryMethod="createTemplateInfo">
<factory bean="DSDeploymentTemplateInfoFactory"/>
<parameter>org.jboss.profileservice.management.templates.JmsDestinationTemplateInfo</parameter>
<parameter>org.jboss.jms.server.destination.TopicServiceMO</parameter>
<parameter>TopicTemplate</parameter>
<parameter>A template for JMS topic *-service.xml deployments</parameter>
</constructor>
<property name="destinationType">TopicTemplate</property>
</bean>
</deployment>
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=removeUser">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
</server>
14:23:32,328 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@125ff6c6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)6e4d4b9d destination=queue/removeUser destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
javax.jms.JMSSecurityException: User: null is not authorized to read from destination removeUser
at org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.java:312)
at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:112)
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:597)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.createConsumerDelegate(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionCreateConsumerDelegateRequest.serverInvoke(SessionCreateConsumerDelegateRequest.java:100)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.remoting.Client.invoke(Client.java:617)
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.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createConsumerDelegate$aop(ClientSessionDelegate.java:267)
at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_8721389917985689973.invokeTarget(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConsumerDelegate(StateCreationAspect.java:142)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConsumerDelegate_1627839533.invoke(StateCreationAspect_z_handleCreateConsumerDelegate_1627839533.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ConsumerAspect.handleCreateConsumerDelegate(ConsumerAspect.java:76)
at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect_z_handleCreateConsumerDelegate_1627839533.invoke(ConsumerAspect_z_handleCreateConsumerDelegate_1627839533.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientSessionDelegate.createConsumerDelegate(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossConnectionConsumer.<init>(JBossConnectionConsumer.java:126)
at org.jboss.jms.client.container.SessionAspect.handleCreateConnectionConsumer(SessionAspect.java:772)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleCreateConnectionConsumer_1627839533.invoke(SessionAspect_z_handleCreateConnectionConsumer_1627839533.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.createConnectionConsumer(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.createConnectionConsumer(JBossConnection.java:140)
at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.setupConsumer(JmsServerSessionPool.java:289)
at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.start(JmsServerSessionPool.java:89)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupSessionPool(JmsActivation.java:656)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:359)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559898#559898]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[jBPM] - Measuring time before a task is taken
by Jimmy Smith
Jimmy Smith [http://community.jboss.org/people/swd_eagle] created the discussion
"Measuring time before a task is taken"
To view the discussion, visit: http://community.jboss.org/message/559886#559886
--------------------------------------------------------------
What is the best way to measure how long it takes for a task to be taken after creation? Eg, task is created and a group of users are assigned as candidates. But we want to know for reporting purposes how long it actually takes someone to take the task and start processing it.
I haven't tested it, but thought about using the progress field and then check that in the history, if possible. So when the progress changes from 0 (not started) to 1 (start), you can get an interval. Would setting the priority create history entries that can be used for this purpose?
Still need to figure out how to effectively manage a task that is released again and re-taken by someone else... might have to use some custom event handlers?
Any other suggestions?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559886#559886]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[jBPM] - jBPM not in Eclipse preferences; no runtime locations
by Maria Webster
Maria Webster [http://community.jboss.org/people/mmwebster] created the discussion
"jBPM not in Eclipse preferences; no runtime locations"
To view the discussion, visit: http://community.jboss.org/message/559875#559875
--------------------------------------------------------------
I've just installed jBPM 4.4 with Eclipse Helios on a CentOS 5.5 virtual machine. For the most part, I followed the instructions in the User Guide - veering off-course only when the instructions didn't exactly match my system, e.g. the screenshots for Windows, etc.
Here's my problem. In the User Guide, Section 2.11.3. "Configuring the jBPM runtime", I'm told to select jPBM from the options listed on the left side of the "Preferences" window. Unfortunately, jBPM isn't listed, so I can't specify the proper runtime location. This results in a number of errors (about 1000) in the GPD, and my installation is therefore incomplete, and broken.
How do I (a) get jBPM to appear correctly if I've followed all other installation steps correctly, and/or (b) is there another way to point to the proper runtime location without too much hacking?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559875#559875]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months