This won't work if the codebase leaves the vm, and now what happens if
the path contains a '+' ?
- Original Message -
From: "Hiram Chirino" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 24, 2001 11:54 PM
Subject: Re: [JBoss-dev] (no subject)
>
> Ok.. if finished that
Ok.. if finished that workaround. I don't know if it will break anything
else, but at least it fixes our test case. To use it, add the following
line to the top of the tstMO main() method.
FileURLSpaceFixer.install();
below is the FileURLSpaceFixer.java file.
-
im
I think if found a possible workaround...
It involves using the URL.setURLStreamHandlerFactory(..) method to implement
custom Protocol handlers for file and jar.
We just encode the URL ' ' with '+''es..
I'm going to clean up a bit and post some source in a little bit..
Regards,
Hiram
>From: "
I also ran the TestDynLoading tests against my server install that has the
space in the path and it passed without errors.
Seems like I'm doing something from the servlet that is causing problems.
I'll see if I can create a small test case to test out with.
Regards,
Hiram
>From: "Hiram Chir
Change Notes item #455065, was opened at 2001-08-24 12:20
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=455065&group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: David Jencks (d_jencks)
Assigned to: Nobody/Anonymous (nobody
User: d_jencks
Date: 01/08/24 12:09:32
Modified:.build.xml config.xml
Log:
updated build.xml and config.xml to work a little better in buildmagic and included
draft of chapter on resources
Revision ChangesPath
1.4 +16 -35manual/build.xml
Index: bu
User: d_jencks
Date: 01/08/24 12:09:33
Modified:src/docs jbossdocs.xml resource.xml
Log:
updated build.xml and config.xml to work a little better in buildmagic and included
draft of chapter on resources
Revision ChangesPath
1.24 +18 -6 manual/src/docs/jbossdocs
User: d_jencks
Date: 01/08/24 11:59:16
Modified:src/resources/jdbc-rar/META-INF ra.xml
Log:
updated ra.xml files to correspond better with previously updated drivers. In
particular got transaction isolation support into jdbc-rar.
Revision ChangesPath
1.5 +15 -1
User: d_jencks
Date: 01/08/24 11:59:16
Modified:src/resources/xa-rar/META-INF ra.xml
Log:
updated ra.xml files to correspond better with previously updated drivers. In
particular got transaction isolation support into jdbc-rar.
Revision ChangesPath
1.3 +5 -4
The error happens when I access a servlet that does a JNDI lookup of the
home interface of a session bean. (The lookup is done against the ejb's
global reference).
The servlet and ejbs are being deployed together in an ear. I'm also using
Jetty.
Regards,
Hiram.
>From: "Scott M Stark" <[EM
On the side of the RMI connection that is receiving the class that needs to
be
downloaded you should see a msg like:
[junit] Fri Aug 24 11:17:02 PDT
2001:loader:main:LoaderHandler.loadClass: lo
ading class "org.jboss.test.jrmp.ejb.AString" from
[http://succubus-si:8083/WebClassLoader@7150347/
> > javax.naming.CommunicationException. Root exception is
> > java.net.MalformedURLException: no protocol:
> > 4.0/enet-appserver/tmp/deploy/Default/lib1003.jar
> > at java.net.URL.(URL.java:473)
> > at java.net.URL.(URL.java:376)
> > at java.net.URL.(URL.java:330)
> >
Well the task was not that simple as I have not written a grammar for two
years and
yacc is an LALR parser while JavaCC is a LL parser. I had to rewrite the
grammar
to get rid of left recursion and get the operator precedence and
associativity correct.
The basics are working but I have not tested
User: starksm
Date: 01/08/24 10:28:58
Added: src/main/org/jboss/test/jbossmq/test TestSelectorParser.java
Log:
Basic tests of expressions associativty and precedence for the
org.jboss.mq.selectors.SelectorParser.
Revision ChangesPath
1.1
jbosstest/
User: starksm
Date: 01/08/24 10:28:22
Added: src/examples TestSelectorParser.java
Log:
Basic tests of expressions associativty and precedence for the
org.jboss.mq.selectors.SelectorParser.
Revision ChangesPath
1.1 jbossmq/src/examples/TestSelectorPa
I added all those options and I did not see anything extra to help figure
out why the space in the path is causing a problem..
Below is the the extra rmi logging and the exception again:
[WebContainer.Jetty] JSP: init
[WebContainer.Jetty] Started NotFoundHandler in HandlerContext[/]
Fri Aug 24
For Xerces as soon as a DTD is present it will be resolved even though
features such as
"http://apache.org/xml/features/nonvalidating/load-external-dtd"; is set to
false.
This from the Xercex FAQ:
* keep your DTD and DTD references local
* use internal DTD subsets, if possible
* load files from s
This is coming from the RMI codebase. Try adding this
-Dsun.rmi.loader.logLevel=VERBOSE
to your server and client command line to see where it is coming from.
Additional rmi debugging flags that may help are:
-Dsun.rmi.log.debug=true
-Dsun.rmi.transport.logLevel=VERBOSE
-Dsun.rmi.transport.tcp.lo
So has anybody figured out why runing JBoss 2.4.0 on Windows with spaces in
the path that is installed to causes problems???
It looks like a URL is trying to be built that has a space in it which is a
no no... Where is this problem steming from???
Here is my stack trace:
[WebContainer.Jetty]
That doesn't narrow the issue down as I can perform this type of access
pattern without
seeing a problem. What is the username/principal being passed to the
DatabaseServerLoginModule
for authentication when you see the failure?
If you have a test ear that reproduces the problem I can look into th
FWIW, I noticed that the service provider spec
defines that the config files live in a sub director "services" under
META-INF
Ie if services.xml is the services config file,
shouldn't it be located as follows:
META-INF/services/services.xml
or was the services.xml file intended as an xm
No, the codebase is no longer proportional to the server classpath. It is
always
fixed to a single url for the web service.
- Original Message -
From: "Lennart Petersson" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Friday, August 24, 2001 2:40 AM
Subject: [JBoss-de
Bugs item #454964, was opened at 2001-08-24 07:19
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=454964&group_id=22866
Category: JBossMQ
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Christian Riege (lqd)
Assigned to: Nobody/Anonymo
User: chirino
Date: 01/08/24 05:26:38
Removed: src/etc/conf/default Tag: Branch_2_4 jbossmq.properties
jbossmq.xml
Log:
These files are not need anymore as was describied in Feature Requests item #454916
___
Jboss
User: pra
Date: 01/08/24 04:54:20
Modified:src/main/org/jboss/jms/ra/client Tag: Branch_2_4
JmsConnectionFactory.java JmsSessionFactory.java
Log:
Backported jms-ra to work with new JBossMQ
Revision ChangesPath
No revision
hi everybody,
just to let you know: the backport of JBossMQ 1.0.0beta to the 2.4 JBoss
branch works really well. i've pumped about 250MB (its 500 messages of
roughly 500k each initially, these get split up internally into about
8 messages of about 1k-10k size each) of data through it w/ no
ar
Feature Requests item #454916, was opened at 2001-08-24 03:25
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376688&aid=454916&group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (
Change Notes item #454915, was opened at 2001-08-24 03:23
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=454915&group_id=22866
Category: None
Group: v2.4.1
Status: Open
Priority: 5
Submitted By: Peter Antman (pra)
Assigned to: Nobody/Anonymous (nobody)
S
Change Notes item #454914, was opened at 2001-08-24 03:22
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=381174&aid=454914&group_id=22866
Category: None
Group: v2.4.1
Status: Open
Priority: 5
Submitted By: Peter Antman (pra)
Assigned to: Nobody/Anonymous (nobody)
S
User: pra
Date: 01/08/24 03:17:26
Modified:src/bin Tag: Branch_2_4 mdbtest.sh
Log:
Added log4j.jar to mdbtest.sh to get it to work with new JBossMQ
Revision ChangesPath
No revision
No revision
1.3.2.2 +1 -0
User: pra
Date: 01/08/24 02:56:23
Modified:src/main/org/jboss/ejb Tag: Branch_2_4
MessageDrivenEnterpriseContext.java
Log:
Merged in the setRollbackOnly bugfix for MDB, also added the log4j.jar into client,
because JMS clients need that in classpath
User: pra
Date: 01/08/24 02:56:23
Modified:src/main/org/jboss/metadata Tag: Branch_2_4
MessageDrivenMetaData.java
Log:
Merged in the setRollbackOnly bugfix for MDB, also added the log4j.jar into client,
because JMS clients need that in classpath
Re
User: pra
Date: 01/08/24 02:56:23
Added: src/client Tag: Branch_2_4 log4j.jar
Log:
Merged in the setRollbackOnly bugfix for MDB, also added the log4j.jar into client,
because JMS clients need that in classpath
Revision ChangesPath
No revision
Did it ever come to a conclusion? Where do we stand today? Does the network traffic
still get bloated by a somethimes rather large URL list?
/L
===
Lennart Petersson
www.benefit.se/english
[EMAIL PROTECTED]
___
Jboss-development mail
I reproduced the error today.
back to 2.4.0.23 o.k
-> 2.4.0.26 faild
-> 2.4.0.23 o.k
-> 2.4.0 faild
fist I copied my jboss.jcml from the 23 release but in the last test I
merged my configuration into the jBoss.jcml from final release.
I will descripe the steps leading to the error more, perhaps
35 matches
Mail list logo
