[
https://jira.jboss.org/jira/browse/JBESB-1507?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1507:
-------------------------------------
I spent a lot of time over the weekend trying to reproduce this issue but have been
unable.
Examining the jUDDI code shows that there may be an issue with the JDBCDataStore in that
it is possible for the connection to remain null, leading to a similar issue in the log.
I am not convinced that this is the root cause as the issue is generic and I would expect
it to impact on more areas. One possible explanation could be that the error is transient
and that the attempt to handle the processing takes so long that the error becomes likely,
for example one of the responses in my testing exceeded 500K in size!
I will try to investigate this further during the week and see if anything else can be
discovered, although the impact of this has been reduced dramatically as a consequence of
the performance changes in JBESB-2155 as the business detail should no longer be requested
during normal EPR operations.
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