[JBoss JIRA] (WFLY-10201) There are in doubt transactions that should be rolled back after communication failure
by Flavia Rainone (JIRA)
[ https://issues.jboss.org/browse/WFLY-10201?page=com.atlassian.jira.plugin... ]
Flavia Rainone commented on WFLY-10201:
---------------------------------------
I'm adding a dependency on the WFLY-10174. If wildfly-transaction-client 1.0.3.Final comes before 1.1.0.Final, this will require an update.
> There are in doubt transactions that should be rolled back after communication failure
> --------------------------------------------------------------------------------------
>
> Key: WFLY-10201
> URL: https://issues.jboss.org/browse/WFLY-10201
> Project: WildFly
> Issue Type: Bug
> Reporter: Flavia Rainone
> Assignee: Flavia Rainone
>
> We have two servers, one deployment on each.
> TX impl: jta
> there is remote outbound connection on the EAP 1 for EJB call from EAP1 to EAP2
> outbound connection points to socket proxy which is managable (communication can be stopped) and forward communication to EAP2 (location that should be used in remote outbound connection without socket proxy)
> Scenario:
> call servlet on EAP 1 which trigger EJB on the EAP 1
> EJB enlists dummy xa resource and writes to DB
> EJB call EJB on the EAP 2 via remote outbound connection
> EJB on the server 2 enlists dummy xa resource and writes to DB and return
> at the exit of the prepare phase in dummy xa resource on EAP 2 communication (socket proxy) is killed
> Transaction is supposed to be rolled back.
> However, we can see that there are prepared resources on the EAP 2 that have not been rolled back
> [INFO] Transaction
> Xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff0a280499:6a6c4aa6:59885e66:12, node_name=0, branch_uid=0:ffff0a280499:6a6c4aa6:59885e66:27, subordinatenodename=1, eis_name=0 >
> Type:StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA
> ParentNodeName:0
> Participant:false
> CreationTime:Mon, 07 Aug 2017 14:35:11 +0200
> AgeInSeconds:128
> Id:0:ffff0a280499:-166fadbf:59885e75:10
> Participant
> HeuristicValue:-1
> Status:PREPARED
> JndiName:java:/TestXAResource
> GlobalTransactionId:[B@4e1b1193
> HeuristicStatus:UNKNOWN
> NodeName:null
> Timeout:0
> FormatId:-1
> BranchQualifier:[B@39a95e4c
> Type:/StateManager/AbstractRecord/XAResourceRecord
> Participant:true
> EisProductVersion:EAP Test
> ClassName:com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord
> EisProductName:Crash Recovery Test
> Id:0:ffff0a280499:-166fadbf:59885e75:1a
> Participant
> HeuristicValue:-1
> Status:PREPARED
> JndiName:java:jboss/eap2-ds-jndi
> GlobalTransactionId:[B@5c4ce097
> HeuristicStatus:UNKNOWN
> NodeName:null
> Timeout:0
> FormatId:-1
> BranchQualifier:[B@6945cfc7
> Type:/StateManager/AbstractRecord/XAResourceRecord
> Participant:true
> EisProductVersion:9.3.15
> ClassName:com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord
> EisProductName:PostgreSQL
> Id:0:ffff0a280499:-166fadbf:59885e75:22
> [INFO] ..........................................................................................
> There is no evidence (eap1.server.log) that periodic recovery process is looking for in doubt transactions on the other server that could be rolled back.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2138) Upgrade Jaxb depedency
by Petar Tahchiev (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2138?page=com.atlassian.jira.plugi... ]
Petar Tahchiev commented on DROOLS-2138:
----------------------------------------
I don't think it should be a big issue. At the moment drools is using jaxb-2.2.11:
{code}
[INFO] \- org.kie.server:kie-server-client:jar:7.7.0.Final:compile
[INFO] +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile
[INFO] \- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile
{code}
and if you look at the jaxb-parent 2.2.11:
view-source:http://repo1.maven.org/maven2/com/sun/xml/bind/mvn/jaxb-paren...
You will see they declare the ${tools.jar} dependency which in java9 is no longer there.
However jaxb released last year 2.3.0 which no longer has this dependency:
view-source:http://repo1.maven.org/maven2/com/sun/xml/bind/mvn/jaxb-paren...
So all you have to do is stop using 4-year old dependencies.
> 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}
> <!-- JDK dependencies -->
> <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, 3 months
[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-116:
------------------------------------------
Attachment: screenshot-1.png
> Reinstall openshift production cluster
> --------------------------------------
>
> Key: SWSQE-116
> URL: https://issues.jboss.org/browse/SWSQE-116
> Project: Kiali QE
> Issue Type: Task
> Reporter: Filip Brychta
> Assignee: Guilherme Baufaker Rêgo
> Attachments: screenshot-1.png
>
>
> Currently there are following problems with our OS cluster:
> * docker on nodes is using loopback devices which is strongly discouraged for production use
> * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs"
> * different root passwords
> We need to:
> # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade)
> # reinstall RHELs with recommended partitions
> # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/...
> # install OS 3.9
> # create mojo documentation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (SWSQE-127) Kiali Openshift REST Python Module
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-127?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo commented on SWSQE-127:
-----------------------------------------------
I have an idea of creating Pypi module that will be reusable for json-test and ui-test
> Kiali Openshift REST Python Module
> ----------------------------------
>
> Key: SWSQE-127
> URL: https://issues.jboss.org/browse/SWSQE-127
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
>
> As an automation test engineer I would like a reusable and shareable Python Kiali Openshift REST module that could be consumed by any Python automation framework.
> Examples of module feeatures:
> * Get namespace list of installed Service Mesh's
> * Get namespace for specific mesh, such as BookInfo
> * Scale a service, such as BookInfo Ratings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (SWSQE-127) Kiali Openshift REST Python Module
by Matt Mahoney (JIRA)
Matt Mahoney created SWSQE-127:
----------------------------------
Summary: Kiali Openshift REST Python Module
Key: SWSQE-127
URL: https://issues.jboss.org/browse/SWSQE-127
Project: Kiali QE
Issue Type: Story
Reporter: Matt Mahoney
Assignee: Michael Foley
As an automation test engineer I would like a reusable and shareable Python Kiali Openshift REST module that could be consumed by any Python automation framework.
Examples of module feeatures:
* Get namespace list of installed Service Mesh's
* Get namespace for specific mesh, such as BookInfo
* Scale a service, such as BookInfo Ratings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (SWSQE-127) Kiali Openshift REST Python Module
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-127?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo reassigned SWSQE-127:
---------------------------------------------
Assignee: Guilherme Baufaker Rêgo (was: Michael Foley)
> Kiali Openshift REST Python Module
> ----------------------------------
>
> Key: SWSQE-127
> URL: https://issues.jboss.org/browse/SWSQE-127
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
>
> As an automation test engineer I would like a reusable and shareable Python Kiali Openshift REST module that could be consumed by any Python automation framework.
> Examples of module feeatures:
> * Get namespace list of installed Service Mesh's
> * Get namespace for specific mesh, such as BookInfo
> * Scale a service, such as BookInfo Ratings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10199) Using jboss-modules loading outside WildFly 12 is broken
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10199?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-10199:
------------------------------------
It must be a problem with the fix in the 1.7 branch; I'd call it a new issue.
> Using jboss-modules loading outside WildFly 12 is broken
> --------------------------------------------------------
>
> Key: WFLY-10199
> URL: https://issues.jboss.org/browse/WFLY-10199
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 12.0.0.Final
> Reporter: Martin Perina
> Assignee: David Lloyd
>
> oVirt is using jboss-modules not only for dependencies inside WildFly, but also when executing command line tools outside WildFly process. We are using following method which worked fine from JBoss 7 to WildFly11:
> export JAVA_MODULEPATH="<PATH TO OUR MODULES>"
> exec "${JAVA_HOME}/bin/java" \
> -jar "${JBOSS_HOME}/jboss-modules.jar" \
> -dependencies org.ovirt.engine.core.tools \
> -class org.ovirt.engine.core.cryptotool.Main \
> "$@"
> where "org.ovirt.engine.core.tools" is one of our existing module and in class we have standard Java class with main() method executing logic of specific command line tool.
> When I try to execute this code with WildFly 12.0.0.FINAL I receive following exception:
> Exception in thread "main" java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:460)
> at java.util.Properties.setProperty(Properties.java:166)
> at java.lang.System.setProperty(System.java:796)
> at org.jboss.modules.PropertyWriteAction.run(PropertyWriteAction.java:40)
> at org.jboss.modules.PropertyWriteAction.run(PropertyWriteAction.java:28)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.modules.Main.main(Main.java:390)
> When I tried to replace jboss-modules.jar provided by WildFly 12.0.0.FINAL with manuall build using latest code in 1.7 branch (commit a52a323c5c3d71cf9597f06951155e4639cbb707) I receive different error:
> org.jboss.modules.ModuleNotFoundException: org.ovirt.engine.core.tools
> at org.jboss.modules.Module.addPaths(Module.java:1221)
> at org.jboss.modules.Module.link(Module.java:1577)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1605)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:426)
> I haven't found any documentation describing such incompatible between 1.6 and 1.7, so is there any way how to have above execution compatible with both jboss-modules versions?
> Thanks
> Martin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months