[JBossWS] - Cannot obtain endpoint meta data when accessing web service
by outlawjose
Having an issue getting my web service to work.
I installed JBossWS 3.1.0 GA into my server (bundled JBoss AS 4.2.3 / JBoss Portal 2.7.2) and deployed a web service using JBoss Dev Studio 2.0.0.CR2. The web service implementation has one method that takes a string and returns a string (nothing fancy). I used the JBoss tools to generate the web service from a WSDL. The packaged web service (J2EE EAR with web.xml updated to add a servlet/mapping) deploys without any errors.
It shows up in the Registered Service Endpoint, but when I click on the link, I get an error stating IllegalStateException: Cannot obtain endpoint meta data and the browser shows the generic error that "XML must have a top level element" since it is an empty file.
Are the above releases I am deploying to compatible? If not can someone point me to the correct combination? Or am I missing something? Any avenues to investigate would be appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221341#4221341
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221341
17 years
[JCA/JBoss] - Re: jboss ha datasource configuration to the same host
by adrian@jboss.org
"brettcave" wrote : Would something like this work?
|
| I am using heartbeat + ldirector for HA and loadbalancing of sql servers.
|
| I find that jboss applications become unavailable for a while if the connection gets lost - which happens occassionally due to packet loss. So in trying to get a stable jboss + mysql infrastructure, I would like to use
| <ha-tx-local-datasource>
| <connection-url>jdbc:mysql://ha.host:3306/db|jdbc:mysql://ha.host:3306/db</connection-url>
|
I don't think that will work? Looking at the HAXAConnectionFactory the urls
get parsed to an "XAData" which is treated as equal if the urls are the same.
But then again it stores them in a List rather than a Set so it might still work?
anonymous wrote :
| Also, i read somewhere that using background-validation with check-valid-connection-sql can cause a conflict, but cant find further info on it... any recommendations for detecting whether connections are valid?
|
??? It is duplicate work, I don't know it is a conflict since one works on
idle connections, the other on connections just about to be used (i.e. not idle).
anonymous wrote :
| lastly, is using jdbc:mysql://ha.host:3306/db?autoReconnect=true the same as leaving "autoReconnect=true" off the URL and adding it to <connection-property> ?
Completely broken if you use any form of transactions.
AFAIK, the reconnect will use a different connection that knows nothing about previous
work in an ongoing transaction.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221316#4221316
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221316
17 years