[Messaging, JMS & JBossMQ] - JMS Queue Corruption Questions
by ihety
Folks,
i have some questions in regards to JMS Queues - We are trying to simulate some test conditions and any help would be much appreciated.
1)Where is the JMS queue information stored within the DB? Once the association has been made can you actually go into the DB and change the value so it now has a different queue it can process.
2) Is it possible to accumulate messages within the JMS queue and test for how many store/retrieve requests it can hold and can this be logged/audited. Furthermore can we test for ensure that the messages get processed once we return the JMS queue to its ?normal behaviour??
3) Can we corrupt JMS queues i.e. make sure that they have become corrupt during processing and ensure that stores/retrieves continue to accumulate and get processed once the queue is restored (and what the restoration process would be?)
4) Is it possible to monitor a JMS queue and kill it/halt it during processing?
Cheers
Sham
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997626#3997626
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997626
19 years, 3 months
[JBoss Portal] - Re: WSRP
by chris.laprun＠jboss.com
"sridhark79" wrote :
| But when we edit the information say RSS News Feed .We are getting the following error
|
| | 16:32:39,716 WARN [ActionHandler] Requesting clone before write but since this is not currently supported we switch to read only
| |
| | {snip}
| |
| | 16:34:25,247 WARN [WSRPConsumerImpl] Portlet '781F3EE5-22DF-4ef9-9664-F5FC759065DB' will store persistent state for each user. To be handled properly, this would require supporting portlet cloning, which we don't currently do. This portlet will be excluded from the list of offered portlets for producer NetUnity
| |
It is as said on the console... :) We don't currently support portlet cloning (this will be implemented in the upcoming Alpha release for 2.6) so portlets that require a state change (and therefore an implicit/explicit cloning of the portlet) will fail at this point.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997624#3997624
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997624
19 years, 3 months
[JBoss Seam] - @Out/@DataModelSelection issues when using s:link but not wi
by cmdrclueless
I've run into strange issues when trying to use s:link verses ice:commandLink for performing an action when the selected item is in a dataTable element. I'm just trying to find out if it's a bug or a horrible misunderstanding on my part.
In a nutshell I have a Session bean with three private member: A list annotated with @DataModel, an item annotated with @DataModelSelection, and another item annotated with @Out(required=false).
If I use <ice:commandLink action="#{manager.updateItem}" value="#{itemBean.name}"> then SEAM correctly updates the data model selection. I set the @Out member in the updateItem() method and then return a JSF navigation string to a new page. Everything works as expected on the new page and the corresponding manager's @In annotation.
I was using <s:link action="#{manager.updateItem}" value="#{itemBean.name}">, the method would get invoked but data model selection was always null. The @Out annotated member did not work either, even if I set the value during the updateItem() method with a 'new Item()' value.
Is the the correct behavior?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997623#3997623
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997623
19 years, 3 months
[JBoss Portal] - Re: WSRP
by chris.laprun＠jboss.com
"sridhark79" wrote :
| How do one know what registration information need to be passed to a remote portlet. Would it be available in the wsdl file? Please let me know.
|
There should be some information on the console when that's the case.
As far as your other problem goes, I'd need to see a more detailed stack trace to see what's going on since it doesn't seem to be registration-related but rather a problem with retrieving the service description from the producer. Note also that the public producers are NOT always available so it might happen that the one you're trying to access is currently down.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997621#3997621
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997621
19 years, 3 months
[JBoss Seam] - Mapping entity primary key to Postgresql serial sequence
by trickyvail
While testing an entity bean mapped to a Postgresql database table I recieved some "duplicate key violates unique constraint" errors. The errors occured during concurrant access to the database by jboss and psql using different database roles. After setting the SequenceGenerator annotation attribute allocationSize = 1 this issue was resolved.
| // database table
| CREATE TABLE people (
| id SERIAL PRIMARY KEY
| , name VARCHAR(32)
| );
| // CREATE TABLE will create implicit sequence "people_id_seq" for serial column "people.id"
|
| // entity bean
| @Entity
| @Table(name = "people", schema = "public")
| public class People implements Serializable
| {
| private static final long serialVersionUID = 1234L;
| private int id;
| private String name;
|
| public People() {}
|
| @Id
| @SequenceGenerator(name = "identifier", sequenceName = "people_id_seq", initialValue = 1, allocationSize = 1)
| @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "identifier")
| @NotNull
| public int getId()
| {
| return id;
| }
|
| public void setId(int id)
| {
| this.id = id;
| }
|
| @Column(name = "name", length = 32)
| @Length(max = 32)
| public String getName()
| {
| return this.name;
| }
|
| public void setName(String name)
| {
| this.name = name;
| }
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997615#3997615
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997615
19 years, 3 months