|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
|
|
[Issue 1094] New - WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
Issue #|1094 Summary|WSA Interop-109 EJB deployment errors with Metro 2.0 a |nd Glassfish V2 Component|wsit Version|2.0 Platform|All OS/Version|All URL| Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|jaxws-runtime Assigned to|jitu Reported by|jbenoit ------- Additional comments from jbenoit@... Fri Feb 27 20:53:32 +0000 2009 ------- JAX-WSA Interop Tests - JSR 109 EJB deployment using metro 2.0 on Glassfish V2 using JDK1.5.0_15,OS SunOS Test Suite IndigoClient Tests: WSAddressing:Test1150 WSAddressing:Test1250 WSAddressingAugust2004:Test1150 WSAddressingAugust2004:Test1250 all see error similar to this one: Service_Endpoint_Address = http://parada.czech.sun.com:8080/wsaTestService1/WsaTestImpl1 ERROR: System.TimeoutException: This request operation sent to http://parada.czech.sun.com:8080/wsaTestService1/WsaTestImpl1 did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. Server stack trace: at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at XwsInterop.WSAddressingCR.EchoContract.Echo(EchoInMessage text) at XwsInterop.WSAddressingCR.WSAddressingCRClient.RunEchoTest(Int32 testID, Uri address, MessageVersion messageVersion, Boolean isDualBinding, Boolean manualAddressing) at XwsInterop.WSAddressingCR.WSAddressingCRClient.Run(Int32 testID, Uri address, MessageVersion messageVersion) at XwsInterop.HostedClient.HostedClientSoapImpl.RunScenario(String scenarioName, Uri address) at XwsInterop.HostedClient.HostedClientSoapImpl.runScenario(String featureName, String scenarioName, HostedClientParameter[] parameters) Tests: WSAddressing:Test1200 WSAddressing:Test1251 WSAddressingAugust2004:Test1200 WSAddressingAugust2004:Test1251 all see errors similar to this one: Service_Endpoint_Address = http://parada.czech.sun.com:8080/wsaTestService2/WsaTestImpl2 ERROR: System.ServiceModel.CommunicationException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Send(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at XwsInterop.WSAddressingCR.NotifyContract.Notify(NotifyMessage message) at XwsInterop.WSAddressingCR.WSAddressingCRClient.RunNotifyTest(Int32 testID, Uri address, MessageVersion messageVersion) at XwsInterop.WSAddressingCR.WSAddressingCRClient.Run(Int32 testID, Uri address, MessageVersion messageVersion) at XwsInterop.HostedClient.HostedClientSoapImpl.RunScenario(String scenarioName, Uri address) at XwsInterop.HostedClient.HostedClientSoapImpl.runScenario(String featureName, String scenarioName, HostedClientParameter[] parameters) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
------- Additional comments from jbenoit@... Fri Feb 27 20:55:44 +0000 2009 ------- Created an attachment (id=815) test4u JAX-WSA Interop-109 EJB Deployment log file --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
------- Additional comments from jbenoit@... Fri Feb 27 20:57:23 +0000 2009 ------- Created an attachment (id=816) Glassfish domain1 server.log file --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
------- Additional comments from jbenoit@... Fri Feb 27 20:57:59 +0000 2009 ------- Created an attachment (id=817) Glassfish domain2 server.log file --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
------- Additional comments from jbenoit@... Fri Feb 27 20:58:35 +0000 2009 ------- Created an attachment (id=818) test4u installation/setup log file --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
------- Additional comments from jbenoit@... Fri Feb 27 20:59:27 +0000 2009 ------- Created an attachment (id=819) test4u xtest properties log file --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
User jitu changed the following: What |Old value |New value ================================================================================ Assigned to|jitu |jbenoit -------------------------------------------------------------------------------- ------- Additional comments from jitu@... Fri Oct 16 23:05:32 +0000 2009 ------- Since I see that WSA 109 interop tests are passing, see if it needs to be closed. Otherwise, give a reproducible testcase. --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
User jbenoit changed the following: What |Old value |New value ================================================================================ Status|NEW |STARTED -------------------------------------------------------------------------------- ------- Additional comments from jbenoit@... Sun Oct 25 05:29:12 +0000 2009 ------- the xtest.properties file shows these were testing against 3.0 endpoints (java11.india.sun.com machine), and those 3.0 results are currently showing 0% passing. woodstox-osgi.jar has been added to classpath to get past current error, but most recent results don't reflect that change. the next promoted build tests should not be blocked by woodstox-osgi.jar missing from classpath. if this error is not shown at that time, this bug can be closed. --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 1094] WSA Interop-109 EJB deployment errors with Metro 2.0 and Glassfish V2https://wsit.dev.java.net/issues/show_bug.cgi?id=1094
User jbenoit changed the following: What |Old value |New value ================================================================================ Status|STARTED |RESOLVED -------------------------------------------------------------------------------- Resolution| |FIXED -------------------------------------------------------------------------------- ------- Additional comments from jbenoit@... Wed Oct 28 04:48:30 +0000 2009 ------- the originally reported error: "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server." is no longer occurring using GF V3 b69 for JAX-WSA Interop Tests - JSR 109 EJB deployment, so closing bug as fixed in latest release of Glassfish. --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
| Free embeddable forum powered by Nabble | Forum Help |