Issue with sending xml jaxb object to servlet body

[Julien Raynal]

I have been working on this simple call to a servlet that reads the xml passed to it but keep getting a 500 error. Could anyone point me in the right direction?

Here is the client code:

 URL url = null;
		int responseCode = 0;
		try {
			url = new URL(servletUrl);
			System.out.println("Connecting to: " + servletUrl);
			HttpURLConnection conn = (HttpURLConnection) url.openConnection();
			conn.setRequestMethod("POST");
			conn.setDoOutput(true);
			conn.setDoInput(true);
			JAXBContext context = JAXBContext.newInstance(jaxbObject.getClass());
		    Marshaller marshaller = context.createMarshaller();
		    marshaller.marshal(jaxbObject, conn.getOutputStream());
			//output.close();
			responseCode = conn.getResponseCode();
			if (responseCode < 200 || responseCode > 299) {
			throw new IOException("Error loading xml from jaxb: " +  responseCode);
			}   

I cannot figure out what is wrong... Going crazy. I am simply creating a jaxb object and marshalling it to the servlet output stream.

Here is the servlet code:

 public void getStrategyData(HttpServletRequest request, HttpServletResponse response) throws IOException {
		
		Object data = null;
		
		try {
		BufferedReader in = new BufferedReader(new 
				InputStreamReader(request.getInputStream()));
		
		JAXBContext context = JAXBContext.newInstance("com.mypackage");
		Unmarshaller unmarshaller = context.createUnmarshaller();
        data = unmarshaller.unmarshal(in);   

Thanks for the help...

jaydev

[David Newton]

Is there nothing in the server logs, like a stack trace?

[Bauke Scholtz]

A HTTP 500 error means that there is a serious and unhandled problem in the server side code.

In case of a Java webapplication, this generally means that there's an exception been thrown. If you don't see it (fully) in the error page itself (read the response), you normally can find the complete exception details and the trace back in the appserver's logs. This information should be enough to solve the problem yourself.

[Julien Raynal]

Thanks for the reply. I finally found some hint on Tomcat that indicates a "Premature enf of file" SAXParseException, which allowed me to figure out that when the servlet reads:

   try {
		BufferedReader in = new BufferedReader(new 
				InputStreamReader(request.getInputStream()));
		String inputLine;

	      while ((inputLine = in.readLine()) != null) {
	        System.out.println(inputLine);
	      } 

No data is being read, which means that for some reason, the jaxb object that is supposed to be written to the ouput stream on the client is not written. I am not sure why. Any suggestions would be great. I deugged the jaxb object and I know that it is not null and has data. Am I not writing correctly on the client?

[Bauke Scholtz]

You need to flush and close the outputstream. It's apparently buffered.
If that doesn't help, try invoking URLConnection#getInputStream().