[JBoss JIRA] Created: (JBESB-1023) DefaultESBPropertiesSetter setExpiration should calculate the TTL from the JMSExpiration value
by Daniel Bevenius (JIRA)
DefaultESBPropertiesSetter setExpiration should calculate the TTL from the JMSExpiration value
----------------------------------------------------------------------------------------------
Key: JBESB-1023
URL: http://jira.jboss.com/jira/browse/JBESB-1023
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 IR1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Trivial
Fix For: 4.2.1 IR1
I saw the method setJMSExpiration and thought that an application could set the JMSExpiration time before sending the message. This is not true. The ttl is specified via the method send(Message message,int deliveryMode,int priority,long timeToLive) and the message provider sets the JMSExpiration value. The default behaviour in the ESB is to pass the value of getJMSExpiration as a property within the ESB, and upon leaving again setting the JMSExpiration.
The task should involve calculating the TTL from the JMSExpiration. And also use the send method described above so pass along the TTL. The last change also something needed for JBESB-646
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBESB-1047) org.jboss.soa.esb.mail.smtp.auth not present in jbossesb-properties.xml
by Eric Cartman (JIRA)
org.jboss.soa.esb.mail.smtp.auth not present in jbossesb-properties.xml
-----------------------------------------------------------------------
Key: JBESB-1047
URL: http://jira.jboss.com/jira/browse/JBESB-1047
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2
Reporter: Eric Cartman
Assigned To: Mark Little
org.jboss.soa.esb.mail.smtp.auth is not present in the default jbossesb-properties.xml.
Without this property, the smtp authentication is not working.
So I discovered the property reading the code at org.jboss.soa.esb.helpers.Email, line 381:
String sAuth = Configuration.getSmtpAuth();
if(sAuth != null) {
if(!sAuth.trim().equals("")) {
logger.warn("'" + Environment.SMTP_AUTH + "' set to an empty value.");
}
oMailP.setProperty("mail.smtp.auth", sAuth);
}
Fixed, including at deploy/jbossesb.sar/jbossesb-properties.xml.
<property name="org.jboss.soa.esb.mail.smtp.auth" value="true"/>
Thanks,
Erik
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBESB-1042) New version of /trunk/product/samples/quickstarts/tests/src/org/jboss/soa/esb/quickstart/test/SimpleCBRTest.java available for svn commit
by Len DiMaggio (JIRA)
New version of /trunk/product/samples/quickstarts/tests/src/org/jboss/soa/esb/quickstart/test/SimpleCBRTest.java available for svn commit
-----------------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-1042
URL: http://jira.jboss.com/jira/browse/JBESB-1042
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.2.1 IR1
Environment: ESB downloaded from svn - Sept 14 - revision 15120
Reporter: Len DiMaggio
Assigned To: Mark Little
Priority: Minor
Fix For: 4.2.1 IR1
A new version of a quickstart-based test is avalilable for /trunk/product/samples/quickstarts/tests/src/org/jboss/soa/esb/quickstart/test/SimpleCBRTest.java
The (2) affected files are:
1) File to replace - see attached:
/trunk/product/samples/quickstarts/tests/src/org/jboss/soa/esb/quickstart/test/SimpleCBRTest.java
2) File to update: /trunk/product/samples/quickstarts/simple_cbr
[ldimaggi@ldimaggi simple_cbr]$ diff jboss-esb.xml.new jboss-esb.xml
57,59d56
< <action name="action1" class="org.jboss.soa.esb.actions.SystemPrintln">
< <property name="print_full" value="true"/>
< </action>
68c65
< </action>
---
> </action>
85,87d81
< <action name="action2" class="org.jboss.soa.esb.actions.SystemPrintln">
< <property name="print_full" value="true"/>
< </action>
113,115d106
< <action name="action3" class="org.jboss.soa.esb.actions.SystemPrintln">
< <property name="print_full" value="true"/>
< </action>
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBESB-820) Programmatic Routing Documentation/Examples
by Burr Sutter (JIRA)
Programmatic Routing Documentation/Examples
-------------------------------------------
Key: JBESB-820
URL: http://jira.jboss.com/jira/browse/JBESB-820
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.2 Milestone Release 3
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Minor
Fix For: 4.2.1
Update documentation (perhaps update one of the quickstart examples as well) to demonstrate the use of ServiceInvoker as a method to programmatically perform routing in a custom action class.
You would still want load-balancing/fail-over as well as the retry with auto-routing to the DLQ capabilities even when you are programmatically routing.
Using ServiceInvoker sounds like the best technique.
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBESB-1031) /trunk/product/samples/quickstarts/transform*/log4j.xml files include non-printing characters at start of file
by Len DiMaggio (JIRA)
/trunk/product/samples/quickstarts/transform*/log4j.xml files include non-printing characters at start of file
--------------------------------------------------------------------------------------------------------------
Key: JBESB-1031
URL: http://jira.jboss.com/jira/browse/JBESB-1031
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2
Environment: RHEL5
JBESB downloaded from svn on Sept 12 2007
Reporter: Len DiMaggio
Assigned To: Mark Little
/trunk/product/samples/quickstarts/transform*/log4j.xml files include non-printing characters at start of file
These files:
transform_CSV2XML/log4j.xml
transform_EDI2XML_Groovy_XSLT/log4j.xml
transform_XML2POJO/log4j.xml
transform_XML2XML_date_manipulation/log4j.xml
transform_XML2XML_simple/log4j.xml
Include these characters:
od -ha /opt/ESB/trunk/product/samples/quickstarts/transform_CSV2XML/log4j.xml | head
0000000 bbef 3cbf 783f 6c6d 7620 7265 6973 6e6f
o ; ? < ? x m l sp v e r s i o n
0000020 223d 2e31 2230 6520 636e 646f 6e69 3d67
= " 1 . 0 " sp e n c o d i n g =
0000040 5522 4654 382d 3f22 0a3e 213c 4f44 5443
" U T F - 8 " ? > nl < ! D O C T
0000060 5059 2045 6f6c 3467 3a6a 6f63 666e 6769
Y P E sp l o g 4 j : c o n f i g
0000100 7275 7461 6f69 206e 5953 5453 4d45 2220
u r a t i o n sp S Y S T E M sp "
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBESB-1040) helloworld quickstart - Unexpected exception caught while processing the action pipeline
by Len DiMaggio (JIRA)
helloworld quickstart - Unexpected exception caught while processing the action pipeline
----------------------------------------------------------------------------------------
Key: JBESB-1040
URL: http://jira.jboss.com/jira/browse/JBESB-1040
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 IR1
Environment: RHEL5
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode)
JBoss ESB as downloaded from svn Sept 13, 2007
Reporter: Len DiMaggio
Assigned To: Mark Little
I'm seeing this with the helloworld quickstart:
12:51:29,724 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline
org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:265)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at java.lang.String.<init>(String.java:479)
at org.jboss.soa.esb.samples.quickstart.helloworld.MyJMSListenerAction.displayMessage(MyJMSListenerAction.java:38)
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)
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
The offending line (MyJMSListenerAction.java:38) is:
---------------------------------------------
System.out.println("Body: " + new String(message.getBody().getByteArray()));
---------------------------------------------
getByteArray() has been deprecated - this line resolves the problem for this quickstart:
---------------------------------------------
System.out.println("Message = " + message.getBody().get("org.jboss.soa.esb.message.defaultEntry"));
---------------------------------------------
--
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
17 years, 5 months