Hi, Ryan, The strangest thing is some computers that worked before all stopped working. There were no changes to the server and no change to the clients (4 total). Some of the clients are in the same subnet within the firewall, some of them are out side of the firewall on the internet.
Is there any way to enalbe some debugging feature so that we can verify what the problem might be? Please see my reply inline too. Thanks -Jimmy > [EMAIL PROTECTED] wrote: >> Hi, >> >> We have been using piggybank/semantic bank as our social bookmarking >> tools >> and they had been working greatly until several weeks ago. > > Do you have any indication of what changed several weeks ago? > -- JD: Nothing was changed in the configuration. But the server's NIC card got some errors once and I need to reboot the server and the NIC card started working again. Not sure if that is related >> We found out now we can only save the bookmarks to our local bank >> correctly. > > Local Piggy Bank or local Semantic Bank? -- JD: Local Piggy Bank > >> Even though we see some success message box if we resave all >> our local banks info into the remote semantic bank, nothing can be saved >> there. In the tomcat logs, we can see the following error messages: >> >> [ERROR] Failed to add data to corpus >> http://127.0.0.1:8080/account#accountCorpus#proudbug >> org.openrdf.sesame.sail.SailUpdateException: java.io.IOException: >> Invalid >> argument >> at >> org.openrdf.sesame.sailimpl.nativerdf.NativeTransaction.addStatement(NativeTransaction.java:231) >> at >> org.openrdf.sesame.repository.DefaultTransaction.add(DefaultTransaction.java:335) >> at >> org.openrdf.sesame.repository.DefaultTransaction.add(DefaultTransaction.java:367) >> at >> org.openrdf.sesame.repository.DefaultTransaction.add(DefaultTransacti > > That's an invalid URL. That may not be your actual issue, but I should > point out that you can't have two hashes in the fragment part of a URI. -- JD: I didn't notice this two hash problem. I will check why this occured. >> The strange thing is we can still save to semantic from one of the >> computers with the same user account(this computer is in the same subnet >> as the server and are not DHCPed). On last Saturday, I downloaded >> Firefax >> 2.0 and PiggyBank 3.0.1 and can successfully publish a bookmark to >> semantic bank, but today it can no longer publish with the same error. > > I'm having a hard time nailing down what you're describing. Could you > perhaps separately describe the two computers and their environments, > and their success or failure with publishing to SemBank? > -- JD: I tried again today and noticed that the computer that worked on Sunday stopped working today. So far none of our computers are working. All the computers have piggybank 3.0.1 installed. >> I guess the problem might be network address related but cannot confirm. >> At first I thought DHCP may have caused the problem, but after I >> disabled >> that, problem still exists. I remember there was some Java API problem >> regarding DHCP before. > > Network-related problems are more likely to have to deal with firewalls > or proxies. > >> The technical environment is: >> Semantic Bank: Fedora 4, Tomcat 5.0.28, LongWell-2.4.1 >> Piggy Bank: Windows XP SP2, Firefox 1.5-2.0, PiggyBank 3.0.1, JDK 1.4.2, >> JDK 1.5 >> >> Has anyone encountered similar problem before? We didn't change our >> semantic bank version/configuration since it started working 2-3 months >> ago. > > -- > Ryan Lee [EMAIL PROTECTED] > MIT CSAIL Research Staff +1.617.253.5327 > http://simile.mit.edu/ > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
