Bugs item #462187, was opened at 2001-09-17 00:12
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=462187&group_id=22866
Category: None
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobo
David Maplesden wrote:
> Ahh, this is a bug I came across about two weeks ago when developing my own
> mbean.
>
> It is actually a bug in the MBeanServerImpl when working with mbeans that
> use the default domain in the object name (i.e. ":service=Jetty" instead of
> "SomeDomain:service=Jetty").
JBoss daily test results
SUMMARY
Number of tests run: 129
Successful tests: 101
Errors:18
Failures: 10
[time of test: 17 September 2001 6:31 GMT]
[java.version:
JBoss daily test results
SUMMARY
Number of tests run: 95
Successful tests: 62
Errors:23
Failures: 10
[time of test: 17 September 2001 5:13 GMT]
[java.version: 1
Can you be very specific about how to reproduce this problem? I have
wondered if something like this would show up but haven't seen it yet.
Thanks
david jencks
On 2001.09.16 19:34:00 -0400 Peter Fagerlund wrote:
> It looks like problem with GC (Garbage Collection) while playing with JMX
> hotde
JBoss daily test results
SUMMARY
Number of tests run: 156
Successful tests: 128
Errors:18
Failures: 10
[time of test: 17 September 2001 3:31 GMT]
[java.version:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
[execmodules] location: class org.jboss.te
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
java.class.path:
/home/lubega/jbossro/jbo
User: jules_gosnell
Date: 01/09/16 17:59:04
Modified:src/etc/conf/default j2eedeployment-service.xml
Log:
be consistant in Jetty Service naming
Revision ChangesPath
1.4 +3 -3 jboss/src/etc/conf/default/j2eedeployment-service.xml
Index: j2eedeployment-serv
User: jules_gosnell
Date: 01/09/16 17:48:45
Modified:src/etc/conf/default jetty-service.xml
Log:
this seems to work around a problem with undeployment of this service
Revision ChangesPath
1.4 +1 -1 jboss/src/etc/conf/default/jetty-service.xml
Index: jetty
Andreas Schaefer wrote:
> Hi Jules
>
> I am not talking about the Jetty source but about the
> JMX wrapper for jetty called:
> org.jboss.jetty.JettyService
> etc.
>
[jules@zeuglodon 3.0]$ cvs status
plugins/jetty/src/main/org/jboss/jetty/JettyService.java
[EMAIL PROTECTED]'s password:
==
Andreas Schaefer wrote:
> Doesn't the question marks indicating that these directories/files
> are not added to the CVS ??
Yes - but these are not the important ones. The important ones ARE checked in
to HEAD
Jules
>
>
> Try to add these files to CVS and hopefully it works.
>
> Andy
>
> -
OK,
Things are getting better..
Undeployment appears to work, but redeployment fails - It looks liek someone
is not shutting down Jetty properly - I guess the ball is back in my court !
Thanks,
Jules
[J2eeDeployer#Default] J2EE application:
file:/mnt/megalodon/home/jules/cvs/JBoss/3.0/build/o
Hi Jules
I figured out how to go around by
just coping the "jetty" directory from
the "contrib" module into the new
"plugins" directory.
But now I got this exception:
[ServiceController] java.lang.ClassCircularityError:
org/mortbay/util/JarFileResource
which prevents the JettyService to start
Hi Jules
I am not talking about the Jetty source but about the
JMX wrapper for jetty called:
org.jboss.jetty.JettyService
etc.
Andy
- Original Message -
From: "Julian Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 16, 2001 5:15 PM
Subject: Re: [JBoss-dev] S
Bug reported to JMX team but no response up to now.
Andy
- Original Message -
From: "David Maplesden" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 16, 2001 5:02 PM
Subject: RE: [JBoss-dev] JSR/SAR (Jetty) Undeployment...
> Ahh, this is a bug I came across about t
Doesn't the question marks indicating that these directories/files
are not added to the CVS ??
Try to add these files to CVS and hopefully it works.
Andy
- Original Message -
From: "Julian Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 16, 2001 5:28 PM
Sub
OK - I'll try that.
Thanks for getting back to me so quickly.
Jules
David Maplesden wrote:
> Ahh, this is a bug I came across about two weeks ago when developing my own
> mbean.
>
> It is actually a bug in the MBeanServerImpl when working with mbeans that
> use the default domain in the objec
My current plugins directory looks like this :
[jules@zeuglodon 3.0]$ ls -l plugins/
total 12
drwxrwxr-x2 julesjules4096 Sep 3 22:43 CVS
drwxrwxr-x8 julesjules4096 Sep 17 01:01 jetty
drwxrwxr-x5 julesjules4096 Sep 17 01:01 varia
[jules@zeuglodon 3.
Ahh, this is a bug I came across about two weeks ago when developing my own
mbean.
It is actually a bug in the MBeanServerImpl when working with mbeans that
use the default domain in the object name (i.e. ":service=Jetty" instead of
"SomeDomain:service=Jetty"). It fails to find the mbean when it
You won't find a Java file - because the Jetty source is not yet checked in.
You should have all the jars you need in thirdparty/mortbay :
thirdparty/mortbay/
thirdparty/mortbay/CVS
thirdparty/mortbay/CVS/Root
thirdparty/mortbay/CVS/Repository
thirdparty/mortbay/CVS/Entries
thirdparty/mortbay/jet
Hot-deploying the Jetty service works fine.
Hot-undeploying generates the following exception :
[AutoDeployer] Auto undeploy of
file:/mnt/megalodon/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0alpha/deploy/jetty-service.xml
[JettyService] Stopping
[Jetty] Stopped SocketListener on 0.0.0.0
Hi Jules
I tried to search for the Service class for jetty referenced
in the jetty-service.xml (org.jboss.jetty.JettyService).
But I couldn't find this class in the jboss-all module
(find . -name JettyService.java -print).
The only exception I get is the following when I run
the build JBoss:
[D
- Original Message -
From: "Julian Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 16, 2001 5:00 PM
Subject: Re: [JBoss-dev] Still problems with Jetty
> Or is the problem that you can't find the Jetty source, because
> contrib/jetty no longer exists ?
>
>
on 1-09-17 00.50, Dean Anderson at [EMAIL PROTECTED] wrote:
>> sh build.sh
cgwin on NT ???
What version checked out ???
with what command ???
>BTW, the claim that source comes with the 2.4.0 and 2.4.1 package is false.
h ... do U have a filter applied inbetween ... what Country do U
downl
Or is the problem that you can't find the Jetty source, because
contrib/jetty no longer exists ?
look in plugins
I'm guessing here - you'll have to be a little more specific about the
problem
Jules
Julian Gosnell wrote:
> Would you post the exception please .
>
> I've done a find thr
Would you post the exception please .
I've done a find through the whole of my RH source tree and the only
places I find this string is in doc files and CVS dirs (because the 3.0
tree seems to be a view on the old 2.x tree)
I'll fix it as soon as you let me know what the problem is,
Thanks,
What OS, Version, Hardware(yes, cvs command do You use ?
/peter_f
on 1-09-17 00.50, Dean Anderson at [EMAIL PROTECTED] wrote:
> I did another cvs update, and the problem still exists.
>
> Basically, I'm kind of getting a bit frustrated with this group. No one has
> answered or FAQ'ed even sim
It looks like problem with GC (Garbage Collection) while playing with JMX
hotdeploy ? ... i am not sure ! but wanted to ask ? if it is seen somewhere
else ? ...
That is -the state of a thread in a JMX MBean is stale -and when I try to
reimplement it ... the VM still has reference to last -allth
I did another cvs update, and the problem still exists.
Basically, I'm kind of getting a bit frustrated with this group. No one has
answered or FAQ'ed even simple questions on building. If it doesn't build,
it doesn't exist.
BTW, the claim that source comes with the 2.4.0 and 2.4.1 package is f
Hi Jules
I downloaded the latest from CVS jboss-all module, clean it up to
build it from scratch.
It seems that "contrib/jetty/" is not part of jboss-all, any ideas ?
Andy
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforg
User: jules_gosnell
Date: 01/09/16 11:04:29
Modified:jbossbuild.xml
Log:
jetty should now start up OK with RH - if not, let me know
Revision ChangesPath
1.29 +3 -7 build/jboss/build.xml
Index: build.xml
===
User: jules_gosnell
Date: 01/09/16 11:04:29
Modified:src/etc/conf/default j2eedeployment-service.xml
Log:
jetty should now start up OK with RH - if not, let me know
Revision ChangesPath
1.3 +1 -1 jboss/src/etc/conf/default/j2eedeployment-service.xml
Index
User: jules_gosnell
Date: 01/09/16 10:42:22
Modified:jetty/src/etc jetty.properties
Log:
a temporary hack to get JSPs to work better
Revision ChangesPath
1.3 +2 -1 contrib/jetty/src/etc/jetty.properties
Index: jetty.properties
==
User: jules_gosnell
Date: 01/09/16 10:45:25
Modified:src/etc/conf/default jetty-service.xml
Log:
update jar dependencies and prepare to lose JettyHome
Revision ChangesPath
1.3 +7 -3 jboss/src/etc/conf/default/jetty-service.xml
Index: jetty-service.xml
=
User: jules_gosnell
Date: 01/09/16 10:31:02
Modified:jetty/src/etc jetty.xml
Log:
rip all stuff that expects a jetty install tree - since there isn't one.
I will put this back when the problem is resolved
Revision ChangesPath
1.4 +0 -128contrib/jetty/src/etc/
User: jules_gosnell
Date: 01/09/16 10:14:17
Modified:jetty/src/main/org/jboss/jetty JBossLogSink.java
JBossUserRealm.java Jetty.java JettyMBean.java
JettyResolver.java JettyService.java
JettyServiceMBean.java SetupH
User: gropi
Date: 01/09/16 10:00:38
Modified:src/docs doco.jsp
Log:
Updated to new cvs module name for the manual.
Revision ChangesPath
1.2 +1 -1 newsite/src/docs/doco.jsp
Index: doco.jsp
==
User: patriot1burke
Date: 01/09/16 08:29:07
Modified:src/main/org/jboss/ha HAPartitionImpl.java
DistributedReplicantManagerImpl.java
ClusterPartition.java
Log:
still a work in progress, but I'm progressing...Still doesn't work yet!!!
They were moved. If you checkout jboss-all, they are in the plugins
module. If you browse cvs, they are contrib/varia.
david jencks
On 2001.09.16 04:26:16 -0400 Ole Husgaard wrote:
> Hi,
>
> It seems that all the source files in the directory
> jboss/jboss/src/main/org/jboss/tm/plugins/tyrex w
So what?
Let me summarize: we have some jars that aren't legal to be included in the
same pack with a LGPL license. Sun could say something at the respect. But
they haven't so far. I suppose they are waiting, because, to be fair, JBoss
is miles away from the J2EE server they include in their SDK.
User: jules_gosnell
Date: 01/09/16 04:57:44
Modified:src/docs binary.jsp
Log:
bumb JBoss/Jetty release
Revision ChangesPath
1.7 +3 -3 newsite/src/docs/binary.jsp
Index: binary.jsp
===
RCS
me too, I am very confused by what this means to
JBoss, I am researching the issue to start getting some alternative marketing
out around these forums...any comments or suggestions or interpretations are
welcome...
my reading is that it is the J2EE licensing and
certification that are the
User: jules_gosnell
Date: 01/09/16 04:39:34
Modified:src/resources/web/WEB-INF Tag: Branch_2_4 web.xml
Log:
Jetty doesn't like these mappings:
In section 5.4 the spec says:
* Servlet Path: The path section that directly corresponds to the mapping which
activated this
r
Hi,
It seems that all the source files in the directory
jboss/jboss/src/main/org/jboss/tm/plugins/tyrex were
moved into the CVS attic about 5 weeks ago.
The change had the commit message:
Merging changes from jboss_buildmagic into HEAD.
Is there any reason for removing this plugin, or
was it
James Ward wrote:
> So can JBoss avoid these issues by just not being J2EE branded or
> "certified"?
J2EE is a trademark of Sun, in the field of application servers.
Suns official policy on their trademarks can be found at
http://www.sun.com/policies/trademarks/, but it is important to
view this
46 matches
Mail list logo
