[JBoss Web Services] - MessageContext lost data while passing a handler (outgoing)
by web.leo
web.leo [https://community.jboss.org/people/web.leo] created the discussion
"MessageContext lost data while passing a handler (outgoing)"
To view the discussion, visit: https://community.jboss.org/message/747720#747720
--------------------------------------------------------------
Hej hej,
I´m using JBoss in Version 5.1.1 (build: SVNTag=JBPAPP_5_1_1 date=201105171607) and the JBossWS Native Stack in Version 3.1.2 GA.
I´ve implemented a WebService with two handlers. On of these handler (first one for incoming and last one for outgoing messages) put an hibernate entity to the message context. During processing of the WebService logic this entity will be completed with some data and should be stored to database at the end (which means in the last handler the message passes).
When I send some more or less parallel requests to the service it sometime happens that some of the data in the hibernate entity get lost which was set in the WS logic part. The data which was set shortly before storing the data is still there - also the data which was set from handlers when the message came in.
I tried to find a solution but i didn´t find some page where this problem was correctly described... Does someone know how to solve this issue?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/747720#747720]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 5 months
[jBPM] - java.lang.NullPointerException when you try to getProcessInstance of bad instance.
by hiro.y
hiro.y [https://community.jboss.org/people/hiro.y] created the discussion
"java.lang.NullPointerException when you try to getProcessInstance of bad instance."
To view the discussion, visit: https://community.jboss.org/message/747659#747659
--------------------------------------------------------------
I found good way of trouble shooting.
If you try to getProcessInstance and get java.lang.NullPointerException,
Try to check your DB manually.
1.Start h2 manually
${install.home} > java -cp db\driver\h2.jar org.h2.tools.Server
2.Connect to your db from browser ( http://172.22.14.186:8082/ http://172.22.14.186:8082/)
driver class :org.h2.Driver
JDBC URL : jdbc:h2:tcp://localhost/runtime/jbpm
3.Select processinstanceinfo
SELECT * FROM PROCESSINSTANCEINFO
https://community.jboss.org/servlet/JiveServlet/showImage/2-747659-18999/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-747659-18...
4.And search bad processinstance which contains null in dataset.
When I got error like below, this solved the problem.
Hope this help you.
------------------------------------------------
2012/07/10 15:08:13,697 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gwt-console-server].[Resteasy]] (http--0.0.0.0-8080-5) サーブレット Resteasy のServlet.service()が例外を投げました: org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
at org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:345) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:321) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:534) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:496) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.2.1.GA.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) [classes:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:480) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: java.lang.NullPointerException
at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89) [:1.6.0_21]
at org.jbpm.persistence.processinstance.ProcessInstanceInfo.getProcessInstance(ProcessInstanceInfo.java:132) [jbpm-persistence-jpa-5.3.0.Final.jar:]
at org.jbpm.persistence.processinstance.JPAProcessInstanceManager.getProcessInstance(JPAProcessInstanceManager.java:83) [jbpm-persistence-jpa-5.3.0.Final.jar:]
at org.jbpm.process.instance.ProcessRuntimeImpl.getProcessInstance(ProcessRuntimeImpl.java:204) [jbpm-flow-5.3.0.Final.jar:]
at org.drools.common.AbstractWorkingMemory.getProcessInstance(AbstractWorkingMemory.java:1100) [drools-core-5.4.0.Final.jar:]
at org.drools.impl.StatefulKnowledgeSessionImpl.getProcessInstance(StatefulKnowledgeSessionImpl.java:297) [drools-core-5.4.0.Final.jar:]
at org.drools.command.runtime.process.GetProcessInstanceCommand.execute(GetProcessInstanceCommand.java:48) [drools-core-5.4.0.Final.jar:]
at org.drools.command.runtime.process.GetProcessInstanceCommand.execute(GetProcessInstanceCommand.java:25) [drools-core-5.4.0.Final.jar:]
at org.drools.command.impl.DefaultCommandService.execute(DefaultCommandService.java:36) [drools-core-5.4.0.Final.jar:]
at org.drools.persistence.SingleSessionCommandService.execute(SingleSessionCommandService.java:367) [drools-persistence-jpa-5.4.0.Final.jar:]
at org.drools.command.impl.CommandBasedStatefulKnowledgeSession.getProcessInstance(CommandBasedStatefulKnowledgeSession.java:125) [drools-core-5.4.0.Final.jar:]
at org.jbpm.integration.console.CommandDelegate.getActiveNodeInstances(CommandDelegate.java:211) [jbpm-gwt-core-5.3.0.Final.jar:]
at org.jbpm.integration.console.ProcessManagement.getProcessInstances(ProcessManagement.java:75) [jbpm-gwt-core-5.3.0.Final.jar:]
at org.jboss.bpm.console.server.ProcessMgmtFacade.getInstancesJSON(ProcessMgmtFacade.java:192) [classes:]
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.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:255) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:220) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:209) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:519) [resteasy-jaxrs-2.2.1.GA.jar:]
... 24 more
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/747659#747659]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 5 months
[jBPM] - Exposing WorkItemHandler as an EJB (3.1) and referencing that work item handler from the BPMN process definition
by Mark Egan
Mark Egan [https://community.jboss.org/people/xmrk] created the discussion
"Exposing WorkItemHandler as an EJB (3.1) and referencing that work item handler from the BPMN process definition"
To view the discussion, visit: https://community.jboss.org/message/747651#747651
--------------------------------------------------------------
JBPM 4.4 allowed us to expose an EJB and reference that <java> node within the JPDL using the attribute ejb-jndi-name ([per devguide: http://docs.jboss.com/jbpm/v4/devguide/html_single/#java http://docs.jboss.com/jbpm/v4/devguide/html_single/#java]). This was remarkable as it allowed deploying new, heavy Activities without the need of cracking open the process engine component itself.
+Does jBPM 5.x have any similar capabilities?+
The following two options would allow a similar pattern. I have made an attempt to avoid Spring injection as I haven't found a need for it given the current capabilities of EJB 3.1 / CDI:
-----
#1: Implement a configuration @Singleton internal to the process engine component that exposes the following:
{code}public void addWorkItemHandler(String id, WorkItemHandler workItem);
public void removeWorkItemHandler(String id);{code}
and delegates the following:
{code}private Map<String, WorkItemHandlers> workItemHandlers;{code}
Implement an external @Singleton EJB that provides a WorkItemHandler. That WorkItemHandler is injected with configuration @Singleton and registers itself with that configuration during the @PostConstruct callback.
I used singletons here to easy state consistency (or render it unnecessary). As such, it doesn't take advantage of pooling. There may be ways to do something similar with other EJB 3.1 / CDI technologies - I haven't explored some of the other options.
-----
#2: Implement a proxy WorkItemHandler internal to the process engine component that is provided a JNDI name within the parameters Map. That WorkItemHandler would perform a lookup on the JNDI name and call executeWorkItem on the resolved resource by forwarding the original workItem and manager. This would allow container managed pooling.
-----
I originally implemented #1 when I jumped into this issue only to think of #2 later. I'll likely be refactoring to the #2 pattern if no one has a better option for me. My hope is that jBPM 5.x already provides a community vetted and exercised solution rather than having to implement my own.
Thanks,
-mark
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/747651#747651]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 5 months
[JBoss Messaging] - Failed to Route Reference[message#]:RELIABLE to queue
by runurathi
runurathi [https://community.jboss.org/people/runurathi] created the discussion
"Failed to Route Reference[message#]:RELIABLE to queue"
To view the discussion, visit: https://community.jboss.org/message/747623#747623
--------------------------------------------------------------
We have a queue that is deployed successfully and is visible in the JmxConsole on a remote JBoss 5.0.1 server instance. We can also see that there are messages in the queue as well.
We are seeing the following error from the MDB when attempting to do a send. The MDB is deployed on a local JBoss 5.0.1 server instance. Both the remote and local instances are using JBM 1.4.3.GA
javax.jms.JMSException: Failed to route Reference[23511337789456384]:RELIABLE to werner.ais.smart.q.POImportResponse. I have included the full stack trace below.
I can successfully post to the queue using a stand-alone JMS client. I am doing a jndi lookup to the queue and the using MessageProducer to send the message in both JMS client and the MDB. It works in a JMS client but does not from within the MDB. Any suggestions on how to resolve the issue.?
2012-07-11 12:03:11,409 ERROR [org.jboss.messaging.util.ExceptionUtil] (WorkManager(2)-50) SessionEndpoint[jz1-fgsqni4h-1-xoiini4h-7jwivt-k372us4] send [kz1-xksqni4h-1-xoiini4h-7jwivt-k372us4]
javax.jms.JMSException: Failed to route Reference[23511337789456384]:RELIABLE to werner.ais.smart.q.POImportResponse
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:771)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:399)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeTarget(SessionAdvised$send_7280680627620114891.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
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.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:157)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1927)
at org.jboss.remoting.Client.invoke(Client.java:770)
at org.jboss.remoting.Client.invoke(Client.java:758)
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$send$aop(ClientSessionDelegate.java:499)
at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeTarget(ClientSessionDelegate$send_6145266547759487588.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.client.container.SessionAspect.handleSend(SessionAspect.java:661)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleSend_1038552594.invoke(SessionAspect_z_handleSend_1038552594.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.send(ClientSessionDelegate.java)
at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:276)
at org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect_z_handleSend_1038552594.invoke(ProducerAspect_z_handleSend_1038552594.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.ClientProducerDelegate.send(ClientProducerDelegate.java)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:165)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:208)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:146)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:137)
at com.werner.util.jms.AbstractJmsUtil.send(AbstractJmsUtil.java:152)
at com.werner.purchaseOrder.PurchaseOrderRequestMb.onMessage(PurchaseOrderRequestMb.java:142)
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.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:76)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:62)
at sun.reflect.GeneratedMethodAccessor471.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_1038552594.invoke(InvocationContextInterceptor_z_fillMethod_1038552594.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_1038552594.invoke(InvocationContextInterceptor_z_setup_1038552594.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.TxPolicy.invokeInNoTx(TxPolicy.java:66)
at org.jboss.ejb3.tx.TxInterceptor$NotSupported.invoke(TxInterceptor.java:114)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:282)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:299)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:152)
at $Proxy344.onMessage(Unknown Source)
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:179)
at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic(ClientConsumer.java:160)
at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleRun_1038552594.invoke(SessionAspect_z_handleRun_1038552594.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.ClientSessionDelegate.run(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossSession.run(JBossSession.java:199)
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:236)
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:662)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/747623#747623]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 5 months
[Beginner's Corner] - JBoss erststart nicht korrekt ?
by Jack Gruber
Jack Gruber [https://community.jboss.org/people/hijack1112] created the discussion
"JBoss erststart nicht korrekt ?"
To view the discussion, visit: https://community.jboss.org/message/747507#747507
--------------------------------------------------------------
hi,
ich habe heute erstmals JBoss Server runtergeladen und entpackt. JAVA_HOME und JBOSSESB_HOME wurden gesetzt. Dann starte ich run.bat ...
+16:26:54,556 INFO [JBoss4ESBDeployer] create esb service, soap.esb+
+16:27:00,110 INFO [JBoss4ESBDeployer] create esb service, spring.esb+
+16:27:00,110 ERROR [URLDeploymentScanner] Incomplete Deployment listing:+
+--- MBeans waiting for other MBeans ---+
+ObjectName: jboss.esb:service=JuddiRMI+
+ State: FAILED+
+ Reason: java.lang.ExceptionInInitializerError+
+ I Depend On:+
+ jboss.esb:service=JUDDIDatabaseInitializer+
+ jboss.esb:service=PropertyService+
+ Depends On Me:+
+ jboss.esb:service=JuddiClient+
+--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---+
+ObjectName: jboss.esb:service=JuddiRMI+
+ State: FAILED+
+ Reason: java.lang.ExceptionInInitializerError+
+ I Depend On:+
+ jboss.esb:service=JUDDIDatabaseInitializer+
+ jboss.esb:service=PropertyService+
+ Depends On Me:+
+ jboss.esb:service=JuddiClient+
+16:27:00,141 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8+
+080+
+16:27:00,188 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009+
+16:27:00,188 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos+
+s_4_2_3_GA date=200807181417)] Started in 37s:85ms+
Was bedeutet diese Fehlermeldung oben genau bzw. wie kann ich sie beheben?
Lg
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/747507#747507]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 5 months
