| Anonymous | Login | Signup for a new account | 12-17-2024 11:01 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0002618 | [Resin] | minor | always | 04-22-08 10:43 | 04-22-08 14:25 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 3.1.6 | Product Version | |||||
| Product Build | |||||||||
| Summary | 0002618: ActiveMQ timeout | ||||||||
| Description |
(rep by wesley) In my topic producer I manually create a JmsSesion and JmsConnection using JmsFactory and send a TextMessage, then close the connection explicitly. In my message driven bean I did not inject anything because resin should be responsible to call onMessage() method when there is a new message in topic. I've met the 6h max-active-time problem. After server running for 6 hours, it prints a log message: closing pool item from active timeout:PoolItem[activemq, 0, ActiveMQManagedConnection] |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0003005) ferg 04-22-08 14:25 |
server/30l4 |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 04-22-08 10:43 | ferg | New Issue | |
| 04-22-08 14:25 | ferg | Note Added: 0003005 | |
| 04-22-08 14:25 | ferg | Assigned To | => ferg |
| 04-22-08 14:25 | ferg | Status | new => closed |
| 04-22-08 14:25 | ferg | Resolution | open => fixed |
| 04-22-08 14:25 | ferg | Fixed in Version | => 3.1.6 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |  |
