[JBoss Web Services] - Unable to obtain wsdl when running in IPv6 mode
by Paul Robinson
Paul Robinson [https://community.jboss.org/people/paul.robinson] created the discussion
"Unable to obtain wsdl when running in IPv6 mode"
To view the discussion, visit: https://community.jboss.org/message/740945#740945
--------------------------------------------------------------
All,
I'm experiencing a problem when I try to obtain the wsdl of a JAX-WS service when the latest (master as of 9am BST today) build of JBossAS is started in IPv6 mode. I think I'm configuring the server correctly for IPv6 as I use the same config as JBoss QE use.
To reproduce:
Build today's JBossAS7 master (~9am if having trouble reproducing)
Download the attatched simple project and unzip
cd jax-ws-simple
mvn install
cp target/echo_service-1.0.war $JBOSS_HOME/standalone/deployments/
Start jboss:
sh bin/standalone.sh -Djboss.bind.address=localhost -Djboss.bind.address.management=localhost -Djboss.bind.address.unsecure=localhost -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true
Try to obtain the wsdl:
curl http://localhost:8080/echo_service-1.0/EchoServiceService?wsdl
Observe the following from curl:
<html><head><title>JBoss Web/7.0.16.Final - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Cannot obtain destination for: /echo_service-1.0/EchoServiceService
org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:164)
org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:81)
org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:187)
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:115)
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the JBoss Web/7.0.16.Final logs.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/7.0.16.Final</h3></body></html>admins-MacBook-Pro:jax-ws-simple paul
And the following on the JBossAS console output:
11:38:06,110 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/echo_service-1.0].[org.my.simple.server.EchoServiceImpl]] (http-/0:0:0:0:0:0:0:1:8080-1) Servlet.service() for servlet org.my.simple.server.EchoServiceImpl threw exception: javax.servlet.ServletException: Cannot obtain destination for: /echo_service-1.0/EchoServiceService
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:164)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:81)
at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:187)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.1.0.Beta1.jar:2.1.0.Beta1]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.16.Final.jar:]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final.jar:]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31]
If you repeat, by starting up the server without my additional parameters, you should see that the wsdl is returned without issue.
Thanks,
Paul.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/740945#740945]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[JNDI and Naming] - Not working injection with Service
by Marco Col
Marco Col [https://community.jboss.org/people/lanrjtokenring] created the discussion
"Not working injection with Service"
To view the discussion, visit: https://community.jboss.org/message/740924#740924
--------------------------------------------------------------
Hi all,
I have this problem and I cannot get rid ot it!
I have a JBoss service like this:
@Service()
@Local(MyServLocal.class)
@Remote(MyServRemote.class)
@Management(MyServRemoteManagement.class)
@Depends("jboss.ha:service=HASingletonDeployer,type=Barrier")
@Clustered
public class MyService
implements MyServLocal,MyServRemote {
@Resource(mappedName="activemq/TopicConnectionFactory")
private TopicConnectionFactory tConnFactory;
@Resource(mappedName="topic/CTOST")
private Topic ctostopic;
public void create(){
if(tConnFactory!=null){
System.out.println("[Start] Scheduler started");
} else {
System.out.println("[Start] Failed");
}
}
public void start() {
this.create();
}
Either tConnFactory and ctostopic are null. By the way I can see the resources in JNDIView and, if I call after JBoss startup a EJB injecting the same resources, references are correctly injected.
Can anybode help on this? Any idea?
This is with JBoss 5.1, but also with 6.
Regards
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/740924#740924]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[JNDI and Naming] - Lookups from jboss 7 to jboss 4
by Carlos Rodríguez
Carlos Rodríguez [https://community.jboss.org/people/caalroja] created the discussion
"Lookups from jboss 7 to jboss 4"
To view the discussion, visit: https://community.jboss.org/message/721367#721367
--------------------------------------------------------------
Hello, a couple years ago I created and deployed 2 applications that work together on jboss 4. Now, I want to migrate one of them (because the other one is too coupled to jboss 4) to jboss 7 but I have a problem when I make the lookups calls. When I make a lookup on my current server (jboss 7) everything works good, but when I try to make the jboss 4 lookups this message is shown
17:35:06,898 ERROR [stderr] (http--127.0.0.1-8080-4) javax.naming.NameNotFoundException: map-server/ClientBean/remote -- service jboss.naming.context.java.map-server.ClientBean.remote
17:35:06,902 ERROR [stderr] (http--127.0.0.1-8080-4) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
17:35:06,902 ERROR [stderr] (http--127.0.0.1-8080-4) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
17:35:06,902 ERROR [stderr] (http--127.0.0.1-8080-4) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113)
17:35:06,903 ERROR [stderr] (http--127.0.0.1-8080-4) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:213)
17:35:06,903 ERROR [stderr] (http--127.0.0.1-8080-4) at javax.naming.InitialContext.lookup(InitialContext.java:392)
- My original Initial Context code (when the the app was on jboss 4) was this:
Properties env = new Properties();
env.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
env.put("java.naming.provider.url", url);
InitialContext ctx = new InitialContext(env);
and I used to make the lookups this way:
client = (Client) ctx.lookup("Appear/ClientBean/remote");
- My new Initial Context code (Jboss 7) is this:
Properties env = new Properties();
env.put("java.naming.factory.initial", "org.jboss.as.naming.InitialContextFactory"); //this change
env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
env.put("java.naming.provider.url", Params.getValue("com.ogangi.mimampp3.NAMING_PROVIDER_URL"));
InitialContext ctx = new InitialContext(env);
and a I still make same the lookups:
client = (Client) ctx.lookup("Appear/ClientBean/remote");
Any Idea?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/721367#721367]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years