[
https://jira.jboss.org/jira/browse/JBWS-1822?page=com.atlassian.jira.plug...
]
Christian Groove commented on JBWS-1822:
----------------------------------------
Salut mecs,
the problem hints to an inavailable ressource on the
session bean, like a delayed of unavailable
datasource.You shold check the server.log for any
kind of ressource problems.
In our case, our web-services suddently ran
into the same problem,. throwing the same exception.
We are using an Oracle-DB for to persist our data.
Sombody changed the OracleDialect to OracleDialect
or another one finally we hat the problems with our
webservice.
Some week later i noticed error messages (only one
line) like this one:
server.log.2009-10-02:2009-10-02 11:28:36,575 INFO [org.hibernate.dialect.Dialect] Using
dialect: org.hibernate.dialect.Oracle10gDialect
server.log.2009-10-02:2009-10-02 11:39:37,602 INFO [org.hibernate.dialect.Dialect] Using
dialect: org.hibernate.dialect.OracleDialect
server.log.2009-10-02:2009-10-02 11:39:37,602 WARN [org.hibernate.dialect.Oracle9Dialect]
The Oracle9Dialect dialect has been deprecated; use either Oracle9iDialect or
Oracle10gDialect instead
Despite the fact, that this are only warnings, i guess,
i found that smoking gun.
Assumption:
The error/warning condition slowed down the
session bean, causing the WS unsuccessfully
searching for a session bean, that has not been
started.
I switched to the Oracle10gDialect and the problem
disappeared!
Voila
Cannot find service endpoint target
-----------------------------------
Key: JBWS-1822
URL:
https://jira.jboss.org/jira/browse/JBWS-1822
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-2.0.1
Environment: WindowsXP, JDK5U11, JBoss4.2.1
Reporter: Harro Harten
Assignee: Richard Opalka
Attachments: Test_JBossws_201.rar
Hello,
I´ve taken the TestSample called 'webservice' of the JbossWS-native-2.0.1GA
package and modified it by adding a simple TestBean with the @EJB annotation inside of the
'EJB3Bean01.java'. This works very well, only if all classes are in the same
package,
if you move the TestBean in another package, the following Error occur:
ERROR [org.jboss.deployment.MainDeployer] Could not start deployment:
file:/C:/jboss_4.2.1_WS_2.0.1/server/default/tmp/deploy/tmp39184test.ear-contents/jaxws-samples-webservice01-ejb3.jar
javax.xml.ws.WebServiceException: Cannot find service endpoint target:
jboss.j2ee:name=EJB3Bean01,service=EJB3,jar=jaxws-samples-webservice01-ejb3.jar,ear=test.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:115)
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)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy32.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor29.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.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
I´ve added the whole eclipse project as an attachment.
Thanks,
Harry
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira