headers
Michael Ovelgönne | 1 Jul 09:47
Picon
Picon

user logging

Hi,

I'm using the WCK to create a store. I need to know which user caused the call of a write method
(createResource, setResourceContent, ...). Where do I get this information?

best regards
Michael
Permalink | Reply | 0 comments |
headers
Edmund Urbani | 1 Jul 10:46

getting PROTOCOL_NOT_SUPPORTED error using IE and navigateFrame


Hi!

I'm trying to use an IE specific feature to access the slide server
directly as a webfolder from a html page. to do this I'm using the
javascript method navigateFrame. this does work with an old webdav
repository here (tomcat 4.1 + some slide 2.1 beta) but it won't work on
other systems with more recent tomcat+slide (tomcat 5.0.x and slide
2.1/slide 2.2pre1). i'm not sure whether the versions have anything to
do with the problem. it could also be something about tomcat's/slide's
configuration. i have not really been able to narrow it down.

the navigateFrame method returns "OK" for the old repository and
"PROTOCOL_NOT_SUPPORTED" for the other ones i tried. when it works i get
the webfolder view in a new window, when it does not the window (which i
created with javascript window.open) remains empty.

any ideas? anyone seen this kind of error before?

 Edmund
Permalink | Reply | 3 comments |
headers
Miguel Figueiredo | 1 Jul 11:19
Picon
Favicon

RE: getting PROTOCOL_NOT_SUPPORTED error using IE and navigateFrame


 Hello Edmund,

 That problem is similar with one I saw in this mailing list some months
ago. In short, it's an M$ problem in obeying HTTP specification, and
stubbornness of tomcat's team to follow a slightly different behaviour where
HTTP spec is kind of shallow.

 If it is what I'm thinking, it's a problem with the interpretation of the
expect-continue http header witch, M$ sends to the server, but instead of
waiting for de 100-continue response, it just starts to send the body of the
message. When the server receives the request with expect header, and it's
body, the server thinks the body is another HTTP request, witch obviously is
not. Result: server returns PROTOCOL_NOT_SUPPORTED http code.

 How to solve this? Turn off expect-header in M$ side or keep-alive
connections (auch).

 Hope this helps,

 Miguel Figueiredo

-----Original Message-----
From: Edmund Urbani [mailto:emu <at> liland.org] 
Sent: sexta-feira, 1 de Julho de 2005 9:46
To: slide-user <at> jakarta.apache.org
Subject: getting PROTOCOL_NOT_SUPPORTED error using IE and navigateFrame

Hi!
(Continue reading)

Permalink | Reply | 2 comments |
headers
Edmund Urbani | 1 Jul 12:20

Re: getting PROTOCOL_NOT_SUPPORTED error using IE and navigateFrame

Miguel Figueiredo wrote:

> 
>
> Hello Edmund,
>
> 
>
> That problem is similar with one I saw in this mailing list some months
>ago. In short, it's an M$ problem in obeying HTTP specification, and
>stubbornness of tomcat's team to follow a slightly different behaviour where
>HTTP spec is kind of shallow.
>
> 
>
> If it is what I'm thinking, it's a problem with the interpretation of the
>expect-continue http header witch, M$ sends to the server, but instead of
>waiting for de 100-continue response, it just starts to send the body of the
>message. When the server receives the request with expect header, and it's
>body, the server thinks the body is another HTTP request, witch obviously is
>not. Result: server returns PROTOCOL_NOT_SUPPORTED http code.
>
> 
>
> How to solve this? Turn off expect-header in M$ side or keep-alive
>connections (auch).
>
> 
>
> Hope this helps,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Radek Muzika - ANNECA | 1 Jul 12:32
Picon

How get informations about store?

Hello,

How can I determine number of files stored in store and their total size?

I tried some ways, but they were always slow, or throwed out of memory.

Thanks,
Radek
Permalink | Reply | 0 comments |
headers
Edmund Urbani | 1 Jul 15:01

Re: getting PROTOCOL_NOT_SUPPORTED error using IE and navigateFrame

Edmund Urbani wrote:

>Miguel Figueiredo wrote:
>
>  
>
>>Hello Edmund,
>>
>>
>>
>>That problem is similar with one I saw in this mailing list some months
>>ago. In short, it's an M$ problem in obeying HTTP specification, and
>>stubbornness of tomcat's team to follow a slightly different behaviour where
>>HTTP spec is kind of shallow.
>>
>>
>>
>>If it is what I'm thinking, it's a problem with the interpretation of the
>>expect-continue http header witch, M$ sends to the server, but instead of
>>waiting for de 100-continue response, it just starts to send the body of the
>>message. When the server receives the request with expect header, and it's
>>body, the server thinks the body is another HTTP request, witch obviously is
>>not. Result: server returns PROTOCOL_NOT_SUPPORTED http code.
>>
>>
>>
>>How to solve this? Turn off expect-header in M$ side or keep-alive
>>connections (auch).
>>
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peder Nordvaller | 2 Jul 00:05
Picon

