[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=comments#action_12310960 ] Dimitris Andreadis commented on JBMICROCONT-4: -- I've been experimenting with wrapping apache-vfs as a plug-in to jboss-vdf (virtual deployment framework?) As a starting point I made some packages under: org.jboss.vdf.spi org.jboss.vdf.plugins.vfs and I'm trying to re-write a deployment scanner over this, slowly adding the features required. It still needs a lot of work and testing but the result seems interesting, in that we could have a single scanner potentially scanning different filesystem types over the VFS plug-in by simply supplying different URIs, e.g.: file:/c:/jboss/deploy webdav:http://remote.server/deploy smb: ... (samba filesystem) (you could also have a different VDF plug-in, or plug-ins to the VFS plugin...) Then, I'd probably try to re-write one of the deployers using this, assuming this is the only way to come up with a working VDF api. I'm wondering about the proper location for checking in this. Currently I need to have it in HEAD/system to drive the development using a working server. I just chose package names that will presumably move easily to the HEAD/kernel module at a later time. Is there a better location for this code? > Virtual File System service > --- > > Key: JBMICROCONT-4 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 > Project: JBoss MicroContainer > Type: Feature Request > Reporter: Ivelin Ivanov > Assignee: Dimitris Andreadis > Priority: Critical > Fix For: JBossMC_1_0_0M2 > > > [Adrian] > Ok, here is the design I have in mind for the new deployer aspects. > This will be part of JBoss Kernel M2 release due by end of January. > Deploying Deployers: > First you have to be able to deploy a deployer. Not an easy task as I imagine > the deployer will have dependencies on other services. The aim will be to > minimize > these dependencies to ease the problem. > Basic Architecture: > The basic architecture of the aspectized deployer is that the deployments > work with a tree of DeploymentInfo objects just like the deployers do now. > There are two major differences: > 1) The deployers do not deal with urls, they deal with VFS contexts > 2) The deployers do not create objects directly, instead they create kernel > MetaData objects and submit them to the kernel for instantiation/configuration > to obtain correct ordering of startup/shutdown > Deployment Mode: > The deployers work in two different modes > 1) The first step is to ask who recognises the VFS context. This is so > the responsible deployer can correctly decide which part of the context > takes part in the classloading and where the metadata is located. > Additionally, this may introduce subdeployments (VFS contexts) if the > deployment allows/contains them. > 2) The second step (the main chain) allows each deployer to augment the > kernel metadata with its own config. > Deployer Ordering: > Since the deployers are working on a metadata model rather than > constructing objects directly, there should be less problem with ordering. > Most ordering will be in the classloader/instantiation/config stage, > the deployer should insert that ordering in the form of dependencies in the > metadata. > The only ordering required of the deployer chain is where one deployer > needs to work on the kernel metadata output of another deployer. > Killing two birds with one stone: > The problems mentioned with the deployer requiring other services > and the first tasks performed by package specific deployers, > i.e. identifying the deployment and its structure > can be easily solved by splitting the deployers into two classes > 1) A structural component that says "I recognise this deployment and this is > how it is structured" > 2) An interpretive component that creates the kernel metadata from the > package. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-68) Added missing MdbEjb.jsp in web-console
[ http://jira.jboss.com/jira/browse/JBAS-68?page=comments#action_12314521 ] Dimitris Andreadis commented on JBAS-68: The new jsp code is checked in, so just get it fro m CVS or find it in the new v4.0.1 > Added missing MdbEjb.jsp in web-console > --- > > Key: JBAS-68 > URL: http://jira.jboss.com/jira/browse/JBAS-68 > Project: JBoss Application Server > Type: Task > Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-5.0 Alpha > Attachments: screenshot-1.jpg > > > added missing MDB page, contributed by [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBMICROCONT-5) Main Deployer
[ http://jira.jboss.com/jira/browse/JBMICROCONT-5?page=history ] Dimitris Andreadis reassigned JBMICROCONT-5: Assign To: Dimitris Andreadis > Main Deployer > - > > Key: JBMICROCONT-5 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-5 > Project: JBoss MicroContainer > Type: Task > Components: Deployment > Reporter: Adrian Brock > Assignee: Dimitris Andreadis > Fix For: JBossMC_1_0_0M2 > > > MainDeployer > > The primary methods of MainDeployer are > (re/un)deploy(URL) > other methods are > (un)register/register(deployer, priority) > which will be used by the microcontainer > when a deployer is installed > stats based methods that expose information from the VDF > and config/constructors methods for things like the VDF and > initial deployers. > deploy(url) > 1) create a skeleton VDF context for the top level deployment > 2) ask the structural component chain who recognises it > repeat recursively for identified subcontexts > 3) invoke down the deployment component chain > starting with the deepest subcontexts first > redeploy(url) > similar to deploy() but performing a reinstall on the > microcontainer (i.e. suspend on valve for components being > reinstalled) > undeploy(url) > invoke down the deployment chain in reverse order > to remove the installed components > Reverse order means both in terms of subcontexts > and priority. > (un)register/register(deployer) > The deployer here identifies the structural and > deployment components of the deployer > and their respective "priorities". > This will be the name in the registry which > might be instantiated later. > Where present, the deployer is added to the > relevent chain. > ISSUE: Need to tighten up the semantics of the > register/unregister(deployer) for when the > deployment component has dependencies and > cannot be instantiated immediately -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-11) Extend the VDF BasicComponent to handle http and/or webdav
Extend the VDF BasicComponent to handle http and/or webdav -- Key: JBMICROCONT-11 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-11 Project: JBoss MicroContainer Type: Feature Request Environment: org.jboss.deployment.vdf.plugins.basic Reporter: Dimitris Andreadis Fix For: JBossMC_1_0_0 final Currently it handles locals files/directories (file:/./xx) so it should be extended to handle remote urls, including webdav enabled ones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1294) commons-logging.jar should be in default/lib
[
http://jira.jboss.com/jira/browse/JBAS-1294?page=comments#action_12314708 ]
Dimitris Andreadis commented on JBAS-1294:
--
I think it has to be in ./server/{default|all}/lib as well, because it is only
conditionally included in the boot classpath:
org/jboss/system/Server/ServerLoader.java
...
// If the home URL begins with http add the webav and httpclient jars
if( homeURL.getProtocol().startsWith("http") == true )
{
this.addLibrary("webdavlib.jar");
this.addLibrary("commons-httpclient.jar");
this.addLibrary("commons-logging.jar");
}
> commons-logging.jar should be in default/lib
>
>
> Key: JBAS-1294
> URL: http://jira.jboss.com/jira/browse/JBAS-1294
> Project: JBoss Application Server
> Type: Bug
> Versions: JBossAS-5.0 Alpha
> Reporter: Ryan Campbell
> Assignee: Scott M Stark
> Priority: Minor
>
>
> commons-logging is a dependency of Tomcat 5.5, however it is included in the
> default config via the ws4ee sar. Since it is a dependency of both,
> shouldn't it be removed from ws4ee and added to default lib? So that we go
> from:
> ./lib/commons-logging.jar
> ./server/all/lib/commons-logging.jar
> ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar
> ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar
> to:
> ./lib/commons-logging.jar
> ./server/all/lib/commons-logging.jar
> ./server/default/lib/commons-logging.jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-5) Main Deployer
[ http://jira.jboss.com/jira/browse/JBMICROCONT-5?page=comments#action_12314837 ] Dimitris Andreadis commented on JBMICROCONT-5: -- I'm adding a comment here, because the forums are down.. Lets say we have: a.bean |-b.bean |-c.jar And just 3 deployers, registered in that priority order: (C)lassLoadingDeployer -> (B)eanDeployer -> (J)ARDeployer. After the deployment structure is analyzed (by the bean & jar deployers) we have the corresponding DeploymentContext/subcontexts in place with each one having recorded its own url as a classpath. How 2nd stage deployment processing would work in this case, wrt depth and priority (.jar comes before .bean, according to suffix rules) C(c.jar) C(b.bean) C(a.bean) B(c.jar) B(b.bean) B(a.bean) J(c.jar) J(b.bean) J(a.bean) Or C(c.jar) B(c.jar) J(c.jar) C(b.bean) B(b.bean) J(b.bean) C(a.bean) B(a.bean) J(a.bean) Also, in the 1st case, should the MainDeployer control the traversal, or simply pass the base context to each deployer, and he traverses at will? Finally, what would the ClassLoadingDeployer do? Judging from the 3.x/4.x mechanism it seems to be creating a UCL for the base node, then adding the classpath of all subnodes to this UCL. (but processing here is parent first). Should I just go to the top most deployment, create a plain URLClassLoader, add all classpaths, and point to it from subcontexts? > Main Deployer > - > > Key: JBMICROCONT-5 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-5 > Project: JBoss MicroContainer > Type: Task > Components: Deployment > Reporter: Adrian Brock > Assignee: Dimitris Andreadis > Fix For: JBossMC_1_0_0M2 > > > MainDeployer > > The primary methods of MainDeployer are > (re/un)deploy(URL) > other methods are > (un)register/register(deployer, priority) > which will be used by the microcontainer > when a deployer is installed > stats based methods that expose information from the VDF > and config/constructors methods for things like the VDF and > initial deployers. > deploy(url) > 1) create a skeleton VDF context for the top level deployment > 2) ask the structural component chain who recognises it > repeat recursively for identified subcontexts > 3) invoke down the deployment component chain > starting with the deepest subcontexts first > redeploy(url) > similar to deploy() but performing a reinstall on the > microcontainer (i.e. suspend on valve for components being > reinstalled) > undeploy(url) > invoke down the deployment chain in reverse order > to remove the installed components > Reverse order means both in terms of subcontexts > and priority. > (un)register/register(deployer) > The deployer here identifies the structural and > deployment components of the deployer > and their respective "priorities". > This will be the name in the registry which > might be instantiated later. > Where present, the deployer is added to the > relevent chain. > ISSUE: Need to tighten up the semantics of the > register/unregister(deployer) for when the > deployment component has dependencies and > cannot be instantiated immediately -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1321) MdbEjb.jsp should use small caps for attrs (getstats() vs getStats())
MdbEjb.jsp should use small caps for attrs (getstats() vs getStats()) - Key: JBAS-1321 URL: http://jira.jboss.com/jira/browse/JBAS-1321 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.1 Final Environment: web-console Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-5.0 Alpha In 4.x, in contrast to 3.x, attribute names were changes from: getStats() to getstats() and that broke the jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1321) MdbEjb.jsp should use small caps for attrs (getstats() vs getStats())
[ http://jira.jboss.com/jira/browse/JBAS-1321?page=history ] Dimitris Andreadis updated JBAS-1321: - Fix Version: JBossAS-4.0.2RC1 Thanks to: [EMAIL PROTECTED] > MdbEjb.jsp should use small caps for attrs (getstats() vs getStats()) > - > > Key: JBAS-1321 > URL: http://jira.jboss.com/jira/browse/JBAS-1321 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 Final > Environment: web-console > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1 > > Original Estimate: 30 minutes > Remaining: 30 minutes > > In 4.x, in contrast to 3.x, attribute names were changes from: > getStats() > to > getstats() > and that broke the jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1321) MdbEjb.jsp should use small caps for attrs (getstats() vs getStats())
[ http://jira.jboss.com/jira/browse/JBAS-1321?page=history ] Dimitris Andreadis closed JBAS-1321: Resolution: Done > MdbEjb.jsp should use small caps for attrs (getstats() vs getStats()) > - > > Key: JBAS-1321 > URL: http://jira.jboss.com/jira/browse/JBAS-1321 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 Final > Environment: web-console > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1 > > Original Estimate: 30 minutes > Remaining: 30 minutes > > In 4.x, in contrast to 3.x, attribute names were changes from: > getStats() > to > getstats() > and that broke the jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1359) Remove the castor dependency for the snmp adapter, use jbossxb
Remove the castor dependency for the snmp adapter, use jbossxb -- Key: JBAS-1359 URL: http://jira.jboss.com/jira/browse/JBAS-1359 Project: JBoss Application Server Type: Task Environment: varia, snmp adaptor Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final The snmp-adaptor uses castor for generating POJO metadata classes, and for parsing its configuration xml files. Replacing this with JBossXB will make it a lot lighter and remove the unecessary castor dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1362) bin/shutdown reports -S to be the default option
bin/shutdown reports -S to be the default option Key: JBAS-1362 URL: http://jira.jboss.com/jira/browse/JBAS-1362 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.1 Final Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Trivial bin/shutdown reports -S to be the default option, but it requires it to perform the actual shutdown. Default is probably -h -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1365) Allow arbitrary creation of filters in ListenerServiceMBeanSupport
Allow arbitrary creation of filters in ListenerServiceMBeanSupport -- Key: JBAS-1365 URL: http://jira.jboss.com/jira/browse/JBAS-1365 Project: JBoss Application Server Type: Feature Request Environment: system/src/main/org/jboss/system/ListenerServiceMBeanSupport Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Optional Allow arbritrary creation of NotificationFilters when subscribing for notifications. Currently, only NotificationFilterSupport is suppported. We should at least add the 2 other standard filters, AttributeChangeNotificationFilter & MBeanServerNotificationFilter We'll do it through a factory mechanism, because each filter is initialized in a different way, eg: bla bla -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1454) Extend snmp-adaptor as required an implement a basic jboss MIB
Extend snmp-adaptor as required an implement a basic jboss MIB -- Key: JBAS-1454 URL: http://jira.jboss.com/jira/browse/JBAS-1454 Project: JBoss Application Server Type: Feature Request Environment: varia/src/main/org/jboss/jmx/adaptors/snmp/agent Reporter: Dimitris Andreadis Priority: Minor We need to gauge interest to see how many people would need a) JBoss to implement a basic MIB, for integration purposes b) Do this in an extensible way to support user provided mappings This is not trivial, so we need to know if the investment in development cycles is worth it... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1506) CDROutputStream.create_input_stream is wrong when there are deferred writes
CDROutputStream.create_input_stream is wrong when there are deferred writes
---
Key: JBAS-1506
URL: http://jira.jboss.com/jira/browse/JBAS-1506
Project: JBoss Application Server
Type: Patch
Components: IIOP service
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
Environment: This related to a jacorb bug, see:
http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=532
Reporter: Dimitris Andreadis
Assigned to: Dimitris Andreadis
Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final
An exception is thrown when trying to insert a byte[] larger than 4000 bytes
into any any:
package test;
import java.util.Properties;
import org.omg.CORBA.ORB;
import org.omg.CORBA.Any;
import org.omg.CORBA.OctetSeqHelper;
public class Test
{
public static final void main(String[] args)
{
System.out.println("*** Starting test ***");
try
{
Properties props = new Properties();
props.put("org.omg.CORBA.ORBClass", "org.jacorb.orb.ORB");
props.put("org.omg.CORBA.ORBSingletonClass",
"org.jacorb.orb.ORBSingleton");
ORB orb = ORB.init(args, props);
byte[] bytes = new byte[4001];
Any any = orb.create_any();
OctetSeqHelper.insert(any, bytes);
}
catch (Exception e)
{
e.printStackTrace();
}
}
}
===
[java] *** Starting test ***
[java] [ jacorb.home unset! Will use '.' ]
[java] [ File .\jacorb.properties for configuration jacorb not found ]
[java] java.lang.ArrayIndexOutOfBoundsException
[java] at java.lang.System.arraycopy(Native Method)
[java] at org.jacorb.orb.CDROutputStream.create_input_stream(Unknown So
urce)
[java] at org.omg.CORBA.OctetSeqHelper.insert(OctetSeqHelper.java:41)
[java] at test.Test.main(Test.java:24)
===
With a byte[] of size 4000 or less, it works!
I've noticed that the exception actually originates from the Helper class that
comes from Sun's JDK:
...
public abstract class OctetSeqHelper
{
private static String _id = "IDL:omg.org/CORBA/OctetSeq:1.0";
public static void insert (org.omg.CORBA.Any a, byte[] that)
{
org.omg.CORBA.portable.OutputStream out = a.create_output_stream ();
a.type (type ());
write (out, that);
a.read_value (out.create_input_stream (), type ());
}
The same class from the jacorb distribution does not perform that final
"a.read_value(...)" line that causes the exception:
public static void insert (org.omg.CORBA.Any any, byte[] s)
{
any.type (type ());
write (any.create_output_stream (), s);
}
public static void write (final org.omg.CORBA.portable.OutputStream
_out, byte[] _s)
{
_out.write_long(_s.length);
_out.write_octet_array(_s,0,_s.length);
}
Also, if you look into jacorb's CDROutputStream, there is somewhere a hardcoded
4000 limit:
public final void write_octet_array( final byte[] value,
final int offset,
final int length)
{
if( value != null )
{
if( length > 4000 )
{
deferredArrayQueue.add( new DeferredWriteFrame( index, offset,
length, value ));
index += length;
deferred_writes += length;
}
else
{
check(length);
System.arraycopy(value,offset,buffer,pos,length);
index += length;
pos += length;
}
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1506) CDROutputStream.create_input_stream is wrong when there are deferred writes
[
http://jira.jboss.com/jira/browse/JBAS-1506?page=comments#action_12315650 ]
Dimitris Andreadis commented on JBAS-1506:
--
According to franscisco this is best solved by modifying CDROutputStream.java:
public org.omg.CORBA.portable.InputStream create_input_stream() {
if (deferred_writes > 0)
{
ByteArrayOutputStream baos = new ByteArrayOutputStream(index+1);
try
{
write(baos, 0, index);
}
catch (IOException e)
{
throw new MARSHAL(e.toString());
}
return new CDRInputStream(orb, baos.toByteArray());
}
else
{
byte[] result = new byte[index+1];
System.arraycopy(buffer, 0, result, 0, result.length);
return new CDRInputStream(orb, result);
}
}
> CDROutputStream.create_input_stream is wrong when there are deferred writes
> ---
>
> Key: JBAS-1506
> URL: http://jira.jboss.com/jira/browse/JBAS-1506
> Project: JBoss Application Server
> Type: Patch
> Components: IIOP service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
> Environment: This related to a jacorb bug, see:
> http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=532
> Reporter: Dimitris Andreadis
> Assignee: Dimitris Andreadis
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final
>
>
> An exception is thrown when trying to insert a byte[] larger than 4000 bytes
> into any any:
> package test;
> import java.util.Properties;
> import org.omg.CORBA.ORB;
> import org.omg.CORBA.Any;
> import org.omg.CORBA.OctetSeqHelper;
> public class Test
> {
>public static final void main(String[] args)
>{
> System.out.println("*** Starting test ***");
>
> try
> {
> Properties props = new Properties();
> props.put("org.omg.CORBA.ORBClass", "org.jacorb.orb.ORB");
> props.put("org.omg.CORBA.ORBSingletonClass",
> "org.jacorb.orb.ORBSingleton");
>
> ORB orb = ORB.init(args, props);
>
> byte[] bytes = new byte[4001];
> Any any = orb.create_any();
> OctetSeqHelper.insert(any, bytes);
> }
> catch (Exception e)
> {
> e.printStackTrace();
> }
>}
> }
> ===
> [java] *** Starting test ***
> [java] [ jacorb.home unset! Will use '.' ]
> [java] [ File .\jacorb.properties for configuration jacorb not found ]
> [java] java.lang.ArrayIndexOutOfBoundsException
> [java] at java.lang.System.arraycopy(Native Method)
> [java] at org.jacorb.orb.CDROutputStream.create_input_stream(Unknown
> So
> urce)
> [java] at org.omg.CORBA.OctetSeqHelper.insert(OctetSeqHelper.java:41)
> [java] at test.Test.main(Test.java:24)
> ===
> With a byte[] of size 4000 or less, it works!
> I've noticed that the exception actually originates from the Helper class
> that comes from Sun's JDK:
> ...
> public abstract class OctetSeqHelper
> {
> private static String _id = "IDL:omg.org/CORBA/OctetSeq:1.0";
> public static void insert (org.omg.CORBA.Any a, byte[] that)
> {
> org.omg.CORBA.portable.OutputStream out = a.create_output_stream ();
> a.type (type ());
> write (out, that);
> a.read_value (out.create_input_stream (), type ());
> }
> The same class from the jacorb distribution does not perform that final
> "a.read_value(...)" line that causes the exception:
> public static void insert (org.omg.CORBA.Any any, byte[] s)
> {
> any.type (type ());
> write (any.create_output_stream (), s);
> }
> public static void write (final org.omg.CORBA.portable.OutputStream
> _out, byte[] _s)
> {
>
> _out.write_long(_s.length);
> _out.write_octet_array(_s,0,_s.length);
> }
> Also, if you look into jacorb's CDROutputStream, there is somewhere a
> hardcoded 4000 limit:
> public final void write_octet_array( final byte[] value,
> final int offset,
> final int length)
> {
> if( value != null )
> {
> if( length > 4000 )
> {
> deferredArrayQueue.add( new DeferredWriteFrame( index,
> offset, length, value ));
> index += length;
> deferred_writes += length;
> }
> else
> {
> check(length);
> System.arraycopy(value,offset,buffer,pos,length);
> index += length;
> pos += length;
> }
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was s
[JBoss-dev] [JBoss JIRA] Assigned: (JBADMCON-59) Port DeploymentService updates to Branch_4_0
[ http://jira.jboss.com/jira/browse/JBADMCON-59?page=history ] Dimitris Andreadis reassigned JBADMCON-59: -- Assign To: Dimitris Andreadis > Port DeploymentService updates to Branch_4_0 > > > Key: JBADMCON-59 > URL: http://jira.jboss.com/jira/browse/JBADMCON-59 > Project: JBoss Admin Console > Type: Patch > Components: General Console > Versions: 1.1 alpha > Reporter: Charles Crouch > Assignee: Dimitris Andreadis > Fix For: 1.1 alpha > > > Porting the updates made to DeploymentService to the JBoss 4.0 branch will > enable people to deploy the Admin Console to existing 4.0.x servers, assuming > they update with the correct jars from the 4.0 branch. A comment should be > made when resolving this issue describing which updated jars are required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBADMCON-59) Port DeploymentService updates to Branch_4_0
[ http://jira.jboss.com/jira/browse/JBADMCON-59?page=history ] Dimitris Andreadis updated JBADMCON-59: --- Original Estimate: 28800 Remaining Estimate: 28800 > Port DeploymentService updates to Branch_4_0 > > > Key: JBADMCON-59 > URL: http://jira.jboss.com/jira/browse/JBADMCON-59 > Project: JBoss Admin Console > Type: Patch > Components: General Console > Versions: 1.1 alpha > Reporter: Charles Crouch > Assignee: Dimitris Andreadis > Fix For: 1.1 alpha > > Original Estimate: 1 day > Remaining: 1 day > > Porting the updates made to DeploymentService to the JBoss 4.0 branch will > enable people to deploy the Admin Console to existing 4.0.x servers, assuming > they update with the correct jars from the 4.0 branch. A comment should be > made when resolving this issue describing which updated jars are required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBADMCON-91) 'isSameRMValue' always gets set to true or false
[ http://jira.jboss.com/jira/browse/JBADMCON-91?page=history ] Dimitris Andreadis closed JBADMCON-91: -- Resolution: Rejected It is possible to *not* include the isSameRM-override-value entry by simply not including the key in the properties map. Look for example the "use-java-context" property in the xa-datasource template. No value is passed and nothing gets produced in the testsuite. I also verified that explicitly with isSameRM. > 'isSameRMValue' always gets set to true or false > -- > > Key: JBADMCON-91 > URL: http://jira.jboss.com/jira/browse/JBADMCON-91 > Project: JBoss Admin Console > Type: Bug > Components: DataSource > Versions: 1.0 alpha > Reporter: Charles Crouch > Assignee: Dimitris Andreadis > Fix For: 1.1 alpha > > Original Estimate: 4 hours > Remaining: 4 hours > > The 'isSameRMValue' property for an XA DataSource is always being set to > either true or false, there is no way to leave it unspecified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1506) CDROutputStream.create_input_stream is wrong when there are deferred writes
[
http://jira.jboss.com/jira/browse/JBAS-1506?page=comments#action_12315792 ]
Dimitris Andreadis commented on JBAS-1506:
--
It has been resolved for 4.x/HEAD, waiting to see whether to check in
jacorb.jar in 3.x as well, since that was based on an older version of jacorb.
> CDROutputStream.create_input_stream is wrong when there are deferred writes
> ---
>
> Key: JBAS-1506
> URL: http://jira.jboss.com/jira/browse/JBAS-1506
> Project: JBoss Application Server
> Type: Patch
> Components: IIOP service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
> Environment: This related to a jacorb bug, see:
> http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=532
> Reporter: Dimitris Andreadis
> Assignee: Dimitris Andreadis
> Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha
>
>
> An exception is thrown when trying to insert a byte[] larger than 4000 bytes
> into any any:
> package test;
> import java.util.Properties;
> import org.omg.CORBA.ORB;
> import org.omg.CORBA.Any;
> import org.omg.CORBA.OctetSeqHelper;
> public class Test
> {
>public static final void main(String[] args)
>{
> System.out.println("*** Starting test ***");
>
> try
> {
> Properties props = new Properties();
> props.put("org.omg.CORBA.ORBClass", "org.jacorb.orb.ORB");
> props.put("org.omg.CORBA.ORBSingletonClass",
> "org.jacorb.orb.ORBSingleton");
>
> ORB orb = ORB.init(args, props);
>
> byte[] bytes = new byte[4001];
> Any any = orb.create_any();
> OctetSeqHelper.insert(any, bytes);
> }
> catch (Exception e)
> {
> e.printStackTrace();
> }
>}
> }
> ===
> [java] *** Starting test ***
> [java] [ jacorb.home unset! Will use '.' ]
> [java] [ File .\jacorb.properties for configuration jacorb not found ]
> [java] java.lang.ArrayIndexOutOfBoundsException
> [java] at java.lang.System.arraycopy(Native Method)
> [java] at org.jacorb.orb.CDROutputStream.create_input_stream(Unknown
> So
> urce)
> [java] at org.omg.CORBA.OctetSeqHelper.insert(OctetSeqHelper.java:41)
> [java] at test.Test.main(Test.java:24)
> ===
> With a byte[] of size 4000 or less, it works!
> I've noticed that the exception actually originates from the Helper class
> that comes from Sun's JDK:
> ...
> public abstract class OctetSeqHelper
> {
> private static String _id = "IDL:omg.org/CORBA/OctetSeq:1.0";
> public static void insert (org.omg.CORBA.Any a, byte[] that)
> {
> org.omg.CORBA.portable.OutputStream out = a.create_output_stream ();
> a.type (type ());
> write (out, that);
> a.read_value (out.create_input_stream (), type ());
> }
> The same class from the jacorb distribution does not perform that final
> "a.read_value(...)" line that causes the exception:
> public static void insert (org.omg.CORBA.Any any, byte[] s)
> {
> any.type (type ());
> write (any.create_output_stream (), s);
> }
> public static void write (final org.omg.CORBA.portable.OutputStream
> _out, byte[] _s)
> {
>
> _out.write_long(_s.length);
> _out.write_octet_array(_s,0,_s.length);
> }
> Also, if you look into jacorb's CDROutputStream, there is somewhere a
> hardcoded 4000 limit:
> public final void write_octet_array( final byte[] value,
> final int offset,
> final int length)
> {
> if( value != null )
> {
> if( length > 4000 )
> {
> deferredArrayQueue.add( new DeferredWriteFrame( index,
> offset, length, value ));
> index += length;
> deferred_writes += length;
> }
> else
> {
> check(length);
> System.arraycopy(value,offset,buffer,pos,length);
> index += length;
> pos += length;
> }
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&o
[JBoss-dev] [JBoss JIRA] Assigned: (JBADMCON-91) 'isSameRMValue' always gets set to true or false
[ http://jira.jboss.com/jira/browse/JBADMCON-91?page=history ] Dimitris Andreadis reassigned JBADMCON-91: -- Assign To: Dimitris Andreadis > 'isSameRMValue' always gets set to true or false > -- > > Key: JBADMCON-91 > URL: http://jira.jboss.com/jira/browse/JBADMCON-91 > Project: JBoss Admin Console > Type: Bug > Components: DataSource > Versions: 1.0 alpha > Reporter: Charles Crouch > Assignee: Dimitris Andreadis > Fix For: 1.1 alpha > > Original Estimate: 4 hours > Remaining: 4 hours > > The 'isSameRMValue' property for an XA DataSource is always being set to > either true or false, there is no way to leave it unspecified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBADMCON-59) Port DeploymentService updates to Branch_4_0
[ http://jira.jboss.com/jira/browse/JBADMCON-59?page=history ] Dimitris Andreadis closed JBADMCON-59: -- Resolution: Done It should work like it does in head, I verified it using the testsuite which has been ported, too. The only difference with HEAD are due to JBossXB not being fully synchronized between 4.0 and HEAD I don't understand the comment about which jars, to copy, etc. > Port DeploymentService updates to Branch_4_0 > > > Key: JBADMCON-59 > URL: http://jira.jboss.com/jira/browse/JBADMCON-59 > Project: JBoss Admin Console > Type: Patch > Components: General Console > Versions: 1.1 alpha > Reporter: Charles Crouch > Assignee: Dimitris Andreadis > Fix For: 1.1 alpha > > Original Estimate: 1 day > Remaining: 1 day > > Porting the updates made to DeploymentService to the JBoss 4.0 branch will > enable people to deploy the Admin Console to existing 4.0.x servers, assuming > they update with the correct jars from the 4.0 branch. A comment should be > made when resolving this issue describing which updated jars are required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1362) bin/shutdown reports -S to be the default option
[ http://jira.jboss.com/jira/browse/JBAS-1362?page=history ] Dimitris Andreadis closed JBAS-1362: Resolution: Done Fix Version: JBossAS-4.0.2RC1 JBossAS-5.0 Alpha JBossAS-3.2.8 Final > bin/shutdown reports -S to be the default option > > > Key: JBAS-1362 > URL: http://jira.jboss.com/jira/browse/JBAS-1362 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.1 Final > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Trivial > Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final > > > bin/shutdown reports -S to be the default option, but it requires it to > perform the actual shutdown. Default is probably -h -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1577) white-space in ServiceMBean EVENT types
white-space in ServiceMBean EVENT types --- Key: JBAS-1577 URL: http://jira.jboss.com/jira/browse/JBAS-1577 Project: JBoss Application Server Type: Bug Components: System Service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Environment: org.jboss.system.ServiceMBean Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final Any particular reason those 4 event types contain a leading space in their name? /** The JMX notification event type for a service create state */ public static final String CREATE_EVENT = " org.jboss.system.ServiceMBean.create"; /** The JMX notification event type for a service create state */ public static final String START_EVENT = " org.jboss.system.ServiceMBean.start"; /** The JMX notification event type for a service create state */ public static final String STOP_EVENT = " org.jboss.system.ServiceMBean.stop"; /** The JMX notification event type for a service create state */ public static final String DESTROY_EVENT = " org.jboss.system.ServiceMBean.destroy"; This is obviously wrong, it is there on all branches and unless there is a good reason for *not* fixing this, I'm going to remove the space. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1365) Allow arbitrary creation of filters in ListenerServiceMBeanSupport
[ http://jira.jboss.com/jira/browse/JBAS-1365?page=history ] Dimitris Andreadis closed JBAS-1365: Resolution: Done Fix Version: JBossAS-4.0.2 Final JBossAS-5.0 Alpha JBossAS-3.2.8 Final The filter mechanism has been extended to support specification of arbitrary filters, using dynamic filter factory plugins implementing the NotificationFilterFactory interface. Three filter factories corresponding to the "standard" jmx notification filters are supplied by default in package org.jboss.system.filterfactory. For example: + + + + + + + + + + + + + + + + + + + + + > Allow arbitrary creation of filters in ListenerServiceMBeanSupport > -- > > Key: JBAS-1365 > URL: http://jira.jboss.com/jira/browse/JBAS-1365 > Project: JBoss Application Server > Type: Feature Request > Components: JMX > Environment: system/src/main/org/jboss/system/ListenerServiceMBeanSupport > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Optional > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 1 day > Remaining: 1 day > > Allow arbritrary creation of NotificationFilters when subscribing for > notifications. Currently, only NotificationFilterSupport is suppported. > We should at least add the 2 other standard filters, > AttributeChangeNotificationFilter & MBeanServerNotificationFilter > We'll do it through a factory mechanism, because each filter is initialized > in a different way, eg: > > > > bla bla > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1577) white-space in ServiceMBean EVENT types
[ http://jira.jboss.com/jira/browse/JBAS-1577?page=history ] Dimitris Andreadis closed JBAS-1577: Resolution: Done removed whitespace and fixed the comment > white-space in ServiceMBean EVENT types > --- > > Key: JBAS-1577 > URL: http://jira.jboss.com/jira/browse/JBAS-1577 > Project: JBoss Application Server > Type: Bug > Components: System Service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Environment: org.jboss.system.ServiceMBean > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final > > Original Estimate: 10 minutes > Remaining: 10 minutes > > Any particular reason those 4 event types contain a leading space in their > name? >/** The JMX notification event type for a service create state */ >public static final String CREATE_EVENT = " > org.jboss.system.ServiceMBean.create"; >/** The JMX notification event type for a service create state */ >public static final String START_EVENT = " > org.jboss.system.ServiceMBean.start"; >/** The JMX notification event type for a service create state */ >public static final String STOP_EVENT = " > org.jboss.system.ServiceMBean.stop"; >/** The JMX notification event type for a service create state */ >public static final String DESTROY_EVENT = " > org.jboss.system.ServiceMBean.destroy"; > This is obviously wrong, it is there on all branches and unless there is a > good reason for *not* fixing this, I'm going to remove the space. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1506) CDROutputStream.create_input_stream is wrong when there are deferred writes
[ http://jira.jboss.com/jira/browse/JBAS-1506?page=history ]
Dimitris Andreadis closed JBAS-1506:
Resolution: Done
Fixed in 4.x/HEAD.
> CDROutputStream.create_input_stream is wrong when there are deferred writes
> ---
>
> Key: JBAS-1506
> URL: http://jira.jboss.com/jira/browse/JBAS-1506
> Project: JBoss Application Server
> Type: Patch
> Components: IIOP service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
> Environment: This related to a jacorb bug, see:
> http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=532
> Reporter: Dimitris Andreadis
> Assignee: Dimitris Andreadis
> Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha
>
> Time Spent: 2 days
>Remaining: 0 minutes
>
> An exception is thrown when trying to insert a byte[] larger than 4000 bytes
> into any any:
> package test;
> import java.util.Properties;
> import org.omg.CORBA.ORB;
> import org.omg.CORBA.Any;
> import org.omg.CORBA.OctetSeqHelper;
> public class Test
> {
>public static final void main(String[] args)
>{
> System.out.println("*** Starting test ***");
>
> try
> {
> Properties props = new Properties();
> props.put("org.omg.CORBA.ORBClass", "org.jacorb.orb.ORB");
> props.put("org.omg.CORBA.ORBSingletonClass",
> "org.jacorb.orb.ORBSingleton");
>
> ORB orb = ORB.init(args, props);
>
> byte[] bytes = new byte[4001];
> Any any = orb.create_any();
> OctetSeqHelper.insert(any, bytes);
> }
> catch (Exception e)
> {
> e.printStackTrace();
> }
>}
> }
> ===
> [java] *** Starting test ***
> [java] [ jacorb.home unset! Will use '.' ]
> [java] [ File .\jacorb.properties for configuration jacorb not found ]
> [java] java.lang.ArrayIndexOutOfBoundsException
> [java] at java.lang.System.arraycopy(Native Method)
> [java] at org.jacorb.orb.CDROutputStream.create_input_stream(Unknown
> So
> urce)
> [java] at org.omg.CORBA.OctetSeqHelper.insert(OctetSeqHelper.java:41)
> [java] at test.Test.main(Test.java:24)
> ===
> With a byte[] of size 4000 or less, it works!
> I've noticed that the exception actually originates from the Helper class
> that comes from Sun's JDK:
> ...
> public abstract class OctetSeqHelper
> {
> private static String _id = "IDL:omg.org/CORBA/OctetSeq:1.0";
> public static void insert (org.omg.CORBA.Any a, byte[] that)
> {
> org.omg.CORBA.portable.OutputStream out = a.create_output_stream ();
> a.type (type ());
> write (out, that);
> a.read_value (out.create_input_stream (), type ());
> }
> The same class from the jacorb distribution does not perform that final
> "a.read_value(...)" line that causes the exception:
> public static void insert (org.omg.CORBA.Any any, byte[] s)
> {
> any.type (type ());
> write (any.create_output_stream (), s);
> }
> public static void write (final org.omg.CORBA.portable.OutputStream
> _out, byte[] _s)
> {
>
> _out.write_long(_s.length);
> _out.write_octet_array(_s,0,_s.length);
> }
> Also, if you look into jacorb's CDROutputStream, there is somewhere a
> hardcoded 4000 limit:
> public final void write_octet_array( final byte[] value,
> final int offset,
> final int length)
> {
> if( value != null )
> {
> if( length > 4000 )
> {
> deferredArrayQueue.add( new DeferredWriteFrame( index,
> offset, length, value ));
> index += length;
> deferred_writes += length;
> }
> else
> {
> check(length);
> System.arraycopy(value,offset,buffer,pos,length);
> index += length;
> pos += length;
> }
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBo
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1359) Remove the castor dependency for the snmp adapter, use jbossxb
[ http://jira.jboss.com/jira/browse/JBAS-1359?page=history ] Dimitris Andreadis closed JBAS-1359: Resolution: Done snmp-adaptor now uses JBossXB (MappingObjectModelFactory & GenericObjectModelFactory). There are slight differences between the 4.x and HEAD versions, due to JBossXB. Castor and all references to it have been completely removed from the 4.x/HEAD branch. It remains in the 3.x branch, mostly because we don't want to maintain yet another JBossXB port, especially the API is still in flux. snmp-adaptor.jar was moved inside snmp-adaptor.sar. The only dependency is in snmp-support.jar that contains the joesnmp classes. The latter is used also by the log4j snmp appender. There is some deprecated code in the varia module, namely pachackes: org/jboss/tm/plugins/tyrex/*.java org/jboss/jaxr/ebxmlrr/*.java org/jboss/jdo/castor/*.java > Remove the castor dependency for the snmp adapter, use jbossxb > -- > > Key: JBAS-1359 > URL: http://jira.jboss.com/jira/browse/JBAS-1359 > Project: JBoss Application Server > Type: Task > Components: JMX > Environment: varia, snmp adaptor > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final > > Original Estimate: 1 day > Remaining: 1 day > > The snmp-adaptor uses castor for generating POJO metadata classes, and for > parsing its configuration xml files. > Replacing this with JBossXB will make it a lot lighter and remove the > unecessary castor dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1579) Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes
[ http://jira.jboss.com/jira/browse/JBAS-1579?page=comments#action_12316258 ] Dimitris Andreadis commented on JBAS-1579: -- I've fixed a couple of classes: org.jboss.deployment.DeploymentState org.jboss.deployment.SerializedDeploymentInfo org.jboss.system.ServiceContext org.jboss.jmx.adaptor.snmp.agent.ManagerRecord org.jboss.management.j2ee.statistics.* org.jboss.services.deployment.metadata.* The following shouldn't probably be serializable: org.jboss.management.j2ee.J2EEManagedObject org.jboss.metadata.EjbPortComponentMetadata org.jboss.metadata.IorSecurityConfigMetadata I presume the castor stuff is gone, too. > Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes > - > > Key: JBAS-1579 > URL: http://jira.jboss.com/jira/browse/JBAS-1579 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1 > Reporter: Scott M Stark > Priority: Blocker > Fix For: JBossAS-4.0.2 Final > Attachments: SerializableHasSerialVersionUIDField.zip > > > I'm seeing incomptibilities between versions that are simply due to the fact > that Serializable/Externalizable classes are letting their serialVersionUIDs > float instead of explicitly defining them. We need to get this cleaned up. > There should not be a single Serializable/Externalizable class that does not > fix its serialVersionUID and then take responsibility for maintaining > compatibility with the indicated version. > The attached SerializableHasSerialVersionUIDField.zip unzips to create a > SerializableHasSerialVersionUIDField-index.html and > SerializableHasSerialVersionUIDField directory which is a report of all > classes in the 4.0 codebase that are not defining a serialVersionUID as they > should. > The JDK object serialization spec defines all you need to know about the apis > and contracts for object serialization: > http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/serialTOC.html > In particular, Versioning of Serializable Objects: > http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/version.html#wp9419 > talks about binary compatibility and what is available to manage this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-55) Aspectize DynamicLoginConfig
[ http://jira.jboss.com/jira/browse/JBAS-55?page=comments#action_12316262 ] Dimitris Andreadis commented on JBAS-55: Independent of how we proceed with the aspectized deployers, I think we should probably backport from HEAD to 4.x/3.x the hooks that let you pluggin a DynamicInterceptor to an XMBean, which in turn, enables the capability of attaching/detaching dynamically interceptors at runtime. Not sure why people will want to use this (but what the heck, why the'll want to use dynamic AOP, anyway :) > Aspectize DynamicLoginConfig > > > Key: JBAS-55 > URL: http://jira.jboss.com/jira/browse/JBAS-55 > Project: JBoss Application Server > Type: Task > Components: MicroContainer bus, Security > Versions: JBossAS-5.0 Alpha > Environment: org.jboss.security.auth.login > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > > > Create an interceptor based on DynamicLoginConfig module that can be attached > either statically or dynamically to any deployer, thus adding the ability to > create and remove security domains, if a META-INF/login-config.xml component > is included in the deployment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBJMX-85) Extend XMBeans to provide "default" behaviour when wrapping Standard MBeans
Extend XMBeans to provide "default" behaviour when wrapping Standard MBeans --- Key: JBJMX-85 URL: http://jira.jboss.com/jira/browse/JBJMX-85 Project: JBoss JMX Type: Feature Request Environment: jbossmx Reporter: Dimitris Andreadis Priority: Optional A problem we have we xmbeans is the verbosity of the xmbean descriptor. It is often the case that we just want to xmbean-ize an existing StandardMBean in order to use one of the xmbean features, like attribute persistence, attribute change notifications, attach an interceptor, or simply provide a richer metadata description to appear in the jmx-console. I would be great to investigate if we could somehow provide defaults, for the case of wrapping StandardMBeans, where we only need to specify what is "different" (i.e. extra or overriden somehow) from the StandardMBean attribute/operation binding, rather than having to explicitly describe the MBean interface which could be derived from the StandardMBean, anyways. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1517) SAR detection broken
[ http://jira.jboss.com/jira/browse/JBAS-1517?page=history ] Dimitris Andreadis reassigned JBAS-1517: Assign To: Dimitris Andreadis > SAR detection broken > > > Key: JBAS-1517 > URL: http://jira.jboss.com/jira/browse/JBAS-1517 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 SP1 > Environment: JBoss 4.0.1sp1 with EJB3 Preview 3 installed. Java > 1.5.0_01_b08-27 on MacOS X Tiger. > Reporter: Alain Penders > Assignee: Dimitris Andreadis > > > JBoss uses the SARDeployer for any file ending on "sar". It should only do > so for files ending on ".sar" (including the dot). > To reproduce, get joda-time-1.0.jar from http://joda-time.sourceforge.net/, > and copy the jar to the deploy directory. > JBoss will throw a DeploymentException: > 11:17:03,371 ERROR [MainDeployer] Could not initialise deployment: > file:/Users/alain/jboss/jboss-4.0.1sp1/server/lgs/deploy/joda.jar > org.jboss.deployment.DeploymentException: Failed to find > META-INF/jboss-service.xml > at > org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:533) > at org.jboss.deployment.SARDeployer.init(SARDeployer.java:140) > at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) > ... > After removing the file "org/joda/time/tz/data/Asia/Makassar" from the jar, > the exception disappears. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1517) SAR detection broken
[ http://jira.jboss.com/jira/browse/JBAS-1517?page=comments#action_12316334 ] Dimitris Andreadis commented on JBAS-1517: -- The problem is really caused by SubDeployerSupport, before SuffixOrderHelper was introduced, when we changed from a "static" list, to a dynamic list obtained by the MainDeployer, which in turn, delegated to DeploymentSorter, that didn't use dots '.' and hyphens '-' > SAR detection broken > > > Key: JBAS-1517 > URL: http://jira.jboss.com/jira/browse/JBAS-1517 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 SP1 > Environment: JBoss 4.0.1sp1 with EJB3 Preview 3 installed. Java > 1.5.0_01_b08-27 on MacOS X Tiger. > Reporter: Alain Penders > Assignee: Dimitris Andreadis > > > JBoss uses the SARDeployer for any file ending on "sar". It should only do > so for files ending on ".sar" (including the dot). > To reproduce, get joda-time-1.0.jar from http://joda-time.sourceforge.net/, > and copy the jar to the deploy directory. > JBoss will throw a DeploymentException: > 11:17:03,371 ERROR [MainDeployer] Could not initialise deployment: > file:/Users/alain/jboss/jboss-4.0.1sp1/server/lgs/deploy/joda.jar > org.jboss.deployment.DeploymentException: Failed to find > META-INF/jboss-service.xml > at > org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:533) > at org.jboss.deployment.SARDeployer.init(SARDeployer.java:140) > at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) > ... > After removing the file "org/joda/time/tz/data/Asia/Makassar" from the jar, > the exception disappears. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1517) SAR detection broken
[ http://jira.jboss.com/jira/browse/JBAS-1517?page=history ] Dimitris Andreadis closed JBAS-1517: Resolution: Done Fix Version: JBossAS-4.0.2 Final JBossAS-5.0 Alpha The suffixes have been updated to include dots (.) and hyphens (-). The suffix list now is: .deployer,-deployer.xml,aop,aop.xml,.sar,-service.xml,.rar,-ds.xml,.har,.jar,.war,.wsr,.ear,.zip,.bsh,.last For the aop deployer the aop binary needs updating > SAR detection broken > > > Key: JBAS-1517 > URL: http://jira.jboss.com/jira/browse/JBAS-1517 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 SP1 > Environment: JBoss 4.0.1sp1 with EJB3 Preview 3 installed. Java > 1.5.0_01_b08-27 on MacOS X Tiger. > Reporter: Alain Penders > Assignee: Dimitris Andreadis > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final > > > JBoss uses the SARDeployer for any file ending on "sar". It should only do > so for files ending on ".sar" (including the dot). > To reproduce, get joda-time-1.0.jar from http://joda-time.sourceforge.net/, > and copy the jar to the deploy directory. > JBoss will throw a DeploymentException: > 11:17:03,371 ERROR [MainDeployer] Could not initialise deployment: > file:/Users/alain/jboss/jboss-4.0.1sp1/server/lgs/deploy/joda.jar > org.jboss.deployment.DeploymentException: Failed to find > META-INF/jboss-service.xml > at > org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:533) > at org.jboss.deployment.SARDeployer.init(SARDeployer.java:140) > at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) > ... > After removing the file "org/joda/time/tz/data/Asia/Makassar" from the jar, > the exception disappears. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1449) Update the ServerInfo memory ops to use the jdk 5 mbeans
[ http://jira.jboss.com/jira/browse/JBAS-1449?page=history ] Dimitris Andreadis reassigned JBAS-1449: Assign To: Dimitris Andreadis > Update the ServerInfo memory ops to use the jdk 5 mbeans > > > Key: JBAS-1449 > URL: http://jira.jboss.com/jira/browse/JBAS-1449 > Project: JBoss Application Server > Type: Feature Request > Components: JMX, MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 4 hours > Remaining: 4 hours > > The memory related ops of the org.jboss.system.server.ServerInfo need to be > updated to use the jdk 5 memory mbeans. > http://java.sun.com/j2se/1.5.0/docs/guide/management/mxbeans.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1448) Update the ServerInfo listThreadDump to use the jdk 5 stack traces
[ http://jira.jboss.com/jira/browse/JBAS-1448?page=history ] Dimitris Andreadis reassigned JBAS-1448: Assign To: Dimitris Andreadis > Update the ServerInfo listThreadDump to use the jdk 5 stack traces > -- > > Key: JBAS-1448 > URL: http://jira.jboss.com/jira/browse/JBAS-1448 > Project: JBoss Application Server > Type: Feature Request > Components: MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > The org.jboss.system.server.ServerInfo mbean's listThreadDump operation which > display a tree of the system threads should be updated to use the jdk 5 > mbeans which provides stack trace information when the bean that uses the > java.lang.management.ThreadMXBean > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ThreadMXBean.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1610) Integrate jdk5 MXBeans (platform MBeans) to JBoss
Integrate jdk5 MXBeans (platform MBeans) to JBoss - Key: JBAS-1610 URL: http://jira.jboss.com/jira/browse/JBAS-1610 Project: JBoss Application Server Type: Feature Request Components: JMX Environment: common, jmx, system Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final Implement the ability to optionally run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes, thus integrating MXBeans (platform MBeans) with JBoss' own MBeans. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1614) listMessageCounterHistory returns nothing on Topics but works on Queues
listMessageCounterHistory returns nothing on Topics but works on Queues --- Key: JBAS-1614 URL: http://jira.jboss.com/jira/browse/JBAS-1614 Project: JBoss Application Server Type: Bug Components: JMS service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Environment: org.jboss.mq.server.jmx.DestinationMBeanSupport Reporter: Dimitris Andreadis Priority: Minor When JMX operation listMessageCounterHistory() is called on a Queue you get a nice html table, like the following: Queue 'ex'Date 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Total 3/24/050 0 When called on a Topic, it returns nothing -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1610) Integrate jdk5 MXBeans (platform MBeans) to JBoss
[ http://jira.jboss.com/jira/browse/JBAS-1610?page=history ] Dimitris Andreadis closed JBAS-1610: Resolution: Done Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console > Integrate jdk5 MXBeans (platform MBeans) to JBoss > - > > Key: JBAS-1610 > URL: http://jira.jboss.com/jira/browse/JBAS-1610 > Project: JBoss Application Server > Type: Feature Request > Components: JMX > Environment: common, jmx, system > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 days > Remaining: 2 days > > Implement the ability to optionally run jboss using the 'platform > MBeanServer' on jdk1.5+ runtimes, thus integrating MXBeans (platform MBeans) > with JBoss' own MBeans. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1614) listMessageCounterHistory returns nothing on Topics but works on Queues
[ http://jira.jboss.com/jira/browse/JBAS-1614?page=comments#action_12316386 ] Dimitris Andreadis commented on JBAS-1614: -- I actually brought this question here from the forums... It's not that obvious that listMessageCounterHistory() only refers to durable messages, or needs a durable subscription to get activated. (is that right?) Is there any doco for this, I could find any, other than the admin guide? "String listMessageCounterHistory(): This operation display an html table showing the hourly message counts per hour for each day of history." > listMessageCounterHistory returns nothing on Topics but works on Queues > --- > > Key: JBAS-1614 > URL: http://jira.jboss.com/jira/browse/JBAS-1614 > Project: JBoss Application Server > Type: Bug > Components: JMS service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Environment: org.jboss.mq.server.jmx.DestinationMBeanSupport > Reporter: Dimitris Andreadis > Priority: Minor > > > When JMX operation listMessageCounterHistory() is called on a Queue you get a > nice html table, like the following: > Queue 'ex'Date 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 > Total 3/24/050 0 > When called on a Topic, it returns nothing -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-86) setAttribute does not find correct method
[ http://jira.jboss.com/jira/browse/JBJMX-86?page=comments#action_12316400
]
Dimitris Andreadis commented on JBJMX-86:
-
Can you be more specific about the use-case you want to implement? Maybe,
provide an example.
> setAttribute does not find correct method
> -
>
> Key: JBJMX-86
> URL: http://jira.jboss.com/jira/browse/JBJMX-86
> Project: JBoss JMX
> Type: Bug
> Versions: JBossAS-4.0.1
> Reporter: Michael Kopp
>
>
> The setAttribute searches for a method:
> Class[] clArr = null;
> if (attribute.getValue() != null)
> {
>clArr = new Class[]{attribute.getValue().getClass()};
> }
> Method method = implementation.getClass().getMethod("set" +
> attribute.getName(), clArr);
> This means that if the value is DomElement, the class would be a
> org.apache.xerces.dom.DeferredElementImpl. But the Setter would normally
> reference org.w3c.dom.Element.
> The feature of jboss to support Element in a -service.xml is pretty useless
> this way.
> I think this should be done in the same way as Java5 does it. search for a
> method with the right name and the right number of parameters. for the found
> ones, check if the paramters are assignable. This way subclass and
> implementations of interfaces can be supported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1448) Update the ServerInfo listThreadDump to use the jdk 5 stack traces
[ http://jira.jboss.com/jira/browse/JBAS-1448?page=comments#action_12316448 ] Dimitris Andreadis commented on JBAS-1448: -- Example output when running under jdk1.3/1.4 (same as before): Total Threads: 55Total Thread Groups: 7Thread Group: system : max priority:10, demon:falseThread: Reference Handler : priority:10, demon:trueThread: Finalizer : priority:8, demon:trueThread: Signal Dispatcher : priority:10, demon:trueThread: CompilerThread0 : priority:10, demon:trueThread: RMI TCP Accept-1098 : priority:5, demon:trueThread: RMI Reaper : priority:5, demon:falseThread: GC Daemon : priority:2, demon:trueThread: RMI TCP Accept- : priority:5, demon:trueThread Group: main : max priority:10, demon:falseThread: DestroyJavaVM : priority:5, demon:falseThread Group: jboss : max priority:10, demon:falseThread: Thread-0 : priority:5, demon:trueThread: ScannerThread : priority:5, demon:trueThread: Thread-2 : priority:5, demon:trueThread: PooledInvokerAcceptor#0-4445 : priority:5, demon:falseThread: ContainerBackgroundProcessor[StandardEngine[jboss.web]] : priority:5, demon:trueThread: HSQLDB Timer @1d532ae : priority:5, demon:trueThread: JBossMQ Cache Reference Softner : priority:5, demon:trueThread: Thread-4 : priority:5, demon:trueThread: TimeoutFactory : priority:5, demon:trueThread: IdleRemover : priority:5, demon:falseThread: JCA PoolFiller : priority:5, demon:falseThread: JBossLifeThread : priority:5, demon:falseThread: http-0.0.0.0-8080-Processor1 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor2 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor3 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor4 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor5 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor6 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor7 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor8 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor9 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor10 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor11 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor12 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor13 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor14 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor15 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor16 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor17 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor18 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor19 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor20 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor21 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor22 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor23 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor24 : priority:5, demon:trueThread: http-0.0.0.0-8080-Processor25 : priority:5, demon:trueThread: http-0.0.0.0-8080-Monitor : priority:5, demon:falseThread: TP-Processor1 : priority:5, demon:trueThread: TP-Processor2 : priority:5, demon:trueThread: TP-Processor3 : priority:5, demon:trueThread: TP-Processor4 : priority:5, demon:trueThread: TP-Monitor : priority:5, demon:trueThread Group: JBoss Pooled Threads : max priority:10, demon:falseThread: ClassLoadingPool(2)-1 : priority:5, demon:trueThread Group: System Threads : max priority:10, demon:falseThread: JBoss System Threads(1)-1 : priority:5, demon:trueThread Group: JBossMQ Server Threads : max priority:10, demon:falseThread: UILServerILService Accept Thread : priority:5, demon:falseThread Group: RMI Runtime : max priority:10, demon:false > Update the ServerInfo listThreadDump to use the jdk 5 stack traces > -- > > Key: JBAS-1448 > URL: http://jira.jboss.com/jira/browse/JBAS-1448 > Project: JBoss Application Server > Type: Feature Request > Components: MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > The org.jboss.system.server.ServerInfo mbean's listThreadDump operation which > display a tree of the system threads should be updated to use the jdk 5 > mbeans which provides stack trace information when the bean that uses the > java.lang.management.ThreadMXBean > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ThreadMXBean.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.c
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1448) Update the ServerInfo listThreadDump to use the jdk 5 stack traces
[ http://jira.jboss.com/jira/browse/JBAS-1448?page=comments#action_12316449 ] Dimitris Andreadis commented on JBAS-1448: -- Example output when running under jdk5+: Total Threads: 54Total Thread Groups: 7Thread Group: system : max priority:10, demon:falseThread: Reference Handler : priority:10, demon:true, threadId:2, threadState:WAITING, threadLockName:[EMAIL PROTECTED](Native Method)java.lang.Object.wait(Object.java:474)java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)Thread: Finalizer : priority:8, demon:true, threadId:3, threadState:WAITING, threadLockName:[EMAIL PROTECTED](Native Method)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)Thread: Signal Dispatcher : priority:10, demon:true, threadId:4, threadState:RUNNABLE, threadLockName:nullThread: RMI TCP Accept-1098 : priority:5, demon:true, threadId:14, threadState:RUNNABLE, threadLockName:nulljava.net.PlainSocketImpl.socketAccept(Native Method)java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)java.net.ServerSocket.implAccept(ServerSocket.java:450)java.net.ServerSocket.accept(ServerSocket.java:421)sun.rmi.transport.tcp.TCPTransport.run(TCPTransport.java:334)java.lang.Thread.run(Thread.java:595)Thread: RMI Reaper : priority:5, demon:false, threadId:16, threadState:WAITING, threadLockName:[EMAIL PROTECTED](Native Method)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:336)java.lang.Thread.run(Thread.java:595)Thread: GC Daemon : priority:2, demon:true, threadId:17, threadState:TIMED_WAITING, threadLockName:[EMAIL PROTECTED](Native Method)sun.misc.GC$Daemon.run(GC.java:100)Thread: RMI TCP Accept- : priority:5, demon:true, threadId:20, threadState:RUNNABLE, threadLockName:nulljava.net.PlainSocketImpl.socketAccept(Native Method)java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)java.net.ServerSocket.implAccept(ServerSocket.java:450)java.net.ServerSocket.accept(ServerSocket.java:421)sun.rmi.transport.tcp.TCPTransport.run(TCPTransport.java:334)java.lang.Thread.run(Thread.java:595) ... ... ... > Update the ServerInfo listThreadDump to use the jdk 5 stack traces > -- > > Key: JBAS-1448 > URL: http://jira.jboss.com/jira/browse/JBAS-1448 > Project: JBoss Application Server > Type: Feature Request > Components: MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > The org.jboss.system.server.ServerInfo mbean's listThreadDump operation which > display a tree of the system threads should be updated to use the jdk 5 > mbeans which provides stack trace information when the bean that uses the > java.lang.management.ThreadMXBean > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ThreadMXBean.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1448) Update the ServerInfo listThreadDump to use the jdk 5 stack traces
[ http://jira.jboss.com/jira/browse/JBAS-1448?page=history ] Dimitris Andreadis closed JBAS-1448: Resolution: Done (actually the output looks a little better :) ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really. > Update the ServerInfo listThreadDump to use the jdk 5 stack traces > -- > > Key: JBAS-1448 > URL: http://jira.jboss.com/jira/browse/JBAS-1448 > Project: JBoss Application Server > Type: Feature Request > Components: MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > > The org.jboss.system.server.ServerInfo mbean's listThreadDump operation which > display a tree of the system threads should be updated to use the jdk 5 > mbeans which provides stack trace information when the bean that uses the > java.lang.management.ThreadMXBean > http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ThreadMXBean.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBJMX-87) Implement getFixedRate() and add fixed-rate notification inTimerMBean, as of JMX1.2
Implement getFixedRate() and add fixed-rate notification inTimerMBean, as of
JMX1.2
---
Key: JBJMX-87
URL: http://jira.jboss.com/jira/browse/JBJMX-87
Project: JBoss JMX
Type: Feature Request
Versions: JBossAS-4.0.0
Environment: (jmx) javax.management.timer.Timer
Reporter: Dimitris Andreadis
Priority: Minor
public Integer addNotification(String type, String message, Object userData,
Date date, long period, long nbOccurences, boolean fixedRate) throws
IllegalArgumentException
{
// [todo] implement addNotification
throw new RuntimeException("NYI");
}
public Boolean getFixedRate(Integer id)
{
//[todo] implement getFixedRate
throw new RuntimeException("NYI");
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1627) Evaluate and implement missing JSR-88 functionality
Evaluate and implement missing JSR-88 functionality --- Key: JBAS-1627 URL: http://jira.jboss.com/jira/browse/JBAS-1627 Project: JBoss Application Server Type: Feature Request Components: Deployment Service Versions: JBossAS-4.0.1 Final Environment: deployment module Reporter: Dimitris Andreadis -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1449) Update the ServerInfo memory ops to use the jdk 5 mbeans
[ http://jira.jboss.com/jira/browse/JBAS-1449?page=comments#action_12316514 ] Dimitris Andreadis commented on JBAS-1449: -- I had a look at the information provided by the jdk5 platform mbeans, wrt memory metrics, but I don't see how it is different from what the ServerInfo MBean already exposes. The reported metrics currently are: MaxMemory TotalMemory FreeMemory. I checked the above number with the numbers reported by the new MemoryMXBean and we have: Committed memory = TotalMemory MaxMemory = MaxMemory Finally MemoryMXBean reports "used" memory instead of "free" memory, but the values can be derived by subtracting from committed or total memory. What you get with the new platform mbeans is the detailed break down of memory into memory pools, plus some threhold notifications. > Update the ServerInfo memory ops to use the jdk 5 mbeans > > > Key: JBAS-1449 > URL: http://jira.jboss.com/jira/browse/JBAS-1449 > Project: JBoss Application Server > Type: Feature Request > Components: JMX, MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 4 hours > Remaining: 4 hours > > The memory related ops of the org.jboss.system.server.ServerInfo need to be > updated to use the jdk 5 memory mbeans. > http://java.sun.com/j2se/1.5.0/docs/guide/management/mxbeans.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1480) Web Console: Monitors: Errors in the log
[ http://jira.jboss.com/jira/browse/JBAS-1480?page=history ] Dimitris Andreadis reassigned JBAS-1480: Assign To: Dimitris Andreadis > Web Console: Monitors: Errors in the log > > > Key: JBAS-1480 > URL: http://jira.jboss.com/jira/browse/JBAS-1480 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.2 Final > Environment: JBoss 4.0.1 > Reporter: Anil Saldhana > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final > Attachments: FreeMemoryMonitor-service.xml > > > I see an error in the server log when using web console which is shown below. > Step 1: Create a monitor on Free Memory and call it "FreeMemoryMonitor". > Step 2: You will have a file called "FreeMemoryMonitor-service.xml" in > deploy/management/monitors. [Attached to the case]. > See error in the server log as follows: > 16:35:10,364 ERROR [MainDeployer] Could not make local copy for > file:/Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > java.io.FileNotFoundException: > /Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > at > org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:71) > at > org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:80) > at java.net.URL.openStream(URL.java:913) > at org.jboss.deployment.MainDeployer.copy(MainDeployer.java:1174) > at > org.jboss.deployment.MainDeployer.makeLocalCopy(MainDeployer.java:112 > No big deal. The error should not be thrown in a production environment with > multiple monitors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1631) Cleanup System.out from console servlets and mbeans
Cleanup System.out from console servlets and mbeans --- Key: JBAS-1631 URL: http://jira.jboss.com/jira/browse/JBAS-1631 Project: JBoss Application Server Type: Task Components: Management Service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Environment: console Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1631) Cleanup System.out from console servlets and mbeans
[ http://jira.jboss.com/jira/browse/JBAS-1631?page=history ] Dimitris Andreadis closed JBAS-1631: Resolution: Done Done > Cleanup System.out from console servlets and mbeans > --- > > Key: JBAS-1631 > URL: http://jira.jboss.com/jira/browse/JBAS-1631 > Project: JBoss Application Server > Type: Task > Components: Management Service > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Environment: console > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > > Original Estimate: 2 hours > Remaining: 2 hours > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBJMX-89) Access the interface not the implementation
[ http://jira.jboss.com/jira/browse/JBJMX-89?page=history ] Dimitris Andreadis reassigned JBJMX-89: --- Assign To: Dimitris Andreadis > Access the interface not the implementation > --- > > Key: JBJMX-89 > URL: http://jira.jboss.com/jira/browse/JBJMX-89 > Project: JBoss JMX > Type: Bug > Versions: JBossAS-4.0.1 > Reporter: Michael Kopp > Assignee: Dimitris Andreadis > > > I have a package private MBean class, the StandardMBean interface is public > though! > class WorkManager implements WorkManagerMBean > WorkManager is private > WorkManagerMBean is public > Unfortunatelly jboss jmx accesses the implementation directly, thus throwing > an IllegalAccessException. If it would access the mbean via the provided > interface this would not happen. (like jdk 5 is doing) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-88) Support primitive types
[ http://jira.jboss.com/jira/browse/JBJMX-88?page=comments#action_12316552 ] Dimitris Andreadis commented on JBJMX-88: - I suppose you mean jmx-console. If there is indeed a bug there, post it seperately. > Support primitive types > --- > > Key: JBJMX-88 > URL: http://jira.jboss.com/jira/browse/JBJMX-88 > Project: JBoss JMX > Type: Bug > Versions: JBossAS-4.0.1 > Reporter: Michael Kopp > > > If I have a property/parameter with type 'int' I have to pass it as Integer > into the setAttribute/invoke method. nevertheless, the correct method should > be found. > That does not happen right now! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1480) Web Console: Monitors: Errors in the log
[ http://jira.jboss.com/jira/browse/JBAS-1480?page=comments#action_12316515 ] Dimitris Andreadis commented on JBAS-1480: -- This is actually king-of a race condition: The console DeploymentFileRepository generates a xxx-service.xml.tmp descriptor, then immediately renames that to xxx-service.xml. Obviously the DeploymentScanner picked up the .tmp file, which is gone immediately afterwards. We should really have the ".tmp" suffix excluded by the DeploymentFilter and the default configuration in conf/jboss-service.xml (DeploymentScanner). Actually, I was surprised we don't do that already. If Scott doesn't have a problem with that, I'll add this. > Web Console: Monitors: Errors in the log > > > Key: JBAS-1480 > URL: http://jira.jboss.com/jira/browse/JBAS-1480 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.2 Final > Environment: JBoss 4.0.1 > Reporter: Anil Saldhana > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final > Attachments: FreeMemoryMonitor-service.xml > > > I see an error in the server log when using web console which is shown below. > Step 1: Create a monitor on Free Memory and call it "FreeMemoryMonitor". > Step 2: You will have a file called "FreeMemoryMonitor-service.xml" in > deploy/management/monitors. [Attached to the case]. > See error in the server log as follows: > 16:35:10,364 ERROR [MainDeployer] Could not make local copy for > file:/Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > java.io.FileNotFoundException: > /Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > at > org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:71) > at > org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:80) > at java.net.URL.openStream(URL.java:913) > at org.jboss.deployment.MainDeployer.copy(MainDeployer.java:1174) > at > org.jboss.deployment.MainDeployer.makeLocalCopy(MainDeployer.java:112 > No big deal. The error should not be thrown in a production environment with > multiple monitors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-89) Access the interface not the implementation
[ http://jira.jboss.com/jira/browse/JBJMX-89?page=comments#action_12316519 ] Dimitris Andreadis commented on JBJMX-89: - Where exactly is the problem? What's your use case? The 1.2 spec says (pp.34) "It is not a requirement for an MBean of any type to be a public class." but then, "An MBean must be of a public concrete class with a public constructor if it is to be instantiated by a JMX agent..." So, if you class is not public it can not be loaded by the jboss .sar deployment mechanism, and that's normal. I presume you could code one of your public MBeans to act as a factory and create/register the package private MBean to the MBeanServer (to be honest, I haven't tested that.) > Access the interface not the implementation > --- > > Key: JBJMX-89 > URL: http://jira.jboss.com/jira/browse/JBJMX-89 > Project: JBoss JMX > Type: Bug > Versions: JBossAS-4.0.1 > Reporter: Michael Kopp > > > I have a package private MBean class, the StandardMBean interface is public > though! > class WorkManager implements WorkManagerMBean > WorkManager is private > WorkManagerMBean is public > Unfortunatelly jboss jmx accesses the implementation directly, thus throwing > an IllegalAccessException. If it would access the mbean via the provided > interface this would not happen. (like jdk 5 is doing) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1480) Web Console: Monitors: Errors in the log
[ http://jira.jboss.com/jira/browse/JBAS-1480?page=comments#action_12316516 ] Dimitris Andreadis commented on JBAS-1480: -- kind-of > Web Console: Monitors: Errors in the log > > > Key: JBAS-1480 > URL: http://jira.jboss.com/jira/browse/JBAS-1480 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.2 Final > Environment: JBoss 4.0.1 > Reporter: Anil Saldhana > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final > Attachments: FreeMemoryMonitor-service.xml > > > I see an error in the server log when using web console which is shown below. > Step 1: Create a monitor on Free Memory and call it "FreeMemoryMonitor". > Step 2: You will have a file called "FreeMemoryMonitor-service.xml" in > deploy/management/monitors. [Attached to the case]. > See error in the server log as follows: > 16:35:10,364 ERROR [MainDeployer] Could not make local copy for > file:/Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > java.io.FileNotFoundException: > /Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > at > org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:71) > at > org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:80) > at java.net.URL.openStream(URL.java:913) > at org.jboss.deployment.MainDeployer.copy(MainDeployer.java:1174) > at > org.jboss.deployment.MainDeployer.makeLocalCopy(MainDeployer.java:112 > No big deal. The error should not be thrown in a production environment with > multiple monitors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1449) Update the ServerInfo memory ops to use the jdk 5 mbeans
[ http://jira.jboss.com/jira/browse/JBAS-1449?page=history ] Dimitris Andreadis updated JBAS-1449: - Original Estimate: 28800 (was: 14400) Remaining Estimate: 28800 (was: 14400) Fix Version: JBossAS-4.0.3 Final (was: JBossAS-4.0.2 Final) Move this for 4.0.3, it requires a bit more work. > Update the ServerInfo memory ops to use the jdk 5 mbeans > > > Key: JBAS-1449 > URL: http://jira.jboss.com/jira/browse/JBAS-1449 > Project: JBoss Application Server > Type: Feature Request > Components: JMX, MicroContainer bus > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Dimitris Andreadis > Fix For: JBossAS-3.2.8 Final, JBossAS-4.0.3 Final > > Original Estimate: 1 day > Remaining: 1 day > > The memory related ops of the org.jboss.system.server.ServerInfo need to be > updated to use the jdk 5 memory mbeans. > http://java.sun.com/j2se/1.5.0/docs/guide/management/mxbeans.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBJMX-88) Support primitive types
[ http://jira.jboss.com/jira/browse/JBJMX-88?page=comments#action_12316594 ] Dimitris Andreadis commented on JBJMX-88: - I've FAQed it here: http://www.jboss.org/wiki/Wiki.jsp?page=HowDoIPassCorrectlyPrimitiveValuesWhenInvokingOperations > Support primitive types > --- > > Key: JBJMX-88 > URL: http://jira.jboss.com/jira/browse/JBJMX-88 > Project: JBoss JMX > Type: Bug > Versions: JBossAS-4.0.1 > Reporter: Michael Kopp > > > If I have a property/parameter with type 'int' I have to pass it as Integer > into the setAttribute/invoke method. nevertheless, the correct method should > be found. > That does not happen right now! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1627) Evaluate and implement missing JSR-88 functionality
[ http://jira.jboss.com/jira/browse/JBAS-1627?page=history ] Dimitris Andreadis reassigned JBAS-1627: Assign To: Dimitris Andreadis > Evaluate and implement missing JSR-88 functionality > --- > > Key: JBAS-1627 > URL: http://jira.jboss.com/jira/browse/JBAS-1627 > Project: JBoss Application Server > Type: Feature Request > Components: Deployment Service > Versions: JBossAS-4.0.1 Final > Environment: deployment module > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBJMX-86) setAttribute does not find correct method
[ http://jira.jboss.com/jira/browse/JBJMX-86?page=history ]
Dimitris Andreadis reassigned JBJMX-86:
---
Assign To: Dimitris Andreadis
> setAttribute does not find correct method
> -
>
> Key: JBJMX-86
> URL: http://jira.jboss.com/jira/browse/JBJMX-86
> Project: JBoss JMX
> Type: Bug
> Versions: JBossAS-4.0.1
> Reporter: Michael Kopp
> Assignee: Dimitris Andreadis
>
>
> The setAttribute searches for a method:
> Class[] clArr = null;
> if (attribute.getValue() != null)
> {
>clArr = new Class[]{attribute.getValue().getClass()};
> }
> Method method = implementation.getClass().getMethod("set" +
> attribute.getName(), clArr);
> This means that if the value is DomElement, the class would be a
> org.apache.xerces.dom.DeferredElementImpl. But the Setter would normally
> reference org.w3c.dom.Element.
> The feature of jboss to support Element in a -service.xml is pretty useless
> this way.
> I think this should be done in the same way as Java5 does it. search for a
> method with the right name and the right number of parameters. for the found
> ones, check if the paramters are assignable. This way subclass and
> implementations of interfaces can be supported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1480) Web Console: Monitors: Errors in the log
[ http://jira.jboss.com/jira/browse/JBAS-1480?page=history ] Dimitris Andreadis closed JBAS-1480: Resolution: Done Fix Version: JBossAS-3.2.8 Final fixed > Web Console: Monitors: Errors in the log > > > Key: JBAS-1480 > URL: http://jira.jboss.com/jira/browse/JBAS-1480 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.2 Final > Environment: JBoss 4.0.1 > Reporter: Anil Saldhana > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.2 Final, JBossAS-3.2.8 Final > Attachments: FreeMemoryMonitor-service.xml > > > I see an error in the server log when using web console which is shown below. > Step 1: Create a monitor on Free Memory and call it "FreeMemoryMonitor". > Step 2: You will have a file called "FreeMemoryMonitor-service.xml" in > deploy/management/monitors. [Attached to the case]. > See error in the server log as follows: > 16:35:10,364 ERROR [MainDeployer] Could not make local copy for > file:/Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > java.io.FileNotFoundException: > /Users/anil/jboss-4.0.1/server/default/deploy/management/monitors/FreeMemoryMonitor-service.xml.tmp > at > org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:71) > at > org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:80) > at java.net.URL.openStream(URL.java:913) > at org.jboss.deployment.MainDeployer.copy(MainDeployer.java:1174) > at > org.jboss.deployment.MainDeployer.makeLocalCopy(MainDeployer.java:112 > No big deal. The error should not be thrown in a production environment with > multiple monitors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBMICROCONT-6) Virtual Deployment Framework
[ http://jira.jboss.com/jira/browse/JBMICROCONT-6?page=history ] Dimitris Andreadis reassigned JBMICROCONT-6: Assign To: Dimitris Andreadis > Virtual Deployment Framework > > > Key: JBMICROCONT-6 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-6 > Project: JBoss MicroContainer > Type: Task > Components: Deployment > Reporter: Adrian Brock > Assignee: Dimitris Andreadis > Fix For: JBossMC_1_0_0M2 > > > VDF - Virtual Deployment Framework > -- > VDF registry > The VDF registry acts as a helper/registry of the VDF contexts. > Each deployment is made up a top level VDF context > which might contain sub VDF contexts. > It does: > 1) Unpack subdeployments > 2) Download remote deployments > 3) Abstract packed/unpacked > 4) Allow config/registration of url handlers for things like webdav > 5) Supplying "directory" lists, cf (3) and (4) > VDF Context > The VDF context is a replacement for the DeploymentInfo > of current JBoss it holds the following information: > name - a name probably a shorted version of the url > deployer - the identified structural deployer > logicalURL - the url presented to the user > physicalURL - the url where it is really located > parentVDFContext - any parent VDF context (null when top level) > subVDFContexts - any subdeployments > classpath - the urls where classes are located > metainf - the location of any meta data > manifest - any manifest information > classloader - constructed by the classloading deployer > stats/state - e.g. when deployed, the state of the deployment, any errors, etc > There will be a set of utility methods that provide > other access, e.g. get me the metadata url for "ejb-jar.xml" > VDF Context - extensions > Each structural component can extend the VDF context > to add more information > There will also be a "slot" available for each > deployment component to associate some data with the deployment. > Context identification > -- > A top level deployment must have a structure deployer > subdeployments that are not explcitly identifed > (cf Default SubContext processing) that don't have > deployers are ignored. > Explicity identified subdeployments must have a > structure deployer > Default SubContext processing > - > All files in the root of the deployment > are treated as possible subcontexts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=history ] Dimitris Andreadis closed JBMICROCONT-4: Resolution: Done This is part of VDF Virtual Deployment Framework > Virtual File System service > --- > > Key: JBMICROCONT-4 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 > Project: JBoss MicroContainer > Type: Feature Request > Reporter: Ivelin Ivanov > Assignee: Dimitris Andreadis > Priority: Critical > Fix For: JBossMC_1_0_0M2 > > > [Adrian] > Ok, here is the design I have in mind for the new deployer aspects. > This will be part of JBoss Kernel M2 release due by end of January. > Deploying Deployers: > First you have to be able to deploy a deployer. Not an easy task as I imagine > the deployer will have dependencies on other services. The aim will be to > minimize > these dependencies to ease the problem. > Basic Architecture: > The basic architecture of the aspectized deployer is that the deployments > work with a tree of DeploymentInfo objects just like the deployers do now. > There are two major differences: > 1) The deployers do not deal with urls, they deal with VFS contexts > 2) The deployers do not create objects directly, instead they create kernel > MetaData objects and submit them to the kernel for instantiation/configuration > to obtain correct ordering of startup/shutdown > Deployment Mode: > The deployers work in two different modes > 1) The first step is to ask who recognises the VFS context. This is so > the responsible deployer can correctly decide which part of the context > takes part in the classloading and where the metadata is located. > Additionally, this may introduce subdeployments (VFS contexts) if the > deployment allows/contains them. > 2) The second step (the main chain) allows each deployer to augment the > kernel metadata with its own config. > Deployer Ordering: > Since the deployers are working on a metadata model rather than > constructing objects directly, there should be less problem with ordering. > Most ordering will be in the classloader/instantiation/config stage, > the deployer should insert that ordering in the form of dependencies in the > metadata. > The only ordering required of the deployer chain is where one deployer > needs to work on the kernel metadata output of another deployer. > Killing two birds with one stone: > The problems mentioned with the deployer requiring other services > and the first tasks performed by package specific deployers, > i.e. identifying the deployment and its structure > can be easily solved by splitting the deployers into two classes > 1) A structural component that says "I recognise this deployment and this is > how it is structured" > 2) An interpretive component that creates the kernel metadata from the > package. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1562) Expose getEntityLockMonitor in the MBean EntityLockMonitorMBean
[ http://jira.jboss.com/jira/browse/JBAS-1562?page=history ] Dimitris Andreadis updated JBAS-1562: - Original Estimate: 28800 Remaining Estimate: 28800 > Expose getEntityLockMonitor in the MBean EntityLockMonitorMBean > --- > > Key: JBAS-1562 > URL: http://jira.jboss.com/jira/browse/JBAS-1562 > Project: JBoss Application Server > Type: Feature Request > Components: EJBs, JMX > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, > JBossAS-3.2.6 Final > Reporter: Yaron Zakai Or > Assignee: Dimitris Andreadis > > Original Estimate: 1 day > Remaining: 1 day > > In order to perform proper monitoring of EJB locks, the current functionality > is not enough for the following reasons: > 1. The LockMonitor is saved per EJB name, where multiple EJBs can have the > same name. The solution should be to store it based on the jndi name. > 2. The only way to get per-EJB information is to use the printLockMonitor > method. This will create a non reasonable overhead for a real-life monitoring > solution. The solution here is to expose the method getEntityLockMonitor in > the MBean interface. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBWEB-2) Hot deployment of Tomcat
Hot deployment of Tomcat Key: JBWEB-2 URL: http://jira.jboss.com/jira/browse/JBWEB-2 Project: JBoss Web (Tomcat) Type: Bug Components: Tomcat Versions: JBossWeb-4.0.1 Reporter: Dimitris Andreadis Assigned to: Remy Maucherat Priority: Minor Tomcat waits for a "started" notification from the ServerImpl in order to start its connectors. The problem is if you hot-deploy tomcat *after* the server is started, it never gets the notification, so the connectors are not started. It probably needs to first check if Server is already started in order start immediately its connectors, or delay it, as it is done now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-33) XMBean interceptors instantiated twice
XMBean interceptors instantiated twice -- Key: JBAS-33 URL: http://jira.jboss.com/jira/browse/JBAS-33 Project: JBoss Application Server Type: Bug Components: JMX Versions: JBossAS-5.0 Alpha Environment: JBoss HEAD and probably 4.0/3.2 branches Reporter: Dimitris Andreadis Priority: Minor Interceptors specified in the top section (i.e. MBean level) of the xmbean descriptor are instantiated twice. This has probably go un-noticed for quite some time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-34) EJBDeployer getDeployedApplications is treated as attribute
EJBDeployer getDeployedApplications is treated as attribute
---
Key: JBAS-34
URL: http://jira.jboss.com/jira/browse/JBAS-34
Project: JBoss Application Server
Type: Bug
Components: EJBs
Versions: JBossAS-4.0.2 Final
Environment: org.jboss.ejb.EJBDeployer
Reporter: Dimitris Andreadis
Assigned to: Dimitris Andreadis
Priority: Optional
Although marked as an operation:
/**
* Returns the deployed applications.
*
* @jmx:managed-operation
*/
public Iterator getDeployedApplications()
{
return deployments.values().iterator();
}
it's treated as an attribute due to its name
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-34) EJBDeployer getDeployedApplications is treated as attribute
[ http://jira.jboss.com/jira/browse/JBAS-34?page=history ]
Dimitris Andreadis closed JBAS-34:
--
Resolution: Done
Fix Version: JBossAS-4.0.1 Final
JBossAS-5.0 Alpha
getDeployedApplications() renamed to listDeployedApplications() so that it
appears an an operation, not an attribute
> EJBDeployer getDeployedApplications is treated as attribute
> ---
>
> Key: JBAS-34
> URL: http://jira.jboss.com/jira/browse/JBAS-34
> Project: JBoss Application Server
> Type: Bug
> Components: EJBs
> Versions: JBossAS-4.0.2 Final
> Environment: org.jboss.ejb.EJBDeployer
> Reporter: Dimitris Andreadis
> Assignee: Dimitris Andreadis
> Priority: Optional
> Fix For: JBossAS-4.0.1 Final, JBossAS-5.0 Alpha
>
>
> Although marked as an operation:
>/**
> * Returns the deployed applications.
> *
> * @jmx:managed-operation
> */
>public Iterator getDeployedApplications()
>{
> return deployments.values().iterator();
>}
> it's treated as an attribute due to its name
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-36) jbossweb-tomcat55.sar needs commons-logging.jar
jbossweb-tomcat55.sar needs commons-logging.jar --- Key: JBAS-36 URL: http://jira.jboss.com/jira/browse/JBAS-36 Project: JBoss Application Server Type: Bug Components: Web (Tomcat) service Versions: JBossAS-5.0 Alpha Environment: deploy/jbossweb-tomcat55.sar Reporter: Dimitris Andreadis Assigned to: Scott M Stark Priority: Minor when deploying jbossweb-tomcat55.sar alone, it requires commons-logging.jar which is found in jboss-ws4ee.sar. We probably need another copy of commons-logging.jar in tomcat .sar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBJMX-2) MBeanProxyExt doesn't handle equals correctly
MBeanProxyExt doesn't handle equals correctly - Key: JBJMX-2 URL: http://jira.jboss.com/jira/browse/JBJMX-2 Project: JBoss JMX Type: Bug Environment: org.jboss.mx.util.MBeanProxyExt Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Dynamic proxies created by org.jboss.mx.util.MBeanProxyExt do not implement equals()/hashCode() correctly, so if you do a: proxy.equals(proxy) you get false. I just found out when trying to register to the MainDeployer a proxy of the EJBDeployer rather than a direct reference. Interestingly enough, class MBeanProxy (without Ext) implements similar functionality, although its equal method treats as not equal different proxy instances that point to the same mbean, which is probably wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBJMX-2) MBeanProxyExt doesn't handle equals correctly
[ http://jira.jboss.com/jira/browse/JBJMX-2?page=history ] Dimitris Andreadis closed JBJMX-2: -- Resolution: Done fixed for 4.0/HEAD > MBeanProxyExt doesn't handle equals correctly > - > > Key: JBJMX-2 > URL: http://jira.jboss.com/jira/browse/JBJMX-2 > Project: JBoss JMX > Type: Bug > Environment: org.jboss.mx.util.MBeanProxyExt > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > > > Dynamic proxies created by org.jboss.mx.util.MBeanProxyExt do not implement > equals()/hashCode() correctly, so if you do a: > proxy.equals(proxy) you get false. > I just found out when trying to register to the MainDeployer a proxy of the > EJBDeployer rather than a direct reference. > Interestingly enough, class MBeanProxy (without Ext) implements similar > functionality, although its equal method treats as not equal different proxy > instances that point to the same mbean, which is probably wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-55) Aspectize DynamicLoginConfig
Aspectize DynamicLoginConfig Key: JBAS-55 URL: http://jira.jboss.com/jira/browse/JBAS-55 Project: JBoss Application Server Type: Task Components: MicroContainer bus Versions: JBossAS-5.0 Alpha Environment: org.jboss.security.auth.login Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Create an interceptor based on DynamicLoginConfig module that can be attached either statically or dynamically to any deployer, thus adding the ability to create and remove security domains, if a META-INF/login-config.xml component is included in the deployment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-68) Added missing MdbEjb.jsp in web-console
Added missing MdbEjb.jsp in web-console --- Key: JBAS-68 URL: http://jira.jboss.com/jira/browse/JBAS-68 Project: JBoss Application Server Type: Task Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha added missing MDB page, contributed by [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-68) Added missing MdbEjb.jsp in web-console
[ http://jira.jboss.com/jira/browse/JBAS-68?page=history ] Dimitris Andreadis updated JBAS-68: --- Attachment: screenshot-1.jpg > Added missing MdbEjb.jsp in web-console > --- > > Key: JBAS-68 > URL: http://jira.jboss.com/jira/browse/JBAS-68 > Project: JBoss Application Server > Type: Task > Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha > Attachments: screenshot-1.jpg > > > added missing MDB page, contributed by [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-68) Added missing MdbEjb.jsp in web-console
[ http://jira.jboss.com/jira/browse/JBAS-68?page=history ] Dimitris Andreadis closed JBAS-68: -- Resolution: Done > Added missing MdbEjb.jsp in web-console > --- > > Key: JBAS-68 > URL: http://jira.jboss.com/jira/browse/JBAS-68 > Project: JBoss Application Server > Type: Task > Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha > Attachments: screenshot-1.jpg > > > added missing MDB page, contributed by [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-55) Aspectize DynamicLoginConfig
[ http://jira.jboss.com/jira/browse/JBAS-55?page=history ] Dimitris Andreadis updated JBAS-55: --- Component: Security Fix Version: JBossAS-4.0.1 Final JBossAS-5.0 Alpha > Aspectize DynamicLoginConfig > > > Key: JBAS-55 > URL: http://jira.jboss.com/jira/browse/JBAS-55 > Project: JBoss Application Server > Type: Task > Components: MicroContainer bus, Security > Versions: JBossAS-5.0 Alpha > Environment: org.jboss.security.auth.login > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.1 Final, JBossAS-5.0 Alpha > > > Create an interceptor based on DynamicLoginConfig module that can be attached > either statically or dynamically to any deployer, thus adding the ability to > create and remove security domains, if a META-INF/login-config.xml component > is included in the deployment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-66) MBeanProxyExt doesn't handle equals correctly
[ http://jira.jboss.com/jira/browse/JBAS-66?page=history ] Dimitris Andreadis closed JBAS-66: -- Resolution: Done > MBeanProxyExt doesn't handle equals correctly > - > > Key: JBAS-66 > URL: http://jira.jboss.com/jira/browse/JBAS-66 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.0 Final, JBossAS-3.2.6 Final > Environment: org.jboss.mx.util.MBeanProxyExt > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Fix For: JBossAS-4.0.1 Final, JBossAS-5.0 Alpha > > > see linked issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-66) MBeanProxyExt doesn't handle equals correctly
MBeanProxyExt doesn't handle equals correctly - Key: JBAS-66 URL: http://jira.jboss.com/jira/browse/JBAS-66 Project: JBoss Application Server Type: Bug Components: JMX Versions: JBossAS-4.0.0 Final, JBossAS-3.2.6 Final Environment: org.jboss.mx.util.MBeanProxyExt Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Fix For: JBossAS-4.0.1 Final, JBossAS-5.0 Alpha see linked issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
