[JBoss JIRA] (JBRULES-2792) Provide accessability of types and metadata for declare-d types
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBRULES-2792?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration updated JBRULES-2792:
---------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=917742
> Provide accessability of types and metadata for declare-d types
> ---------------------------------------------------------------
>
> Key: JBRULES-2792
> URL: https://issues.jboss.org/browse/JBRULES-2792
> Project: JBRULES
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: drools-api
> Affects Versions: 5.1.1.FINAL
> Reporter: Wolfgang Laun
> Assignee: Davide Sottara
> Fix For: 6.0.0.Alpha1
>
>
> * All types created or enhanced by a DRL declare construct must be retrievable from the KnowledgeBase using
> Declare getDeclare( String pkg, String name )
> * A Declare object must provide getters String getPackageName(), getName(), Map<String,Object> getMetaData() (same as Rule)
> * A Declare object must provide Class<?> getFactClass() returning the created or enhanced java-lang.Class.
> * A Declare object must provide long getInferredExpires() returning (for @role(event)) the inferred expiration offset or -1 if none.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6666) Custom log handler properties should support expressions
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/AS7-6666?page=com.atlassian.jira.plugin.s... ]
James Perkins closed AS7-6666.
------------------------------
Resolution: Rejected
This is already done upstream in 7.2.
> Custom log handler properties should support expressions
> --------------------------------------------------------
>
> Key: AS7-6666
> URL: https://issues.jboss.org/browse/AS7-6666
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Logging
> Affects Versions: 7.1.1.Final
> Reporter: Oliver Bock
> Assignee: James Perkins
> Priority: Minor
>
> The configuration of a custom-handler for the logging subsystem in standalone.xml doesn't support expressions in the value attribute of its properties/property elements. Those would be very useful, e.g. for OpenShift.
> Example ([...] denote omissions for clarity):
> {noformat}
> <custom-handler [...]>
> [...]
> <properties>
> <property name="myProp" value="${env.MY_PROP_VALUE}"/>
> </properties>
> </custom-handler>
> {noformat}
> TIA
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6668) OOME (Threads) if scoped EJB context (EJBCLIENT-34) is used with lookups in a loop
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created AS7-6668:
-------------------------------------
Summary: OOME (Threads) if scoped EJB context (EJBCLIENT-34) is used with lookups in a loop
Key: AS7-6668
URL: https://issues.jboss.org/browse/AS7-6668
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.2.0.Alpha1
Environment: AS7 build base on AS 7 tag 7.2.0.Final-prerelease1 (4ed76ceef253c568b7475780a92e49a034f540c5)
Can be reproduced with AS8 (upstream)
Reporter: Wolf-Dieter Fink
Assignee: jaikiran pai
Priority: Blocker
If a simple java-main application use the scoped-context each lookup will create 6 new threads (task-[1234]; read-1; write-1)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6667) jboss.as MBean subtree missing when profiling agent used
by dpocock (JIRA)
[ https://issues.jboss.org/browse/AS7-6667?page=com.atlassian.jira.plugin.s... ]
dpocock commented on AS7-6667:
------------------------------
David, thanks for the fast response, Jira created the ticket before I had inserted the description details.
Please see the description, and you will be able to reproduce the problem exactly with the procedure on my blog.
I've tried it with JDK 1.6.0u38 and 1.7.0u15. I observe the problem with both 7.1.0.Final and 7.1.1.Final
> jboss.as MBean subtree missing when profiling agent used
> --------------------------------------------------------
>
> Key: AS7-6667
> URL: https://issues.jboss.org/browse/AS7-6667
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Affects Versions: 7.1.0.Final
> Reporter: dpocock
> Labels: jconsole
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6667) jboss.as subtree missing when profiling agent used
by dpocock (JIRA)
[ https://issues.jboss.org/browse/AS7-6667?page=com.atlassian.jira.plugin.s... ]
dpocock updated AS7-6667:
-------------------------
Description:
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. I can see various subtrees, including jboss.as
Then I 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
> jboss.as subtree missing when profiling agent used
> --------------------------------------------------
>
> Key: AS7-6667
> URL: https://issues.jboss.org/browse/AS7-6667
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Affects Versions: 7.1.0.Final
> Reporter: dpocock
> Labels: jconsole
>
> 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. I can see various subtrees, including jboss.as
> Then I 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6667) jboss.as MBean subtree missing when profiling agent used
by dpocock (JIRA)
[ https://issues.jboss.org/browse/AS7-6667?page=com.atlassian.jira.plugin.s... ]
dpocock updated AS7-6667:
-------------------------
Summary: jboss.as MBean subtree missing when profiling agent used (was: jboss.as subtree missing when profiling agent used)
> jboss.as MBean subtree missing when profiling agent used
> --------------------------------------------------------
>
> Key: AS7-6667
> URL: https://issues.jboss.org/browse/AS7-6667
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Affects Versions: 7.1.0.Final
> Reporter: dpocock
> Labels: jconsole
>
> 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. I can see various subtrees, including jboss.as
> Then I 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6667) jboss.as MBean subtree missing when profiling agent used
by dpocock (JIRA)
[ https://issues.jboss.org/browse/AS7-6667?page=com.atlassian.jira.plugin.s... ]
dpocock updated AS7-6667:
-------------------------
Description:
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
was:
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. I can see various subtrees, including jboss.as
Then I 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
> jboss.as MBean subtree missing when profiling agent used
> --------------------------------------------------------
>
> Key: AS7-6667
> URL: https://issues.jboss.org/browse/AS7-6667
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Affects Versions: 7.1.0.Final
> Reporter: dpocock
> Labels: jconsole
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months