Slide concurrency / "sequential-mode"

Hello,

I've deployed a clean installation of Slide 2.1 (as a webapp/.war), and 
configured it to be used with MySQL 4.1 which works like a charm. However, 
when I try to upload several files that takes a while to transfer at once to 
a directory they seem to be uploaded sequentially which hinders concurrent 
performance when many users put files. I noticed the configuration-parameter 
"sequential-mode" that was set to full in the base installation of slide:

            <!-- Can be "off", "write" and "full" -->
            <parameter name="sequential-mode">full</parameter>

But when I change it to "off" to allow concurrent puts of files, all PUT's 
done while another one is currently uploading eventually fails, with a 
Deadlock-error in the logs (see below). Is it not possible to turn off the 
sequential-mode to achieve better concurrency in Slide, or have I configured 
slide wrong in any way?

Regards, Peder

02 Jul 2005 00:00:53 - org.apache.slide.store.impl.rdbms.MySqlRDBMSAdapter - 
ERROR - SQL error 1205 on /files/test/David_o_Mickey_02.tif: Deadlock found 
when trying to get lock; Try restarting transaction message from server: 
"Lock wait timeout exceeded; try restarting transaction"
java.sql.SQLException: Deadlock found when trying to get lock; Try 
restarting transaction message from server: "Lock wait timeout exceeded; try 
restarting transaction"
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1997)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1906)
at com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:997)
(Continue reading)

Permalink | Reply | 1 comment |
headers
John MccLain | 2 Jul 00:09

test webdav connection???

I am having trouble connecting to our exchange server (microsoft) via
webdav. To isolate the problem to a library issue or an exchange
configuration issue, I wanted to try to connect to a webdav server out there
in cyberspace via the slide libraries. If I can, then I know its a server
configuration issue. If I can't then I know its a slide library issue.

Is there a webdav server anywhere that I can connect to for free???

John McClain
Senior Software Engineer
TCS Healthcare
jmcclain <at> tcshealthcare.com
(530)886-1700x235
"Skepticism is the first step toward truth"
Permalink | Reply | 0 comments |
headers
Oliver Zeigermann | 2 Jul 11:41
Picon
Gravatar

Re: Slide concurrency / "sequential-mode"

Well, the idea of the sequential mode is to avoid deadlocks. If you
turn it off, you may experience deadlocks. It depends on your RDBMS
how ofter they occur. Trying sequential mode "write" where there is at
most one write at a time, but concurrent reads are possible may be
something to try.

I started implementing a locking that only blocks concurrent writes to
the same directory, but never really finished that. Judging from my
very limited current and future time resources, I am afraid I never
will.

Oliver

On 7/2/05, Peder Nordvaller <peder.nordvaller <at> vitaminapplications.se> wrote:
> Hello,
> 
> I've deployed a clean installation of Slide 2.1 (as a webapp/.war), and
> configured it to be used with MySQL 4.1 which works like a charm. However,
> when I try to upload several files that takes a while to transfer at once to
> a directory they seem to be uploaded sequentially which hinders concurrent
> performance when many users put files. I noticed the configuration-parameter
> "sequential-mode" that was set to full in the base installation of slide:
> 
>             <!-- Can be "off", "write" and "full" -->
>             <parameter name="sequential-mode">full</parameter>
> 
> But when I change it to "off" to allow concurrent puts of files, all PUT's
> done while another one is currently uploading eventually fails, with a
> Deadlock-error in the logs (see below). Is it not possible to turn off the
> sequential-mode to achieve better concurrency in Slide, or have I configured
(Continue reading)

Permalink | Reply | 0 comments |
headers
gaLihhari | 3 Jul 20:51

Problem in retrieving property name

Hi,

I have a problem in retrieving property name of a resource.
In slide doc i got explanation about how to contruct a request of property
name by give a parameter in propfindMethod with (public static final int
        NAMES         2). But it still doesnt't work.

--------------- Taken from Slide Doc -----------------

NAMES

public static final int NAMES

    Request of all properties name.

------------------------------------------------------

Here is my code :

  HttpURL url = new HttpURL(host);
  url.setUserinfo(username, password);
  WebdavResource wdr = new WebdavResource(url);

  Enumeration resProp = wdr.propfindMethod(path, wdr.NAMES);
  while(resProp.hasMoreElements())
  {
      out.println(resProp.nextElement().toString());
  }

  wdr.close();
(Continue reading)

Permalink | Reply | 0 comments |

Gmane