Hi Bala,

normally Bugzilla doesn't need any additional configuration. We currently try to reproduce your problem and we will inform you as soon as we know something new. I guess you are using a self-signed SSL certificate?


Regards,

Tobias Schmitt

Hi Tobias,

We have applied SSL certificate given by a CA. This Bugzilla Server is on a public IP and only identified ports are exposed for any external interactions. I hope these design considerations have been taken into account as part of Klaros Software v3.1 which i am using for test purposes.

Regards
Bala

Hi Westphal,

I am using Bugzilla 3.6 version. As part of Issue Management configuration in Klaros , i have given a valid url and it got validated upon the click of the button "Validate the URL". The following messages are shown in the Klaros console:

ERROR - 14:42:15 - Bugzilla authentication failed (wrong user name or password).(Though user credentials are correct)
INFORMATION - 14:41:22 - Successfully connected. The URL http://bugzilla.server.net/ is valid.

The following is observed on the Tomcat Console.(What is not provided as part of the Klaros configuration for Issue Management which is throwing a Null Pointer Exception?)

SEVERE: /pages/subviews/configure/issueManagements.jspx @174,106 value="#{element.type}": Error writing 'type' on type de.verit.klaros.web.beans.wrapper.IssueManagementWrapper
j[b]ava.lang.NullPointerException
at de.verit.klaros.web.beans.wrapper.IssueManagementWrapper.setType(IssueManagementWrapper.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.el.BeanELResolver.setValue(BeanELResolver.java:108)
at javax.el.CompositeELResolver.setValue(CompositeELResolver.java:69)
at com.sun.faces.el.FacesCompositeELResolver.setValue(FacesCompositeELResolver.java:100)
at org.jboss.el.parser.AstPropertySuffix.setValue(AstPropertySuffix.java:73)
at org.jboss.el.parser.AstValue.setValue(AstValue.java:84)
at org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249)
at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:93)
at javax.faces.component.UIInput.updateModel(UIInput.java:771)
at javax.faces.component.UIInput.processUpdates(UIInput.java:703)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at com.icesoft.faces.component.ext.HtmlDataTable.processKids(HtmlDataTable.java:342)
at com.icesoft.faces.component.ext.HtmlDataTable.iterate(HtmlDataTable.java:293)
at com.icesoft.faces.component.panelseries.UISeries.processUpdates(UISeries.java:343)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIForm.processUpdates(UIForm.java:260)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081)
at javax.faces.component.UIViewRoot.processUpdates(UIViewRoot.java:728)
at com.sun.faces.lifecycle.UpdateModelValuesPhase.execute(UpdateModelValuesPhase.java:78)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at de.verit.klaros.web.beans.application.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:52)
at com.icesoft.faces.webapp.http.core.JsfLifecycleExecutor.apply(JsfLifecycleExecutor.java:18)
at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.renderCycle(ReceiveSendUpdates.java:132)
at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.service(ReceiveSendUpdates.java:74)
at com.icesoft.faces.webapp.http.core.RequestVerifier.service(RequestVerifier.java:31)
at com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer.service(PathDispatcherServer.java:24)
at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:53)
at com.icesoft.faces.webapp.http.servlet.SessionVerifier.service(SessionVerifier.java:26)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at de.verit.klaros.web.servlet.ExceptionHandlingPersistentFacesServlet.service(ExceptionHandlingPersistentFacesServlet.java:51)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:56)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:861)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1584)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 1:57:04 PM com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.

Regards
Bala

Hi WestPhal,

I also have one other question in this regard. In Bugzilla setup we have Classification / Product / Component created as part of the defect management categorization. When configuring Issue Management System in Klaros , what name should be entered for Project?

Is it the Classification or Product or Component? Ideally i would think it is the Product but i would like to know which one is considered by Klaros as Project Name? Or am i missing a point here.

Or should this be the same name as the base project that we created in Klaros?

Regards
Bala

Hi Westphal

I have also figured out in the process that the pop up which Klaros shows where the User credentials can be entered , even without entering the password , when the user hits an enter , Authentication failure message is being displayed. Can we get an alert asking the user if the credentials does not have a password before submitting the request to the server for validation?

Most importantly i would like to know what is causing the Null Pointer Exception? Is the form being displayed has some hidden parameters which is getting set to null , hence any method call set on this object reference is throwing a Null Pointer Exception? I am sure the form is wanting to capture some important information. Let me know if i am wrong.

Also when can i expect the next build release of Klaros with fixes to Bugzilla Integration. Any future date that i can revisit.

Regards
Bala

Hi Westphal,

While i wait for September 27th for the next version release , will the document contain instructions to migrate from one version to another? I am thinking about any possible schema changes that can come in and if the version needs to update the schema, will it execute a patch script on top of the existing schema or a whole new schema will get created and we redo on the entire exercise?

Anonymous account will not be entertained in our Bugzilla server as we have domain based email ids as user ids and so that is ruled out. More so with groups created and privileges set on various user identities for various admin activities in Bugzilla, probably it may not work out in my case.

Regards
Bala