Package-manager fails to look for sun/nio/cs/US_ASCII$Encoder #1432
Comments
|
Can you describe how you updated eXist-db please? |
|
Sure, same way I did since 2.1 or so: drag old exist from |
|
Silly question, but are you sure the version of Java it is using is Java 8? |
|
from earlier in the same log: Can't check in monex, since that hasn't been updated yet. But i don't see how another java version could have been silently installed on the system. |
|
@duncdrum I am not sure what is happening just yet. However the Java you are using makes me very suspicious, as it is not the standalone JRE or JDK but whatever is bundled with the Internet Applet Plugin. Rather, I think your Java path should look like: or the JRE equivalent. |
|
yes i noticed that line as well, hence i updated java JDK, but that still doesn't explain why after the upgrade from 3.1 if would look for a different java path: |
|
@duncdrum In the 3.2.0 release, nothing has changed in the installer or App since 3.1.1. So I am not sure what is going on here. I think that even though you have installed JDK, you need to have a log like you posted above that shows the JDK is used an not the Applet plug-in. |
|
@adamretter and where would I change the path so exist starts up with |
|
@duncdrum I am not certain, I would imagine you would need to set it in your users profile ( |
|
nope, i have set $JAVA_HOME and it persist after reboots. Yet, exist.app insists on looking in the wrong location. Uninstalled the JAVA browser plug-in and now I we are at "Can't find JAVA RUNTIME ENVIRONMENT" error during start. Doing a clean install from back up now, i have given up trying to figure out where the wrong path is coming from. |
|
I am lost here:
good
bad
|
|
FYI, I'm also experiencing similar weird issues, investigating too. FYI, the instructions you linked to were just for deleting the JRE. That page does link to instructions for deleting the JDK - see http://docs.oracle.com/javase/8/docs/technotes/guides/install/mac_jdk.html. |
|
The instructions for JDK are in the link further down on that page: more java fun (now with 3.1.1 holding off 3.2 for now).
👍 JDK ftw
😞 JRE @adamretter I don't think the path is wrong, its the default path for the JRE on macOS as far as i can tell. Something that didn't need it before seems to require JDK, not sure what and where though. |
|
@duncdrum I had all the same issues as you on my Mac system. Updating to the latest monex (0.9.8), released today, helped somewhat. (To ensure it installed on startup, I wiped my data directory, and put the new version in my autodeploy directory.) But still, when starting up via the .app or via java -jar start.jar, I noticed that monex's Console pane would say "Disconnected". I finally had a breakthrough starting eXist via |
|
@joewiz 3.1.1 works fine for me. My java foo is too feeble to have any idea where the problem might come from. If anybody wants to me to reproduce or try something let me know. OK tried on my other machine on eXist 3.2 using i could open package-manager after logging into dashboard AND monex. No warnings or errors in the logs. |
|
As which user is exist running? Please could you dump the environment settings for this user? |
|
So just to see what is happening I attempted to install I then double-clicked eXist-db in the "Applications" folder and it installed as expected. I then used the eXist icon on the mac:OS tool bar to view the So all appears to have installed fine. I note my eXist there also uses the Java in /Library/Internet So I don't see any problems there. I am also able to visit the eXist Dashboard and click the Monex icon and don't see any problems. Monex opens just fine here. So, er... I am not sure what the problem @duncdrum is experiencing. I think @wolfgangmm and @joewiz might have some seem similar things? |
|
@adamretter monex opens fine for me to, package-manager is causing problems (see title above), there are no available packages, and it takes multiple attempts to log in to, logging into monex first seems to help with logging into package-manager afterwards, although i don't see why that should be the case, logging into dashboard should be sufficient. @dizzzz I m not following do you mean exist user account, or macOS user account? Do you want my bashprofile? environment.plist? etc/usr/...? |
|
Run 'set' as the user that runs existdb |
|
Ok, thnx. Nothing special i'd say (actually running X11??) |
|
yes I still need X11, i highly doubt it has anything to do with the issue at hand. To sum up:
can we label this as a bug, since i m not the only one experiencing this? |
|
Ah no that was not the intention of my X11 question, i was only wondering :) |
|
@adamretter @duncdrum I'm not seeing any errors related to Dashboard > Package Manager, except that the "Remember Me" checkbox has to be selected for the Package Manager to come up at all; if it's not selected, Package Manager fails to come up at all, though there is no indication of an error in exist.log. The problem I have with 3.2.0 besides the quitting problem (#1431) involves running monex — not opening it up, but specifically with going to the Remote Console pane. Remote Console should come up as "Connected", as shown here under 3.1.1: But with 3.2.0 or develop, it shows up as "Disconnected" (even after shift-reload), and with each request like this, exist.log shows error messages about I'm using Java 8u121 with macOS 10.12.4. In all cases, I'm starting up from a completely blank database - using |
|
@joewiz ah i misunderstood your earlier post, but in both cases we get errors related to console and. |
|
@duncdrum Great, thanks for spotting that shared error message related to |
|
Here is a new variation of the theme. Start Exist3.2 using mouse:, use menu bar to start monex (log-in). SO far so good, now use menu-bar to open dashboard: Result no dashboard. in addition to @joewiz's |
|
it looks like that the std JRE jar files are (yet?) missing on the class path or so...... |
|
@dizzzz beats me, works fine for 3.1.1 or when starting from CLI. Is there a better way to see where eXist is looking for things? |
|
Hi duncdrun, |
|
@duncdrum: Restarting offered the same situation. I'm not a terminal-guru, neither a good XQuery-programmer, so tell me when I do things wrong. When I put eXist as a startup-item (in the system-preferences), it start automatically. I've noticed that the "remember me" selection does weird things. When I don't select "remember me", I can go to the User-manager, create and see the users without bugs. Without selecting "remember me" I can create collections in db/apps/ and I can save documents in that collection. When I select "remember me" while I login as admin, I can't make new collections and can't change get in the user-manager anymore! (see bug-screendump in previous message) |
|
Hi @Rondiekon, it looks that
|
|
@duncdrum, that doesn't seem to work: |
|
I don't think |
|
@dizzzz, @duncdrum , quote from duncdrum's link says:
|
|
How is user manager running now? |
|
@duncdrum Ah,...... Now I see, it is a bit confusing! That path is actually not an macOS application, but just eXist-db extracted in /Applications/eXist :-) in 2012 we did not have a DMG/.app in place... |
|
@duncdrum ,Same issues, if I select "remember me", I get the bug as before. If I login with "remember me" deselected I can get into user manager and edit. I also can make new collections |
|
@Rondiekon Glad it worked (sort of). You seem to be suffering from this issue, which is not the one Joe and I are experiencing since 3.2. @dizzzz would you mind making a PR to the documentation repo? In the brave new world of homebrew this might need clarification. |
|
@Rondiekon no bother at all. I found two related (??) bugs that I can reliably reproduce in 3.2 and fix by downgrading to 3.1.1. The user-manager(remember_me) issue appeared between 2.x and 3.x, it doesn't seem to be affected by the method of installation. But should you feel inquisitive by all means compile away and see if you can help track the problem down. The dashboard ticket hasn't seen much action since Aug 2016. |
|
@duncdrum OK,thx. I let the bugs as what it is. I have my focus on learning XQuery, XForms & XSLT/XSL-FO. I've been testing-software for several vendors in the past, mostly after reporting a BUG. Best regards, Ron |
|
Poking around bit further, I m beginning to think that the problem mentioned here might be relevant. |
|
Whenever I follow up on errors in the logs I end at problems with path expressions (Java classpath or xpath). I believe that something is converting the path string to something illegal on macOS, maybe the whitespace in the default JRE location is partially to blame. There is another problem with persistent log-in, maybe its related I can't tell. But together they make 3.2 unuseable with frequent crashes and hangs. I really need that debug system back up and running so if nobody has any more ideas to try out, i ll revert to 3.1.1 soon. |
|
Interesting theory, worth probing! My workaround for using 3.2.0 on macOS has been to start via bin/startup.sh rather than start.jar or eXist-db.app. This way, I have none of the problems I had with monex or shutting down. I miss the menu bar and think we should try to restore the wrapper's functionality on macOS, but this workaround has allowed me to use 3.2.0+. |
|
@joewiz ok i just made a clean install of 3.2 using homebrew.
dashboard will start, but changing admin pw via user-manager doesn't work (s.a.), package-manager loads with a delay but can't find any packages (see op) shut down, auto-quite hanging process, reboot.
no idea whats going on this used to work before.
|
|
Updated from 3.1.1 to 3.3 via bintray .dmg installer. Initial run
Subsequent run (relog OS user)
Errors
Subsequent run (reboot)
I can live with having to force-quite exist after accessing monex, which still works despite the errors, on my test system for a while. Somehow starting monex, causes errors related to sorting (JulianCalendar, ASCII$Encoder, Comparators$NaturalOrderComparator) which more or less crash exist (no more collection, packages, or graceful quitting) progress i guess |
|
I have an idea: eXist-db/dashboard#57 |
|
@duncdrum the dashboard does not ship with any Java libraries, so the warning has no effect. The only package which does include Java jars is monex. But I already tested removing those altogether as well as copying them into |
|
@wolfganmm to bad, still does anything speak against adding sem-ver min 3.0 to the default apps, 2.x doesn't check for sem-ver iirc, and less false warnings can only help in locating the source of the problem? |
|
no, for the current version of those apps, semver-min 3.0 should be fine. |
|
@duncdrum Thanks for reporting your experience with 3.3.0. @wolfgangmm Since this illusive issue began sometime after the 3.1.1 release and during the development cycle of 3.2.0, could one narrow down the source by checking out each commit and building/performing the startup-with-wrapper-then-open-monex-console-then-try-quitting test? This would take some time, as there are 113 commits between 3.1.1 and 3.2.0, but at least this is a finite number. Do you think this would help? If so, I could get started. |
|
🥁 #1490 |
|
#1490 fixes the Mac app-related instability issues for me. Looking forward to hearing if it does for you too! |
|
throwable wrapped 🖨 is no more 🎉 |
What is the problem
After upgrade to eXist 3.2.0 via dmg installer, the package-manager (sp?) can't find available packages causing the following error:
2017-05-03 12:06:15,259 [qtp430944645-64] WARN (LogFunction.java [writeLog]:196) - (Line: 152 /db/apps/dashboard/plugins/packageManager/packages.xql) Error while retrieving app packages: sun/nio/cs/US_ASCII$Encoderfull log
after logging in the following lines seem relevant from the log
What did you expect
A working package manager.
Describe how to reproduce or add a test
Update exist, select open dashboard, log-in (with remember me unticked), click package-manager. (since i just filed another issues this error is happening after rebooting, so not just on initial run)
Context information
Please always add the following information
The text was updated successfully, but these errors were encountered: