[JBoss Portal] - Re: Comparing JBoss Portal to Liferay or other portal produc
by chris.laprun@jboss.com
"syllant" wrote : Thanks for this more moderate tone Chris :-)
It's very easy to get frustrated on online forums :)
"syllant" wrote : Concerning forum and JIRA management, I fully understand and I would never have mentioned it if a JBM team member didn't blame me for not contributing.
|
Considering that forum user names don't map to JIRA, it's not obvious who ends up filing JIRA tasks...
"syllant" wrote : And I never reproached JBP team to not answer in forums or to not be helpful :-) Initially, I just point it as a fact to consider for newcomers as it's a major criteria when you have to select an OS product.
We'd like to have a resource dedicated to answering forum questions but as it's not the case, we rely on our community of users (who are generally doing a great job) and try to fill in when questions go unanswered when we can find some time. Given the limited amount of time we have, we give the priority to improving the product. :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130861#4130861
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130861
18 years, 2 months
[JBoss Getting Started Documentation]Configuring Oracle
by Stephen Davidson
Greetings.
The Wiki page for configuring Oracle is, to put it mildly, misleading. The way
it is laid it, it implies that local-tx datasources are what should be used for
Oracle Databases. This might have been correct for Oracle 8 and before, but is
definitely not the case for Oracle 10.
The page I am concerned about is;
http://www.jboss.com/wiki/Wiki.jsp?page=SetUpAOracleDatasource
Proposed correction attached. I can upload if you would like, or post a
revision (or if somebody wants to update, go ahead).
The major change was to add a few statements just before the sample Datasource
files, and to switch the order the Datasource Examples are given in the
document. This should help cut down on the number of Transaction Manager
complaints as well, I would think. (Would have eliminated them from me, anyways).
Regards,
Steve
18 years, 2 months
[Messaging, JMS & JBossMQ] - Re: JMSXDeliveryCount with GenericDLQHandler
by svadu
Hi Adrian,
Thanks for your reaction.
"adrian(a)jboss.org" wrote : "svadu" wrote :
| | Can someone give me a clue on the problem (I hope I described the problem more or less accurately)?
| |
| JMSXDeliveryCount is a property set by the JMS provider (Tibco) not JBoss.
| We just use it to determine number of redeliveries when it exists (it is optional).
|
Considering that GenericDLQHandler doesn't increment it I came to the same conclusion.
anonymous wrote :
| Perhaps it is a property Tibco doesn't support, but the message originated
| in some other system that does set the property. i.e. Tibco just copied it?
|
Well it's imported from other messaging system (TIBCO specific) which doesn't know about JMSXDeliveryCount. But TIBCO EMS (which performes the import) does support the property.
anonymous wrote :
| anonymous wrote :
| | Do I need to rely (would require even more vendor specific configuration) on the external JMS server (Tibco in this case) to handle redelivery counts?
| |
|
| No idea. But I'd imagine Tibco has internal support for DLQs or
| some other poisened message handler?.
|
Yes in fact it does, but the queue is not configurable (and I like being able to configure DLQ name per queue, for example).
anonymous wrote :
| So you probably don't need to configure a DLQ handler in JBoss at all?
|
| * Set the activation-config-property useDLQ=false
| * Configure a DLQ (or whatever mechanism they have) for your queue/topic in Tibco.
|
Not using the DLQ at all might see the most portable option here, I don't like relying on TIBCO's dlq even more... Fortunately, it seemed that the problem was due to very high load in TIBCO EMS (or corrupt data). Anyway I set max delivery to 1 in the MDB so that if the counter is greater 1 (it was 2 in my case) it is delivered to DLQ. It works so far (and for new messages it is increasing for some reason). May be the problem was queue settings (queues can be made synchronized for better thread safety when writing to the file system). Anyway, the problem is, somewhat resolved.
anonymous wrote :
| The only reason the DLQ handler exists in the MDB is because JBossMQ
| doesn't support them internally. Most other JMS providers do support them
| inside the server.
I hope it stays this way (the generic DLQ support).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130857#4130857
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130857
18 years, 2 months
[Clustering/JBoss] - Re: Potential issue with JGroups using JBoss 3.2.7 and Java
by ross.nelson@saic.com
Finally I thought it worthwhile posting a view of what happened around the time of the "hang" from the STD Out logs of one of the unaffected kernels...
1 kernel leaves and rejoins then around 2 minutes later the problem kernel leaves the cluster.
11:23:45,111 INFO [DefaultPartition] Suspected member: cathlbgts06:39562 (additional data: 16 bytes)
11:23:45,111 INFO [DefaultPartition] New cluster view for partition DefaultPartition (id: 19, delta: -1) : [10.9.181.48:1104, 10.9.181.51:1104, 10.9.118.3:1104, 10.9.118.2:1104]
11:23:45,112 INFO [DefaultPartition] I am (10.9.181.48:1104) received membershipChanged event:
11:23:45,112 INFO [DefaultPartition] Dead members: 1 ([10.9.181.50:1104])
11:23:45,112 INFO [DefaultPartition] New Members : 0 ([])
11:23:45,112 INFO [DefaultPartition] All Members : 4 ([10.9.181.48:1104, 10.9.181.51:1104, 10.9.118.3:1104, 10.9.118.2:1104])
11:23:46,394 INFO [DefaultPartition] New cluster view for partition DefaultPartition (id: 20, delta: 1) : [10.9.181.48:1104, 10.9.181.51:1104, 10.9.118.3:1104, 10.9.118.2:1104, 10.9.181.50:1104]
11:23:46,394 INFO [DefaultPartition] I am (10.9.181.48:1104) received membershipChanged event:
11:23:46,394 INFO [DefaultPartition] Dead members: 0 ([])
11:23:46,395 INFO [DefaultPartition] New Members : 1 ([10.9.181.50:1104])
11:23:46,395 INFO [DefaultPartition] All Members : 5 ([10.9.181.48:1104, 10.9.181.51:1104, 10.9.118.3:1104, 10.9.118.2:1104, 10.9.181.50:1104])
26651.767: [Rescan (parallel) , 0.0052600 secs]26726.655: [Rescan (parallel) , 0.0429900 secs]11:25:42,333 INFO [DefaultPartition] Suspected member: cathlbgts01:35704 (additional data: 15 bytes)
11:25:42,335 INFO [DefaultPartition] New cluster view for partition DefaultPartition (id: 21, delta: -1) : [10.9.181.48:1104, 10.9.181.51:1104, 10.9.118.3:1104, 10.9.181.50:1104]
11:25:42,335 INFO [DefaultPartition] I am (10.9.181.48:1104) received membershipChanged event:
11:25:42,335 INFO [DefaultPartition] Dead members: 1 ([10.9.118.2:1104])
11:25:42,335 INFO [DefaultPartition] New Members : 0 ([])
11:25:42,335 INFO [DefaultPartition] All Members : 4 ([10.9.181.48:1104, 10.9.181.51:1104, 10.9.118.3:1104, 10.9.181.50:1104])
Thanks in advance for any assistance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130848#4130848
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130848
18 years, 2 months