[
https://issues.apache.org/jira/browse/AXIS2-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka updated AXIS2-4723:
---------------------------------------
Attachment: AXIS2-4723-update1.patch
Restored the test cases back to their original state. Summary of changes:
* Added a separate axis2.xml for client side usage (in the client side we
should use a different port than the server side)
* I encountered some problems (possible bug) in ListenerManager/ServiceClient
which leads to the same transport listener being initialized twice. I have
added a simple workaround for that in the respective test cases (look for
TODOs). This problem is now also being discussed in the mailing list. Depending
on the outcome of that we can change/remove the workarounds
If you are wondering why these issues did not show up until now, it was because
of the following bit of code in the TCPServer class (which I have removed):
public ServerSocket openSocket(int port) throws AxisFault {
for (int i = 0; i < 5; i++) {
try {
return new ServerSocket(port + i);
} catch (IOException e) {
// What I'm gonna do here. Try again.
}
}
throw new AxisFault(Messages.getMessage("failedToOpenSocket"));
}
So the above code basically catches bind exceptions and try to start the
listener on a different port. This has been masking the error all along.
> Make it Possible to Configure the TCP Transport at Service Level
> ----------------------------------------------------------------
>
> Key: AXIS2-4723
> URL: https://issues.apache.org/jira/browse/AXIS2-4723
> Project: Axis2
> Issue Type: Improvement
> Components: transports
> Affects Versions: 1.5
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> Attachments: AXIS2-4723-update1.patch, AXIS2-4723.patch
>
>
> Currently the TCP transport can only be configured in the axis2.xml
> (globally). It would be nice to be able to configure the transport at service
> level. We can do this by using the Axis2TransportListenerEx API. (I will soon
> attach a patch)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
