[JBoss JIRA] Created: (JBESB-1302) QS helloworld_file_notifier issues
by Jaroslaw Kijanowski (JIRA)
QS helloworld_file_notifier issues
----------------------------------
Key: JBESB-1302
URL: http://jira.jboss.com/jira/browse/JBESB-1302
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1
Reporter: Jaroslaw Kijanowski
1. missing "mep" attributes in jbos-esb-unfiltered.xml causes WARN messages
2. sendesb target in build.xml should run org.jboss.soa.esb.samples.quickstart.helloworldfilenotifier.test.SendEsbMessage but runs org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage
3. org.jboss.soa.esb.samples.quickstart.helloworldfilenotifier.MyJMSListenerAction should be aware that it can get two types of message, a String and a byte array:
public Message displayMessage(Message message) throws Exception{
String content = null;
if (message.getBody().get() instanceof String) {
content = (String)message.getBody().get();
} else if (message.getBody().get() instanceof byte[]) {
content = new String((byte[])message.getBody().get());
}
System.out.println("&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&");
System.out.println("Body: " + content);
System.out.println("&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&");
return message;
}
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBESB-719) The messages can be lost in case of ESB termination
by Jiri Pechanec (JIRA)
The messages can be lost in case of ESB termination
---------------------------------------------------
Key: JBESB-719
URL: http://jira.jboss.com/jira/browse/JBESB-719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assigned To: Mark Little
Even if the ESB is using internally reliable JMS as a transport the messages can be lost during ESB termination. The reasons for this behaviour are two
1) ESB uses internally queue sessions with AUTO_ACK flag
2) Pick-up and deliver couriers works in different session
Proposed solution
1) Change flag to CLIENT_ACK
2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If the allocated session is stored into ThreadLocal variable and returned by the subsequent calls by the same thread and get commited on call JMSConnectionPool.closeSession() then all internal message transfers via JMS will be done in transaction - one transfer/one transaction.
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBESB-1319) Problem with ByteArray in the trailblazer
by Kurt Stam (JIRA)
Problem with ByteArray in the trailblazer
-----------------------------------------
Key: JBESB-1319
URL: http://jira.jboss.com/jira/browse/JBESB-1319
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1
Reporter: Kurt Stam
Fix For: 4.2.1 CP1
I just heard from a user that:
"The trailblazer application required some changes. I was getting a NullPointerException in the BankResponseActions class (I think it was line 47 - the code is - ConfigTree tree = ConfigTree.fromXml(new String(message.getBody().getByteArray()));). The getByteArray() is causing the NullPointerException. I had to change the code to ConfigTree tree = ConfigTree.fromXml((String)message.getBody().get());
This allowed the trailblazer application to run successfully. "
It looks to me that this is still a problem.
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBESB-1318) DataFilerQueue messages generates warnings
by Jiri Pechanec (JIRA)
DataFilerQueue messages generates warnings
------------------------------------------
Key: JBESB-1318
URL: http://jira.jboss.com/jira/browse/JBESB-1318
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Priority: Minor
Internally in ESB there are messages generated and sent to DataFilerQueue. As they do not have ReplyTo set, the messages generates warnings
12:30:49,726 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DataFilerQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-4099 RelatesTo: jms:correlationID#39b6adae-7ebd-411f-a9ee-ef97b5e1db55
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBESB-1035) jbpm admin console throws exceptions on shutdown of App Server/ESB Server
by Burr Sutter (JIRA)
jbpm admin console throws exceptions on shutdown of App Server/ESB Server
-------------------------------------------------------------------------
Key: JBESB-1035
URL: http://jira.jboss.com/jira/browse/JBESB-1035
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2.1 IR1
12:08:56,040 ERROR [JDBCExceptionReporter] You are trying to use a connection factory that has been
shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException:
You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is nul
l.)
12:08:56,041 ERROR [JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds
org.hibernate.exception.GenericJDBCException: Cannot open connection
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.j
ava:103)
--
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
18 years, 5 months