[JBoss JIRA] Created: (JBESB-849) Should smooks test be an integration test?
by Mark Little (JIRA)
Should smooks test be an integration test?
------------------------------------------
Key: JBESB-849
URL: http://jira.jboss.com/jira/browse/JBESB-849
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Tom Fennelly
Priority: Trivial
[java] [junit] 10:22:35,254 ERROR [main][SmooksInstanceManager] Lookup of the JMS ConnectionFactory failed for the Transformation configuration Update Listener. Update listener not enabled!
[java] [junit] org.jboss.soa.esb.ConfigurationException: JNDI lookup of JMS Connection Factory [ConnectionFactory] failed.
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.getJmsConnectionFactory(SmooksInstanceManager.java:161)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.connect(SmooksInstanceManager.java:203)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:122)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:109)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager.<init>(SmooksInstanceManager.java:67)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialiseLocalSmooksInstanceManager(SmooksTransformer.java:236)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialise(SmooksTransformer.java:218)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.transform(SmooksTransformerUnitTest.java:82)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.test_trans(SmooksTransformerUnitTest.java:69)
indicates that the test needs JMS set up beforehand. So doesn't that tend to imply it's an integration test?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBESB-1164) Crash creates multiple EPRs for same service in JUDDI
by Tom Cunningham (JIRA)
Crash creates multiple EPRs for same service in JUDDI
-----------------------------------------------------
Key: JBESB-1164
URL: http://jira.jboss.com/jira/browse/JBESB-1164
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2.1 IR1
Reporter: Tom Cunningham
Assigned To: Mark Little
If the AS or ESB server crashes or does not cleanly shut down, JUDDI will duplicate EPR records in its database table. For the monitoring/management console, this is a real problem because it depends on the fact that there will be only one EPR for its services per ESB server.
Post-crash, every time the console tries to collect data, it is getting back results from multiple EPRs on the same machine, which is causing ConstraintViolations when we try to store results. This is causing JBESB-1139.
JUDDI should probably clean up EPR records post-crash.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months
[JBoss JIRA] Created: (JBESB-866) jUDDI retains invalid EPRs
by Jiri Pechanec (JIRA)
jUDDI retains invalid EPRs
--------------------------
Key: JBESB-866
URL: http://jira.jboss.com/jira/browse/JBESB-866
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Mark Little
If the ESB is terminated (crashes) it will retain EPRs in the database. Unfortunately when the EPR is changed e.g. by renaming of underlaying queue, both old and new EPRs are stored in jUDDI registry on the next start. Then under heavier load both EPRs are selected with the result of lot error messages related to unavailable EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months
[JBoss JIRA] Created: (JBESB-1166) ESB Message Property setter/getter shortcut
by Burr Sutter (JIRA)
ESB Message Property setter/getter shortcut
-------------------------------------------
Key: JBESB-1166
URL: http://jira.jboss.com/jira/browse/JBESB-1166
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 IR1
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2.1
I have noticed that in my code I have a lot of this kind of usage for the properties on the esb message object:
esbMessage.getProperties().setProperty("MAIL_SUBJECT",subject);
esbMessage.getProperties().setProperty("MAIL_MESSAGE_NUMBER",mailMessage.getMessageNumber());
esbMessage.getProperties().setProperty("MAIL_SENT_DATE",mailMessage.getSentDate());
I propose we create "shortcut" methods on the Message class itself like so:
esbMessage.setProperty("MAIL_SUBJECT",subject);
esbMessage.setProperty("MAIL_MESSAGE_NUMBER",mailMessage.getMessageNumber());
esbMessage.setProperty("MAIL_SENT_DATE",mailMessage.getSentDate());
The use of the word "property" in the setter/getter should make it obvious what part of the message it is going into. We should also consider the same for header, attachment, etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months