Nothing been changed, user getting started to not able to import model into Rhapsody DM project area
![]()
Env:Rhapsody DM 4.x, Websphere Server v8.0.x, Derby DB, Websphere Federated repository.
No change done on the User01 both for license and permission and project role info.
Later using User01 to add more user accounts in Websphere and JTS, and then assigned the floating license to each user account.
After repeating user login/logout for each new added user account successfully.
Login DM by User01 again and start to import model into the same project area, Client browser showing error message like " this user has no permission for this operation"
In dm.log, error message is "com.ibm.xtools.rmps.frontservice.jfsclient.RmpsRuntimeException: 400 (ERROR) :RHAPERR:invalidPermissions
"
In my understanding, only if design manager license is not granted or required roles are not assigned to the user, the import operation could be rejected.
Strange thing is, In this case, User01 has ever successfully imported a model into the same project area and no change been done on the User01 info itself. why after creating more user, suddenly importing operation is failed for User01?
Anyone can give me some hints?
Where I need to take a check?
What could be the possible causes?
Thank You
|
15 answers
![]()
I paste the stack info here, can you see some issues below?
com.ibm.xtools.rmps.frontservice.jfsclient.RmpsRuntimeException: 400 (ERROR) :RHAPERR:invalidPermissions
at com.ibm.rational.carter.util.PermissionValidator.validateUserPermission(PermissionValidator.java:48)
at com.ibm.rational.carter.publish.PublishFrontService.rmpsPost(PublishFrontService.java:217)
at com.ibm.xtools.rmps.frontservice.RmpsFrontService.rmpsService(RmpsFrontService.java:366)
at com.ibm.xtools.rmps.frontservice.RmpsFrontService.doPost(RmpsFrontService.java:548)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:176)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:281)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1640)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1214)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:926)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1023)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:895)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1049)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:643)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659)
|
![]()
Hi Jin,
Where all the steps done in the same browser session? If so, can you delete your browser cache/cookies (or using a different browser) and then try again? Dan |
![]()
Hi, Daniel
Thanks for your suggestion.
But unfortunately things are not getting improved ever after deleting the cache/cookies of the browser or start a new window or restart the server.
As all the created user accounts could be successfully login/logout, I think the user info stored in WAS is correct. Just JTS couldn't grant the user with the permission to import model though it should be supposed to as the user had ever imported a model successfully.
Hi, Daniel, can you explain some info regarding below? Thank you in advance.
(1) Whether it's JTS used for handling floating licenses? I have assigned totally 5 floating licenses to 13 users. It shouldn't be an issue, I believe.
(2) The problem was first time detected right after creating a group of users and doing login/logout for each new created users successfully.
Do you think the database info is possibly not correct or partially broken?
Is there a way to check whether the database information is correctly stored or not?
(3) Do you think I need to configure JTS again(re-setup)? In that case, whether I need to register all the user info from right beginning?
Next time, I'm thinking to try the import on another project area.
Right now I really don't have any idea to understand what actually could be the root cause? Any point else you can suggest me to check or test?
Thank You
Best Regards
|
![]()
Hi, Daniel
If you could recommend someone who is the expert on this area, I want to know according to the log tracing I pasted above, whether you can judge the runtime exception was occurred inside of JTS or it was reported by the registered RDM(Rhapsody DM) application?
I think the license info is managed by JTS, but the user roles to a specific Project Area should be managed on RDM.
If User doesn't have required license or hasn't been assigned with the required project role, (import) operation permission error would happen. So I want to first make sure what application reported the permission error.
Thank You for kind help
Regards
|
![]()
Hi Jin,
Can you please try to assign the license only for 5 users and retry (after restaring the server)? Maybe you send us all the logs from the server? Thanks. Sasha. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.