[EJB 3.0] - Please help~~deployment of webservice
by sim9739
HI all,
I am using jboss 4.0.4, jwsdp-2.0 and jbpm-bpel 1.1 beta 3. I have install everything needed to run the web service. after the installation, i deploy the hello example in the folder of jbpm-bpel.
I can see the hello service in this link
http://localhost:8080/jbossws/services
then , i click the link http://localhost:8080/hello/greeter?wsdl
then nothing is shown up in the browser. i am using safari as my browser.
Is that suppose to see something after clicking the link?
and i start my web service by going to link http://localhost:8080/hello/greeter
it throws an exception
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.jboss.util.NotImplementedException: HTTP GET not supported
org.jboss.ws.server.ServiceEndpointServlet.doGet(ServiceEndpointServlet.java:95)
javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.
Did i do something wrong? Can anyone tell me why it throws exception? And How to fix the problem?
Thanks a lot!!!!!
sim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111753#4111753
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111753
18 years, 4 months
[EJB 3.0] - Please help~~deployment of webservice
by sim9739
HI all,
I am using jboss 4.0.4, jwsdp-2.0 and jbpm-bpel 1.1 beta 3. I have install everything needed to run the web service. after the installation, i deploy the hello example in the folder of jbpm-bpel.
I can see the hello service in this link
http://localhost:8080/jbossws/services
then , i click the link http://localhost:8080/hello/greeter?wsdl
then nothing is shown up in the browser. i am using safari as my browser.
Is that suppose to see something after clicking the link?
and i start my web service by going to link http://localhost:8080/hello/greeter
it throws an exception
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.jboss.util.NotImplementedException: HTTP GET not supported
org.jboss.ws.server.ServiceEndpointServlet.doGet(ServiceEndpointServlet.java:95)
javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.
Did i do something wrong? Can anyone tell me why it throws exception? And How to fix the problem?
Thanks a lot!!!!!
sim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111752#4111752
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111752
18 years, 4 months
[Installation, Configuration & DEPLOYMENT] - exception occurs while deployingDB2JDBC driver jar
by wedny＠embt
Hello All,
Our application uses Jboss4.03 with 1.5 jdk. It works fine till now we updated the DB2 JDBC Driver jar from IBM.
With the new DB2 JDBC Driver jar, the server gets "java.io.IOException: non class file" threw by "org.jboss.ejb3.EJB3Deployer.hasEjbAnnotation".
The whole stacktrace:
13:33:47,606 ERROR [MainDeployer] Could not initialise deployment: file:/C:/EMServer/server/all/deploy/6_ems.sar.ear/
org.jboss.deployment.DeploymentException: exception in init of file:/C:/EMServer/server/all/tmp/deploy/tmp21386ems.sar-contents/lib/drivers/db2/
ava.lang.RuntimeException: java.io.IOException: non class file)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:887)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:881)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:881)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor52.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 $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.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)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.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)
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 $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
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.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 $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:464)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: java.io.IOException: non class file
at org.jboss.ejb3.EJB3Deployer.hasEjbAnnotation(EJB3Deployer.java:219)
at org.jboss.ejb3.EJB3Deployer.accepts(EJB3Deployer.java:251)
at sun.reflect.GeneratedMethodAccessor13.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.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:109)
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 $Proxy30.accepts(Unknown Source)
at org.jboss.deployment.MainDeployer.findDeployer(MainDeployer.java:1060)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:846)
... 68 more
Caused by: java.io.IOException: non class file
at javassist.bytecode.ClassFile.read(ClassFile.java:611)
at javassist.bytecode.ClassFile.(ClassFile.java:52)
at org.jboss.ejb3.EJB3Deployer.hasEjbAnnotation(EJB3Deployer.java:199)
Does somebody know how to fix it?
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111747#4111747
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111747
18 years, 4 months
[JBossWS] - Re: Document Literal style
by alessio.soldano＠jboss.com
"zeeshan.javeed" wrote : Hi,
| I have to modify the current webservices developed using old version of Jbossws. Now I have complied the server side with new jbossws 2.0.2 and new wsdl file is generated and deployed. The new client created against this wsdl file using wsconsume works very fine but the old client, created with pervious version are not working.
This is a quite common issue for users that have been using old JBossWS versions. If you need to expose a wsdl contract that is exactly the same of your previous one, you should try with the top-down approach. See this for further information: http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools#Top...
This way your service clients should work without changes.
anonymous wrote : After my investigation, I am of the view that problme is due to mapping and document literal style. Earlier code generated a mapping.xml file and now this time no mapping.xml file is generated. So that is the main reason I asked how we can use the Document Literal in a right way.
As previously said, the jaxrpc-mapping.xml is not related to the wsdl style you use (Document/literal, rpc/literal, etc.). That mapping file is simply not generated by our jax-ws stack.
anonymous wrote : Secondly, my wsdl file is always generated and deployed in Jboss , default/data folder. I wanted to deploy it some other location and with different port , for example 8080 instead of 80, so that i can debug the out put using TCP MON. Can Any body, help me how to
| 1) use Document Literal ( so that it generates mapping.xml file )
| 2) change locatoin and port of wsdl file.
Is your concern about the wsdl address or the endpoint address?
Please take a look at the FAQ to understand how the endpoint address relates to the context configuration (i.e. how you can change that address): http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#How_do_I_know_what_e...
The port used for every endpoints depends on the jboss-web configuration of your application server.
You might also be interested in reading how you can configure JBossWS to rewrite the endpoint addresses in the wsdl files (once you download the wsdl, you get the endpoint address from it's contents... and that automatically generated address can be rewritten changing the host and port):
http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#How_does_rewriting_o...
Finally, it seems to me there has been a little misunderstanding with Richard on what you need to do. The wsdlLocation attribute of @WebService should be used to point the stack to the wsdl location during the deployment phase. As a matter of fact jbossws needs to read the wsdl (if you decide to expose your own one instead of letting it generate it for you) and wsdlLocation specifies the relative URL to the wsdl. You can of course deploy your wsdl as a simple xml file everywhere you want as a simple jboss-web app and then have jbossws read it from there... but imho that's not the suggest way to go. Please give us some further information to better understand your usecase.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111744#4111744
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111744
18 years, 4 months
[Remoting] - Re: JBREM-786:
by jahlborn
hi,
sorry i haven't replied in a while. i kind of got away from this for a bit. anyway, we certainly have a mix of code. just fyi, we are using jboss 4.0.5.GA in production, so my changes are built on top of the remoting version in that release, which i believe is actually JBossRemoting 1.4.3.
to respond to your question about the leaky connections, i believe we have that fix: that is the change which extends the "synchronized(this)" block up around the clientpool updates in ServerThread.run, correct?
in our application, we have a high number of relatively quick remote calls happening on ~60 threads in each client app server. Since we had ~10 client servers running ~60 threads all banging on the same remote server, we easily hit the 300 thread maximum in the server thread pool. this means that new requests to the server can cause "evict()" to be called on the clientpool (in SocketServerInvoker). This eviction will cause a socket to be closed after an in-flight call ends. On the client side, this will cause a pooled socket to be fine for one call, and then throw an EOFException the next time it is used. With the retry logic backported, it would seem highly unlikely that a single request would see 3 closed client sockets in a row (especially with the "flush" call before the last attempt). However, when we fired up the system at full speed, we would see at least one of these complete failures per "job" (which could be ~100k remote calls to the remote server among all the client boxes).
the flushConnectionPool() call on the last attempt was obviously an attempt to mitigate this problem, however it still does not gaurantee that the client will get a fresh connection on the next attempt, only makes it more likely. apparently, in our application, this was not a good enough effort as we still saw the issue (albeit infrequently). When i implemented the changes included in the patch, however, this problem stopped occurring at all.
It seems clear, though, that this patch would be more appropriate for the 2.0 code base, not the 1.4.x code base (unless there is more backporting planned).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111743#4111743
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111743
18 years, 4 months