Date of First Response: 2007-10-30 10:32:11
project_key: SOA

The juddi DB BINDING_TEMPLATE ACCESS_POINT_URL field is hard to
read. Also, for the table records created with an ESB server connects
to a juddi DB, the field does not contain information such as the ESB
server hostname that would be helpful in debugging.

The table has this schema:

mysql> describe BINDING_TEMPLATE;
+--------------------+--------------+------+-----+-------------------+-------+
| Field              | Type         | Null | Key | Default           | Extra |
+--------------------+--------------+------+-----+-------------------+-------+
| SERVICE_KEY        | varchar(41)  | NO   | MUL | NULL              |       | 
| BINDING_KEY        | varchar(41)  | NO   | PRI | NULL              |       | 
| ACCESS_POINT_TYPE  | varchar(20)  | YES  |     | NULL              |       | 
| ACCESS_POINT_URL   | text         | YES  |     | NULL              |       | 
| HOSTING_REDIRECTOR | varchar(255) | YES  |     | NULL              |       | 
| LAST_UPDATE        | timestamp    | YES  |     | CURRENT_TIMESTAMP |       | 
+--------------------+--------------+------+-----+-------------------+-------+
6 rows in set (0.01 sec)

The (3) records that I'm seeing created when an ESB server connects to
the DB at server startup look like this:

| 68E1E480-6C6A-11DC-A480-B20EE2C535EB |
690A7B20-6C6A-11DC-BB20-DAF5754397D8 | other |
%3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22%3F%3E%0A%3CFrom+xmlns%3Aws
a%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2004%2F08%2Faddressing%22%3E%0A+
+++%3Cwsa%3AAddress%3Ejms%3A%2F%2Flocalhost%2Fqueue%2FDataCollectorQueue%3C%2Fw
sa%3AAddress%3E%0A++++%3Cwsa%3AReferenceProperties%3E%0A++++++++%3Cjbossesb%3Ad
estination-type+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F200
7%2F01%2Fjbossesb%22%3Equeue%3C%2Fjbossesb%3Adestination-type%3E%0A++++++++%3Cj
bossesb%3Aspecification-version+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.jbos
s.com%2Fws%2F2007%2F01%2Fjbossesb%22%3E1.1%3C%2Fjbossesb%3Aspecification-versio
n%3E%0A++++++++%3Cjbossesb%3Aconnection-factory+xmlns%3Ajbossesb%3D%22http%3A%2
F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3EConnectionFactory%3C%2Fj
bossesb%3Aconnection-factory%3E%0A++++++++%3Cjbossesb%3Atype+xmlns%3Ajbossesb%3
D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Eurn%3Ajboss
%2Fesb%2Fepr%2Ftype%2Fjms%3C%2Fjbossesb%3Atype%3E%0A++++%3C%2Fwsa%3AReferencePr
operties%3E%0A%3C%2FFrom%3E%0A
| NULL | 2007-09-26 15:55:19 |

| 6924E0F0-6C6A-11DC-A0F0-ACD90A7E7F24 | 692C0CE0-6C6A-11DC-8CE0-A9C37D487E65 |
 other             | %3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22%3F%3E
%0A%3CFrom+xmlns%3Awsa%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2004%2F08%2
Faddressing%22%3E%0A++++%3Cwsa%3AAddress%3Ejms%3A%2F%2Flocalhost%2Fqueue%2FDead
MessageQueue%3C%2Fwsa%3AAddress%3E%0A++++%3Cwsa%3AReferenceProperties%3E%0A++++
++++%3Cjbossesb%3Adestination-type+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.j
boss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Equeue%3C%2Fjbossesb%3Adestination-typ
e%3E%0A++++++++%3Cjbossesb%3Aspecification-version+xmlns%3Ajbossesb%3D%22http%3
A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3E1.1%3C%2Fjbossesb%3As
pecification-version%3E%0A++++++++%3Cjbossesb%3Aconnection-factory+xmlns%3Ajbos
sesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3EConn
ectionFactory%3C%2Fjbossesb%3Aconnection-factory%3E%0A++++++++%3Cjbossesb%3Atyp
e+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbos
sesb%22%3Eurn%3Ajboss%2Fesb%2Fepr%2Ftype%2Fjms%3C%2Fjbossesb%3Atype%3E%0A++++%
3C%2Fwsa%3AReferenceProperties%3E%0A%3C%2FFrom%3E%0A | NULL               | 2007-09-26 15:55:20 | 

