[JBoss JIRA] (WFLY-11565) WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204
1:53 a.m.
[
https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin...
]
Deepak Sahu commented on WFLY-11565:
------------------------------------
I had already tried that, but I get a deployment error when I try to deploy my war file in
WildFly 15.0.0 Final.
Please find the error below:
13:08:38,196 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 76)
HHH000206: hibernate.properties not found
13:08:38,425 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 77)
WFLYCLINF0002: Started client-mappings cache from ejb container
13:08:39,790 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool
-- 76) HCANN000001: Hibernate Commons Annotations {5.0.4.Final}
13:08:40,381 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 76)
HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
13:08:40,447 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 76)
HHH000431: Unable to determine H2 database version, certain features may not work
13:08:40,625 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService
Thread Pool -- 76) Envers integration enabled? : true
13:08:41,742 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 76)
MSC000001: Failed to start service
jboss.persistenceunit."VHQRest-3.11.27.06.war#dbPersistence":
org.jboss.msc.service
.StartException in service
jboss.persistenceunit."VHQRest-3.11.27.06.war#dbPersistence":
java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to
org.dom4j.DocumentFactory
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
at
org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
at
org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at
org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to
org.dom4j.DocumentFactory
at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:92)
at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:33)
at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:27)
at
org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.workWithClassLoader(ClassLoaderServiceImpl.java:483)
at org.hibernate.internal.util.xml.XMLHelper.<init>(XMLHelper.java:26)
at
org.hibernate.envers.boot.internal.EnversServiceImpl.initialize(EnversServiceImpl.java:116)
at
org.hibernate.envers.boot.internal.AdditionalJaxbMappingProducerImpl.produceAdditionalMappings(AdditionalJaxbMappingProducerImpl.java:101)
at
org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:297)
at
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:904)
at
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:935)
at
org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:141)
at
org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:67)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:356)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$1300(PersistenceUnitServiceImpl.java:71)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:190)
... 9 more
I already tried adding jboss-deployment-structure.xml in the path
..\wildfly-15.0.0.Final\modules\system\layers\base\org\jboss\as\product\wildfly-full\dir\META-INF,
but it did not help.
Then I stopped my process of deployment in WildFly 15 final as I thought, I am deviating
from the actual issue which I am facing.
Let me know if you need any other information.
WildFly Server Adds Transfer Encoding Chunk Header to the
HttpResponse with status code 204
-------------------------------------------------------------------------------------------
Key: WFLY-11565
URL: https://issues.jboss.org/browse/WFLY-11565
Project: WildFly
Issue Type: Bug
Affects Versions: 9.0.0.Final
Reporter: Deepak Sahu
Assignee: Jason Greene
Priority: Major
I am using WildFly Server 9.0.0 Final, Javax ws, Jersey for developing Rest APIs. For all
the responses whose httpStatus code is 204, the wildfly server adds Transfer encoding
Chunked in the response header, which is not correct as per the Rest Standards. Because of
this behavior some of the RestAPI clients hang, as they keep waiting for the response
(which is not at all there).
To verify the issue, I tried the same with Springboot instead of deploying the war in
WildFly and the Response Header was not added with Transfer Encoding Chuncked.
Let me know if some other information is required to fix this issue, if this is already
fixed is there any patch for this issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
2130
days inactive
2130
days old
0 comments
1 participants
participants (1)
-
Deepak Sahu (Jira)