[JBoss Messaging] - How to configure application specific Queue and Topics in destinations-service.xml
by Rahul Aahir
Rahul Aahir [http://community.jboss.org/people/rahul9885] created the discussion
"How to configure application specific Queue and Topics in destinations-service.xml"
To view the discussion, visit: http://community.jboss.org/message/562113#562113
--------------------------------------------------------------
Hello All,
I am Configuring my application specific Queue and Topics in *destinations-service.xml ,* but Queue is not getting register in jboss.
I am getting following error in jboss :
[ServiceConfigurator] Problem configuring service jboss.messaging.destination:service=Queue,name=jms/servers/logmon/MonitorInQueue
org.jboss.deployment.DeploymentException: Exception setting attribute mailto:javax.management.Attribute@1e32382 javax.management.Attribute@1e32382 on mbean jboss.messaging.destination:service=Queue,name=jms/servers/logmon/MonitorInQueue; - nested throwable: (javax.management.AttributeNotFoundException: not found: DestinationManager)
at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:698)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:380)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
My *destinations-service.xml* is unsder "*jboss-4.3.0\server\MySiteServer\deploy\jboss-messaging.sar" ,* not in *deploy* directory of jboss.
*Is it right plcae to configure destination queue and topics ??*
My *destinations-service.xml* is like given below *:*
<?xml version="1.0" encoding="UTF-8"?>
<server>
.
.
.
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,*name=jms/servers/logmon/MonitorInQueue*"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<depends optional-attribute-name="DestinationManager">jboss.messaging:service=DestinationManager</depends>
<depends optional-attribute-name="SecurityManager">jboss.messaging:service=SecurityManager</depends>
<attribute name="SecurityConf">
<security>
<role name="guest" read="true" write="true"/>
<role name="publisher" read="true" write="true" create="false"/>
<role name="noacc" read="false" write="false" create="false"/>
</security>
</attribute>
</mbean>
</server>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/562113#562113]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 7 months
[jBPM] - Concept of different locales/time zones in jBPM5
by Peter Horvath
Peter Horvath [http://community.jboss.org/people/h.peter] created the discussion
"Concept of different locales/time zones in jBPM5"
To view the discussion, visit: http://community.jboss.org/message/562109#562109
--------------------------------------------------------------
Hello All,
I believe the work on the upcoming release of jBPM has already been started - at least the planning, requirement gathering and establishing basic concepts. What I don't really see is the way times and dates will be handled by jBPM 5.
As far as I know the current 4.4 version does not really have any concept of different locales or time zones and business calendars: it seems that the assumption is that all end users / workflow actions will be in the same time zone.
This is a limitation even small / midsized companies can hit. Although having say a few hours difference between the US east and west coast might not be a big deal in most of the cases but the lack of locale/time zone support can be significant in other cases. For example I don’t really see the means to handle the scenario where your workflow crosses country borders and you want to set the task due date expressed in business days according the local environment.
Or if you have an application running with jBPM embedded into it in different time zones, but using the same database you might experience strange issues: some tasks might seem to be created in the future. Since the audit history contains the timestamps using the local date and time you might see a task being completed before the previous step, or even the before the date task itself was created.
What do you think about this – is there any plan to include support for different locales / time zones and business calendars in jBPM 5?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/562109#562109]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 7 months
[Beginner's Corner] - Working around transaction timeouts
by dfisher
dfisher [http://community.jboss.org/people/dfisher] created the discussion
"Working around transaction timeouts"
To view the discussion, visit: http://community.jboss.org/message/560919#560919
--------------------------------------------------------------
+Using JBoss 5.1.0+
I've got a long running clean up task that repeatedly invokes a stateless session bean.
The problem I'm having is that the task takes longer than 5 minutes to run, which is the default transaction timeout.
Rather than change the default value or define a custom value on the SSB, I'm trying to wire things up so each SSB call uses it's own transaction.
My current design looks like:
MBean
invoke Task [SSB with @TransactionAttribute(NEVER)]
invoke Search [SSB with @TransactionAttribute(REQUIRED)], look up entities to operate on
for each entity
invoke Operation [SSB with @TransactionAttribute(REQUIRED)], perform operation
My expectation is that Task does not have a transaction.
The Search transaction will commit when all entities are found.
A new transaction will run and commit for each invocation on Operation.
However, what occurs is that all operations rollback after 5 minutes.
Can anyone explain the correct way to do this?
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/560919#560919]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 7 months