November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9573) EJB invocation over HTTP fails for calls that use application specific classes

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-9573?page=com.atlassian.jira.plugin.... ] jaikiran pai updated WFLY-9573: ------------------------------- Summary: EJB invocation over HTTP fails for calls that use application specific classes (was: problem executing remote ejb call) > EJB invocation over HTTP fails for calls that use application specific classes > ------------------------------------------------------------------------------ > > Key: WFLY-9573 > URL: https://issues.jboss.org/browse/WFLY-9573 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming, Remoting > Affects Versions: 11.0.0.Final > Reporter: peter craddock > Assignee: David Lloyd > > I first raised this as a discussion and [~jaikiran] asked that I raise this as a bug because he has recreated the issue in a small test case. > Discussion is here > https://developer.jboss.org/thread/276635 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9573) problem executing remote ejb call

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-9573?page=com.atlassian.jira.plugin.... ] jaikiran pai edited comment on WFLY-9573 at 11/24/17 8:59 AM: -------------------------------------------------------------- A PR has been submitted containing the fix https://github.com/wildfly/wildfly-http-client/pull/14 was (Author: jaikiran): A PR has been submitting containing the fix https://github.com/wildfly/wildfly-http-client/pull/14 > problem executing remote ejb call > --------------------------------- > > Key: WFLY-9573 > URL: https://issues.jboss.org/browse/WFLY-9573 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming, Remoting > Affects Versions: 11.0.0.Final > Reporter: peter craddock > Assignee: David Lloyd > > I first raised this as a discussion and [~jaikiran] asked that I raise this as a bug because he has recreated the issue in a small test case. > Discussion is here > https://developer.jboss.org/thread/276635 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9573) problem executing remote ejb call

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-9573?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-9573: ------------------------------------ A PR has been submitting containing the fix https://github.com/wildfly/wildfly-http-client/pull/14 > problem executing remote ejb call > --------------------------------- > > Key: WFLY-9573 > URL: https://issues.jboss.org/browse/WFLY-9573 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming, Remoting > Affects Versions: 11.0.0.Final > Reporter: peter craddock > Assignee: David Lloyd > > I first raised this as a discussion and [~jaikiran] asked that I raise this as a bug because he has recreated the issue in a small test case. > Discussion is here > https://developer.jboss.org/thread/276635 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9573) problem executing remote ejb call

by peter craddock (JIRA)

