[JBoss JIRA] Created: (TEIID-1601) When the webservice translator cannot reach the endpoint url, the exception message should include the endpoint
3:27 p.m.
When the webservice translator cannot reach the endpoint url, the exception message should
include the endpoint
----------------------------------------------------------------------------------------------------------------
Key: TEIID-1601
URL: https://issues.jboss.org/browse/TEIID-1601
Project: Teiid
Issue Type: Enhancement
Components: XML Connector
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
When the webservice endpoint was not reachable, the exception on the server didn't
indicate which endpoint that was not accessible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:37 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1601) When the webservice translator cannot reach the endpoint url, the exception message should include the endpoint
[
https://issues.jboss.org/browse/TEIID-1601?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1601:
---------------------------------------
Can you provide a stack trace? It seems like this is a CXF issue. All teiid gets back is
a WebServicesException that may not be particularly meaningful. There are no codes or
anything for us to check.
When the webservice translator cannot reach the endpoint url, the
exception message should include the endpoint
----------------------------------------------------------------------------------------------------------------
Key: TEIID-1601
URL: https://issues.jboss.org/browse/TEIID-1601
Project: Teiid
Issue Type: Enhancement
Components: XML Connector
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
When the webservice endpoint was not reachable, the exception on the server didn't
indicate which endpoint that was not accessible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:10 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1601) When the webservice translator cannot reach the endpoint url, the exception message should include the endpoint
[
https://issues.jboss.org/browse/TEIID-1601?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1601:
------------------------------------
Here's the stack trace from trying to run the US States example:
Here is the stacktrace for the webservice US_States model. The same message is likely to
be repeated with my repeated attempts to run the query.
10:33:53,544 INFO [SessionFactoryObjectFactory] Not binding factory to JNDI, no JNDI name
configured
10:33:53,546 INFO [NamingHelper] JNDI InitialContext properties:{}
10:35:15,190 INFO [ReflectionServiceFactoryBean] Creating Service {http://teiid.org}teiid
from class org.apache.cxf.jaxws.support.DummyImpl
10:35:15,382 WARNING [PhaseInterceptorChain] Interceptor for
{http://teiid.org}teiid#{http://cxf.apache.org/jaxws/dispatch}Invoke has thrown exception,
unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:484)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:310)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:262)
at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:297)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:257)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:195)
at
org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:132)
at
org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:263)
at
org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281)
at
org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71)
at
org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123)
at
org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107)
at
org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188)
at
org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116)
at
org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:975)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:916)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:841)
at
sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1019)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1954)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1906)
at
org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
at
org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1972)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:640)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
... 20 more
10:35:15,420 WARN [CONNECTOR] Connector worker process failed for
atomic-request=4q1Ee3uuBbjI.0.3.0
[TranslatorException]Could not send Message.
1 [SOAPFaultException]Could not send Message.
2 [Fault]Could not send Message.
3 [ConnectException]Connection refused
at
org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:136)
at
org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:263)
at
org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281)
at
org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71)
at
org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123)
at
org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107)
at
org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188)
at
org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116)
at
org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.xml.ws.soap.SOAPFaultException: Could not send Message.
at org.apache.cxf.jaxws.DispatchImpl.mapException(DispatchImpl.java:235)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:264)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:195)
at
org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:132)
... 12 more
Caused by: org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:484)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:310)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:262)
at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:297)
at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:257)
... 14 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:975)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:916)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:841)
at
sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1019)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1954)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1906)
at
org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
at
org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1972)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:640)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
... 20 more
10:35:15,432 WARN [PROCESSOR] Processing exception 'Could not send Message.' for
request 4q1Ee3uuBbjI.0. Exception type org.teiid.core.TeiidProcessingException thrown
from java.net.PlainSocketImpl.socketConnect(Native Method). Enable more detailed logging
to see the entire stacktrace.
When the webservice translator cannot reach the endpoint url, the
exception message should include the endpoint
----------------------------------------------------------------------------------------------------------------
Key: TEIID-1601
URL: https://issues.jboss.org/browse/TEIID-1601
Project: Teiid
Issue Type: Enhancement
Components: XML Connector
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
When the webservice endpoint was not reachable, the exception on the server didn't
indicate which endpoint that was not accessible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:22 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1601) When the webservice translator cannot reach the endpoint url, the exception message should include the endpoint
[
https://issues.jboss.org/browse/TEIID-1601?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1601:
---------------------------------------
I think the best approach would be to update the exception handling in DataTierTuple
source to add the translator instance name to the exception message.
Anything more specific than that would best be implemented in cxf rather than having us
unwrap the exception.
When the webservice translator cannot reach the endpoint url, the
exception message should include the endpoint
----------------------------------------------------------------------------------------------------------------
Key: TEIID-1601
URL: https://issues.jboss.org/browse/TEIID-1601
Project: Teiid
Issue Type: Enhancement
Components: XML Connector
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
When the webservice endpoint was not reachable, the exception on the server didn't
indicate which endpoint that was not accessible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 a.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1601) When the webservice translator cannot reach the endpoint url, the exception message should include the endpoint
[
https://issues.jboss.org/browse/TEIID-1601?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1601.
-----------------------------------
Fix Version/s: 7.4.1
Resolution: Done
Updated the exception message to be prefixed with the translator instance name.
When the webservice translator cannot reach the endpoint url, the
exception message should include the endpoint
----------------------------------------------------------------------------------------------------------------
Key: TEIID-1601
URL: https://issues.jboss.org/browse/TEIID-1601
Project: Teiid
Issue Type: Enhancement
Components: XML Connector
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.4.1
When the webservice endpoint was not reachable, the exception on the server didn't
indicate which endpoint that was not accessible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:14 a.m.
New subject: [JBoss JIRA] (TEIID-1601) When the webservice translator cannot reach the endpoint url, the exception message should include the endpoint
[
https://issues.jboss.org/browse/TEIID-1601?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1601.
---------------------------------
When the webservice translator cannot reach the endpoint url, the
exception message should include the endpoint
----------------------------------------------------------------------------------------------------------------
Key: TEIID-1601
URL: https://issues.jboss.org/browse/TEIID-1601
Project: Teiid
Issue Type: Enhancement
Components: XML Connector
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.4.1, 7.5
When the webservice endpoint was not reachable, the exception on the server didn't
indicate which endpoint that was not accessible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4687
days inactive
4963
days old
5 comments
2 participants
participants (2)
-
Steven Hawkins (JIRA) -
Van Halbert (JIRA)