[JBoss JIRA] (WFLY-11857) Multi JSF Installer error in deployment
by Erick de Oliveira Leal (Jira)
[ https://issues.jboss.org/browse/WFLY-11857?page=com.atlassian.jira.plugin... ]
Erick de Oliveira Leal updated WFLY-11857:
------------------------------------------
Description:
Using Windows 10.
I used mvn -Djsf-version=2.3.3-Pmyfaces clean assembly:single to generate cli script, ok.
Tried to deploy it with the following command:
deploy C:\wildfly-16.0.0.Final\bin\install-myfaces-2.3.3.cli
Got:
org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate C:\Users\Administrador\AppData\Local\Temp\vfs\cli-1552682962092\cli-1552682962092c7cc554a5d9bf7e0\install-myfaces-2.3.3.cli-a80aafee764c05cb\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
was:
Using Windows 10.
I used mvn -Djsf-version=2.3.1 -Pmyfaces clean assembly:single to generate cli script, ok.
Tried to deploy it with the following command:
deploy C:\wildfly-16.0.0.Final\bin\install-myfaces-2.3.3.cli
Got:
org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate C:\Users\Administrador\AppData\Local\Temp\vfs\cli-1552682962092\cli-1552682962092c7cc554a5d9bf7e0\install-myfaces-2.3.3.cli-a80aafee764c05cb\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
> Multi JSF Installer error in deployment
> ---------------------------------------
>
> Key: WFLY-11857
> URL: https://issues.jboss.org/browse/WFLY-11857
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 16.0.0.Final
> Reporter: Erick de Oliveira Leal
> Assignee: Farah Juma
> Priority: Major
>
> Using Windows 10.
> I used mvn -Djsf-version=2.3.3-Pmyfaces clean assembly:single to generate cli script, ok.
> Tried to deploy it with the following command:
> deploy C:\wildfly-16.0.0.Final\bin\install-myfaces-2.3.3.cli
> Got:
> org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate C:\Users\Administrador\AppData\Local\Temp\vfs\cli-1552682962092\cli-1552682962092c7cc554a5d9bf7e0\install-myfaces-2.3.3.cli-a80aafee764c05cb\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup
by Rakesh K. Cherukuri (Jira)
[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ]
Rakesh K. Cherukuri updated WFLY-11858:
---------------------------------------
Description:
We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) with following error
_WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
In our application, a bootstrap servlet startup services (Stateless EJBs) during server startup. During this process the server gives up with above error.
Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in.
was:
We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) with following error
_WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
In our application, a bootstrap servlet startup services (Stateless EJBs) during server startup. During this process the server gives up with above error.
Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
> [Wildfly16] CDI fails to inject InitialContext during startup
> -------------------------------------------------------------
>
> Key: WFLY-11858
> URL: https://issues.jboss.org/browse/WFLY-11858
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 16.0.0.Final
> Reporter: Rakesh K. Cherukuri
> Assignee: Matej Novotny
> Priority: Blocker
> Attachments: stacktrace.log
>
>
> We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) with following error
> _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
> In our application, a bootstrap servlet startup services (Stateless EJBs) during server startup. During this process the server gives up with above error.
> Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
> Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
> Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup
by Rakesh K. Cherukuri (Jira)
[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ]
Rakesh K. Cherukuri updated WFLY-11858:
---------------------------------------
Description:
We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) with following error
_WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
In our application, a bootstrap servlet startup services (Stateless EJBs) during server startup. During this process the server gives up with above error.
Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
was:
We are in the process of upgrading from 14.0.1.Final. In our application, a bootstrap servlet startup services (Stateless EJBs) during server startup.
While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) with following error
_WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
> [Wildfly16] CDI fails to inject InitialContext during startup
> -------------------------------------------------------------
>
> Key: WFLY-11858
> URL: https://issues.jboss.org/browse/WFLY-11858
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 16.0.0.Final
> Reporter: Rakesh K. Cherukuri
> Assignee: Matej Novotny
> Priority: Blocker
> Attachments: stacktrace.log
>
>
> We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) with following error
> _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
> In our application, a bootstrap servlet startup services (Stateless EJBs) during server startup. During this process the server gives up with above error.
> Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
> Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup
by Rakesh K. Cherukuri (Jira)
Rakesh K. Cherukuri created WFLY-11858:
------------------------------------------
Summary: [Wildfly16] CDI fails to inject InitialContext during startup
Key: WFLY-11858
URL: https://issues.jboss.org/browse/WFLY-11858
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 16.0.0.Final
Reporter: Rakesh K. Cherukuri
Assignee: Matej Novotny
Attachments: stacktrace.log
We are in the process of upgrading from 14.0.1.Final. In our application, a bootstrap servlet startup services (Stateless EJBs) during server startup.
While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) with following error
_WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11832) Transaction for Hibernate Interceptor is null
by Gail Badner (Jira)
[ https://issues.jboss.org/browse/WFLY-11832?page=com.atlassian.jira.plugin... ]
Gail Badner commented on WFLY-11832:
------------------------------------
[~smarlow], I've confirmed that making the following change seems to fix it:
diff --git a/hibernate-core/src/main/java/org/hibernate/internal/SessionImpl.java b/hibernate-core/src/main/java/org/hibernate/internal/SessionImpl.java
index 9a5b59b601..5c62098e32 100644
--- a/hibernate-core/src/main/java/org/hibernate/internal/SessionImpl.java
+++ b/hibernate-core/src/main/java/org/hibernate/internal/SessionImpl.java
@@ -2506,7 +2506,7 @@ public final class SessionImpl
}
try {
- getInterceptor().afterTransactionCompletion( getCurrentTransaction() );
+ getInterceptor().afterTransactionCompletion( accessTransaction() );
}
catch (Throwable t) {
log.exceptionInAfterTransactionCompletionInterceptor( t );
I'm not sure if this is a proper fix though.
[~mchur], please do open a Hibernate issue.
> Transaction for Hibernate Interceptor is null
> ---------------------------------------------
>
> Key: WFLY-11832
> URL: https://issues.jboss.org/browse/WFLY-11832
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Transactions
> Affects Versions: 14.0.0.Final, 15.0.1.Final, 16.0.0.Final
> Reporter: Markus Chur
> Assignee: Scott Marlow
> Priority: Major
> Attachments: hibernate-interceptor-reproducer-0.0.1-SNAPSHOT.jar, src -WFLY-11832.zip
>
>
> With Wildfly 13 - javaee7 transactions in hibernate interceptors were never null.
> Since Wildfly 14 - javaee8 transactions in hibernate interceptors are always null.
> Attached sources and a jar of a minimal reproducer for Wildfly 16. This is reproducible by using a fresh unchanged Wildfly 16 and unchanged standalone.xml. Extract Wildfly 16, drop in the jar in the deployments folder and start the server.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11857) Multi JSF Installer error in deployment
by Erick de Oliveira Leal (Jira)
[ https://issues.jboss.org/browse/WFLY-11857?page=com.atlassian.jira.plugin... ]
Erick de Oliveira Leal updated WFLY-11857:
------------------------------------------
Description:
Using Windows 10.
I used mvn -Djsf-version=2.3.1 -Pmyfaces clean assembly:single to generate cli script, ok.
Tried to deploy it with the following command:
deploy C:\wildfly-16.0.0.Final\bin\install-myfaces-2.3.3.cli
Got:
org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate C:\Users\Administrador\AppData\Local\Temp\vfs\cli-1552682962092\cli-1552682962092c7cc554a5d9bf7e0\install-myfaces-2.3.3.cli-a80aafee764c05cb\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
was:
I used mvn -Djsf-version=2.3.1 -Pmyfaces clean assembly:single to generate cli script, ok.
Tried to deploy it with the following command:
deploy C:\wildfly-16.0.0.Final\bin\install-myfaces-2.3.3.cli
Got:
org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate C:\Users\Administrador\AppData\Local\Temp\vfs\cli-1552682962092\cli-1552682962092c7cc554a5d9bf7e0\install-myfaces-2.3.3.cli-a80aafee764c05cb\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
> Multi JSF Installer error in deployment
> ---------------------------------------
>
> Key: WFLY-11857
> URL: https://issues.jboss.org/browse/WFLY-11857
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 16.0.0.Final
> Reporter: Erick de Oliveira Leal
> Assignee: Farah Juma
> Priority: Major
>
> Using Windows 10.
> I used mvn -Djsf-version=2.3.1 -Pmyfaces clean assembly:single to generate cli script, ok.
> Tried to deploy it with the following command:
> deploy C:\wildfly-16.0.0.Final\bin\install-myfaces-2.3.3.cli
> Got:
> org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate C:\Users\Administrador\AppData\Local\Temp\vfs\cli-1552682962092\cli-1552682962092c7cc554a5d9bf7e0\install-myfaces-2.3.3.cli-a80aafee764c05cb\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11857) Multi JSF Installer error in deployment
by Erick de Oliveira Leal (Jira)
Erick de Oliveira Leal created WFLY-11857:
---------------------------------------------
Summary: Multi JSF Installer error in deployment
Key: WFLY-11857
URL: https://issues.jboss.org/browse/WFLY-11857
Project: WildFly
Issue Type: Bug
Components: JSF
Affects Versions: 16.0.0.Final
Reporter: Erick de Oliveira Leal
Assignee: Farah Juma
I used mvn -Djsf-version=2.3.1 -Pmyfaces clean assembly:single to generate cli script, ok.
Tried to deploy it with the following command:
deploy C:\wildfly-16.0.0.Final\bin\install-myfaces-2.3.3.cli
Got:
org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate C:\Users\Administrador\AppData\Local\Temp\vfs\cli-1552682962092\cli-1552682962092c7cc554a5d9bf7e0\install-myfaces-2.3.3.cli-a80aafee764c05cb\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Liz Clayton closed DROOLS-3731.
-------------------------------
Resolution: Duplicate Issue
[~tirelli] The overlay is already covered by this jira: https://issues.jboss.org/browse/DROOLS-3674. If you need anything else though please let me know and I'll open a new jira. Thanks.
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3731:
-------------------------------------
[~manstis] Sounds good, I'll close this one as a duplicate. Thanks!
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months