Contributions
Is there a limitation on number of files you can add to a review
We're using Collab 11.0 with RTC 6.0.2 integration. One user has a large changeset (@ 200 files) in his RTC work item and when he tries to create a review (using a work item state transition (eg. in progress to in review) the Collab review item gets created and linked but no files are attached to the review. We've been using the integration for quite some time without encountering this issue. Is there a limitation on the number of files that can be attached? Also in this changeset the user has a .classpath file. As no files are attached to the review (perhaps due to the number of files) should this file get attached automatically? There are no collab exclusion rules for this extension. Norm1.3KViews0likes1CommentCollab 11 SEVERE: Exception News feed
we're running collab 11 on a RHEE server with not internet access. I noted that we are getting numerous exceptions in the error.log. Anyone know how to address this? May 26, 2017 8:30:30 AM org.apache.catalina.core.ApplicationContext log SEVERE: Exception while dispatching incoming RPC call com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract com.smartbear.ccollab.datamodel.client.unversioned.INewsData com.smartbear.ccollab.datamodel .client.unversioned.IUnversionedClientApi.getNewsData() throws com.smartbear.ccollab.service.api.v7001.ServiceRuntimeException' threw an unexpected exception: java.lang.Illegal ArgumentException: unexpected url: at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:415) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:605) at com.smartbear.ccollab.rpc.RpcGwtServlet.processCall(RpcGwtServlet.java:274) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:648) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.smartbear.ccollab.AuthTicketFilter.doFilter(AuthTicketFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.smartbear.ccollab.CollabCleanupFilter.doFilter(CollabCleanupFilter.java:30) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:217) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at com.smartbear.ccollab.auth.AuthTicketValve.invoke(AuthTicketValve.java:32) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1500) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1456) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalArgumentException: unexpected url: at com.squareup.okhttp.Request$Builder.url(Request.java:163) at com.smartbear.ccollab.datamodel.client.unversioned.impl.UnversionedServerDMFactory.newNewsData(UnversionedServerDMFactory.java:406) at com.smartbear.ccollab.service.impl.unversioned.UnversionedClientApiImpl.getNewsData(UnversionedClientApiImpl.java:468) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.smartbear.ccollab.rpc.RpcGwtServlet$GwtInvocationHandler.invoke(RpcGwtServlet.java:423) at com.smartbear.util.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:28) at com.sun.proxy.$Proxy8.getNewsData(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606)1.9KViews0likes1CommentCollaborator 11
Remove host/ip info from messages sent to users as it isin my opinion useless info and can be a security concern. In our instance, the server is behind a reverse proxy. Users only know the url. The host info is registered in DNS to the proxy. Sending the actual server's host info to the user on a password reset is meaningless and negates the purpose of the proxy to hide the actual server from the end users.5.3KViews3likes0CommentsRTC not finding Collaborator
Yesterday users reported an issue with creating a review from RTC. The ccm.log reports : 2016-11-17 07:19:07,060 [ccm: AsynchronousTaskRunner-2 @@ 07:19] ERROR com.smartbear.collaborator.rtc.process - unexpected throwable com.smartbear.ccollab.client.CollabClientServerUrlConnectionException: Could not connect to a Collaborator Server at http://jazzweb.deveng.local:8080/xmlrpc/secure: Does not appear to be a running Collaborator Server at com.smartbear.ccollab.client.ClientExceptionExpert.checkDataModelCommunicationException(ClientExceptionExpert.java:1 32) at com.smartbear.ccollab.client.ClientExceptionExpert.analyze(ClientExceptionExpert.java:36) at com.smartbear.ccollab.client.LoginUtils.establishEngineConnection(LoginUtils.java:203) at com.smartbear.ccollab.client.LoginUtils.establishEngineConnection(LoginUtils.java:236) at com.smartbear.ccollab.client.LoginUtils.login(LoginUtils.java:297) at com.smartbear.collaborator.rtc.process.CollaboratorService.login(CollaboratorService.java:444) at com.smartbear.collaborator.rtc.process.CreateOrUpdateReviewTask.doUploadChangeSets(CreateOrUpdateReviewTask.java:94) at com.smartbear.collaborator.rtc.process.CreateOrUpdateReviewTask.uploadFilesInChangeSets(CreateOrUpdateReviewTask.java:88) at com.smartbear.collaborator.rtc.process.CreateOrUpdateReviewTask.transactionSucceeded(CreateOrUpdateReviewTask.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportPro xyServiceRecord.java:56) at com.sun.proxy.$Proxy3019.transactionSucceeded(Unknown Source) at com.ibm.team.repository.service.internal.AsynchronousTaskSchedulerService$4.transactionSucceeded(AsynchronousTaskSchedulerService.java:997) at com.ibm.team.repository.service.internal.AsynchronousTaskSchedulerService$4.executeTask(AsynchronousTaskSchedulerService.java:1006) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:185) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:138) at java.lang.Thread.run(Thread.java:761) Both Collab (8.5) and RTC (502) run on the same server (RHEL 6.4) and have been running without issue for some time. I've stopped restarted the server and even rebooted the server to no avail. I've got over the config but do not see any problems Anyone have any thoughts on this?1.5KViews0likes0CommentsServer virtualization and rename
We are in the process of relocating selected services into its own vlan and well as visualizing them where we can. As it is we currently have JAZZ CLM and Collab on the same host. We are virtualizing jazz servers (per app) in conjunction with moving them onto a more secure vlan . In doing so we will be moving Collab to the same vlan. We have setup the Collab and RTC integration as well. My questions: 1. Does Collab support virtualization? 2. Can we rename the collab URL to something else without data loss including links (re: jazz work item links)? Regards Norm Dignard1.2KViews0likes0CommentsCollaborator - a few users getting several notifications for same review
env Collab 8.5.8502 & IBM JAZZ 5.0.2 We added a few new users and enabled their JAZZ PA for peer reviews. Sfor some stange reason these users are getting several email notifications when a review is assigned to them for the same ticket/event. Other users don't have this issue. We have not done any customizations to Collab. From the JAZZ side , the only difference I can see compared to users in other groups is that their JAZZ project is based on IBm's OpenUp process template. All our other JAZZ users are using either Formal or Scrom process templates. Regardless of the JAZZ process used, the Coolab intergation is basically the same. So why are these users getting several emails and how to fix this? Cheers NormSolved1.9KViews0likes1CommentChangelist update not updating
Running Collab 8x integrated with JAZZ RTC 502. We have noted a few issues in collab behavior that we can't seem to resolve and it appears top be a bug on the collab side when you take a review out of the "closed" state. The changeset does not get updated regardless of what we do. Take this scenerio - In RTC a new changeset is associated witha work item (eg. a defect). Thestate of the record is then put to "in review" which(as a result of the integration with RTC) creates a Collab review record, links in the changeset from the rtc work item, and creates links between both collab and rtc records. In collab, the review is performed and if no issues found, the reviewersapprove the review and the review record is closed. On the RTC side some rework is done for whatever reason. The work item is re-opened, a newchangeset created and associated with the work item. The work item is then put back into the "in review"state. This typically updates the Collab record with then new changeset and the review is re-assessed. The above works, provided that the Collab review record is not closed. If it is closed - then this is where we seethe problem. In the closed state, nothing changes. This would be expected. If the review is re-opened, it does not matter what state transistions occur on the RTC work item side, the new changeset does not get pushed to collab. Cycling the RTC work item ( from in-review -> rework -> in-review) does nothing. If you can't use the samereview record once it was in a closed state, Ok we could live with it but youcan't create a second review record linked to the same RTC work item. (At least not in the way the current RTC-Collab integration is defined.) Has someone come across this and havesolution to this problem? Regards Norm DignardSolved1.7KViews0likes1CommentCollaborator IBM RTC & Subversion
We've intergrated RTC and Collab - adding the hooks to various work items in RTC to kick off Collaborator reviews. This works fine with the Collab record getting the changeset info from the RTC work item record. We have a new project onboarding but they want to continue to use Subversion for their scm tool. In their Eclipsework bench they'are added the RTC and Subversion plugins. The Subversionrevisions are linked to the RTC work item. When trying to create the Collab review record (by state transistion of the RTC work item to a "in review" state) the Collab record dos not get created as it fails to get the change set info. There are also some authenticiation issues (RTC to Subversion) that required manually specing the userid/password. Can Collaborator grab the Subverisons info via the RTC work item link? Note that we have multiple project areas in RTC and most are usingRTC for SCM. Is therea work around to this issue via cmd line functions that can achive this?1.1KViews0likes0CommentsRe: How install the code collaborator RTC 3.0.1 plug-in
I asked the same question from support. JAZZ_ROOT is the installation dir of the JazzTeam Server. We installed a suite of JAZZ tools under /opt/IBM. JAZZROOT in our case was /opt/IBM/JazzTeamServer/ccollab-update-site As for the com.smartbear.ccollab-profile.ini - according to support the path is not relative to the provision_profiles directory. They believe its relative to $JAZZ_ROOT/server/conf. For the server reset in - Request the server reset from the 'ccm' app (aka RTC) not JTS Admin.845Views0likes0Comments