[Management, JMX/JBoss] - How to remove a timer from JMX Console
by icordoba
Hi there,
I have a big problem in a very important JBoss App. It creates several instances of the same timer. Until I fix it I need to remove the duplicated instances without shutting down JBoss.
I see in JMX Console, listing Timers:
[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB]
handle: [id=30,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],first=05-Feb-2007 00:28:56.269,periode=120000]
[id=30,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],remaining=-66924226,periode=120000,active]
handle: [id=32,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],first=05-Feb-2007 18:18:48.400,periode=120000]
[id=32,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],remaining=-2732095,periode=120000,active]
handle: [id=31,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],first=05-Feb-2007 18:00:16.395,periode=120000]
[id=31,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],remaining=-3844100,periode=120000,active]
handle: [id=37,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],first=05-Feb-2007 19:07:39.903,periode=120000]
[id=37,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],remaining=79407,periode=120000,active]
handle: [id=29,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],first=05-Feb-2007 18:05:15.942,periode=120000]
[id=29,target=[target=jboss.j2ee:jndiName=tuportal/MailRelay,service=EJB],remaining=-3544554,periode=120000,active]
Whick MBean and how must I invoke it to remove timers with ids 32, 31, 37 and 29?
thanks for any help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011469#4011469
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011469
19Â years, 2Â months
[JBoss Eclipse IDE (users)] - Re: can't create a jboss configuration
by frank.steinhauer.odl
"jfrohome" wrote : It seems jboss ide 1.5 and 1.6 are intended to be used with ecplise 3.1 and NOT with eclipse 3.2. documentation for jboss ide is overaged and neither there is documentation concerning installation jboss ide 1.6 or 2.0 beta nor there are any helpful information given by jboss which software prequesites are needed to run which jboss ide version.
Well, they say for the 1.5 version it is not intended for Eclipse 3.2 - but nothing for 1.6. At least I found that 2.0 is especially for 3.2 ...
"jfrohome" wrote : @jboss: If you want your customer use your software at least there should be more information on how to install, what are software prequesites, what are dependencies on a specific eclipse version, and how to quick start use your NEW software version. Its make no sense to show availability of jboss ide 2.0 beta1 with BIG BANG on your website and customer have problems to install and get this stuff working WITH NO ACTUAL documentation for this.
Full ACK! It would be really easy to add a short "1.6 is for Eclipse3.1 only" or better - "Do this and 1.6 will work with 3.2"!
It took me over two hours work to figure out, that 1.6 won't work with eclipse3.2!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011467#4011467
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011467
19Â years, 2Â months
[JBoss Seam] - Remoting: premature end of file
by rdewell
Anyone come across this exception while working with remoting? This trace is from 1.1.0, but this also occurs in 1.1.5.
| [15:58:08,877,ExecutionHandler] Error during remote request
| org.dom4j.DocumentException: Error on line -1 of document : Premature end of file. Nested exception: Premature end of file. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:343) at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:68) at org.jboss.seam.remoting.SeamRemotingServlet.doPost(SeamRemotingServlet.java:77)
|
Not really sure where to begin digging this one out.
Pretty simple:
| @Local
| public interface ReportManagement {
| @WebRemote
| public String deleteReport(String reportId);
| }
|
into a stateless component
| @Stateless(name="ManagerReportManagement")
| @Name("ManagerReportManagement")
| @Interceptors(SeamInterceptor.class)
| public class ReportManagementImpl implements ReportManagement, Serializable{
| private static final long serialVersionUID = 246957185452163877L;
|
| @In(value="bright", create=true)
| private transient EntityManager em;
|
| public String deleteReport(String reportId) {
| try {
| Report r = em.find(Report.class, reportId);
|
| if (r == null){
| return "Report not found.";
| } else {
| em.remove(r);
| return "success:" + reportId;
| }
| } catch (Exception e){
| e.printStackTrace();
| return e.getMessage();
| }
| }
|
|
| }
|
| <script type="text/javascript" src="seam/remoting/interface.js?ManagerReportManagement"/>
|
| etc....
|
| Seam.Component.getInstance("ManagerReportManagement").deleteReport(reportId, deleteReportCallback);
|
Any ideas?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011463#4011463
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011463
19Â years, 2Â months
[JBoss AOP] - Re: How do I access security info in a Interceport class?
by flavia.rainoneï¼ jboss.com
If you are using the EJB deployment descriptor to configure security, I'm afraid that you can't use security aspects from aspect library to access this configuration.
According to this documentation:
http://docs.jboss.org/aop/1.1/aspect-library/
These aspects are a way of activating security features from JBoss AS to plain Java classes, without necessity of using EJB. This means that you should configure the security aspects either with annotations, or xdoclets, or even an xml file. In a few words, these aspects forward security implementation to the same security components JBoss uses on EJB. But, in your case, these components are already doing their work through your configuration on jboss.xml file.
If you want to use these aspects for implementing security, you should move the security configuration of your interest from jboss.xml file to one of the configuration input formats accepted by security aspects. On the other hand, if you want to keep things as is, you still can use the SecurityContext class as a utility. In this case, you will need to initialize its domain field, so you can make it useful for you. But remember of doing so only if your application is not using security aspects.
All this said, I think that the most straightforward and simple solution for you is to cut the security functional code you already have on your slsbs, and paste this code in one or more aspects of yours.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011459#4011459
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011459
19Â years, 2Â months