基于 REST 的简单程序中的 HTTP 500 内部服务器错误.从服务器接收/发送响应时对 GET 和 POST 感到困惑

2022-01-21 00:00:00 rest java glassfish jersey

我是第一次使用 REST 服务实现一个基本的客户端服务器架构.这一次，我通过在客户端和服务器之间共享类对象作为参数来包含更多类和服务，从而使其变得更加复杂.我在 ApacheTomcat7 上运行服务器.它正在成功执行.当我运行我的客户端时，它给了我错误:javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error 我尝试调试我的代码，似乎我没有正确接收/发送响应.我知道在这里分享所有课程并不明智，但我别无选择，因为它浪费了我很多时间.任何帮助将不胜感激.提前致谢.

I am implementing a basic client server architecture using REST services for the first time. This time I making it more complicated with including some more classes and services with sharing class objects as parameters between client and server. I am running server on ApacheTomcat7. It is getting executed successfully. When I am running my client it is giving me error: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error I tried debugging my code, it seems like I am not properly receiving/sending response. I know its not wise idea to share all classes here but I has no choice since it has wasted my time a lot. Any help will be appreciated. Thanks in advance.

以下是我的 ImageProgress 课程.此类在服务器和客户端都存在.

Following is my ImageProgress class. This class is present at both server and client.

@XmlRootElement
public class ImageProgress{
    private String name;

    public ImageProgress( String image_name){
        this.name = image_name;
    }

    public String getName() {
        return name;
    }

    public void setName( String name ){
        this.name = name;
    }
}

HPCResponse 是类，其对象将作为服务器响应返回给客户端.HPCResponse 基本上会返回 ImageProgress 对象，它会给我预期的结果.

HPCResponse is the class whose object will be returned to client as the server response. HPCResponse will basically return the ImageProgress object which will give me the intended result.

@XmlRootElement
public class HPCResponse
{
    private ImageProgress imgProgress;

    public ImageProgress getImgProgress() {
        return imgProgress;
    }

    public void setImgProgress(ImageProgress imgProgress) {
        this.imgProgress = imgProgress;
    }
}

以下是来自名为 HpcService 的服务器的服务类，它将返回 HPCResponse 的对象作为响应.如您所见，startAnalysing 方法接受 HPCInfo 对象.下面还给出了HPCInfo的描述.

Following is the service class from server named HpcService which will return the HPCResponse's object as response. As you can see the method startAnalysing accepts object of HPCInfo. Description of HPCInfo is also given below.

@Path( "/hpc" )
@Consumes( MediaType.APPLICATION_XML )
@Produces( MediaType.APPLICATION_XML )
public class HpcService{

    public HPCInfo hpcInfo;
    public HPCResponse hpcResponse;

    @POST
    @Path( "/analyze" )
    public HPCResponse startAnalysing(HPCInfo _hpcInfo){

        System.out.println( "Started Analyzing..." );

        hpcInfo = _hpcInfo;
        hpcInfo.getImagePath();        

        hpcResponse = new HPCResponse();
        ImageProgress iProg = new ImageProgress(hpcInfo.getImagePath());
        hpcResponse.setImgProgress(iProg);

        System.out.println("Returning response...");
        return hpcResponse;
    }
}

HPCInfo 类也在客户端和服务器端.HPCInfo 类:

HPCInfo class is also at both client and server. HPCInfo class:

    @XmlRootElement
    public class HPCInfo
    {
        private String imagePath = "";

        public String getImagePath(){
            return imagePath;
        }

        public void setImagePath( String imagePath ){
            this.imagePath = imagePath;
        }
    }

最后是我的客户调用 HPCService.

And finally its my client calling for the HPCService.

public class TestClient {
    private static String webServiceURI = "http://localhost:8080/TestServer123";
    public static void main(String[] args) {
        String input = "ABNKidney.scn";
        ClientConfig clientConfig = new ClientConfig();
        Client client = ClientBuilder.newClient(clientConfig);
        URI serviceURI = UriBuilder.fromUri(webServiceURI).build();

        WebTarget webTarget = client.target(serviceURI);

        HPCInfo info = new HPCInfo();
        info.setImagePath(input);

        webTarget = webTarget.path("test").path("hpc").path("analyze");

        HPCResponse hResponse = webTarget.request().accept(MediaType.APPLICATION_XML).post(Entity.entity(info, MediaType.APPLICATION_XML), HPCResponse.class);
    }
}

这是我得到的完整错误描述:

This is the full error description I am getting:

javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
    at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:968)
    at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:795)
    at org.glassfish.jersey.client.JerseyInvocation.access$500(JerseyInvocation.java:91)
    at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:683)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
    at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:424)
    at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:679)
    at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:435)
    at org.glassfish.jersey.client.JerseyInvocation$Builder.post(JerseyInvocation.java:338)
    at com.TestClient.main(TestClient.java:34)

推荐答案

像这样调试的一种方法是创建一个简单的 ExceptionMapper 来捕获未映射的异常.当没有映射器时，异常通常会冒泡到容器级别，这只会给我们提供一般的 500 服务器错误(大多数情况下没有什么帮助).

One way to debug things like this is to create a simple ExceptionMapper to catch exceptions that are not mapped. When there is no mapper, often the exception will bubble up to the container level, which just gives us generic 500 server error (which most of the time is of little help).

@Provider
public class DebugExceptionMapper implements ExceptionMapper<Exception> {

    @Override
    public Response toResponse(Exception exception) {
        exception.printStackTrace();
        return Response.serverError().entity(exception.getMessage()).build();
    } 
}

然后只需注册映射器.使用 ImageProgress 类运行简单测试时，抛出异常时，会打印堆栈跟踪，您可以看到异常消息

Then just register the mapper. When running a simple test with your ImageProgress class, when the exception is thrown, the stacktrace gets printed, and you can see the exception message

...ImageProgress 没有无参数默认构造函数

...ImageProgress does not have a no-arg default constructor

所以只需向 ImageProgress 类添加一个默认(无参数构造函数).这是 JAXB 模型的要求.

So just add a default (no-arg constructor) to the ImageProgress class. This is a requirement with JAXB models.

相关文章