May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1189) Parser error doesn't point at the problematic line in case of extra double quote

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created DROOLS-1189: ----------------------------------------- Summary: Parser error doesn't point at the problematic line in case of extra double quote Key: DROOLS-1189 URL: https://issues.jboss.org/browse/DROOLS-1189 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.4.0.Final Reporter: Toshiya Kobayashi Assignee: Mario Fusco Priority: Minor If you have a rule which wrongly has an extra double quote, {noformat} rule "rule1" when then System.out.println("1""); end rule "rule2" when then System.out.println("2"); end rule "rule3" when then System.out.println("3"); end {noformat} Drools raises parser errors like this: {noformat} [20,0]: [ERR 102] Line 20:0 mismatched input '' [20,0]: [ERR 102] Line 20:0 mismatched input '<eof>' in rule "rule1" [0,0]: Parser returned a null Package {noformat} It doesn't point at the problematic line which actually contains the extra double quote. So it's difficult for users to find the root cause (Imagine you have bunch of rules generated by decision table). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-106) Erroneous in-IDE Message id .. is not unique for messageMethod ... with project code ..

by Michael Vorburger (JIRA)

Michael Vorburger created LOGTOOL-106: ----------------------------------------- Summary: Erroneous in-IDE Message id .. is not unique for messageMethod ... with project code .. Key: LOGTOOL-106 URL: https://issues.jboss.org/browse/LOGTOOL-106 Project: Log Tool Issue Type: Bug Reporter: Michael Vorburger Priority: Critical I'm getting easily reproducible in-IDE "Message id .. is not unique for messageMethod ... with project code .." errors which are erroneous. Perhaps a bug like something isn't being cleaned up when it should, but only affecting environments like IDEs with incremental builds, not one-off e.g. mvn CLI usage? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6642) Automatic ior-settings creation

by Tomasz Adamski (JIRA)

