[JBoss JIRA] (WFLY-1560) PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-1560?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-1560:
-----------------------------
Fix Version/s: 9.0.0.Final
> PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-1560
> URL: https://issues.jboss.org/browse/WFLY-1560
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.0.0.Alpha1
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Fix For: 9.0.0.Final
>
> Attachments: server_log_snippet.txt
>
>
> PartialObjectActivationJarTestCase fails if it runs after InflowFlatTestCase. It seems that the {{inflow2}} resource adapter is not fully unregistered by InflowFlatTestCase before PartialObjectActivationJarTestCase begins to start its own RA.
> Here is the server log snippet (DEBUG level):
> http://pastebin.test.redhat.com/147968
> Line 10 of this snippet corresponds to the invocation of {{setConfiguration("basic.xml");}} in PartialObjectActivationJarTestCase. Then, the server is apparently trying to activate {{MultipleConnectionFactory2Impl}} and {{MultipleAdminObject2Impl}} even though these are not involved in {{basic.xml}} of PartialObjectActivationJarTestCase at all. A suspicious exception is on line 19 there.
> I tried to put some delay between {{remove(address);}} and {{removeModule(defaultPath);}} in {{AbstractModuleDeploymentTestCaseSetup#tearDown()}} but it did not help. I also tried to put {{@Ignore}} to both test methods in the InflowFlatTestCase which also did not help, so it is evidently related only to the RA deployment/undeployment.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-4382) Functionality to allow symbolic links
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4382?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-4382:
-----------------------------
Fix Version/s: 9.0.0.Final
> Functionality to allow symbolic links
> -------------------------------------
>
> Key: WFLY-4382
> URL: https://issues.jboss.org/browse/WFLY-4382
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Reporter: Erdal Yildiz
> Assignee: Jakub Pýcha
> Priority: Minor
> Fix For: 9.0.0.Final
>
>
> There should be a possibility to configure that wildfly follows symbolic links.
> Example which describes the problem:
> $wildflyHome/welcome-content/test/index.html --> localhost:8080/test/index.html ==> works.
> $wildflyHome/welcome-content/symlink/index.html --> localhost:8080/symlink/index.html ==> doesn't work.
> "symlink" is the symbolic link which is created by
> ln -s /path/to/symlink $wildflyHome/welcome-content
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-840) jboss.as MBean subtree missing when profiling agent used
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-840?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated WFLY-840:
----------------------------
Fix Version/s: 9.0.0.Final
> jboss.as MBean subtree missing when profiling agent used
> --------------------------------------------------------
>
> Key: WFLY-840
> URL: https://issues.jboss.org/browse/WFLY-840
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Reporter: dpocock
> Labels: jconsole
> Fix For: 9.0.0.Final
>
>
> I've set up JBoss 7.1.0.Final as a fresh installation and started standalone
> I can successfully connect with regular jconsole or $JBOSS_HOME/bin/jconsole. In the MBeans tab, I can see various subtrees, including jboss.as
> Then I stop JBoss and add the jmxetric monitoring agent, as described here:
> http://danielpocock.com/monitoring-jboss-tomcat-and-application-servers-w...
> Now, with JBoss running with jmxetric, I connect to it with jconsole (either regular jconsole or $JBOSS_HOME/bin/jconsole) and I can see all the same subtrees, except one, jboss.as is missing. I can see jboss.modules, jboss.ws, jboss.msc, jboss.jta and core JVM subtrees
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month