[jboss-jira] [JBoss JIRA] (WFCORE-843) LoggingSubsystemRollbackTestCase fails on HP-UX during byteman initialization

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116645#comment-13116645 ] 

James Perkins commented on WFCORE-843:
--------------------------------------

I looked at that wile debugging I found that error prints out when there's an attempt to initialize byteman twice via the entry point. I didn't look much further since it seemed to work, but if it becomes an issue I can look into it further.

> LoggingSubsystemRollbackTestCase fails on HP-UX during byteman initialization
> -----------------------------------------------------------------------------
>
>                 Key: WFCORE-843
>                 URL: https://issues.jboss.org/browse/WFCORE-843
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 2.0.0.Alpha11
>         Environment: HP-UX eph-04 B.11.31 U ia64
> java version "1.8.0.01-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.01-hp-ux-rc2)
> Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)
>            Reporter: Petr Kremensky
>            Assignee: James Perkins
>
> org.jboss.as.logging.LoggingSubsystemRollbackTestCase fails on HP-UX
> {noformat}
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.15 sec <<< FAILURE! - in org.jboss.as.logging.LoggingSubsystemRollbackTestCase
> org.jboss.as.logging.LoggingSubsystemRollbackTestCase(org.jboss.as.logging.LoggingSubsystemRollbackTestCase)  Time elapsed: 0.147 sec  <<< ERROR!
> java.lang.Exception: BMUnit : Unable to identify test JVM process during agent load
>         at org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:500)
>         at org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:669)
>         at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:73)
>         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>         at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>         at org.junit.runners.Suite.runChild(Suite.java:127)
>         at org.junit.runners.Suite.runChild(Suite.java:26)
>         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>         at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>         at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>         at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>         at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>         at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
>         at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113)
>         at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85)
>         at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54)
>         at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134)
>         at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>         at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>         at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)