May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4029) Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4029?page=com.atlassian.jira.plugi... ] Edoardo Vacchi resolved DROOLS-4029. ------------------------------------ Resolution: Done merged in Quarkus master > Quarkus Extension: Simplify file watch routine to account for DRL, BPMN files compiler > -------------------------------------------------------------------------------------- > > Key: DROOLS-4029 > URL: https://issues.jboss.org/browse/DROOLS-4029 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > Quarkus core hot code reload is assuming that the compiled class file for "Foo.ext" is always "Foo.class", whatever is the ext, whatever the contents. > This is false for DRL, BPMN but it is also false for java. Consider the case: > {code} > /* package-private */ class Blah {} > {code} > which always generates {{{Blah.class}} regardless of the java file name. > see https://github.com/quarkusio/quarkus/issues/2371 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[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: ---------------------------------------- [~soul2zimate], When this issue will be actioned? > 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 > Components: Logging > Reporter: Shreyas Holla p > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12094) Undertow doesn't extract request parameters if PUT method is being called

by Lin Gao (Jira)

[ https://issues.jboss.org/browse/WFLY-12094?page=com.atlassian.jira.plugin... ] Lin Gao moved JBEAP-16928 to WFLY-12094: ---------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12094 (was: JBEAP-16928) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Affects Version/s: (was: 7.2.1.GA) > Undertow doesn't extract request parameters if PUT method is being called > ------------------------------------------------------------------------- > > Key: WFLY-12094 > URL: https://issues.jboss.org/browse/WFLY-12094 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Lin Gao > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > If PUT method is being used, we cannot extract request parameters/values in Undertow using these methods below: > ---------------------------------------- > > + getParameterNames > > + getParameterValues > > + getParameterMap > ---------------------------------------- > Similar bug was fixed via [UNDERTOW-916|https://issues.jboss.org/browse/UNDERTOW-916] however that was only for one method "getParameter(String)". We would like all these methods above fixed :) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12094) Undertow doesn't extract request parameters if PUT method is being called

by Lin Gao (Jira)

[ https://issues.jboss.org/browse/WFLY-12094?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-12094: --------------------------- Labels: downstream_dependency (was: ) > Undertow doesn't extract request parameters if PUT method is being called > ------------------------------------------------------------------------- > > Key: WFLY-12094 > URL: https://issues.jboss.org/browse/WFLY-12094 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Lin Gao > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > If PUT method is being used, we cannot extract request parameters/values in Undertow using these methods below: > ---------------------------------------- > > + getParameterNames > > + getParameterValues > > + getParameterMap > ---------------------------------------- > Similar bug was fixed via [UNDERTOW-916|https://issues.jboss.org/browse/UNDERTOW-916] however that was only for one method "getParameter(String)". We would like all these methods above fixed :) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12094) Undertow doesn't extract request parameters if PUT method is being called

by Lin Gao (Jira)

[ https://issues.jboss.org/browse/WFLY-12094?page=com.atlassian.jira.plugin... ] Lin Gao reassigned WFLY-12094: ------------------------------ Assignee: Lin Gao (was: Flavia Rainone) > Undertow doesn't extract request parameters if PUT method is being called > ------------------------------------------------------------------------- > > Key: WFLY-12094 > URL: https://issues.jboss.org/browse/WFLY-12094 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Major > Labels: downstream_dependency > > If PUT method is being used, we cannot extract request parameters/values in Undertow using these methods below: > ---------------------------------------- > > + getParameterNames > > + getParameterValues > > + getParameterMap > ---------------------------------------- > Similar bug was fixed via [UNDERTOW-916|https://issues.jboss.org/browse/UNDERTOW-916] however that was only for one method "getParameter(String)". We would like all these methods above fixed :) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"

by Святослав Кремлёв (Jira)

Святослав Кремлёв created WFLY-12093: ---------------------------------------- Summary: bug in tutorial "batch-processing" with column "End Time" Key: WFLY-12093 URL: https://issues.jboss.org/browse/WFLY-12093 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 17.0.0.Alpha1 Environment: batch-processing Reporter: Святослав Кремлёв Assignee: Eduardo Martins Attachments: 2019-05-18 23_16_51-Batch Processing.png in file org/jboss/as/quickstarts/batch/controller/JobData.java {code} public Date getEndTime() { endTime = new Date(); return endTime.getTime() == 0 ? null : endTime; } {code} its returns current time every time, not the job endTime -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12092) [GSS](7.2.z) Unknown service name jboss.ejb and txn

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-12092: ----------------------------------- Summary: [GSS](7.2.z) Unknown service name jboss.ejb and txn Key: WFLY-12092 URL: https://issues.jboss.org/browse/WFLY-12092 Project: WildFly Issue Type: Bug Components: EJB, Transactions Affects Versions: 17.0.0.Alpha1 Reporter: Brad Maxwell Assignee: Flavia Rainone Fix For: 17.0.0.Beta1 When EJBRemoting service is not started (it is LAZY), but XA recovery has, we could have the following sort of error: {code} 16:51:46,785 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: WFTXN0034: Failed to acquire a connection for this operation at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.getOperationsXA(RemotingRemoteTransactionPeer.java:139) at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.recover(RemotingRemoteTransactionPeer.java:202) at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:201) at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:197) at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:634) at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:226) at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:171) at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:770) at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:382) Caused by: org.jboss.remoting3.ServiceOpenException: Unknown service name jboss.ejb at org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:429) at org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:46) at org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.WorkerThread.run(WorkerThread.java:591) Suppressed: org.jboss.remoting3.ServiceOpenException: Unknown service name txn ... 6 more {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12088) JAR does not supported for deployment-overlays mechanism

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12088?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-12088: -------------------------------------- I changed this to Major as it doesn't seem like a blocker. I don't know the details so I'll let someone more familiar with the overlays change it back to a blocker if they feel it should be one. > JAR does not supported for deployment-overlays mechanism > -------------------------------------------------------- > > Key: WFLY-12088 > URL: https://issues.jboss.org/browse/WFLY-12088 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 16.0.0.Final > Reporter: Vlad Filipp > Assignee: Richard Opalka > Priority: Major > > When trying to make a link from an overlay to a JAR, classes from overlay libraries are not loaded for a linked JAR. > The situation is similar when creating a link to a JAR which is located inside EAR. > Should overlay deployment mechanism be supported for JARs? > Example standalone.xml: > {code:java} > <deployment-overlays> > ... > <deployment-overlay name="my-overlay-n1"> > <content ...> > <deployment name="my-jar-inside-ear-use-overlays-libs.jar"/> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12088) JAR does not supported for deployment-overlays mechanism

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12088?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12088: --------------------------------- Priority: Major (was: Blocker) > JAR does not supported for deployment-overlays mechanism > -------------------------------------------------------- > > Key: WFLY-12088 > URL: https://issues.jboss.org/browse/WFLY-12088 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 16.0.0.Final > Reporter: Vlad Filipp > Assignee: Richard Opalka > Priority: Major > > When trying to make a link from an overlay to a JAR, classes from overlay libraries are not loaded for a linked JAR. > The situation is similar when creating a link to a JAR which is located inside EAR. > Should overlay deployment mechanism be supported for JARs? > Example standalone.xml: > {code:java} > <deployment-overlays> > ... > <deployment-overlay name="my-overlay-n1"> > <content ...> > <deployment name="my-jar-inside-ear-use-overlays-libs.jar"/> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12091) galleon-pack incorrect processing of subsyste.jaxrs

by r searls (Jira)

r searls created WFLY-12091: ------------------------------- Summary: galleon-pack incorrect processing of subsyste.jaxrs Key: WFLY-12091 URL: https://issues.jboss.org/browse/WFLY-12091 Project: WildFly Issue Type: Bug Components: Build System Affects Versions: 17.0.0.Beta1 Environment: Fedora jdk-10 mvn 3.3.9 wfly 17.0.0.Beta1-SNAPSHOT Reporter: r searls Assignee: Brian Stansberry Attachments: xgalleon-pack-issue-may17.zip The tools are not properly handling a simple attribute addition to subsystem.jaxrs. I have added an attribute to jaxrs/src/main/resources/subsystem-templates/jaxrs.xml. The new definition is this, <subsystem xmlns="urn:jboss:domain:jaxrs:2.0" statistics-enabled="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-enabled:false}}" /> The old definition was this <subsystem xmlns="urn:jboss:domain:jaxrs:2.0"/> I have made the following changes in 2 files galleon-pack files but none of this is reflected in the generated standalone*.xml files. - to galleon-pack/src/main/resources/feature_groups/basic-profile.xml I added <feature spec="subsystem.jaxrs"> <param name="statistics-enabled" value="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-jaxrs:false}}"/> </feature> - to galleon-pack/src/main/resources/layers/standalone/jaxrs/layer-spec.xml I added <feature spec="subsystem.jaxrs"> <param name="statistics-enabled" value="${wildfly.jaxrs.statistics-enabled:${wildfly.statistics-jaxrs:false}}"/> </feature> This change is required for https://issues.jboss.org/browse/WFLY-11943 Attached zip file contains the files I changed and tested with. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2019