Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silk workbench cannot be started on Windows #62

Open
RinkeHoekstra opened this issue May 3, 2016 · 5 comments
Open

Silk workbench cannot be started on Windows #62

RinkeHoekstra opened this issue May 3, 2016 · 5 comments

Comments

@RinkeHoekstra
Copy link

The silk-workbench.bat script in silk-workbench-2.7.1 tries to set the classpath to a very long list of jars. This line is too long as windows will complain "input line too long". Using a wildcard instead does not solve the issue.

Also, when setting the classpath in multiple lines, the line where the workbench is actually started fails too since it cannot find the main class.

@mit2nil
Copy link

mit2nil commented Nov 1, 2016

Hi Silk Devs,

Even I am having this issue. Long list of class names can be resolved by simply adding new line char. However, it fails in finding the class, play.core.server.NettyServer.

Can someone please suggest a workaround? I tried 2.6.x and I am getting same issue.

Nilay

@robertisele
Copy link
Member

Hi,

this is an issue of the sbt native packager that is used by the Play
framework to build the package [1]. As far as I know it only occurs on
Windows. You can workaround by starting the Play Server manually, e.g.:

java -cp "lib/*;" play.core.server.NettyServer .

Cheers,
Robert

[1] sbt/sbt-native-packager#72

On Tue, Nov 1, 2016 at 10:57 PM, Nilay Chheda notifications@github.com
wrote:

Hi Silk Devs,

Even I am having this issue. Long list of class names can be resolved by
simply adding new line char. However, it fails in finding the class,
play.core.server.NettyServer.

Can someone please suggest a workaround? I tried 2.6.x and I am getting
same issue.

Nilay


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#62 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD91kjtZgZjDY-CrgwpoMUOuiZjmBuPiks5q57XLgaJpZM4IWA3V
.

@mit2nil
Copy link

mit2nil commented Nov 3, 2016

Thanks Rob. This seems to be working. I also have one more query. After starting play server, how do I actually start a silk workbench application?

In the documentation, only information available is to run command sbt "project workbench" run

However, that is resulting in the following error:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
[info] Set current project to silk-workbench-2-7-1 (in build file:/C:/stuff/Git/museum-link-curation/record_linkage/datasets/silk-workbench-2.7.1/)
[error] Not a valid project ID: workbench (similar: silk-workbench-2-7-1)
[error] project workbench
[error]

I am not sure what I am missing here. Thanks for the help.

@mit2nil
Copy link

mit2nil commented Nov 3, 2016

By the way, same error I am observing on my virtual machine running latest Fedora distro. So this issue seems to be platform agnostic.

@Gautamshahi
Copy link

Did you solve the issue? I am getting the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants