search

sw360 / sw360chores

WARNING - Work in Progress - It is not Bug Free! Use with Caution. This repository contains Dockerfiles and accompanying scripts that allow deployment of sw360 via docker
Eclipse Public License 1.0
13 stars 18 forks source link

Components page is temporarily unavailable #75

Open dineshr93 opened 4 years ago

dineshr93 commented 4 years ago

Followed procedure: https://gist.github.com/roycyt/b6ddd241caf734732d1780d5de27a6ec

using latest stable release: sw360-8.1.0-M1

In the fresh install of sw360 via docker chores

We have the sw360-8.1.0-M1

image

I have imported users as well

image

and tried to login with different users as well (admin, user etc)

Error log:

Components_ErrorLog.txt

Highlights of error


 ERROR [http-nio-8080-exec-15][ComponentPortlet:1451] Problem retrieving all the Vendor names
 org.apache.thrift.transport.TTransportException: HTTP Response code: 404

ERROR [http-nio-8080-exec-15][UserCacheHolder:75] Unable to fetch user...
 java.util.concurrent.ExecutionException: org.apache.thrift.transport.TTransportException: HTTP Response code: 404

ERROR [http-nio-8080-exec-15][ComponentPortlet:1475] Could not get component total count in backend
org.apache.thrift.transport.TTransportException: HTTP Response code: 404

ERROR [http-nio-8080-exec-15][PortletRequestDispatcherImpl:303] Unable to dispatch request: java.lang.InstantiationException: bean totalRows not found within scope
ERROR [http-nio-8080-exec-15][PortletServlet:119] javax.portlet.PortletException: javax.servlet.ServletException: java.lang.InstantiationException: bean totalRows not found within scope
javax.portlet.PortletException: javax.servlet.ServletException: java.lang.InstantiationException: bean totalRows not found within scope

ERROR [http-nio-8080-exec-15][render_portlet_jsp:131] null
 java.lang.InstantiationException: bean totalRows not found within scope

Also refer https://sw360chat.slack.com/archives/C68C2RYS3/p1586447237060000

milindur commented 4 years ago

Thanks for reporting this issue. We have the same problem and are unable to install/use SW360.

mcjaeger commented 4 years ago

Hello, I am terribly sorry for not updating the issue. But is that is likely resulting from the fact that the setup uer does not have a group. Is that the case?

dineshr93 commented 4 years ago

But is that is likely resulting from the fact that the setup uer does not have a group. Is that the case?

@mcjaeger This issue still persists even after importing sample users and logging into using other ids like admin, user etc

@milindur also stated the same in https://sw360chat.slack.com/archives/C68C2RYS3/p1586447237060000

milindur commented 4 years ago

@mcjaeger When using vagrant deployment in VirtualBox, the issue does not exist. In that case I can see that the CouchDB gets populated with the SW360 databases. But when using the docker deployment, the CouchDB remains empty. I do not know if that matters, but maybe it helps to track the issue down.

I also used the example users and logged in using one of these users.

mcjaeger commented 3 years ago

needs retest

mcjaeger commented 3 years ago

should be retested after this is solved: https://github.com/sw360/sw360chores/issues/new

pro-spero commented 3 years ago

We experienced a similar issue with several components (including "Components") shown as being "temporarily unavailable". We used the docker compose from the v2 directory. The issue was with the backend container(s) not finding the servelets. The problem is with the create-slim-war-files.sh script and the extraction of .jar files. Removing the execution of the script and copying the "fat" .war files appears to solve the issue.

sw360.patch.txt