Tomasz Adamski created WFLY-6642: ------------------------------------ Summary: Automatic ior-settings creation Key: WFLY-6642 URL: https://issues.jboss.org/browse/WFLY-6642 Project: WildFly Issue Type: Enhancement Components: IIOP Affects Versions: 10.0.0.Final Reporter: Tomasz Adamski Assignee: Tomasz Adamski Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6641) Classes not unloaded after undeployment

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-6641: ---------------------------------- Summary: Classes not unloaded after undeployment Key: WFLY-6641 URL: https://issues.jboss.org/browse/WFLY-6641 Project: WildFly Issue Type: Bug Components: CDI / Weld Affects Versions: 8.2.0.Final, 10.0.0.Final Reporter: Brad Maxwell Assignee: Martin Kouba Priority: Blocker Fix For: 10.1.0.Final I deployed a small web application with one single JSF and one managed bean, accessed the page and then undeployed the application. I found the classes of this application had never been unloaded via monitoring with Java VistualVM, also using '-XX:+TraceClassUnloading' JVM option proved the classes not unloaded. Then checking the heap dump of it, I found there were instance for each enum item (the managed bean has one enum type field, which is always initialized when the managed bean constructed) and one array instance including these enum instances. Please refer to the attachment for the same application. I started to verify the classloader memory leak issue because we found hot redeployment of our real application swallow some memory each time, then after lots of redeployment the server was short of memories. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6640) EJB view service allows invocations through before component has started resulting in potential race

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-6640: ---------------------------------- Summary: EJB view service allows invocations through before component has started resulting in potential race Key: WFLY-6640 URL: https://issues.jboss.org/browse/WFLY-6640 Project: WildFly Issue Type: Bug Components: EJB Reporter: Brad Maxwell Assignee: Stuart Douglas The EJB view service does not suspend invocations when a component is not started, but instead forwards to the view interceptor chain. The view interceptors may not be ready yet, which can result in a race. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6632) Unable to create replicated cache

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6632?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-6632: ------------------------------------ Looking at your configuration above, do you really have a JGroups channel called "TCP"? Can you post your JGroups subsystem configuration containing this channel? > Unable to create replicated cache > ---------------------------------- > > Key: WFLY-6632 > URL: https://issues.jboss.org/browse/WFLY-6632 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.2.Final > Reporter: Vinay Lodha > Assignee: Paul Ferraro > Attachments: server.log, spring2-mvc-xml-hello-world-1.0-SNAPSHOT.war, spring2-mvc-xml.zip > > > servers is unable to create replicated or distributed infinispan cache, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6632) Unable to create replicated cache

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6632?page=com.atlassian.jira.plugin.... ] Paul Ferraro edited comment on WFLY-6632 at 5/23/16 12:54 PM: -------------------------------------------------------------- Forgive me, but I don't see anything in your attached application that references the cache. Can you point me in the right direction? Also, please post the error message or stack trace from step 5 - as the attached server.log does not reflect this. EDIT: I do see your resource references in web.xml, but I still don't see where these resources are used. was (Author: pferraro): Forgive me, but I don't see anything in your attached application that references the cache. Can you point me in the right direction? Also, please post the error message or stack trace from step 5 - as the attached server.log does not reflect this. > Unable to create replicated cache > ---------------------------------- > > Key: WFLY-6632 > URL: https://issues.jboss.org/browse/WFLY-6632 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.2.Final > Reporter: Vinay Lodha > Assignee: Paul Ferraro > Attachments: server.log, spring2-mvc-xml-hello-world-1.0-SNAPSHOT.war, spring2-mvc-xml.zip > > > servers is unable to create replicated or distributed infinispan cache, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6638) EJB view service allows invocations through before component has started resulting in potential race

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6638?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-6638: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1330677, https://bugzilla.redhat.com/show_bug.cgi?id=1330678 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1330677) > EJB view service allows invocations through before component has started resulting in potential race > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-6638 > URL: https://issues.jboss.org/browse/WFLY-6638 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > The EJB view service does not suspend invocations when a component is not started, but instead forwards to the view interceptor chain. The view interceptors may not be ready yet, which can result in a race. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6638) EJB view service allows invocations through before component has started resulting in potential race

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6638?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-6638: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1330677 Bugzilla Update: Perform > EJB view service allows invocations through before component has started resulting in potential race > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-6638 > URL: https://issues.jboss.org/browse/WFLY-6638 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > The EJB view service does not suspend invocations when a component is not started, but instead forwards to the view interceptor chain. The view interceptors may not be ready yet, which can result in a race. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-77) ConcurrentModificationException in deploy-artifact

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-77?page=com.atlassian.jira.plugin.... ] James Perkins commented on JBASMP-77: ------------------------------------- I'll put it on my plans for this week. I need to go through the open issues and pull queue, then I can cut a release. > ConcurrentModificationException in deploy-artifact > -------------------------------------------------- > > Key: JBASMP-77 > URL: https://issues.jboss.org/browse/JBASMP-77 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: deploy > Affects Versions: 7.7.Final > Reporter: Daniele Gaffuri > Assignee: Tomas Remes > Fix For: 7.8.Final > > > In the same situation of JBASMP-57 deploy-artifact throws the following exception: > {code} > [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.7.SCE:deploy-artifact (deploy) on project sideup-integration: Could not execute goal deploy-artifact on null. Reason: null: ConcurrentModificationException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.7.SCE:deploy-artifact (deploy) on project sideup-integration: Could not execute goal deploy-artifact on null. Reason: null > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Could not execute goal deploy-artifact on null. Reason: null > at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:159) > at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:112) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: java.util.ConcurrentModificationException > at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:394) > at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405) > at java.util.AbstractCollection.addAll(AbstractCollection.java:341) > at org.jboss.as.plugin.deployment.DeployArtifact.validate(DeployArtifact.java:84) > at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:136) > ... 22 more > {code} > This is probably due to changes in related commit [37bc2c1], causing both deploy and undeploy validate methods to add the set of dependencies to itself: > {code} > final Set<Artifact> dependencies = project.getDependencyArtifacts(); > // Allows provided dependencies to be seen > dependencies.addAll(project.getDependencyArtifacts()); > {code} > {code} > final Set<Artifact> dependencies = project.getDependencyArtifacts(); > dependencies.addAll(this.project.getDependencyArtifacts()); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 2016