Sorry, there is no plan to produce another bug-fixing 4.2.x community release
Next community releases we are working on are 5.2 Beta and later on 6.0 Alpha.
If you really need another release 4.2.x release, either get and build
Branch_4_2 from source, or buy an EAP (Enterprise Application
What you've put there is not a valid JMX 1.2 ObjectName pattern.
But even if you make it a valid ObjectName pattern, it won't work as you would
like it. AFAIK, it will only accept a simple ObjectName, i.e. it won't
dynamically try to resolve the pattern and establish potentially multiple
Just by looking at your description, why not retrieving the active timers
directly after the restart from the EJB that created them in the first place,
they should be there? I don't think you need to store the handle.
View the original post :
JBAS-4598 is an old report against 4.0.5 and many things changed in timers in
4.2.2+
Thinking more about this, maybe the moment you ask for the timers, those are
not created yet? i.e. the target container where the timers belong has not
fully started for it's timers to be there. Can you verify
That html adaptor was a proprietary extension of Sun JMX implementation.
Probably found in jmxtools.jar.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240986#4240986
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240986
Your subscription list is wrong, so try an mbean descriptor like this:
| mbean code=com.sample.jmx.StartupService
name=com.packtpub.jmx:service=StartupClass
| attribute name=MessageHello World/attribute
| /mbean
|
| server
| mbean
Also the 'server' tag is at the wrong place. It should appear in the top.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4235246#4235246
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4235246
Actually since AS 4.2.x TRACE is supported natively by log4j so you can just say
| category name=bla
| priority value=TRACE/
| /category
|
Now, AS 5.1.x includes a logging bridge between java.util.logging and log4j,
meaning that the levels you set in the log4j config are propagated to
You could use the quartz delegating timerservice backend: set the
org.jboss.ejb3.timerservice.factory property to
org.jboss.ejb3.timerservice.quartz.QuartzTimerServiceFactory.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4223589#4223589
Reply to the post :
http://java.sun.com/j2ee/1.4/docs/api/javax/management/MBeanServerFactory.html#findMBeanServer(java.lang.String)
Look for the mbeanserver called jboss
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4222530#4222530
Reply to the post :
Post the whole -service.xml descriptor.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221848#4221848
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221848
___
jboss-user mailing
jboss.ws.SampleWS is *not* a valid JMX ObjectName.
http://java.sun.com/j2se/1.5.0/docs/api/javax/management/ObjectName.html
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221915#4221915
Reply to the post :
There is no magic here. You need to specify in the 'depends' and
'monitoredmbean name= clauses the ObjectName of the mbean you want to monitor.
If you don't know the full mbean name you want to monitor, you need to find it.
Logging to the jmx-console and look for it.
View the original post :
Look in JBOSS_HOME/common/lib/jsp-api.jar, servlet-api.jar
and
JBOSS_HOME/server/xxx/deploy/jbossweb.sar/jsf-libs/jsf-api.jar
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4220708#4220708
Reply to the post :
You must rename your descriptor:
SampleWebServiceMonitor-service.xml
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4219425#4219425
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4219425
You could created a common/deploy directory and enhance the server(s) directory
scanners to look into that directory, as well. Just an idea.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217751#4217751
Reply to the post :
I think it's a 32-bit binary that can run on both 32/64.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217386#4217386
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4217386
___
Ok, I think I've found it. When the file gets copied, filtering was *enabled*
and this probably alters the binary content.
| !-- Compile bin scripts --
| target name=compile-bin depends=init
| mkdir dir=${build.bin}/
| copy todir=${build.bin} filtering=yes
|
View the
It might be that this service/mbean is not written to be re-startable, i.e.
once you stop you can only undeploy. In those case deploy/undeploy may be the
only operations.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217396#4217396
Reply to the post :
Can you try the file attached to the case?
https://jira.jboss.org/jira/browse/JBAS-6613
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4217390#4217390
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4217390
amlodzin wrote :
| The problem, in the app-state case, is that the jboss.web.deployment:*
MBeans use a random id as a key property, in addition to just one other key
property - the war file name. That makes it impossible to link a particular war
file with its parent EAR file (if there is
Why not just fixing your path?
Either remove the trailing slash, or change the order so that it doesn't appear
last (C:\Lang\JProbe 7.0\bin\).
I guess the problem is that the trailing slash followed by '' escapes the
double quote in JAVA_OPTS thus breaking the command line.
View the
You probably have some invalid characters inside your own configuration files.
Search for .xml file containing REQU in your deployments.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4212662#4212662
Reply to the post :
The issue is that the quartz-based timer service has some issues with some
database backends and it's not very well tested in the community. There also
discussion on how to proceed with an improved timer service for ejb3.1. Until
those are finalized I'd suggest to stick with the ejb2 timer
The EJB3 stack can be configured to use Quartz timer service by setting the
system property org.jboss.ejb3.timerservice.factory to
org.jboss.ejb3.timerservice.quartz.QuartzTimerServiceFactory.
Take notice though that this may not be supported in the future.
View the original post :
I think you are right about the shutting down notification! My bad.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4210264#4210264
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4210264
I see you've already created a JIRA for that:
https://jira.jboss.org/jira/browse/JBAS-6499
It looks like when Brian refactored the service, he left this out for some
reason.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4209823#4209823
Reply to the post :
I'll let Brian answer.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4209847#4209847
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4209847
___
jboss-user mailing list
If you're going to re-enable this in Branch_5_x look for the symmetrical
shutting down notification, as well.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4209964#4209964
Reply to the post :
Just get rid of ejb3-timer-service.xml, i.e. remove it.
Ejb3 is configured by default to use the ejb2.x timer service and that should
work.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208519#4208519
Reply to the post :
4 minutes is a lot. How much time does it take to boot the 'default' config out
of the box without your application deployed?
Maybe you should use the 'web' config (run -c web) which is closer to a bare
tomcat config.
View the original post :
Maybe read a unix tutorial first?
./twiddle.sh serverinfo -l
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4205219#4205219
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4205219
To be honest, I haven't seen this type of usage before. I guess the trick is to
make sure you won't have synchronization issues when the MDBs update their
config because they might be doing message processing at the same time, using
some form of copy-on-write semantics.
View the original post
I suppose we can use a combination of the changes you propose: bump up the ORB
defaults a little bit, cut back the stress test, or even alter the test
execution based on the target (JTA vs JTS) doing some property checking.
View the original post :
Try the 'web' config as a starting point (run -c web). It opens only the http
port but has less services configured.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200536#4200536
Reply to the post :
Yes, we should put an empty file there, just in case.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4194965#4194965
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4194965
___
It is an implementation of the Java EE standard; and a lot more ;-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4192613#4192613
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4192613
37 matches
Mail list logo