| 6C40C6F0-6C6A-11DC-86F0-EBE2F1464082 | 6C4BEA80-6C6A-11DC-AA80-D7397329D56E 
| other             | %3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22%3F%
3E%0A%3CFrom+xmlns%3Awsa%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2004%2F0
8%2Faddressing%22%3E%0A++++%3Cwsa%3AAddress%3Ejms%3A%2F%2Flocalhost%2Fqueue%2F
DataFilerQueue%3C%2Fwsa%3AAddress%3E%0A++++%3Cwsa%3AReferenceProperties%3E%0A+
+++++++%3Cjbossesb%3Ajava.naming.factory.initial+xmlns%3Ajbossesb%3D%22http%3A
%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Eorg.jnp.interfaces.Nam
ingContextFactory%3C%2Fjbossesb%3Ajava.naming.factory.initial%3E%0A++++++++%3C
jbossesb%3Ajava.naming.provider.url+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas
.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Ejnp%3A%2F%2F127.0.0.1%3A1099%3C%2F
jbossesb%3Ajava.naming.provider.url%3E%0A++++++++%3Cjbossesb%3Ajava.naming.fact
ory.url.pkgs+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2
F01%2Fjbossesb%22%3Eorg.jboss.naming%3Aorg.jnp.interfaces%3C%2Fjbossesb%3Ajava
.naming.factory.url.pkgs%3E%0A++++++++%3Cjbossesb%3Adestination-type+xmlns%3Aj
bossesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Equ
eue%3C%2Fjbossesb%3Adestination-type%3E%0A++++++++%3Cjbossesb%3Aspecification-v
ersion+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2F
jbossesb%22%3E1.1%3C%2Fjbossesb%3Aspecification-version%3E%0A++++++++%3Cjbosses
b%3Aconnection-factory+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fw
s%2F2007%2F01%2Fjbossesb%22%3EConnectionFactory%3C%2Fjbossesb%3Aconnection-fact
ory%3E%0A++++++++%3Cjbossesb%3Atype+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas
.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Eurn%3Ajboss%2Fesb%2Fepr%2Ftype%2Fj
ms%3C%2Fjbossesb%3Atype%3E%0A++++%3C%2Fwsa%3AReferenceProperties%3E%0A%3C%2FFro
m%3E%0A | NULL               | 2007-09-26 15:55:25 | 

It would help - for example, it woujld have helped me resolve configuration errors in setting up a failover test (JBESB-1066) if these records contained some more readable information.

It's a little better with the records created when ESB archives are deployed to an ESB server. For example, if the ESB on server "stacks2.lab.boston.redhat.com" deploys the helloworld quickstart, this record is written to the DB:


| BD738530-6C6A-11DC-8530-C493A21D0EEC | BD788E40-6C6A-11DC-8E40-C94CB3EAC20E |
 other             | %3C%3Fxml+version%3D%221.0%22+encoding%3D%22UTF-8%22%3F%3
E%0A%3CFrom+xmlns%3Awsa%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2004%2F08
%2Faddressing%22%3E%0A++++%3Cwsa%3AAddress%3Ejms%3A%2F%2Flocalhost%2Fqueue%2Fqu
ickstart_helloworld_Request_esb%3C%2Fwsa%3AAddress%3E%0A++++%3Cwsa%3AReferenceP
roperties%3E%0A++++++++%3Cjbossesb%3Ajava.naming.factory.initial+xmlns%3Ajbosse
sb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Eorg.jnp
.interfaces.NamingContextFactory%3C%2Fjbossesb%3Ajava.naming.factory.initial%3E
%0A++++++++%3Cjbossesb%3Ajava.naming.provider.url+xmlns%3Ajbossesb%3D%22http%3A
%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Ejnp%3A%2F%2Fstacks2.l
ab.boston.redhat.com%3A1099%3C%2Fjbossesb%3Ajava.naming.provider.url%3E%0A+++++
+++%3Cjbossesb%3Ajava.naming.factory.url.pkgs+xmlns%3Ajbossesb%3D%22http%3A%2F%
2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Eorg.jboss.naming%3Aorg.jnp
.interfaces%3C%2Fjbossesb%3Ajava.naming.factory.url.pkgs%3E%0A++++++++%3Cjbosse
sb%3Adestination-type+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws
%2F2007%2F01%2Fjbossesb%22%3Equeue%3C%2Fjbossesb%3Adestination-type%3E%0A++++++
++%3Cjbossesb%3Aspecification-version+xmlns%3Ajbossesb%3D%22http%3A%2F%2Fschema
s.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3E1.1%3C%2Fjbossesb%3Aspecification-
version%3E%0A++++++++%3Cjbossesb%3Aconnection-factory+xmlns%3Ajbossesb%3D%22htt
p%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3EConnectionFactory%
3C%2Fjbossesb%3Aconnection-factory%3E%0A++++++++%3Cjbossesb%3Atype+xmlns%3Ajbos
sesb%3D%22http%3A%2F%2Fschemas.jboss.com%2Fws%2F2007%2F01%2Fjbossesb%22%3Eurn%3
Ajboss%2Fesb%2Fepr%2Ftype%2Fjms%3C%2Fjbossesb%3Atype%3E%0A++++%3C%2Fwsa%3ARefe
renceProperties%3E%0A%3C%2FFrom%3E%0A | NULL               | 2007-09-26 15:57:41 | 


If you look closely, you'll see:

       stacks2.lab.boston.redhat.com         and
       quickstart_helloworld_Request_esb

in the ACCESS_POINT_URL field.