This content has been marked as final.
Show 1 reply
-
1. Re: Cannot find service endpoint error when deploying ear wi
ewinston May 14, 2009 4:37 PM (in response to ewinston)15:15:51,330 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment 15:15:51,345 INFO [JmxKernelAbstraction] installing MBean: persistence.units:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,unitName=WebAlertDataCollection-PU with dependencies: 15:15:51,346 INFO [JmxKernelAbstraction] jboss.jca:name=WebAlertDataCollectionXADS,service=DataSourceBinding 15:15:51,742 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 15:15:51,765 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=VSMAlertRegistration,service=EJB3 with dependencies: 15:15:51,765 INFO [JmxKernelAbstraction] persistence.units:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,unitName=WebAlertDataCollection-PU 15:15:51,765 INFO [JmxKernelAbstraction] jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=SubscriptionMaintenance,service=EJB3 15:15:51,767 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 15:15:51,767 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=VSMDataFilter,service=EJB3 with dependencies: 15:15:51,832 INFO [EJBContainer] STARTED EJB: com.vzw.vsm.opalarm.webalert.session.VSMFilter ejbName: VSMDataFilter 15:15:51,892 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 15:15:51,892 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=SubscriptionMaintenance,service=EJB3 with dependencies: 15:15:51,897 INFO [EJBContainer] STARTED EJB: com.vzw.vsm.opalarm.webalert.session.SubscriptionScheduledAction ejbName: SubscriptionMaintenance 15:15:52,585 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 15:15:52,586 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear,jar=ejb-0.2.2-SNAPSHOT.jar,name=ObjectPersister,service=EJB3 with dependencies: 15:15:52,590 INFO [EJBContainer] STARTED EJB: com.vzw.vsm.opalarm.webalert.session.ObjectPersister ejbName: ObjectPersister 15:15:52,610 INFO [EJB3Deployer] Deployed: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/tmp/deploy/tmp39565WebAlertDataCollection-0.2.2-SNAPSHOT.ear-contents/ejb-0.2.2-SNAPSHOT.jar 15:15:52,834 INFO [DefaultEndpointRegistry] register: jboss.ws:context=WebAlertDataCollection-0.2.2-SNAPSHOT-ejb-0.2.2-SNAPSHOT,endpoint=VSMAlertRegistration 15:15:52,842 INFO [DefaultEndpointRegistry] register: jboss.ws:context=WebAlertDataCollection-0.2.2-SNAPSHOT-ejb-0.2.2-SNAPSHOT,endpoint=VSMDataFilter 15:15:52,979 INFO [TomcatDeployer] deploy, ctxPath=/WebAlertDataCollection-0.2.2-SNAPSHOT-ejb-0.2.2-SNAPSHOT, warUrl=.../tmp/deploy/WebAlertDataCollection-0.2.2-SNAPSHOT.ear-ejb-0.2.2-SNAPSHOT.jar39566.war/ 15:15:56,320 INFO [WSDLFilePublisher] WSDL published to: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/data/wsdl/WebAlertDataCollection-0.2.2-SNAPSHOT.ear/ejb-0.2.2-SNAPSHOT.jar/AlertRegistrationService39567.wsdl 15:15:56,337 INFO [WSDLFilePublisher] WSDL published to: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/data/wsdl/WebAlertDataCollection-0.2.2-SNAPSHOT.ear/ejb-0.2.2-SNAPSHOT.jar/VSMFilterService39570.wsdl 15:15:56,625 ERROR [MainDeployer] Could not start deployment: file:/work/edward/vzw/environment/jboss-4.2.3.GA/server/vzw/tmp/deploy/tmp39565WebAlertDataCollection-0.2.2-SNAPSHOT.ear-contents/ejb-0.2.2-SNAPSHOT.jar javax.xml.ws.WebServiceException: Cannot find service endpoint target: jboss.j2ee:name=VSMAlertRegistration,service=EJB3,jar=ejb-0.2.2-SNAPSHOT.jar,ear=WebAlertDataCollection-0.2.2-SNAPSHOT.ear at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.init(InvocationHandlerEJB3.java:83) at org.jboss.wsf.framework.deployment.DefaultLifecycleHandler.create(DefaultLifecycleHandler.java:51) at org.jboss.wsf.framework.deployment.EndpointLifecycleDeploymentAspect.create(EndpointLifecycleDeploymentAspect.java:42) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
Here is part of the sack trace. I will create a sample project that shows this problem. It looks like the service gets installed but it isn't ready for use the first time it is accessed. I have gotten around the injection problem by looking up the entity manager in JNDI, but it looks like now the entity manager is not cognizant of the injected USerTransaction and the fact that I have started a transaction there.
I am using the JTA transaction type because elsewhere I need it.
Thanks again.
Edward