Opened 10 years ago
Closed 10 years ago
#501 closed bug (fixed)
Bulk Checkout feature does not list documents correctly
Reported by: | jkenyon | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | 7.1.1 |
Keywords: | Cc: |
Description
When using the Bulk Checkout feature, the checkout icon appears for editing, but the documents do not appear in the ‘Bulk Checkout’ popup screen. In version 7.1.1, the column headers (Document, Version, Status) are displayed but in 7.1.2 the popup screen is blank.
Change History (5)
comment:1 Changed 10 years ago by car031
comment:2 Changed 10 years ago by car031
- Resolution set to worksforme
- Status changed from new to closed
Waiting your feedback we close this issue.
comment:3 Changed 10 years ago by jkenyon
Sorry for the delayed response...
Here is the Java console output:
Java Plug-in 11.25.2.18
Using JRE version 1.8.0_25-b18 Java HotSpot?(TM) Client VM
User home directory = C:\Users\jkenyon
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
Missing Application-Name manifest attribute for: https://devdocs.int.bgwgroup.com.au/applet/logicaldoc-enterprise-core.jar
Connect to remote server https://devdocs.int.bgwgroup.com.au/
Delete all temporary files older than Tue Jan 13 09:34:12 EST 2015
Prepared checkin folder in C:\Users\jkenyon\.logicaldoc\checkin
Invoking https://devdocs.int.bgwgroup.com.au/services/Document
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder?".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Error checking out document 4194326
port is invalid: -1
java.lang.IllegalArgumentException?: port is invalid: -1
at org.apache.commons.httpclient.protocol.Protocol.<init>(Protocol.java:183)
at com.logicaldoc.enterprise.checkin.DownloadDoc?.download(DownloadDoc?.java:40)
at com.logicaldoc.enterprise.checkin.DownloadDoc?.download(DownloadDoc?.java:71)
at com.logicaldoc.enterprise.checkin.CheckinApplet?.checkoutDocuments(CheckinApplet?.java:259)
at com.logicaldoc.enterprise.checkin.CheckinApplet?.init(CheckinApplet?.java:81)
at com.sun.deploy.uitoolkit.impl.awt.AWTAppletAdapter.init(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable?.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Invoking https://devdocs.int.bgwgroup.com.au/services/Document
Error checking out document 4194312
port is invalid: -1
java.lang.IllegalArgumentException?: port is invalid: -1
at org.apache.commons.httpclient.protocol.Protocol.<init>(Protocol.java:183)
at com.logicaldoc.enterprise.checkin.DownloadDoc?.download(DownloadDoc?.java:40)
at com.logicaldoc.enterprise.checkin.DownloadDoc?.download(DownloadDoc?.java:71)
at com.logicaldoc.enterprise.checkin.CheckinApplet?.checkoutDocuments(CheckinApplet?.java:259)
at com.logicaldoc.enterprise.checkin.CheckinApplet?.init(CheckinApplet?.java:81)
at com.sun.deploy.uitoolkit.impl.awt.AWTAppletAdapter.init(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable?.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Reload triggered
Checked out 0 documents: []
comment:4 Changed 10 years ago by jkenyon
- Resolution worksforme deleted
- Status changed from closed to reopened
comment:5 Changed 10 years ago by car031
- Resolution set to fixed
- Status changed from reopened to closed
Thanks, this stack trace is really clear and the problem is that the server port is not correctly inferred by the URL. We solved this issue but you will see this fix later in the 7.1.4. Meanwhile please access with this URL: https://devdocs.int.bgwgroup.com.au:443/
We think that this will solve your problem for the moment.
Checked and it should display correctly in the 7.1.2 also. Probably some exception occurred.
You should activate the Java console and report the output.
https://www.java.com/en/download/help/javaconsole.xml