You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2009/05/02 16:37:30 UTC

[jira] Reopened: (JUDDI-224) Exception thrown when I try to use delete_service

     [ https://issues.apache.org/jira/browse/JUDDI-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt T Stam reopened JUDDI-224:
-------------------------------


Hi Richard,

I will update the build to reflect your fix. We're working on a 2.0rc7 build, where it will go into!

Thx,

--Kurt

> Exception thrown when I try to use delete_service
> -------------------------------------------------
>
>                 Key: JUDDI-224
>                 URL: https://issues.apache.org/jira/browse/JUDDI-224
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 2.0rc6
>         Environment: Linux Red Hat 9.0
>            Reporter: Richard Qualis
>            Assignee: Kurt T Stam
>             Fix For: 2.0rc6
>
>
> Whenever I try to use delete_service from the juddi-soapconsole or even from a java program written  using UDDI4J proxy (proxy.delete_service( token.getAuthInfoString(), businessServicePojo.getServiceKey()))  I get the stack trace below.  This was taken from the server log.  Any idea what this could be?
> 2009-04-28 19:31:52,449 INFO  [STDOUT] 19:31:52,449 ERROR [AbstractService] java.util.MissingResourceException: Can't find bundle for base name org.apache.juddi.i18n.MessagesBundle, locale en_US
> 2009-04-28 19:31:52,449 INFO  [STDOUT] 19:31:52,449 ERROR [AbstractService] A serious error has occured while assembling the SOAP Fault.
> java.lang.NullPointerException
> 	at org.apache.axis2.saaj.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:115)
> 	at org.apache.juddi.registry.service.AbstractService.doPost(AbstractService.java:328)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
> 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
> 	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:869)
> 	at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> 	at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> 	at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
> 	at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.