[JBoss JIRA] (WFLY-11866) Cannot get exception as pass-by-reference
by Wolf-Dieter Fink (Jira)
Wolf-Dieter Fink created WFLY-11866:
---------------------------------------
Summary: Cannot get exception as pass-by-reference
Key: WFLY-11866
URL: https://issues.jboss.org/browse/WFLY-11866
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 16.0.0.Final, 17.0.0.Beta1
Reporter: Wolf-Dieter Fink
Despite of <in-vm-remote-interface-invocation pass-by-value="false"/>, an exception is not thrown by reference, which results in java.io.NotSerializableException if the exception doesn't implement Serializable. This is a blocker of a large migration project from WebLogic because it throws by reference even if that doesn't implement Serializable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (JBMETA-416) Make JBoss Medata available in Maven Central
by David Hladky (Jira)
[ https://issues.jboss.org/browse/JBMETA-416?page=com.atlassian.jira.plugin... ]
David Hladky resolved JBMETA-416.
---------------------------------
Resolution: Done
The artifacts are now searchable in Maven Central including the parent artifacts.
> Make JBoss Medata available in Maven Central
> --------------------------------------------
>
> Key: JBMETA-416
> URL: https://issues.jboss.org/browse/JBMETA-416
> Project: JBoss Metadata
> Issue Type: Task
> Reporter: Sanne Grinovero
> Assignee: David Hladky
> Priority: Major
>
> Hello,
> we're using {{jboss-metadata-web}} in Quarkus, and we'd really appreciate if our users could build applications without having to setup their Maven configuration to find dependencies in JBoss Nexus.
> Could someone please take care that releases get synched to Maven Central ?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by SHREYAS HOLLA P (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
SHREYAS HOLLA P updated WFLY-11865:
-----------------------------------
Description:
We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
This happens when we add "<add-logging-api-dependencies value="false"/>".
WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
2 Spring WebApplicationInitializers detected on classpath
was:
We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
2 Spring WebApplicationInitializers detected on classpath
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Chao Wang
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> This happens when we add "<add-logging-api-dependencies value="false"/>".
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by SHREYAS HOLLA P (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
SHREYAS HOLLA P edited comment on WFLY-11865 at 3/19/19 3:01 AM:
-----------------------------------------------------------------
Hi The WAR is more than 30MB so it did not get uploaded. Please find the same here, https://drive.google.com/file/d/18-xzsdwF07qwMnzCEfCAJA4Avu9Jh-ur/view?us...
and add <add-logging-api-dependencies value="false"/> in standalone.xml
was (Author: shreyas.holla):
Hi The WAR is more than 30MB so it did not get uploaded. Please find the same here, https://drive.google.com/file/d/18-xzsdwF07qwMnzCEfCAJA4Avu9Jh-ur/view?us...
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Chao Wang
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3773) [DMN Designer] Improve the Data Types support (7.4)
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3773:
-----------------------------------
Summary: [DMN Designer] Improve the Data Types support (7.4)
Key: DROOLS-3773
URL: https://issues.jboss.org/browse/DROOLS-3773
Project: Drools
Issue Type: Epic
Components: DMN Editor
Reporter: Jozef Marko
Assignee: Guilherme Carreiro
As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
Verification conditions:
Support added for the User to define data-types (ItemDefinition).
This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-2726) Drools core doesn't run on AWS lambda
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-2726?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet reassigned DROOLS-2726:
----------------------------------------
Component/s: core engine
Assignee: Mario Fusco (was: Geoffrey De Smet)
> Drools core doesn't run on AWS lambda
> -------------------------------------
>
> Key: DROOLS-2726
> URL: https://issues.jboss.org/browse/DROOLS-2726
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 7.7.0.Final
> Reporter: Adeela Huma
> Assignee: Mario Fusco
> Priority: Major
>
> When running drools on AWS lambda they get this exception apparently:
> {code}
> java.lang.ExceptionInInitializerError:
> java.lang.ExceptionInInitializerError
> java.lang.ExceptionInInitializerError
> at org.kie.api.internal.utils.ServiceRegistry.getInstance(ServiceRegistry.java:27)
> ...
> Caused by: java.lang.RuntimeException: Child services [org.kie.api.internal.assembler.KieAssemblers] have no parent
> at org.kie.api.internal.utils.ServiceDiscoveryImpl.buildMap(ServiceDiscoveryImpl.java:191)
> at org.kie.api.internal.utils.ServiceDiscoveryImpl.getServices(ServiceDiscoveryImpl.java:97)
> ...
> {code}
> Reporting the bug from stack overflow discussion:
> https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by SHREYAS HOLLA P (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
SHREYAS HOLLA P commented on WFLY-11865:
----------------------------------------
Hi The WAR is more than 30MB so it did not get uploaded. Please find the same here, https://drive.google.com/file/d/18-xzsdwF07qwMnzCEfCAJA4Avu9Jh-ur/view?us...
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Reporter: SHREYAS HOLLA P
> Assignee: Chao Wang
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-2726) Drools core doesn't run on AWS lambda
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-2726?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-2726:
-------------------------------------
Description:
When running drools on AWS lambda they get this exception apparently:
{code}
java.lang.ExceptionInInitializerError:
java.lang.ExceptionInInitializerError
java.lang.ExceptionInInitializerError
at org.kie.api.internal.utils.ServiceRegistry.getInstance(ServiceRegistry.java:27)
...
Caused by: java.lang.RuntimeException: Child services [org.kie.api.internal.assembler.KieAssemblers] have no parent
at org.kie.api.internal.utils.ServiceDiscoveryImpl.buildMap(ServiceDiscoveryImpl.java:191)
at org.kie.api.internal.utils.ServiceDiscoveryImpl.getServices(ServiceDiscoveryImpl.java:97)
...
{code}
Reporting the bug from stack overflow discussion:
https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda
was:
Reporting the bug from stack overflow discussion:
https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda
> Drools core doesn't run on AWS lambda
> -------------------------------------
>
> Key: DROOLS-2726
> URL: https://issues.jboss.org/browse/DROOLS-2726
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 7.7.0.Final
> Reporter: Adeela Huma
> Assignee: Geoffrey De Smet
> Priority: Major
>
> When running drools on AWS lambda they get this exception apparently:
> {code}
> java.lang.ExceptionInInitializerError:
> java.lang.ExceptionInInitializerError
> java.lang.ExceptionInInitializerError
> at org.kie.api.internal.utils.ServiceRegistry.getInstance(ServiceRegistry.java:27)
> ...
> Caused by: java.lang.RuntimeException: Child services [org.kie.api.internal.assembler.KieAssemblers] have no parent
> at org.kie.api.internal.utils.ServiceDiscoveryImpl.buildMap(ServiceDiscoveryImpl.java:191)
> at org.kie.api.internal.utils.ServiceDiscoveryImpl.getServices(ServiceDiscoveryImpl.java:97)
> ...
> {code}
> Reporting the bug from stack overflow discussion:
> https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months