[JMX] - activeSessions Attribute not found exception
by chbmxt
We're continually getting the following error in my log file:
2009-10-19 12:48:49,893 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[Status Servlet]] (http-wsprd2%2F10.20.50.114-8080-1) Servlet.service() for servlet Status Servlet threw exception
javax.management.AttributeNotFoundException: not found: activeSessions
at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:335)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:565)
at org.apache.catalina.manager.StatusTransformer.writeManager(StatusTransformer.java:736)
at org.apache.catalina.manager.StatusTransformer.writeContext(StatusTransformer.java:703)
at org.apache.catalina.manager.StatusTransformer.writeDetailedState(StatusTransformer.java:586)
at org.jboss.web.tomcat.service.StatusServlet.doGet(StatusServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
2009-10-19 12:50:28,610 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[Status Servlet]] (http-wsprd2%2F10.20.50.114-8080-1) Servlet.service() for servlet Status Servlet threw exception
javax.management.AttributeNotFoundException: not found: activeSessions
at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:335)
at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:565)
at org.apache.catalina.manager.StatusTransformer.writeManager(StatusTransformer.java:736)
at org.apache.catalina.manager.StatusTransformer.writeContext(StatusTransformer.java:703)
at org.apache.catalina.manager.StatusTransformer.writeDetailedState(StatusTransformer.java:586)
at org.jboss.web.tomcat.service.StatusServlet.doGet(StatusServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
We're using JBossAS 5.1.0.GA on Linux. We don't have any idea as to what is causing this exception or how to stop it from being generated. It also seems to persist across restarting of the server.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262993#4262993
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262993
16 years, 6 months
[jBPM Users] - Re: JBPM4: How to find leaving transitions of an execution
by nilspreusker
Hi Sebastian,
anonymous wrote : Me: wouldn't it also be nice to be able to query the process instance for the process variables that will be required after a transition?
|
| Sebastian: Maybe you can explain your thoughts a bit more here.
My basic though is that the more details we can get about the process through the API at run-time, the closer we get to creating or generating a default user interface for processes.
If it was possible to retrieve information about the process variables that are required in the resulting task/state/activity node of a transition, one could think of a user interface that shows a default form when a transition is invoked (i.e. default task forms), based on the type and name of the variables. These could be customized by providing task forms along with the process deployment as it is shown in the task form example.
I suppose this is really turning more into a development forum discussion... Please let me know what you think!
Cheers, Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262988#4262988
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262988
16 years, 6 months
[jBPM Users] - Re: JBPM4: How to find leaving transitions of an execution
by sebastian.s
"nilspreusker" wrote : Hi, I just voted:)
Great. :)
"nilspreusker" wrote :
| I think you are going in exactly the right direction. As I understand it (correct me if I'm wrong!), information about how the user can interact with the process instance in jBPM 4 is currently meant to be provided with task forms. A reference implementation exists for the GWT console. However, I totally agree with what Sebastian stated earlier:
|
| anonymous wrote : If you want the user to make this decision you need this information and since it is supplied by the process definition it should be accessible trough the API.
|
| For use cases where no user input - other than a decision - is required, this would provide a very nice way to create dynamic user interfaces without the need for a custom task form implementation.
|
I might even face similar use cases right now. My thoughts right now are pretty much related to dynamic user interfaces. I especially don't like the idea of creating task specific forms for simple things like decisions where just want to the user to decide between "yes" and "no", "A" and "B" etc.
"nilspreusker" wrote : And while we're at it, wouldn't it also be nice to be able to query the process instance for the process variables that will be required after a transition? ...but now I'm getting ahead of myself:)
|
I am not sure if this possible and if this would really make sense. Maybe you can explain your thoughts a bit more here.
"nilspreusker" wrote :
| Anyway, I'm glad to see this discussion here!
|
Yes, me too. This might turn out be a discussion for the developers' forum. I'd love to hear one of the dev's on this. To me at first sight it seems as if this is a "quite simple" API extension which shouldn't break anything.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262974#4262974
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262974
16 years, 6 months
[JBoss Messaging Users] - 2 JBoss instance - 1. for JBoss Messaging and 2. Remote Cons
by ekobir
Hi All
I couldn't figure out how to configure 2. jboss instance to use queues deployed on the 1. jboss instance. As our application is deployed in jboss, we want to cache jms connections as explained in the article below
http://www.jboss.org/community/wiki/ShouldIcacheJMSconnectionsandJMSsessions
In order to use JmsXA with remote messaging provider, I changed jms-ds.xml like below
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider, server=192.168.4.107">
| <attribute name="ProviderName">remoteJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
| <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=192.168.4.107:1300
| </attribute>
|
| </mbean>
|
| <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
| <tx-connection-factory>
| <jndi-name>JmsXA</jndi-name>
| <use-java-context>false</use-java-context>
| <xa-transaction/>
| <rar-name>jms-ra.rar</rar-name>
| <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/remoteJMSProvider</config-property>
| <max-pool-size>20</max-pool-size>
| <security-domain-and-application>JmsXARealm</security-domain-and-application>
| <depends>jboss.messaging:service=ServerPeer</depends>
| </tx-connection-factory>
|
Both JBoss version : 5.0.1.GA
JBossMessaging : 1.4.1.GA
Error : nested exception is javax.naming.NameNotFoundException: queue/outboundQueue
org.springframework.jms.support.destination.DestinationResolutionException: Destination [/queue/outboundQueue] not found in JNDI; nested exception is javax.naming.NameNotFoundException: queue/outboundQueue
There is no problem accessing this queue via XAConnectionFactory, but as you know performance is very important.
Second Part: I was using hsqldb for jboss messaging for initial performance tests. it performed as we expected.
Then I started using mysql db for jboss messaging(this is the only change), application became 5 times slower.
Do you have any suggestion to resolve this?
Thanks for your help and time.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262963#4262963
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262963
16 years, 6 months
[jBPM Users] - jbpm 4.1 - How to stop these Debug Messages in jboss
by makarandk502
Hi,
Jbpm 4.1 , Jboss 5.0.0 GA
When I see Jboss server log (server.log) from Jboss/server/default/log, I can see lot of following JobExecutor DEBUG messages. It seems that some process is running continuosly till we shutdown the jboss.
Server log size is becoming too much after some time.
Can anybody tell me how to stop printing DEBUG messages related to Jobexecutor ?
Your help is highly appreciated
|
| 18:46:33,942 DEBUG [DispatcherThread] DispatcherThread will wait for max 5000ms on org.jbpm.pvm.internal.jobexecutor.JobExecutor@7798cd
| 18:46:38,939 DEBUG [DispatcherThread] DispatcherThread woke up
| 18:46:38,949 DEBUG [AcquireJobsCmd] start querying first acquirable job...
| 18:46:38,949 DEBUG [AcquireJobsCmd] locking jobs []
| 18:46:38,959 DEBUG [GetNextDueDateCmd] getting next due date...
| 18:46:38,959 DEBUG [GetNextDueDateCmd] next due date is null
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262952#4262952
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262952
16 years, 6 months
[jBPM Users] - Re: JBPM4: How to find leaving transitions of an execution
by nilspreusker
Hi, I just voted:)
Regarding your doubts:
anonymous wrote : when the process arrives at a certaion point where a node has more than one outgoing transition, the user actually needs to make a choise which transition to take. So I need to display all possible transitions to the user.
|
| I'm still not sure if I'm running in the wrong direction, because this seems to obvious to me...
I think you are going in exactly the right direction. As I understand it (correct me if I'm wrong!), information about how the user can interact with the process instance in jBPM 4 is currently meant to be provided with task forms. A reference implementation exists for the GWT console. However, I totally agree with what Sebastian stated earlier:
anonymous wrote : If you want the user to make this decision you need this information and since it is supplied by the process definition it should be accessible trough the API.
For use cases where no user input - other than a decision - is required, this would provide a very nice way to create dynamic user interfaces without the need for a custom task form implementation.
And while we're at it, wouldn't it also be nice to be able to query the process instance for the process variables that will be required after a transition? ...but now I'm getting ahead of myself:)
Anyway, I'm glad to see this discussion here!
Cheers, Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262950#4262950
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262950
16 years, 6 months