jUDDI causes serverside exceptions at times, when generating a SOAP fault
message.
----------------------------------------------------------------------------------
Key: JUDDI-79
URL: http://issues.apache.org/jira/browse/JUDDI-79
Project: jUDDI
Type: Bug
Environment: OS: Fedora Core 4 -- KERNEL=2.6.11-1.1369_FC4smp
Software env: JOnAS 4.5.3 + postgresql backend + jUDDI v09.rc4
Reporter: Deepak Bhole
Assigned to: Steve Viens
If a fault has occured during request processing, jUDDI is expected to return a
SOAP fault message. However, it ends up throwing a server side exception
instead. This can be most readily produced by attempting to reproduce Bug# 78.
The exception that occurs during fault message creation:
2005-09-27 14:28:32,368 : PublisherAssertionTable.insert : ERROR: null value in
column "tmodel_key" violates not-null constraint
2005-09-27 14:28:32,369 : SetPublisherAssertionsFunction.execute :
org.postgresql.util.PSQLException: ERROR: null value in column "tmodel_key"
violates not-null constraint
2005-09-27 14:28:32,370 : AbstractService.doPost :
org.postgresql.util.PSQLException: ERROR: null value in column "tmodel_key"
violates not-null constraint
2005-09-27 14:28:32,371 : AbstractService.doPost : A serious error has occured
while assembling the SOAP Fault.
java.lang.IllegalArgumentException: invalid QName local part
at javax.xml.namespace.QName.<init>(QName.java(Inlined Compiled Code))
at javax.xml.namespace.QName.<init>(QName.java(Compiled Code))
at org.apache.axis.AxisFault.setFaultCodeAsString(AxisFault.java:422)
at org.apache.axis.message.SOAPFault.setFaultCode(SOAPFault.java:226)
at
org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:317)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled
Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
at java.security.AccessController.doPrivileged1(Native Method)
at
java.security.AccessController.doPrivileged(AccessController.java(Compiled
Code))
at javax.security.auth.Subject.doAsPrivileged(Subject.java:709)
at
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275)
at
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245)
at
org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50)
at
org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
at java.security.AccessController.doPrivileged1(Native Method)
at
java.security.AccessController.doPrivileged(AccessController.java(Compiled
Code))
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:568)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
