JBossDeveloper

@Andy: I couldn't get to look at this. My branch was unoperational for a while and i was dealing with failing tests.

And talking about failing tests, I'm now dealing with tests that are deploying destinations as part of the testsuite. (Tests that are outside of the JMS integration layer such as EJB, MDBs, Session.. etc). I"m now looking into implementing our config in deployment.

Just am update since i missed the meeting yesterday.

Still proceeding with the jopr integration. The only real thing left to do is to write config for the remaining core management components, queue, acceptor, Address, Bridge, BroadcastGroup, ClusterConnection,DiscoveryGroup and Divert. Theres only queue thats quite large here so hopefully i should get these done in the next couple of days. Anything i have left to do is basically adding to this config, http://anonsvn.jboss.org/repos/jbossas/branches/Branch_Hornet_Temporary_2/hornetq-int/src/resources/META-INF/rhq-plugin.xml, and any additions to the management interfaces in the future will mean only changing this file.

Theres a couple of small issues left to look at, currently jopr doesnt support the viewing of lists in returned results. basically it gives you a message saying it is unsuported and calls toString on each object in the list. I need to check with the jopr guys to see if there is a jira for this and if it is due to be fixed before as6. if not i will need to write some code to convert the results into a map.

Also i am having with issue with the manual add function. This is something that jopr has to allow users to add resources, in our case this would be a remote HornetQ instance (by default we show the local HornetQ instance in embedded). This should be simple config but it doesnt seem to work. I will post on the jopr forum for these last 2 issues.

Also i have been thinking about http://community.jboss.org/thread/147544?tstart=0, i will post on their my thoughts.

One comment on the jopr plugin, if we decide to use this for the standalone management console then we would need to move the code into our repos.

2010/02/15

  work on Stomp protocol

  - added support for missing header (no-local + durable subscription)

  - the code was also missing calls to storageManager context operations. I added it but it creates deadlock. I'll fix it tomorrow

    (i disabled the hanging tests in the trunk for the time being)

basically friday, some of the weekend and monday i have been working with the standalone jopr server. It took quite a bit getting it set up which leads me to the conclusion that for a simple standalone server it is far too heavy weight, it is a pretty nifty bit of software if you want to monitor hardware, AS, databases etc or maybe multiple instance of HornetQ but for a simple managemnt gui not what we need. I have just about managed to get it working but still have a couple of tweaks to do. Since i am running HornetQ (in the AS), the jopr server (which is basically the AS as well), an rhq agent and postgres and trying to build the app server this is really sloooowwwwww.

Since the jopr plugin is not really connected to the AS i am going to move into HornetQ trunk, this will mean a couple of extra build time dependencies but no runtime and we will ship an extra jar. We will then import this as a dependency into the AS for the admin console. If anyone has any issues with this please shout.

Ok let me explain.

The AS has the admin-console, this is an embedded version of jopr that uses the AS jopr plugin. it is a web app with a subset of the functionality of jopr. In this scenario the HornetQ plugin connects to the JMX server InVM and exposes our management beans.

The jopr server is a fully functional server. This consists of the jopr server and a number of agents. Each agent runs on a different host and updates the jopr server with its plugins state, metrics, operations etc. In this scenario the hornetq plugin runs in the agent and connects remotely via a jmx connector to the hornetq server. Currently i am troubleshooting getting this to work properly but i have had some help from the rhq guys and hopefully I should have this working today.

Jon, is a downstream product built on jopr.

- Fixing tests on the AS6 testsuite. I can get MDB2 to work fine now. I'm having some weird issues with Proxies.

- Found a bug on MapMessages as it was affecting an user's performance.

The jopr plugin is just about finished. I have tested all the operations and it works in ther embedded admin console and the standalone jopr server. All i need to do is:

1. Add the changes that have been proposed for creating connection factories. I will do this now in hornetq trunk if no one else is doing it.

2. Theres a classloader issue which isnt actually jopr as it happens with jconsole as well, Jeff was looking at this.

hopefully should get done it wrapped up today, maybe tomorrow.

Next i will fix https://jira.jboss.org/jira/browse/HORNETQ-285