[JBoss JIRA] Created: (JBESB-314) JMS Bank sending reply exception
by Daniel Brum (JIRA)
JMS Bank sending reply exception
--------------------------------
Key: JBESB-314
URL: http://jira.jboss.com/jira/browse/JBESB-314
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0 RC1
Reporter: Daniel Brum
Assigned To: Daniel Brum
Fix For: 4.0
>From the JMSBank code (NON-esb):
[java] 15:12:54,260 INFO [Bank] Bank 'JMSBasedBank' received a request for SSN=1234567890 for $1000 over 12 months.
[java] 15:12:54,263 INFO [Bank] Bank 'JMSBasedBank offers SSN=1234567890 BankQuoteReply=[interestRate=8.60, quoteId=JMSBasedBank-0, errorCode=0, customerUID=1234567890]
[java] 15:12:54,291 INFO [ManagerJMS] Looking up connection factory
[java] 15:12:54,311 INFO [ManagerJMS] Creating connection
[java] 15:12:54,316 INFO [ManagerJMS] Creating session
[java] 15:12:54,350 ERROR [ManagerJMS] This destination does not exist !
[java] javax.jms.JMSException: This destination does not exist !
[java] at org.jboss.mq.server.JMSDestinationManager.createQueue(JMSDestinationManager.java:582)
[java] at org.jboss.mq.server.JMSServerInterceptorSupport.createQueue(JMSServerInterceptorSupport.java:163)
[java] at org.jboss.mq.server.TracingInterceptor.createQueue(TracingInterceptor.java:307)
[java] at org.jboss.mq.server.JMSServerInvoker.createQueue(JMSServerInvoker.java:164)
[java] at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:133)
[java] at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:396)
[java] at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:392)
[java] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
[java] at java.lang.Thread.run(Thread.java:595)
--
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, 4 months
[JBoss JIRA] Created: (JBESB-298) URL parsing in EdtFtpImpl.checkParms()
by Bernard Tison (JIRA)
URL parsing in EdtFtpImpl.checkParms()
--------------------------------------
Key: JBESB-298
URL: http://jira.jboss.com/jira/browse/JBESB-298
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Bernard Tison
Assigned To: Mark Little
I think there might be a problem with the way user/password information is parsed from the FTP URL for a FTP Gateway.
This is based on the static router quickstart example.
The jbossesb.xml contains the following provider definition:
Code:
<ftp-provider name="FTPprovider" hostname="localhost" >
<ftp-bus busid="StaticRouterFtpGW" >
<ftp-message-filter
username="ftpuser"
password="ftppassword"
passive="false"
directory="/tmp/esbInput"
input-suffix=".dat"
/>
</ftp-bus>
</ftp-provider>
This results in the following definition in the jbossesb-gateway.xml:
Code:
<Ftp-Gateway URL="ftp://ftpuser:ftppassword@localhost:/tmp/esbInput"
errorDelete="true" gatewayClass="org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener"
...(non-relevant portion removed) "/>
When the gateway is initialized, the org.jboss.internal.soa.esb.util.EdtFtpImpl class will parse the URL and connect to the FTP server.
To parse the username/password out of the URL, the checkParms() method of the EdtFtpImpl class uses the following code (lines 190-198):
Code:
String[] sa = (null == url) ? null
: url.getAuthority().split(":");
m_sUser = (null!=sa) ? sa[0] :m_oParms.getAttribute(PARMS_USER);
if (null == m_sUser)
throw new Exception("No username specified for FTP");
m_sPasswd = (null!=sa) ? sa[1] :m_oParms.getAttribute(PARMS_PASSWD);
The url.getAuthority() method returns ftpuser:ftppassword@localhost, which results in m_sUser="ftpuser" and m_sPasswd="ftppassword@localhost". This should be: m_sUser="ftpuser" and m_sPasswd="ftppassword".
Suggestion for fix: use url.getUserInfo() to get the user/password out of the FTP URL. This is how it is done in the EdtFtpImpl(FTPEpr p_oP, boolean p_bConnect) constructor.
--
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, 4 months
[JBoss JIRA] Commented: (JBRULES-218) Add 'forall' Conditional Element
by Edson Tirelli (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-218?page=comments#action_12349525 ]
Edson Tirelli commented on JBRULES-218:
---------------------------------------
$ svn log -r 8677 -v
------------------------------------------------------------------------
r8677 | tirelli | 2007-01-03 18:57:09 -0300 (Wed, 03 Jan 2007) | 1 line
Changed paths:
M /labs/jbossrules/trunk/drools-core/.project
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/base/BaseClassFieldExtractor.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Accumulate.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Collect.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Column.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/ConditionalElement.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/EvalCondition.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/From.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/GroupElement.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/LogicTransformer.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/Rule.java
A /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/rule/RuleConditionElement.java
D /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/spi/AvailableVariables.java
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/spi/ColumnExtractor.java
A /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/spi/DeclarationScopeResolver.java (from /labs/jbossrules/trunk/dr
ools-core/src/main/java/org/drools/spi/AvailableVariables.java:8603)
M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/spi/FunctionResolver.java
M /labs/jbossrules/trunk/drools-core/src/test/java/org/drools/rule/LogicTransformerTest.java
M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_processTree1.dat
M /labs/jbossrules/trunk/drools-core/src/test/resources/correct_transform1.dat
JBRULES-218: adding support to variable scope resolution in core
------------------------------------------------------------------------
> Add 'forall' Conditional Element
> --------------------------------
>
> Key: JBRULES-218
> URL: http://jira.jboss.com/jira/browse/JBRULES-218
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Mark Proctor
> Assigned To: Edson Tirelli
> Fix For: 3.1-m2
>
>
> Add 'forall' Conditional Element
--
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, 4 months