Hi All,
This is the full thread dump which I get.
Can Anybody help me understand this dump??
Full thread dump Java HotSpot(TM) Server VM (1.4.0_01-b03 mixed mode):
"JNP Server" prio=1 tid=0x0x877e2c8 nid=0x67d runnable
[5060b000..5060b86c]
at java.net.PlainSocketImpl.socketAccept(Nati
Hi,
I have solved the problem. JBoss was creating and removing lots of
small files in the db/jbossmq directory which was causing performance to
be seriously impacted.
So I mounted a ramdisk on that directory and viola, suddenly all 8 cpu's
were at 100% utilization.
It would be good if someone
Hi Theo,
A separate instance of Digester is loaded by the Tiles framework,
through the ValidatorResourcesInitializer.initialize() method. This is
what I think is causing the problem, and is what I patched with
'digester.setUseContextClassLoader(true);'. Could you send me directly
your copy of jak
I'm having the same problem.
I looked through the source for the 3.0.x/4.0.x integration. It seems
that JBoss creates a StandardContext for each deployment - completely
ignoring the DefaultContext.
I cannot see a way of exerting any control over the proprietary aspects
of hot-deployed apps at
Hi, all. I am using jdk1.4.1 with jboss3.0.3_tomcat-4.1.12. I am
trying to get tomcat to NOT save a
/opt/jboss/tomcat-4.1.x/work/MainEngine/localhost/myapp/SESSIONS.ser
file when I stop jboss or redeploy my app.
I tried putting a element in my tomcat41-service.xml file
underneathe the Defa
Hi Liam,
Sorry for not getting back to you sooner.
I've just tried the patched "validation" file and I still get the same
problem when deploying jakarta-struts-1.1-b2-blank.war (after replacing
framework-validation). I noticed that the Digester is first getting
loaded because LoggedXmlMapper
Hello Michael,
you need to provide a test-case. It works for me, though in
jboss-3.2.0beta2.
alex
Monday, October 14, 2002, 12:50:01 AM, you wrote:
MN> Hi!
MN> There is still a CMR bug present in JBoss 3.2.0 Beta. This bug is easily described:
MN> Whenever one entity bean type A has more than
I am porting a JBoss 2.4.x + bundled Tomcat 3.2.3 / JDK 1.3.0_02 .ear
app to JBoss 3.0.3 + bundled Tomcat 4.1.12 / JDK 1.4.1.
In the past, I had no problem calling servletContext.getRealPath(String)
and it returning something as my previous bundle always unpacked the
.war file that was in the
I have a war file that contains two JSPs, the first is checker.jsp that does
not have any constraints, and the second is secured.jsp.
The contents of the war file is:
[tpenhey]86: jar -tf role-test.war
META-INF/
META-INF/MANIFEST.MF
jsp/
WEB-INF/
jsp/checker.jsp
jsp/secured.jsp
WEB-INF/web.xml
Yes,
When I remove my fix, I see the same error.
The fix is in 2.4, 3.0 and 3.2
You can get the latest versions from CVS,
but you might want to hang fire on 3.0
until a readahead fix has been applied (sometime today?).
Regards,
Adrian
>From: "Chris Pinfold" <[EMAIL PROTECTED]>
>Reply-To: [EMA
Folks,
I am looking for historical release dates of JBoss. Anything that
outlines the release date(s) of JBoss x_x_x would be helpful.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
RH> Could it be that this feature needs first be enabled in some jetty
RH> config file?
bot sure about the context but you could configure a virtual host.
Check this great stuff
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup
a
> should try with beta2 before filing a bug report. Though, it works for
> me.
Could it be that this feature needs first be enabled in some jetty
config file?
> But currently to get beta2 you have to use cvs. Probably, sf.net's
> buids need to be updated.
The later sounds like a good idea.
H
AFAIK, current Branch_3_2 builds jboss-3.2.0beta2 (not beta). So you
should try with beta2 before filing a bug report. Though, it works for
me.
But currently to get beta2 you have to use cvs. Probably, sf.net's
buids need to be updated.
alex
Monday, October 14, 2002, 12:04:25 PM, you wrote:
RH
Hi,
usually, WebApps get deployed to the war name as context-root.
E.g.
foo.war:
+-- index.jsp
+-- WEB-INF
+-- web.xml
Index.jsp can then be found under http://:port/foo/index.jsp
To change this for a standalone web-app, one can put a jboss-web.xml
in WEB-INF/
jboss-web.xml:
David Jencks wrote:
> You could try using 3.2 and setting the TrackConnectionByTx attribute
to
> true: this will prevent trying to do suspend/resume calls.
Where can I set this attribute, and what is the syntax for setting it?
Benjamin
--
16 matches
Mail list logo