peter craddock created WFLY-9573: ------------------------------------ Summary: problem executing remote ejb call Key: WFLY-9573 URL: https://issues.jboss.org/browse/WFLY-9573 Project: WildFly Issue Type: Bug Components: EJB, Naming, Remoting Affects Versions: 11.0.0.Final Reporter: peter craddock Assignee: David Lloyd I first raised this as a discussion and [~jaikiran] asked that I raise this as a bug because he has recreated the issue in a small test case. Discussion is here https://developer.jboss.org/thread/276635 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2138) Upgrade Jaxb depedency

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2138?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer edited comment on DROOLS-2138 at 11/24/17 7:51 AM: -------------------------------------------------------------------------- Our reps are not now compatible with JAVA 9. This isssue seems to be more complicated then simply upgrading the jboss-ip-bom. com.sun:tools:jar:1.6 is not available for community. For more information please look : https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-... was (Author: mbiarnes): our reps are not now compatible with JAVA 9. This isssue seems to be more complicated then simply upgrading the jboss-ip-bom. com.sun:tools:jar:1.6 is not available for community. For more information please look : https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-... > Upgrade Jaxb depedency > ---------------------- > > Key: DROOLS-2138 > URL: https://issues.jboss.org/browse/DROOLS-2138 > Project: Drools > Issue Type: Bug > Reporter: Petar Tahchiev > Assignee: Michael Biarnes Kiefer > > I'm sorry if this is no the correct place to report this but when building my project with jdk9, I get this warning: > {code} > [WARNING] Failed to build parent project for com.sun.xml.bind.mvn:jaxb-bundles:pom:2.2.11 > [WARNING] Failed to build parent project for com.sun.xml.bind:jaxb-core:jar:2.2.11 > [WARNING] Unable to obtain POM for artifact : com.sun.xml.bind:jaxb-core:jar:2.2.11:compile > org.apache.maven.project.InvalidProjectModelException: Some problems were encountered while processing the POMs: > [ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${tools.jar} @ com.sun.xml.bind.mvn:jaxb-parent:[unknown-version], /home/petar/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/2.2.11/jaxb-parent-2.2.11.pom, line 164, column 29 > for project > at org.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:193) > at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:240) > at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) > at org.codehaus.mojo.license.api.DefaultDependenciesTool.loadProjectDependencies(DefaultDependenciesTool.java:233) > at org.codehaus.mojo.license.api.DefaultThirdPartyHelper.loadDependencies(DefaultThirdPartyHelper.java:152) > at org.codehaus.mojo.license.AddThirdPartyMojo.loadDependencies(AddThirdPartyMojo.java:294) > at org.codehaus.mojo.license.AbstractAddThirdPartyMojo.init(AbstractAddThirdPartyMojo.java:400) > at org.codehaus.mojo.license.AbstractLicenseMojo.execute(AbstractLicenseMojo.java:169) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {code} > which happens to be because of the jaxb dependency you have here: > https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > which requires the {{tools.jar}} (from jaxb-parent-2.2.11 pom.xml): > {code} >  > <dependency> > <groupId>com.sun</groupId> > <artifactId>tools</artifactId> > <version>1.6</version> > <scope>system</scope> > <systemPath>${tools.jar}</systemPath> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2138) Upgrade Jaxb depedency

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2138?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer commented on DROOLS-2138: ------------------------------------------------ our reps are not now compatible with JAVA 9. This isssue seems to be more complicated then simply upgrading the jboss-ip-bom. com.sun:tools:jar:1.6 is not available for community. For more information please look : https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-... > Upgrade Jaxb depedency > ---------------------- > > Key: DROOLS-2138 > URL: https://issues.jboss.org/browse/DROOLS-2138 > Project: Drools > Issue Type: Bug > Reporter: Petar Tahchiev > Assignee: Michael Biarnes Kiefer > > I'm sorry if this is no the correct place to report this but when building my project with jdk9, I get this warning: > {code} > [WARNING] Failed to build parent project for com.sun.xml.bind.mvn:jaxb-bundles:pom:2.2.11 > [WARNING] Failed to build parent project for com.sun.xml.bind:jaxb-core:jar:2.2.11 > [WARNING] Unable to obtain POM for artifact : com.sun.xml.bind:jaxb-core:jar:2.2.11:compile > org.apache.maven.project.InvalidProjectModelException: Some problems were encountered while processing the POMs: > [ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${tools.jar} @ com.sun.xml.bind.mvn:jaxb-parent:[unknown-version], /home/petar/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/2.2.11/jaxb-parent-2.2.11.pom, line 164, column 29 > for project > at org.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:193) > at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:240) > at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) > at org.codehaus.mojo.license.api.DefaultDependenciesTool.loadProjectDependencies(DefaultDependenciesTool.java:233) > at org.codehaus.mojo.license.api.DefaultThirdPartyHelper.loadDependencies(DefaultThirdPartyHelper.java:152) > at org.codehaus.mojo.license.AddThirdPartyMojo.loadDependencies(AddThirdPartyMojo.java:294) > at org.codehaus.mojo.license.AbstractAddThirdPartyMojo.init(AbstractAddThirdPartyMojo.java:400) > at org.codehaus.mojo.license.AbstractLicenseMojo.execute(AbstractLicenseMojo.java:169) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {code} > which happens to be because of the jaxb dependency you have here: > https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > which requires the {{tools.jar}} (from jaxb-parent-2.2.11 pom.xml): > {code} >  > <dependency> > <groupId>com.sun</groupId> > <artifactId>tools</artifactId> > <version>1.6</version> > <scope>system</scope> > <systemPath>${tools.jar}</systemPath> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9572) Speed-up clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9572?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-9572: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > Speed-up clustering testsuite > ----------------------------- > > Key: WFLY-9572 > URL: https://issues.jboss.org/browse/WFLY-9572 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9449) Speed-up intermittently failing SingletonPartitionTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9449?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9449: --------------------------------- Issue Type: Task (was: Bug) > Speed-up intermittently failing SingletonPartitionTestCase > ---------------------------------------------------------- > > Key: WFLY-9449 > URL: https://issues.jboss.org/browse/WFLY-9449 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Stuart noticed the test fails in CI intermittently. This is because it is designed to rely on MERGE3 which does not operate quickly enough. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9449) Speed-up intermittently failing SingletonPartitionTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9449?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9449: --------------------------------- Summary: Speed-up intermittently failing SingletonPartitionTestCase (was: SingletonPartitionTestCase can fail intermittently) > Speed-up intermittently failing SingletonPartitionTestCase > ---------------------------------------------------------- > > Key: WFLY-9449 > URL: https://issues.jboss.org/browse/WFLY-9449 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Stuart noticed the test fails in CI intermittently. This is because it is designed to rely on MERGE3 which does not operate quickly enough. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9572) Speed-up clustering testsuite

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9572: ------------------------------------ Summary: Speed-up clustering testsuite Key: WFLY-9572 URL: https://issues.jboss.org/browse/WFLY-9572 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 11.0.0.Final Reporter: Radoslav Husar Assignee: Paul Ferraro For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017