[jira] [Created] (DELTASPIKE-1418) BeanManagerProvider didn't implement the javax.enterprise.inject.spi.Extension interface
THEODOROS CHAIKALIS created DELTASPIKE-1418:
---
Summary: BeanManagerProvider didn't implement the
javax.enterprise.inject.spi.Extension interface
Key: DELTASPIKE-1418
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1418
Project: DeltaSpike
Issue Type: Bug
Security Level: public (Regular issues)
Components: Core
Affects Versions: 1.8.2
Environment: Wildfly 18.1
Deltaspike 1.8.2
Reporter: THEODOROS CHAIKALIS
Iam getting a strange error during deployment:
The scenario is: Iam trying to port the application from Weblogic 12c to
Wildfly 18.1.
The war deploys successfully on WL 12c
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYWELD0021: Service class
org.apache.deltaspike.core.api.provider.BeanManagerProvider didn't implement
the javax.enterprise.inject.spi.Extension interface
FULL ERROR STACK:
{{17:39:06,999 INFO [org.jboss.as.repository] (management-handler-thread - 1)
WFLYDR0001: Content added at location
C:\Wildfly\wildfly-18.0.1.Final\standalone\data\content\ae\a8437df71db3a6747bc93111cc195e59d7355a\content}}
{{17:39:07,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3)
WFLYSRV0027: Starting deployment of "ssp.webservices.process.war"
(runtime-name: "ssp.webservices.process.war")}}
{{17:39:08,786 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
Read persistence.xml for auditPU}}
{{17:39:08,788 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
Read persistence.xml for commonPU}}
{{17:39:08,791 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
Read persistence.xml for processPU}}
{{17:39:08,797 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
Read persistence.xml for registryPU}}
{{17:39:08,800 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
Read persistence.xml for rulesPU}}
{{17:39:09,337 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 83)
WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
'ssp.webservices.process.war#auditPU'}}
{{17:39:09,337 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService
Thread Pool -- 83) HHH000204: Processing PersistenceUnitInfo [}}
{{ name: auditPU}}
{{ ...]}}
{{17:39:09,415 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 95)
WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
'ssp.webservices.process.war#registryPU'}}
{{17:39:09,418 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService
Thread Pool -- 95) HHH000204: Processing PersistenceUnitInfo [}}
{{ name: registryPU}}
{{ ...]}}
{{17:39:09,417 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 96)
WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
'ssp.webservices.process.war#rulesPU'}}
{{17:39:09,429 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService
Thread Pool -- 96) HHH000204: Processing PersistenceUnitInfo [}}
{{ name: rulesPU}}
{{ ...]}}
{{17:39:09,417 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 93)
WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
'ssp.webservices.process.war#processPU'}}
{{17:39:09,438 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService
Thread Pool -- 93) HHH000204: Processing PersistenceUnitInfo [}}
{{ name: processPU}}
{{ ...]}}
{{17:39:09,418 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 94)
WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
'ssp.webservices.process.war#commonPU'}}
{{17:39:09,447 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService
Thread Pool -- 94) HHH000204: Processing PersistenceUnitInfo [}}
{{ name: commonPU}}
{{ ...]}}
{{17:39:09,999 INFO [org.jboss.weld.deployer] (MSC service thread 1-8)
WFLYWELD0003: Processing weld deployment ssp.webservices.process.war}}
{{17:39:10,122 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8)
MSC01: Failed to start service
jboss.deployment.unit."ssp.webservices.process.war".POST_MODULE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."ssp.webservices.process.war".POST_MODULE: WFLYSRV0153:
Failed to process phase POST_MODULE of deployment
"ssp.webservices.process.war"}}
{{ at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)}}
{{ at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)}}
{{ at
org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)}}
{{ at
org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)}}
{{ at
org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)}}
{{ at
org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)}}
{{ at
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[
https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995426#comment-16995426
]
THEODOROS CHAIKALIS commented on DELTASPIKE-1398:
-
Thank you! Do you have any plans in the near future about deploying 1.9.2 to
maven repo?
> Weblogic memory leak
>
>
> Key: DELTASPIKE-1398
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.8.0
>Reporter: THEODOROS CHAIKALIS
>Assignee: Thomas Andraschko
>Priority: Blocker
> Fix For: 1.9.2
>
> Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png,
> mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war,
> server_small.zip
>
>
> This extends previously reported issue 1392
> Iam returning back to a previously reported serious memory leak in Weblogic
> 12.2.1-3.
> To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl)
> are not being garbage collected after application removal.
>
> Steps to reproduce:
>
> # deploy the attached war (server-small)
> # {{open the webpage at /server-small/views/index.xhtml (mleak2)}}
> # monitor the classes created with a profiler (with starting name
> gr.teohaik...) (mleak1)
> # delete the app
> # check again the profiler. The ejbs are still there! (mleak3)
>
> A suggestion in 1392 was to debug BeanManagerProvider, so we did.
> {{but bpmSingleton.bminfos contains 2 objects. but method }}
> {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown)
> }}
> {{is called only once}}
> Attached you can see relevant object contents in the debugger screenshots
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1398) Weblogic memory leak
[
https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992877#comment-16992877
]
THEODOROS CHAIKALIS commented on DELTASPIKE-1398:
-
Can you please consider about resolving this problem?
> Weblogic memory leak
>
>
> Key: DELTASPIKE-1398
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.8.0
>Reporter: THEODOROS CHAIKALIS
>Priority: Blocker
> Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png,
> mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war,
> server_small.zip
>
>
> This extends previously reported issue 1392
> Iam returning back to a previously reported serious memory leak in Weblogic
> 12.2.1-3.
> To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl)
> are not being garbage collected after application removal.
>
> Steps to reproduce:
>
> # deploy the attached war (server-small)
> # {{open the webpage at /server-small/views/index.xhtml (mleak2)}}
> # monitor the classes created with a profiler (with starting name
> gr.teohaik...) (mleak1)
> # delete the app
> # check again the profiler. The ejbs are still there! (mleak3)
>
> A suggestion in 1392 was to debug BeanManagerProvider, so we did.
> {{but bpmSingleton.bminfos contains 2 objects. but method }}
> {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown)
> }}
> {{is called only once}}
> Attached you can see relevant object contents in the debugger screenshots
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (DELTASPIKE-1398) Weblogic memory leak
[
https://issues.apache.org/jira/browse/DELTASPIKE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
THEODOROS CHAIKALIS updated DELTASPIKE-1398:
Priority: Blocker (was: Major)
> Weblogic memory leak
>
>
> Key: DELTASPIKE-1398
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.8.0
>Reporter: THEODOROS CHAIKALIS
>Priority: Blocker
> Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png,
> mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war,
> server_small.zip
>
>
> This extends previously reported issue 1392
> Iam returning back to a previously reported serious memory leak in Weblogic
> 12.2.1-3.
> To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl)
> are not being garbage collected after application removal.
>
> Steps to reproduce:
>
> # deploy the attached war (server-small)
> # {{open the webpage at /server-small/views/index.xhtml (mleak2)}}
> # monitor the classes created with a profiler (with starting name
> gr.teohaik...) (mleak1)
> # delete the app
> # check again the profiler. The ejbs are still there! (mleak3)
>
> A suggestion in 1392 was to debug BeanManagerProvider, so we did.
> {{but bpmSingleton.bminfos contains 2 objects. but method }}
> {{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown)
> }}
> {{is called only once}}
> Attached you can see relevant object contents in the debugger screenshots
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1398) Weblogic memory leak
THEODOROS CHAIKALIS created DELTASPIKE-1398:
---
Summary: Weblogic memory leak
Key: DELTASPIKE-1398
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1398
Project: DeltaSpike
Issue Type: Bug
Security Level: public (Regular issues)
Components: Core
Affects Versions: 1.8.0
Reporter: THEODOROS CHAIKALIS
Attachments: mleak-1.png, mleak-2-leak.png, mleak-2.png,
mleak-debug1.png, mleak-debug2.png, mleak-debug3.png, server_small.war,
server_small.zip
This extends previously reported issue 1392
Iam returning back to a previously reported serious memory leak in Weblogic
12.2.1-3.
To be more precise: EJB helpler classes (EJBName_randomChars_NoIntfViewImpl)
are not being garbage collected after application removal.
Steps to reproduce:
# deploy the attached war (server-small)
# {{open the webpage at /server-small/views/index.xhtml (mleak2)}}
# monitor the classes created with a profiler (with starting name
gr.teohaik...) (mleak1)
# delete the app
# check again the profiler. The ejbs are still there! (mleak3)
A suggestion in 1392 was to debug BeanManagerProvider, so we did.
{{but bpmSingleton.bminfos contains 2 objects. but method }}
{{cleanupStoredBeanManagerOnShutdown(@Observes BeforeShutdown beforeShutdown)
}}
{{is called only once}}
Attached you can see relevant object contents in the debugger screenshots
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1392) Repositories seem to prevent Garbage Collection from Weblogic
[
https://issues.apache.org/jira/browse/DELTASPIKE-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951945#comment-16951945
]
THEODOROS CHAIKALIS commented on DELTASPIKE-1392:
-
Should i do something special about BeanManagerProvider cleanup? It is not
documented in Deltaspike Data webpage
> Repositories seem to prevent Garbage Collection from Weblogic
> -
>
> Key: DELTASPIKE-1392
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1392
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Data-Module
>Affects Versions: 1.8.0
> Environment: Oracle 12c
> Weblogic 12.2.1-3-0
> Java EE 7
> Java SE 8
> Deltaspike 1.8.0
>Reporter: THEODOROS CHAIKALIS
>Priority: Major
> Attachments: Heap_walker_Incoming_References.html,
> Heap_walker_Incoming_References_2.html
>
>
> During my effort to detect possible memory leaks in our application i found a
> strange behavior of Deltaspike regarding the handling of Repositories.
> Specifically, after the *undeployment* and {color:#de350b}*deletion*{color}
> of a Java EE 7 war, Weblogic still holds all references to proxy EJBs that
> created before.
> Attached you will find the Heap dump for an EJB Service where if you trace
> the source you will end up in a
> {{*bmpSingleton* of class
> org.apache.deltaspike.core.api.provider.BeanManagerProvider.}}
>
> Am i missing some critical configuration for Weblogic?
> I already have declared
> {{globalAlternatives.org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.ContainerManagedTransactionStrategy}}
> inside apache-deltaspike.properties.
>
> Thank you
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (DELTASPIKE-1392) Repositories seem to prevent Garbage Collection from Weblogic
[
https://issues.apache.org/jira/browse/DELTASPIKE-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951945#comment-16951945
]
THEODOROS CHAIKALIS edited comment on DELTASPIKE-1392 at 10/15/19 2:02 PM:
---
Should i do something special about BeanManagerProvider cleanup?
was (Author: teohaik):
Should i do something special about BeanManagerProvider cleanup? It is not
documented in Deltaspike Data webpage
> Repositories seem to prevent Garbage Collection from Weblogic
> -
>
> Key: DELTASPIKE-1392
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1392
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Data-Module
>Affects Versions: 1.8.0
> Environment: Oracle 12c
> Weblogic 12.2.1-3-0
> Java EE 7
> Java SE 8
> Deltaspike 1.8.0
>Reporter: THEODOROS CHAIKALIS
>Priority: Major
> Attachments: Heap_walker_Incoming_References.html,
> Heap_walker_Incoming_References_2.html
>
>
> During my effort to detect possible memory leaks in our application i found a
> strange behavior of Deltaspike regarding the handling of Repositories.
> Specifically, after the *undeployment* and {color:#de350b}*deletion*{color}
> of a Java EE 7 war, Weblogic still holds all references to proxy EJBs that
> created before.
> Attached you will find the Heap dump for an EJB Service where if you trace
> the source you will end up in a
> {{*bmpSingleton* of class
> org.apache.deltaspike.core.api.provider.BeanManagerProvider.}}
>
> Am i missing some critical configuration for Weblogic?
> I already have declared
> {{globalAlternatives.org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.ContainerManagedTransactionStrategy}}
> inside apache-deltaspike.properties.
>
> Thank you
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (DELTASPIKE-1392) Repositories seem to prevent Garbage Collection from Weblogic
[
https://issues.apache.org/jira/browse/DELTASPIKE-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
THEODOROS CHAIKALIS updated DELTASPIKE-1392:
Attachment: Heap_walker_Incoming_References_2.html
> Repositories seem to prevent Garbage Collection from Weblogic
> -
>
> Key: DELTASPIKE-1392
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1392
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Data-Module
>Affects Versions: 1.8.0
> Environment: Oracle 12c
> Weblogic 12.2.1-3-0
> Java EE 7
> Java SE 8
> Deltaspike 1.8.0
>Reporter: THEODOROS CHAIKALIS
>Priority: Major
> Attachments: Heap_walker_Incoming_References.html,
> Heap_walker_Incoming_References_2.html
>
>
> During my effort to detect possible memory leaks in our application i found a
> strange behavior of Deltaspike regarding the handling of Repositories.
> Specifically, after the *undeployment* and {color:#de350b}*deletion*{color}
> of a Java EE 7 war, Weblogic still holds all references to proxy EJBs that
> created before.
> Attached you will find the Heap dump for an EJB Service where if you trace
> the source you will end up in a
> {{*bmpSingleton* of class
> org.apache.deltaspike.core.api.provider.BeanManagerProvider.}}
>
> Am i missing some critical configuration for Weblogic?
> I already have declared
> {{globalAlternatives.org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.ContainerManagedTransactionStrategy}}
> inside apache-deltaspike.properties.
>
> Thank you
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1392) Repositories seem to prevent Garbage Collection from Weblogic
THEODOROS CHAIKALIS created DELTASPIKE-1392:
---
Summary: Repositories seem to prevent Garbage Collection from
Weblogic
Key: DELTASPIKE-1392
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1392
Project: DeltaSpike
Issue Type: Bug
Security Level: public (Regular issues)
Components: Data-Module
Affects Versions: 1.8.0
Environment: Oracle 12c
Weblogic 12.2.1-3-0
Java EE 7
Java SE 8
Deltaspike 1.8.0
Reporter: THEODOROS CHAIKALIS
Attachments: Heap_walker_Incoming_References.html
During my effort to detect possible memory leaks in our application i found a
strange behavior of Deltaspike regarding the handling of Repositories.
Specifically, after the *undeployment* and {color:#de350b}*deletion*{color} of
a Java EE 7 war, Weblogic still holds all references to proxy EJBs that created
before.
Attached you will find the Heap dump for an EJB Service where if you trace the
source you will end up in a
{{*bmpSingleton* of class
org.apache.deltaspike.core.api.provider.BeanManagerProvider.}}
Am i missing some critical configuration for Weblogic?
I already have declared
{{globalAlternatives.org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.ContainerManagedTransactionStrategy}}
inside apache-deltaspike.properties.
Thank you
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646135#comment-16646135 ] THEODOROS CHAIKALIS commented on DELTASPIKE-1354: - Yes we are expecting a response from Oracle. Please close it > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 1.8.0_172 >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want to populate db with > data run the Arquillian test in TestA class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a REST call from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > Note: in order for the example to run properly, please remove the "Provided" > scopes from the respective dependencies > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THEODOROS CHAIKALIS updated DELTASPIKE-1354: Description: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want to populate db with data run the Arquillian test in TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a REST call from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] Note: in order for the example to run properly, please remove the "Provided" scopes. was: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want to populate db with data run the Arquillian test in TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a REST call from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 1.8.0_172 >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > Attachments: EnterpriseWebApp.zip > > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want to populate db with > data run the Arquillian test in TestA class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a REST call from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > Note: in order for the example to run properly, please remove the "Provided" > scopes. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THEODOROS CHAIKALIS updated DELTASPIKE-1354: Description: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want to populate db with data run the Arquillian test in TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a REST call from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] Note: in order for the example to run properly, please remove the "Provided" scopes from the respective dependencies was: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want to populate db with data run the Arquillian test in TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a REST call from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] Note: in order for the example to run properly, please remove the "Provided" scopes. > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 1.8.0_172 >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > Attachments: EnterpriseWebApp.zip > > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want to populate db with > data run the Arquillian test in TestA class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a REST call from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > Note: in order for the example to run properly, please remove the "Provided" > scopes from the respective dependencies > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THEODOROS CHAIKALIS updated DELTASPIKE-1354: Environment: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 1.8.0_172 (was: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 8_1) > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 1.8.0_172 >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > Attachments: EnterpriseWebApp.zip > > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want to populate db with > data run the Arquillian test in TestA class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a REST call from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THEODOROS CHAIKALIS updated DELTASPIKE-1354: Environment: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 8_1 (was: Windows 10, Weblogic 12.2.1.3, ) > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, Java EE7, JDK 8_1 >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > Attachments: EnterpriseWebApp.zip > > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want to populate db with > data run the Arquillian test in TestA class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a REST call from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THEODOROS CHAIKALIS updated DELTASPIKE-1354: Description: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want to populate db with data run the Arquillian test in TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a REST call from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] was: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want to populate db with data run the Arquillian test in TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a rest from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > Attachments: EnterpriseWebApp.zip > > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want to populate db with > data run the Arquillian test in TestA class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a REST call from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THEODOROS CHAIKALIS updated DELTASPIKE-1354: Description: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want to populate db with data run the Arquillian test in TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a rest from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] was: I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want Data run the TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a rest from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > Attachments: EnterpriseWebApp.zip > > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want to populate db with > data run the Arquillian test in TestA class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a rest from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DELTASPIKE-1354) CDI producer does not work correctly after application restart on weblogic 12c
THEODOROS CHAIKALIS created DELTASPIKE-1354: --- Summary: CDI producer does not work correctly after application restart on weblogic 12c Key: DELTASPIKE-1354 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 Project: DeltaSpike Issue Type: Bug Components: CdiControl, Data-Module Affects Versions: 1.8.0 Environment: Windows 10, Weblogic 12.2.1.3, Reporter: THEODOROS CHAIKALIS Attachments: EnterpriseWebApp.zip I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. Attached you will find a mini application that demonstrates the problem, please use it. The scenario to reproduce the problem is as follows: 1. Deploy the application on Weblogic. 2. Run a REST service that uses a Deltaspike repository: [http://localhost:7001/ssp.sandbox/persons/all] or [http://localhost:7001/ssp.sandbox/persons/byId/1] 3. Observe that the request runs smoothly. If you want Data run the TestA class 4. from the weblogic console, stop the application 5. Start the application 6. run again a rest from step 2. The following will happen: [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DELTASPIKE-1354) CDI producer does not work properly after application restart on weblogic 12c
[ https://issues.apache.org/jira/browse/DELTASPIKE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THEODOROS CHAIKALIS updated DELTASPIKE-1354: Summary: CDI producer does not work properly after application restart on weblogic 12c (was: CDI producer does not work correctly after application restart on weblogic 12c) > CDI producer does not work properly after application restart on weblogic 12c > - > > Key: DELTASPIKE-1354 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1354 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl, Data-Module >Affects Versions: 1.8.0 > Environment: Windows 10, Weblogic 12.2.1.3, >Reporter: THEODOROS CHAIKALIS >Priority: Major > Labels: cdi, entitymanager, producer, repository > Attachments: EnterpriseWebApp.zip > > > I have an application using Deltaspike 1.8.0 that runs on Weblogic 12.2.1.3. > Attached you will find a mini application that demonstrates the problem, > please use it. > The scenario to reproduce the problem is as follows: > 1. Deploy the application on Weblogic. > 2. Run a REST service that uses a Deltaspike repository: > [http://localhost:7001/ssp.sandbox/persons/all] > or > [http://localhost:7001/ssp.sandbox/persons/byId/1] > 3. Observe that the request runs smoothly. If you want Data run the TestA > class > 4. from the weblogic console, stop the application > 5. Start the application > 6. run again a rest from step 2. The following will happen: > > [https://gist.github.com/teohaik/933d4bc47d38c4441ca9a7409bc90eee] > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
