[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1507:
-------------------------------------
The cause of the NPE is a race within the jUDDI codebase, specifically when reading in the
business details.
The function reads in a list of services associated with the business and then tries to
fill in the details. During this time it is possible for one of the services to be
deleted and, as a consequence, the code reading in the details can fail.
The specific location of this failure is the call to setNameVector as the value of service
is null.
public BusinessService fetchService(String serviceKey)
throws org.apache.juddi.error.RegistryException
{
BusinessService service = null;
try
{
if ((serviceKey != null) && (connection != null))
{
service = BusinessServiceTable.select(serviceKey,connection);
service.setNameVector(ServiceNameTable.select(serviceKey,connection));
service.setDescriptionVector(ServiceDescTable.select(serviceKey,connection));
Vector catVector = ServiceCategoryTable.select(serviceKey,connection);
if (catVector.size() > 0)
{
CategoryBag bag = new CategoryBag();
bag.setKeyedReferenceVector(catVector);
service.setCategoryBag(bag);
}
// 'fetch' the BusinessService's BindingTemplate objects
Vector bindingVector = fetchBindingByServiceKey(serviceKey);
BindingTemplates bindings = new BindingTemplates();
bindings.setBindingTemplateVector(bindingVector);
service.setBindingTemplates(bindings);
}
}
catch(java.sql.SQLException sqlex)
{
throw new RegistryException(sqlex);
}
return service;
}
I believe that the AOP modifications disable calls to this code, at least in the majority
of cases, but I need to see if there are any other paths which exist in the current
codebase.
Odd jUDDI behaviour when under the load for longer time
-------------------------------------------------------
Key: JBESB-1507
URL:
https://jira.jboss.org/jira/browse/JBESB-1507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2.1
Environment: FC7/PostgreSQL/embedded CR1
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Priority: Critical
Fix For: 4.2.1 CP5
Attachments: server.log, server2.log.gz, standalone.zip
I have run something like performance/stress test simulating access to jUDDI by many
clients. After few runs the jUDDI started to generate exceptions.
See attached log
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira