4:54 a.m.
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Reporter: Kevin Conner
Assigned To: Mark Little
Priority: Minor
Fix For: 4.2 Milestone Release 3
The quickstart demonstrates a failing service but also attempts to display the contents of
the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
5 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-705) deadletter quickstart modifications
[ http://jira.jboss.com/jira/browse/JBESB-705?page=comments#action_12369167 ]
Kevin Conner commented on JBESB-705:
------------------------------------
The example also fails when running standalone
[java] 10:55:51,185 ERROR [pool-1-thread-1][J2eeConnectionManager] Could not
initialise instance.
[java] org.jboss.soa.esb.ConfigurationException: java.lang.NullPointerException
[java] at
org.jboss.soa.esb.persistence.manager.J2eeConnectionManager.init(J2eeConnectionManager.java:77)
[java] at
org.jboss.soa.esb.persistence.manager.J2eeConnectionManager.getInstance(J2eeConnectionManager.java:48)
[java] at
org.jboss.soa.esb.persistence.manager.ConnectionManagerFactory.getConnectionManager(ConnectionManagerFactory.java:27)
[java] at
org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.<init>(DBMessageStoreImpl.java:63)
[java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[java] at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
[java] at java.lang.Class.newInstance0(Class.java:350)
[java] at java.lang.Class.newInstance(Class.java:303)
[java] at
org.jboss.internal.soa.esb.persistence.format.MessageStoreFactory.getMessageStoreInstance(MessageStoreFactory.java:85)
[java] at
org.jboss.internal.soa.esb.persistence.format.MessageStoreFactory.getMessageStore(MessageStoreFactory.java:65)
[java] at
org.jboss.soa.esb.samples.quickstart.deadletter.CheckMessageStoreAction.processSuccess(CheckMessageStoreAction.java:63)
[java] at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:574)
[java] at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:317)
[java] at
org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.lang.NullPointerException
[java] at javax.naming.InitialContext.getURLScheme(InitialContext.java:228)
[java] at
javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:277)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:351)
[java] at
org.jboss.soa.esb.persistence.manager.J2eeConnectionManager.init(J2eeConnectionManager.java:73)
[java] ... 18 more
[java] Show all messages in the messageStore with category DLQ
[java] 10:55:51,191 ERROR [pool-1-thread-1][DBMessageStoreImpl]
java.lang.NullPointerException
[java] ***********
[java] Error from message store: java.lang.NullPointerException
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Mark Little
Priority: Minor
The quickstart demonstrates a failing service but also attempts to display the contents
of the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
5 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-705) deadletter quickstart modifications
[ http://jira.jboss.com/jira/browse/JBESB-705?page=all ]
Kevin Conner updated JBESB-705:
-------------------------------
Fix Version/s: (was: 4.2 Milestone Release 3)
Affects Version/s: 4.2 Milestone Release 3
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Mark Little
Priority: Minor
The quickstart demonstrates a failing service but also attempts to display the contents
of the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
7:48 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-705) deadletter quickstart modifications
[ http://jira.jboss.com/jira/browse/JBESB-705?page=all ]
Mark Little updated JBESB-705:
------------------------------
Fix Version/s: 4.2
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kurt Stam
Priority: Minor
Fix For: 4.2
The quickstart demonstrates a failing service but also attempts to display the contents
of the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
7:48 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-705) deadletter quickstart modifications
[ http://jira.jboss.com/jira/browse/JBESB-705?page=all ]
Mark Little reassigned JBESB-705:
---------------------------------
Assignee: Kurt Stam (was: Mark Little)
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kurt Stam
Priority: Minor
Fix For: 4.2
The quickstart demonstrates a failing service but also attempts to display the contents
of the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
8:32 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-705) deadletter quickstart modifications
[ http://jira.jboss.com/jira/browse/JBESB-705?page=all ]
Mark Little updated JBESB-705:
------------------------------
Fix Version/s: 4.2.1
(was: 4.2)
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kurt Stam
Priority: Minor
Fix For: 4.2.1
The quickstart demonstrates a failing service but also attempts to display the contents
of the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
1:17 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-705) deadletter quickstart modifications
[ http://jira.jboss.com/jira/browse/JBESB-705?page=all ]
Work on JBESB-705 started by Kurt Stam.
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kurt Stam
Priority: Minor
Fix For: 4.2.1
The quickstart demonstrates a failing service but also attempts to display the contents
of the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
2:14 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-705) deadletter quickstart modifications
[ http://jira.jboss.com/jira/browse/JBESB-705?page=all ]
Kurt Stam closed JBESB-705.
---------------------------
Fix Version/s: 4.2
(was: 4.2.1)
Resolution: Done
Updated to reflect new use of the DLQ in the ServiceInvoker.
deadletter quickstart modifications
-----------------------------------
Key: JBESB-705
URL: http://jira.jboss.com/jira/browse/JBESB-705
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 3
Reporter: Kevin Conner
Assigned To: Kurt Stam
Priority: Minor
Fix For: 4.2
The quickstart demonstrates a failing service but also attempts to display the contents
of the DLQ after the action has failed.
Unfortunately the DLQ may not contain the failing message at the time the
CheckMessageStoreAction is executed.
Example output from two runs is as follows
10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages
10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ
10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages
10:45:29,843 INFO [STDOUT] ***********
10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007
The message in the second run is the failed message from the first run.
This needs documenting or fixing.
--
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
6390
days inactive
6425
days old
7 comments
3 participants
participants (3)
-
Kevin Conner (JIRA) -
Kurt Stam (JIRA)
-
Mark Little (JIRA)