在json响应中设置对象间歇性返回

如何解决在json响应中设置对象间歇性返回

我有一个特殊的问题，即在json响应中的set对象中，对于相同的请求并不总是出现。

下面是json响应类

public class EmployeeEntity implements Serializable {

    
    /** The id. */
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    @Column(name = "id")
    private Long  employeeEntityId;

    /** The name. */
    @Column(name = "name",length = 45,unique=true)
    private String employeeName;

    /** The description. */
    @Column(name = "instruction",columnDefinition = "mediumtext")
    private String description;

    /** The employee permissions. */
    @ManyToMany(fetch = FetchType.LAZY)
    @Fetch(FetchMode.JOIN)
    @JoinTable(name = "employee_has_permissions",joinColumns = {
            @JoinColumn(name = "employee_id",referencedColumnName = "id") },inverseJoinColumns = {
                    @JoinColumn(name = "employee_permissions_id",referencedColumnName = "id") })
    private Set<EmployeePermissionEntity> employeePermissions;
    
    //setters and getters
    }

在本地环境中，此方法非常正常。但是在开发环境中，对于具有雇员权限的同一请求，响应中不会间歇性地显示雇员权限。我无法弄清楚这里出了什么问题。您能在这里帮我吗？

编辑：我在zuul网关中遇到此问题。经过进一步分析，我发现每当缺少标签时，调用都不会到达应用程序。这是否意味着网关正在部分缓存响应？如果是这样，如何防止这种情况或使其完全响应。

这是响应构造代码。

        HttpServletResponse response; //received as method parameter
        response.setContentType("application/json");
        response.setCharacterEncoding("UTF-8");

        if (LOGGER.isInfoEnabled()) {
            LOGGER.info("Construct resposne : ");
        }
    
        final EmpResponseModel empResponse = new EmpResponseModel(firstName,lastName,token,id,employeeEntity.employeePermissions());
        final ResponseModel responseModel = new ResponseModel(OK,"Operation completeted successfully.",null,new ResponseModel<EmpResponseModel>(empResponse));
        try (OutputStream out = response.getOutputStream()) {
            final ObjectMapper mapper = new ObjectMapper();
            mapper.setSerializationInclusion(Include.NON_NULL);
            //mapper.setVisibility(PropertyAccessor.ALL,JsonAutoDetect.Visibility.ANY);
            mapper.writeValue(out,responseModel);
            out.flush();
        } catch (Exception exception) {
            if (LOGGER.isInfoEnabled()) {
                LOGGER.info("Exception while writing response : " + exception);
            }
        }