You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(14) |
Dec
(56) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(92) |
Feb
(115) |
Mar
(99) |
Apr
(100) |
May
(13) |
Jun
(149) |
Jul
(148) |
Aug
(132) |
Sep
(129) |
Oct
(79) |
Nov
(97) |
Dec
(37) |
2004 |
Jan
(69) |
Feb
(92) |
Mar
(51) |
Apr
(77) |
May
(70) |
Jun
(18) |
Jul
(83) |
Aug
(43) |
Sep
(26) |
Oct
(27) |
Nov
(59) |
Dec
(50) |
2005 |
Jan
(41) |
Feb
(59) |
Mar
(44) |
Apr
(60) |
May
(78) |
Jun
(23) |
Jul
(61) |
Aug
(29) |
Sep
(18) |
Oct
(27) |
Nov
(52) |
Dec
(44) |
2006 |
Jan
(42) |
Feb
(30) |
Mar
(20) |
Apr
(28) |
May
(29) |
Jun
(29) |
Jul
(26) |
Aug
(7) |
Sep
(21) |
Oct
(19) |
Nov
(8) |
Dec
(36) |
2007 |
Jan
(10) |
Feb
(13) |
Mar
(6) |
Apr
(27) |
May
(22) |
Jun
(13) |
Jul
(16) |
Aug
(18) |
Sep
(4) |
Oct
(19) |
Nov
(7) |
Dec
(4) |
2008 |
Jan
(1) |
Feb
(8) |
Mar
(11) |
Apr
|
May
(4) |
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(6) |
2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(3) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Marton B. <bal...@ya...> - 2017-02-08 10:42:13
|
Hi am new to using open jms and just installed it on my RH Linux VM. When running the start script, after displaying a few lines nothing seems to happen: ab-iss$ ./startup.sh Using OPENJMS_HOME: /apps/jms/openjms-0.7.7-beta-1 Using JAVA_HOME: /etc/alternatives/java_sdk OpenJMS 0.7.7-beta-1 The OpenJMS Group. (C) 1999-2007. All rights reserved. http://openjms.sourceforge.net 04:29:34.426 INFO [main] - Server accepting connections on tcp://192.168.0.108:3035/ 04:29:34.461 INFO [main] - JNDI service accepting connections on tcp://192.168.0.108:3035/ 04:29:34.462 INFO [main] - Admin service accepting connections on tcp://192.168.0.108:3035/ 04:29:34.571 INFO [main] - Server accepting connections on rmi://192.168.0.108:1099/ 04:29:34.572 INFO [main] - JNDI service accepting connections on rmi://192.168.0.108:1099/ 04:29:34.572 INFO [main] - Admin service accepting connections on rmi://192.168.0.108:1099/ How can I check the status and what could be the reason for this behaviour? Do I need to do any configuration before running the server? Thank you, Marton |
From: Greg H. <gre...@gm...> - 2015-11-25 07:38:39
|
See activemq, its supported! On 24 November 2015 at 12:47, Vijay Vempati <vij...@ta...> wrote: > Hi, > > > > We are able to run the OpenJms 0.7.7 on Linux using, in the back ground – > openjms.sh run & > > > > But the problem is, it dies down automatically after some time like a day. > Please suggest / help regarding this. > > > > Thanks, > > Vijay > > ************************************************************************************************************************************************************** > DISCLAIMER This e-mail is confidential and may be legally privileged. It is > intended solely for the addressee. If you are not the intended recipient, > you are not authorized to read, print, retain, copy, disseminate, > distribute, or use this message or any part thereof. If you are not the > original intended recipient of the message, please contact the sender by > reply email and destroy all copies of the original message. > www.tarangtech.com > ************************************************************************************************************************************************************** > > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple > OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > _______________________________________________ > openjms-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjms-user > > |
From: mohammad a. <mrm...@gm...> - 2015-11-24 22:22:25
|
Please send me more details On Tue, Nov 24, 2015 at 2:47 PM, Vijay Vempati < vij...@ta...> wrote: > Hi, > > > > We are able to run the OpenJms 0.7.7 on Linux using, in the back ground – > openjms.sh run & > > > > But the problem is, it dies down automatically after some time like a day. > Please suggest / help regarding this. > > > > Thanks, > > Vijay > > ************************************************************************************************************************************************************** > DISCLAIMER This e-mail is confidential and may be legally privileged. It is > intended solely for the addressee. If you are not the intended recipient, > you are not authorized to read, print, retain, copy, disseminate, > distribute, or use this message or any part thereof. If you are not the > original intended recipient of the message, please contact the sender by > reply email and destroy all copies of the original message. > www.tarangtech.com > ************************************************************************************************************************************************************** > > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple > OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > _______________________________________________ > openjms-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjms-user > > -- * Regards,Mohammad AlaaSoftware Engineer <http://eg.linkedin.com/in/engmalaa>Mobile:+2 011 552 22023* |
From: Vijay V. <vij...@ta...> - 2015-11-24 12:59:46
|
Hi, We are able to run the OpenJms 0.7.7 on Linux using, in the back ground - openjms.sh run & But the problem is, it dies down automatically after some time like a day. Please suggest / help regarding this. Thanks, Vijay ************************************************************************************************************************************************************** DISCLAIMER This e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you are not the original intended recipient of the message, please contact the sender by reply email and destroy all copies of the original message. www.tarangtech.com ************************************************************************************************************************************************************** |
From: <lly...@co...> - 2014-03-23 03:15:26
|
I am using derby standalone server 10.9.1.0 along with jms 0.7.7 beta. When I start the JMS server I get the following exception. I have also included the corresponding Derby error log output. Has anyone seen this or know of a fix or work-around? Here's the Derby log segment, notice the offending insert statement in to the destinations table: Thu Mar 20 08:15:24 EDT 2014 Thread[DRDAConnThread_3,5,main] (XID = 412), (SESSIONID = 10), (DATABASE = openjmsdb), (DRDAID = ????????.???-939562076942445192{9}), Failed Statement is: insert into destinations (name, isqueue, destinationid) values (?, ?, ?) with 3 parameters begin parameter #1: gndcon_q :end parameter begin parameter #2: true :end parameter begin parameter #3: 1 :end parameter ERROR 22001: A truncation error was encountered trying to shrink CHAR 'true' to length 1. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown Source) at org.apache.derby.iapi.types.SQLChar.normalize(Unknown Source) at org.apache.derby.iapi.types.SQLChar.normalize(Unknown Source) at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown Source) at org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeColumn(Unknown Source) at org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown Source) at org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown Source) at org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown Source) at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.drda.DRDAStatement.execute(Unknown Source) at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTTobjects(Unknown Source) at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTT(Unknown Source) at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source) at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source) It appears that parameter 2 was meant to be a boolean value. Here's the exception from JMS: OpenJMS 0.7.7-beta-1 The OpenJMS Group. (C) 1999-2007. All rights reserved. http://openjms.sourceforge.net 23:13:21.720 ERROR [main] - Failed to create persistent destination topic1 org.exolab.jms.persistence.PersistenceException: Destinations.add failed with ja va.sql.SQLDataException: A truncation error was encountered trying to shrink CHA R 'false' to length 1. at org.exolab.jms.persistence.Destinations.add(Destinations.java:134) at org.exolab.jms.persistence.RDBMSAdapter.addDestination(RDBMSAdapter.j ava:583) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:620) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureTopics(Des tinationConfigurator.java:149) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:129) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.726 ERROR [main] - Failed to register persistent topic topic1 javax.jms.JMSException: Failed to create persistent destination topic1: Destinat ions.add failed with java.sql.SQLDataException: A truncation error was encounter ed trying to shrink CHAR 'false' to length 1. at org.exolab.jms.messagemgr.DestinationManagerImpl.cleanup(DestinationM anagerImpl.java:784) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:623) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureTopics(Des tinationConfigurator.java:149) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:129) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.740 ERROR [main] - Failed to create persistent destination queue1 org.exolab.jms.persistence.PersistenceException: Destinations.add failed with ja va.sql.SQLDataException: A truncation error was encountered trying to shrink CHA R 'true' to length 1. at org.exolab.jms.persistence.Destinations.add(Destinations.java:134) at org.exolab.jms.persistence.RDBMSAdapter.addDestination(RDBMSAdapter.j ava:583) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:620) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.751 ERROR [main] - Failed to register persistent queue queue1 javax.jms.JMSException: Failed to create persistent destination queue1: Destinat ions.add failed with java.sql.SQLDataException: A truncation error was encounter ed trying to shrink CHAR 'true' to length 1. at org.exolab.jms.messagemgr.DestinationManagerImpl.cleanup(DestinationM anagerImpl.java:784) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:623) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.772 ERROR [main] - Failed to create persistent destination queue2 org.exolab.jms.persistence.PersistenceException: Destinations.add failed with ja va.sql.SQLDataException: A truncation error was encountered trying to shrink CHA R 'true' to length 1. at org.exolab.jms.persistence.Destinations.add(Destinations.java:134) at org.exolab.jms.persistence.RDBMSAdapter.addDestination(RDBMSAdapter.j ava:583) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:620) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.782 ERROR [main] - Failed to register persistent queue queue2 javax.jms.JMSException: Failed to create persistent destination queue2: Destinat ions.add failed with java.sql.SQLDataException: A truncation error was encounter ed trying to shrink CHAR 'true' to length 1. at org.exolab.jms.messagemgr.DestinationManagerImpl.cleanup(DestinationM anagerImpl.java:784) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:623) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.792 ERROR [main] - Failed to create persistent destination queue3 org.exolab.jms.persistence.PersistenceException: Destinations.add failed with ja va.sql.SQLDataException: A truncation error was encountered trying to shrink CHA R 'true' to length 1. at org.exolab.jms.persistence.Destinations.add(Destinations.java:134) at org.exolab.jms.persistence.RDBMSAdapter.addDestination(RDBMSAdapter.j ava:583) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:620) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.802 ERROR [main] - Failed to register persistent queue queue3 javax.jms.JMSException: Failed to create persistent destination queue3: Destinat ions.add failed with java.sql.SQLDataException: A truncation error was encounter ed trying to shrink CHAR 'true' to length 1. at org.exolab.jms.messagemgr.DestinationManagerImpl.cleanup(DestinationM anagerImpl.java:784) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:623) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.813 ERROR [main] - Failed to create persistent destination refinery_q org.exolab.jms.persistence.PersistenceException: Destinations.add failed with ja va.sql.SQLDataException: A truncation error was encountered trying to shrink CHA R 'true' to length 1. at org.exolab.jms.persistence.Destinations.add(Destinations.java:134) at org.exolab.jms.persistence.RDBMSAdapter.addDestination(RDBMSAdapter.j ava:583) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:620) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.831 ERROR [main] - Failed to register persistent queue refinery_q javax.jms.JMSException: Failed to create persistent destination refinery_q: Dest inations.add failed with java.sql.SQLDataException: A truncation error was encou ntered trying to shrink CHAR 'true' to length 1. at org.exolab.jms.messagemgr.DestinationManagerImpl.cleanup(DestinationM anagerImpl.java:784) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:623) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.841 ERROR [main] - Failed to create persistent destination gndcon_q org.exolab.jms.persistence.PersistenceException: Destinations.add failed with ja va.sql.SQLDataException: A truncation error was encountered trying to shrink CHA R 'true' to length 1. at org.exolab.jms.persistence.Destinations.add(Destinations.java:134) at org.exolab.jms.persistence.RDBMSAdapter.addDestination(RDBMSAdapter.j ava:583) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:620) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.852 ERROR [main] - Failed to register persistent queue gndcon_q javax.jms.JMSException: Failed to create persistent destination gndcon_q: Destin ations.add failed with java.sql.SQLDataException: A truncation error was encount ered trying to shrink CHAR 'true' to length 1. at org.exolab.jms.messagemgr.DestinationManagerImpl.cleanup(DestinationM anagerImpl.java:784) at org.exolab.jms.messagemgr.DestinationManagerImpl.createPersistentDest ination(DestinationManagerImpl.java:623) at org.exolab.jms.messagemgr.DestinationManagerImpl.createDestination(De stinationManagerImpl.java:278) at org.exolab.jms.messagemgr.DestinationConfigurator.configureQueues(Des tinationConfigurator.java:180) at org.exolab.jms.messagemgr.DestinationConfigurator.doStart(Destination Configurator.java:130) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) 23:13:21.953 INFO [main] - Server accepting connections on tcp://192.168.1.20:3 035/ 23:13:21.957 INFO [main] - JNDI service accepting connections on tcp://192.168. 1.20:3035/ 23:13:21.960 INFO [main] - Admin service accepting connections on tcp://192.168 .1.20:3035/ 23:13:22.032 INFO [main] - Server accepting connections on rmi://192.168.1.20:1 099/ 23:13:22.034 INFO [main] - JNDI service accepting connections on rmi://192.168. 1.20:1099/ 23:13:22.035 INFO [main] - Admin service accepting connections on rmi://192.168 .1.20:1099/ |
From: Vishal C. <vis...@ya...> - 2013-03-15 23:00:21
|
http://rent-let.dk/wp-content/fresh.php?jbemwv702qgexi ===================== Someone else speaks for me, and I can't get a word in edgewise. |
From: Greg H. <gre...@gm...> - 2012-11-12 13:32:59
|
Not sure this is supported any more, also, if its not too late I would switch to activemq, which is. On 10 November 2012 19:48, Michael O'Sullivan <mj...@gm...> wrote: > Hi there, > > I am using the latest release of openjms. In a small local program I am > running to demonstrate queues, I am trying to create a durable topic > subscriber programmatically to subscribe to a topic I am also creating > programmatically. > However, whenever I call createDurableSubscriber(topic, > "alastingsubscription") on my TopicSession object, I always get the > following exception: > > > Unfortunately, an error occured :javax.jms.InvalidDestinationException: No > destination with name=MobileComputing exists > javax.jms.InvalidDestinationException: No destination with > name=MobileComputing exists > at > org.exolab.jms.messagemgr.ConsumerManagerImpl.getDestination(Consumer > ManagerImpl.java:756) > at > org.exolab.jms.messagemgr.ConsumerManagerImpl.createInactiveDurableCo > nsumer(ConsumerManagerImpl.java:571) > at > org.exolab.jms.messagemgr.ConsumerManagerImpl.createDurableConsumer(C > onsumerManagerImpl.java:345) > at > org.exolab.jms.server.ServerSessionImpl.createDurableConsumer(ServerS > essionImpl.java:343) > at > org.exolab.jms.server.net.RemoteServerSession.createDurableConsumer(R > emoteServerSession.java:245) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:572) > > at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:530) > at > org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(Thread > Pool.java:211) > at > EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So > urce) > at java.lang.Thread.run(Unknown Source) > > I have been trying different things for a while now with no luck. The > strange thing is, if I create a non-durable topic subscriber, it works > perfectly fine. I can also create a TopicPublisher programmatically for the > programatically created topic with no problems. I could create the topic > with the given name in the config file manually and do a context lookup, > and then create a durable subscriber to it, and that does work perfectly. > However, for the purposes of the demonstration, I want the users to be able > to create topics programmatically on the fly. > > I was looking through the source code for openjms using the above stack > trace. The createInactiveDurablableSubscriber() method in > ConsumerManagerImpl.java calls the getDestination() method, also located in > ConsumerManagerImpl.java. It passes a boolean argument of false, called > "create" in the formal parameter list of getDestination(), to > getDestination(). The javadoc for getDestination() says that "create" > indicates if the destination should be created automatically or not if it > does not already exist. This I believe leads to the exception being thrown. > The createSubscriber() method in ConsumerManagerImpl.java also calls > getDestination(), but it passes a true boolean value instead, which leads > to the destination being created in this case, which might explain why > creating a non-durable subscriber above, actually works. So I am not sure > how to approach this problem. > > Any advice here would be very much appreciated. > > Thanks very much, > > Michael > > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > openjms-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjms-user > |
From: <edi...@ci...> - 2012-11-11 08:25:57
|
---------------------------- Confidencialidad: Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucción. Disclaimer: This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately. ---------------------------- |
From: Michael O'S. <mj...@gm...> - 2012-11-10 19:48:41
|
Hi there, I am using the latest release of openjms. In a small local program I am running to demonstrate queues, I am trying to create a durable topic subscriber programmatically to subscribe to a topic I am also creating programmatically. However, whenever I call createDurableSubscriber(topic, "alastingsubscription") on my TopicSession object, I always get the following exception: Unfortunately, an error occured :javax.jms.InvalidDestinationException: No destination with name=MobileComputing exists javax.jms.InvalidDestinationException: No destination with name=MobileComputing exists at org.exolab.jms.messagemgr.ConsumerManagerImpl.getDestination(Consumer ManagerImpl.java:756) at org.exolab.jms.messagemgr.ConsumerManagerImpl.createInactiveDurableCo nsumer(ConsumerManagerImpl.java:571) at org.exolab.jms.messagemgr.ConsumerManagerImpl.createDurableConsumer(C onsumerManagerImpl.java:345) at org.exolab.jms.server.ServerSessionImpl.createDurableConsumer(ServerS essionImpl.java:343) at org.exolab.jms.server.net.RemoteServerSession.createDurableConsumer(R emoteServerSession.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:572) at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:530) at org.exolab.jms.common.threads.ThreadPool$NotifyingRunnable.run(Thread Pool.java:211) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So urce) at java.lang.Thread.run(Unknown Source) I have been trying different things for a while now with no luck. The strange thing is, if I create a non-durable topic subscriber, it works perfectly fine. I can also create a TopicPublisher programmatically for the programatically created topic with no problems. I could create the topic with the given name in the config file manually and do a context lookup, and then create a durable subscriber to it, and that does work perfectly. However, for the purposes of the demonstration, I want the users to be able to create topics programmatically on the fly. I was looking through the source code for openjms using the above stack trace. The createInactiveDurablableSubscriber() method in ConsumerManagerImpl.java calls the getDestination() method, also located in ConsumerManagerImpl.java. It passes a boolean argument of false, called "create" in the formal parameter list of getDestination(), to getDestination(). The javadoc for getDestination() says that "create" indicates if the destination should be created automatically or not if it does not already exist. This I believe leads to the exception being thrown. The createSubscriber() method in ConsumerManagerImpl.java also calls getDestination(), but it passes a true boolean value instead, which leads to the destination being created in this case, which might explain why creating a non-durable subscriber above, actually works. So I am not sure how to approach this problem. Any advice here would be very much appreciated. Thanks very much, Michael |
From: Joshua L. <jos...@gm...> - 2012-09-19 17:14:43
|
Hi, I'm trying to build an OpenJMS heartbeat function. When running the code for long periods of time and sending large amounts of messages to the topic, it appears that the connection is lost. Initially, the heartbeats (sent every 2 seconds, for testing purposes), are sent and received without incident. However, while leaving the program on overnight, I find the following error message: javax.jms.JMSException: Connection lost at org.exolab.jms.client.net.JMSExceptionAdapter.adapt(JMSExceptionAdapter.java:79) at org.exolab.jms.server.net.RemoteServerSession__Proxy.send(RemoteServerSession__Proxy.java:393) at org.exolab.jms.client.net.JmsSessionStubImpl.send(JmsSessionStubImpl.java:153) at org.exolab.jms.client.JmsSession.sendMessage(JmsSession.java:1164) at org.exolab.jms.client.JmsMessageProducer.send(JmsMessageProducer.java:359) at org.exolab.jms.client.JmsMessageProducer.send(JmsMessageProducer.java:247) at HBSignalProducer.startHeartbeatSignal(HBSignalProducer.java:65) at HBSignalProducer.run(HBSignalProducer.java:205) at java.lang.Thread.run(Thread.java:722) Thanks. |
From: sunil c. <sun...@gm...> - 2012-05-02 07:52:47
|
Hi, We have been using OpenJMS for sending messages and have found it to be great. However, one of the members of our team recently changed his router and is experiencing long delays in getting a Session. On most systems the line javax.jms.Session session = s_JmsConnection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE); returns in about 4 seconds. For servers in a single location that are behind a new router, it consistently takes 189 seconds. The server is configured with only the TCP connector. <ServerConfiguration host="*.*.*.*" embeddedJNDI="true" /> <TcpConfiguration port="3035" jndiPort="3035" /> <Connectors> <Connector scheme="tcp"> <ConnectionFactories> <ConnectionFactory name="ConnectionFactory" /> </ConnectionFactories> </Connector> </Connectors> Its truly baffling how changing a router is causing this huge delay in getting a session. Any help is greatly appreciated. Thanks Sunil |
From: N W <ema...@ya...> - 2012-02-13 22:26:21
|
unsubscribe |
From: Greg H. <gre...@gm...> - 2012-02-12 16:17:47
|
Hello, Don't think openJMS is under active develpement any more, checkout http://activemq.apache.org/ Cheers. On 12 February 2012 06:37, achille mbougueng <ach...@ya...>wrote: > Hi > > i'm a new user of openJMS > > After installations and all set ups, i've to write for using > queueconnection > > please find attached my sender code programm > > I'va this exception > > Exception in thread "main" javax.naming.NoInitialContextException: Need to > specify class name in environment or system property, > or as an applet parameter, or in an application resource file: > java.naming.factory.initial > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) > at > javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at Sender.<init>(Sender.java:19) > at Sender.main(Sender.java:44) > > Please how to fix it > > Thanks > ------------------------------ > Achille MBOUGUENG > Tel: 0033 (0)7 61 70 57 45 > skype: sim_patricx > web: achillesimo.creativdev-mada.com > www.andandoo.info <http://achillesimo.creativdev-mada.com/> > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > openjms-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjms-user > > |
From: achille m. <ach...@ya...> - 2012-02-12 06:37:39
|
Hi i'm a new user of openJMS After installations and all set ups, i've to write for using queueconnection please find attached my sender code programm I'va this exception Exception in thread "main" javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) at javax.naming.InitialContext.lookup(InitialContext.java:392) at Sender.<init>(Sender.java:19) at Sender.main(Sender.java:44) Please how to fix it Thanks ________________________________ Achille MBOUGUENG Tel: 0033 (0)7 61 70 57 45 skype: sim_patricx web: achillesimo.creativdev-mada.com www.andandoo.info |
From: Sudharamya K. <sud...@tc...> - 2011-03-08 11:44:43
|
<FONT face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size=2><DIV>Dear tim,</DIV><DIV> </DIV><DIV>Am trying one simple example in tomcat with OPENJMS.</DIV><DIV><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2><P align=left>try</B></FONT></FONT><FONT size=2> {</P><P align=left>String factory_name = </FONT><FONT color=#2a00ff size=2><FONT color=#2a00ff size=2>"JmsTopicConnectionFactory"</FONT></FONT><FONT size=2>;</P><P align=left>Properties props = </FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>new</B></FONT></FONT><FONT size=2> Properties();</P></FONT><FONT size=2><P align=left></FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>if</B></FONT></FONT><FONT size=2> (url.startsWith(</FONT><FONT color=#2a00ff size=2><FONT color=#2a00ff size=2>"rmi"</FONT></FONT><FONT size=2>)) {</P><P align=left>props.put(Context.</FONT><I><FONT color=#0000c0 size=2><FONT color=#0000c0 size=2>INITIAL_CONTEXT_FACTORY</I></FONT></FONT><FONT size=2>,</P><P align=left></FONT><FONT color=#2a00ff size=2><FONT color=#2a00ff size=2>"org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory"</FONT></FONT><FONT size=2>);</P><P align=left></P><P align=left>} </FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>else</B></FONT></FONT><FONT size=2> {</P><P align=left>props.put(Context.</FONT><I><FONT color=#0000c0 size=2><FONT color=#0000c0 size=2>INITIAL_CONTEXT_FACTORY</I></FONT></FONT><FONT size=2>,</P><P align=left></FONT><FONT color=#2a00ff size=2><FONT color=#2a00ff size=2>"org.exolab.jms.jndi.mipc.IpcJndiInitialContextFactory"</FONT></FONT><FONT size=2>);</P><P align=left>}</P><P align=left>props.put(Context.</FONT><I><FONT color=#0000c0 size=2><FONT color=#0000c0 size=2>PROVIDER_URL</I></FONT></FONT><FONT size=2>, url);</P></FONT><FONT size=2><P align=left></FONT><FONT color=#3f7f5f size=2><FONT color=#3f7f5f size=2>// lookup the connection factory from the context</P></FONT></FONT><FONT size=2><P align=left>Context context = </FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>new</B></FONT></FONT><FONT size=2> InitialContext(props);</P></FONT><FONT size=2><P align=left>TopicConnectionFactory factory = (TopicConnectionFactory)</P><P align=left>context.lookup(factory_name);</P></FONT><FONT size=2><P align=left></FONT><FONT color=#3f7f5f size=2><FONT color=#3f7f5f size=2>// if we can't find the factory then throw an exception</P></FONT></FONT><FONT size=2><P align=left></FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>if</B></FONT></FONT><FONT size=2> (factory != </FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>null</B></FONT></FONT><FONT size=2>) {</P><P align=left>TopicConnection connection = factory.createTopicConnection();</P><P align=left>TopicSession session = connection.createTopicSession(</P><P align=left></FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>false</B></FONT></FONT><FONT size=2>, Session.</FONT><I><FONT color=#0000c0 size=2><FONT color=#0000c0 size=2>AUTO_ACKNOWLEDGE</I></FONT></FONT><FONT size=2>);</P><P align=left>Topic topic = session.createTopic(topic_name);</P><P align=left></P><P align=left></FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>if</B></FONT></FONT><FONT size=2> (topic != </FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>null</B></FONT></FONT><FONT size=2>) {</P><P align=left>TopicPublisher publisher = session.createPublisher(topic);</P><P align=left></FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>if</B></FONT></FONT><FONT size=2> (publisher != </FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>null</B></FONT></FONT><FONT size=2>) {</P><P align=left></FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2> for</B></FONT></FONT><FONT size=2> (</FONT><B><FONT color=#7f0055 size=2><FONT color=#7f0055 size=2>int</B></FONT></FONT><FONT size=2> index = 0; index < count; index++) {</P><P align=left> publisher.publish(session.createTextMessage(</P><P align=left></FONT><FONT color=#2a00ff size=2><FONT color=#2a00ff size=2> "publish message "</FONT></FONT><FONT size=2> + count));</P><P align=left> }</P><P align=left>}</P><P align=left>}</P><P align=left>}</P><P align=left></FONT>While running am getting the following error:</P></DIV><DIV>java.lang.NoClassDefFoundError: Could not initialize class org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory</DIV><DIV> </DIV><DIV>jARS iNCLUDED ARE:</DIV><DIV>jms-1.1</DIV><DIV>jndi-1.2.1</DIV><DIV>openjms-client-0.7.6-rc1</DIV><DIV>openjms-0.7.7-beta-1</DIV><DIV>exolabcore-0.3.5</DIV><DIV>openjms-0.7.4<BR></DIV><DIV>Though this class is available in jar, it is not recognizing properly.</DIV><DIV> </DIV><DIV>Please suggest me required JARS, in order to run this example in tomcat.<BR></DIV><DIV>Thanks in Advance,</DIV><DIV> </DIV><DIV>Regards,<BR>Sudha<BR>Tata Consultancy Services<BR>Mailto: <A href="mailto:sud...@tc..." target=blank>sud...@tc...</A><BR></DIV></FONT><pre style="white-space:normal">=====-----=====-----=====<br>Notice: The information contained in this e-mail<br>message and/or attachments to it may contain <br>confidential or privileged information. If you are <br>not the intended recipient, any dissemination, use, <br>review, distribution, printing or copying of the <br>information contained in this e-mail message <br>and/or attachments to it are strictly prohibited. If <br>you have received this communication in error, <br>please notify us by reply e-mail or telephone and <br>immediately and permanently delete the message <br>and any attachments. Thank you<br><br><br></pre> |
From: Eric J. <er...@ti...> - 2010-11-20 01:00:21
|
For the purposes of defining SOAP/JMS, over the past few years, a few of us have been working on defining a JMS URI scheme. Seems like a good idea to explicitly ask if anyone here has any feedback on the proposed URI: http://tools.ietf.org/html/draft-merrick-jms-uri-09 I've got an updated version with a few changes in the works, but they're minor. -Eric. |
From: Dey, A. <anu...@ca...> - 2010-09-02 11:41:53
|
import java.util.HashMap; import javax.jms.JMSException; import javax.jms.Session; import javax.jms.TextMessage; import javax.jms.Topic; import javax.jms.TopicConnection; import javax.jms.TopicConnectionFactory; import javax.jms.TopicPublisher; import javax.jms.TopicSession; /** * The LXKJMSPublisher class publishes messages to a topic. It * contains a constructor, a publishMessages method, and a finish method. * */ public class LXKJMSPublisher { TopicConnection topicConnection = null; TopicSession topicSession = null; Topic topic = null; TopicPublisher topicPublisher = null; int exitResult = 0; String topicName = "topic1"; /** * Constructor: looks up a connection factory and topic and creates a * connection and session. Also creates the publisher. */ public LXKJMSPublisher() { TopicConnectionFactory topicConnectionFactory = null; try { topicConnectionFactory = LXKJMSUtilities.getTopicConnectionFactory(); topicConnection = topicConnectionFactory.createTopicConnection(); topicSession = topicConnection.createTopicSession(false, Session.CLIENT_ACKNOWLEDGE); topic = LXKJMSUtilities.getTopic(topicName, topicSession); topicPublisher = topicSession.createPublisher(topic); } catch (Exception e) { System.out.println("Connection problem: " + e.toString()); if (topicConnection != null) { try { topicConnection.close(); } catch (JMSException ee) {} } System.exit(1); } } /** * Creates text message. * Sends some messages, depending on the event e.g Part release etc. * Messages must be persistent. */ public void publishMessages(HashMap hmInfo, String sEvent) { TextMessage message = null; StringBuilder sbMsgDetails = new StringBuilder(360); try { message = topicSession.createTextMessage(); if(LXKUtil.isNotBlank(sEvent) && "PartRelease".equals(sEvent) && hmInfo != null){ sbMsgDetails.append("<PartName>"); sbMsgDetails.append((String)hmInfo.get("PartName")); sbMsgDetails.append("</PartName>"); } message.setText(sbMsgDetails.toString()); // message.setText("MESSAGE NUMBER 1"); if(LXKUtil.isBlank(sEvent)){ throw new JMSException("Event could not be found."); } if(hmInfo == null){ throw new JMSException("Message details to be published not found."); } System.out.println("PUBLISHER: Publishing message: " + message.getText()); topicPublisher.publish(message); //topicPublisher.setTimeToLive(10000); // Send a non-text control message indicating end of messages. topicPublisher.publish(topicSession.createMessage()); } catch (JMSException e) { /*try { topicSession.rollback(); } catch (JMSException e1) { // TODO Auto-generated catch block e1.printStackTrace(); }*/ System.out.println("Exception occurred: " + e.toString()); exitResult = 1; } } /** * Closes the connection. */ public void finish() { if (topicConnection != null) { try { topicConnection.close(); } catch (JMSException e) { exitResult = 1; } } } public static void main(String[] args) { LXKJMSPublisher pub = new LXKJMSPublisher(); HashMap hmtopic = new HashMap(4); hmtopic.put("PartName", "12344"); pub.publishMessages(hmtopic, "PartRelease"); pub.finish(); LXKJMSUtilities.exit(pub.exitResult); } } |
From: Erick J. D. R. <ede...@co...> - 2010-05-24 05:42:17
|
Hi there, I am having an issue with the OpenJMS v 0.7.5 RC1 used in a third technology. This issue is related to getting a JMS connection to Oracle 11g RAC through JDBC. When I set the openJMS to connect to Oracle 11g without cluster configuration I don’t have any problems, but when I set the cluster configuration using the LOAD_BALANCE and/or FAILOVER features I couldn’t get any connection. The database cluster configuration is set in the openjms.xml configuration file: <DatabaseConfiguration> <RdbmsDatabaseConfiguration driver="oracle.jdbc.driver.OracleDriver" url="*jdbc:oracle:thin:@ (DESCRIPTION=(FAILOVER=on)(LOAD_BALANCE=yes)(ADDRESS=(PROTOCOL=TCP)(HOST= host01-vip.com)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=**host02-vip.com*<http://jborap02-vip.corp.tvglobo.com.br/> *)(PORT=1521))(CONNECT_DATA=(service_name=JBORAP02)))*" user="virageuser" password="*password*" /> </DatabaseConfiguration> And the error description in the open jms log, is: INFO | jvm 1 | 2010/05/04 16:27:41 | org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: java.sql.SQLException:*Exceção de E/S: Connection refused * (DESCRIPTION=(ERR=1153)(VSNNUM=185599488)(ERROR_STACK=(ERROR=(CODE=1153)(EMFI=4)(ARGS='(ADDRESS=(PROTOCOL=TCP)(HOST=host02)(PORT=1521))'))(ERROR=(CODE=305)(EMFI=1)))) I googled this error without success, any suggestions is really appreciated. Thanks Erick J. Delgado Ramirez |
From: Javier G. <god...@gm...> - 2009-12-04 23:33:24
|
Hello OpenJMS users, hopefully someone has gotten HTTPS tunnels working. I'm having a hard time with setting up a simple test. Here is the Java Code, it never gets past the InitialContext line: Hashtable properties = new Hashtable(); properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.exolab.jms.jndi.InitialContextFactory"); properties.put(Context.PROVIDER_URL, "https://localhost:8443/"); properties.put("org.exolab.jms.net.https.keyStore", "/Users/.../.keystore"); properties.put("org.exolab.jms.net.https.trustStore", "/Users/../.keystore"); properties.put("org.exolab.jms.net.https.keyStorePassword", "..."); Context cntx = new InitialContext(properties); Here is the debug: keyStore is : /Users/.../.keystore keyStore type is : jks keyStore provider is : init keystore init keymanager of type SunX509 trustStore is: /Users/.../.keystore trustStore type is : jks trustStore provider is : init truststore adding as trusted cert: Subject: CN=J Godinez, OU=TEST, O=TEST, L=, ST=CA, C=US Issuer: CN=J Godinez, OU=TEST, O=TEST, L=, ST=CA, C=US Algorithm: RSA; Serial number: 0x4b1981f4 Valid from Fri Dec 04 13:41:08 PST 2009 until Thu Mar 04 13:41:08 PST 2010 trigger seeding of SecureRandom done seeding SecureRandom %% No cached client session *** ClientHello, TLSv1 RandomCookie: GMT: 1259902718 bytes = { 139, 80, 78, ..., 172 } Session ID: {} Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA] Compression Methods: { 0 } *** [write] MD5 and SHA1 hashes: len = 79 0000: 01 00 00 4B 03 01 4B 19 97 FE 8B 50 4E 94 20 16 ...K..K....PN. . ... 0040: 09 00 15 00 12 00 03 00 08 00 14 00 11 01 00 ............... main, WRITE: TLSv1 Handshake, length = 79 [write] MD5 and SHA1 hashes: len = 107 0000: 01 03 01 00 42 00 00 00 20 00 00 04 01 00 80 00 ....B... ....... ... 0060: 29 70 49 50 12 00 49 BD FD 3B AC )pIP..I..;. main, WRITE: SSLv2 client hello message, length = 107 [Raw write]: length = 109 ... 0060: 03 B9 29 70 49 50 12 00 49 BD FD 3B AC ..)pIP..I..;. [Raw read]: length = 5 0000: 16 03 01 02 A1 ..... [Raw read]: length = 673 0000: 02 00 00 46 03 01 4B 19 97 FE 3F 50 E0 D0 3C E0 ...F..K...?P..<. ... 0290: 94 CC 3E 84 55 24 B3 9E 12 D9 FD B6 46 0E 00 00 ..>.U$......F... 02A0: 00 . main, READ: TLSv1 Handshake, length = 673 *** ServerHello, TLSv1 RandomCookie: GMT: 1259902718 bytes = { 63, ... 121 } Session ID: {75, ... 226} Cipher Suite: SSL_RSA_WITH_RC4_128_MD5 Compression Method: 0 *** %% Created: [Session-1, SSL_RSA_WITH_RC4_128_MD5] ** SSL_RSA_WITH_RC4_128_MD5 [read] MD5 and SHA1 hashes: len = 74 0000: 02 00 00 46 03 01 4B 19 97 FE 3F 50 E0 D0 3C E0 ...F..K...?P..<. ... 0040: 64 0C C6 76 D5 E4 E2 00 04 00 d..v...... *** Certificate chain chain [0] = [ [ Version: V3 Subject: CN=J Godinez, OU=TEST, O=TEST, L=, ST=CA, C=US Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5 Key: Sun RSA public key, 1024 bits modulus: 107342282817175...430515336218733 public exponent: 65537 Validity: [From: Fri Dec 04 13:41:08 PST 2009, To: Thu Mar 04 13:41:08 PST 2010] Issuer: CN=J Godinez, OU=TEST, O=TEST, L=, ST=CA, C=US SerialNumber: [ 4b1981f4] ] Algorithm: [SHA1withRSA] Signature: 0000: 68 E8 72 6C 95 4B E6 C9 C3 AE C9 5F AD 4F B4 51 h.rl.K....._.O.Q ... 0070: C9 B0 BB 94 CC 3E 84 55 24 B3 9E 12 D9 FD B6 46 .....>.U$......F ] *** Found trusted certificate: [ [ Version: V3 Subject: CN=J Godinez, OU=IIS BU, O=SAIC, L=San Diego, ST=CA, C=US Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5 Key: Sun RSA public key, 1024 bits modulus: 1073422828171758035...430515336218733 public exponent: 65537 Validity: [From: Fri Dec 04 13:41:08 PST 2009, To: Thu Mar 04 13:41:08 PST 2010] Issuer: CN=J Godinez, OU=TEST, O=TEST, L=, ST=CA, C=US SerialNumber: [ 4b1981f4] ] Algorithm: [SHA1withRSA] Signature: 0000: 68 E8 72 6C 95 4B E6 C9 C3 AE C9 5F AD 4F B4 51 h.rl.K....._.O.Q ... 0070: C9 B0 BB 94 CC 3E 84 55 24 B3 9E 12 D9 FD B6 46 .....>.U$......F ] [read] MD5 and SHA1 hashes: len = 595 0000: 0B 00 02 4F 00 02 4C 00 02 49 30 82 02 45 30 82 ...O..L..I0..E0. ... 0240: 19 D7 E9 C9 B0 BB 94 CC 3E 84 55 24 B3 9E 12 D9 ........>.U$.... 0250: FD B6 46 ..F *** ServerHelloDone [read] MD5 and SHA1 hashes: len = 4 0000: 0E 00 00 00 .... *** ClientKeyExchange, RSA PreMasterSecret, TLSv1 [write] MD5 and SHA1 hashes: len = 134 0000: 10 00 00 82 00 80 77 C8 EE 80 12 E9 97 02 15 A8 ......w......... ... 0070: 2C BC 7D EB 78 24 CB 44 B6 8F 16 FA 82 D1 10 4C ,...x$.D.......L 0080: 1F 4F F4 45 3A BC .O.E:. main, WRITE: TLSv1 Handshake, length = 134 [Raw write]: length = 139 0000: 16 03 01 00 86 10 00 00 82 00 80 77 C8 EE 80 12 ...........w.... 0010: E9 97 02 15 A8 2A 3A 5F F1 0A 91 48 5E 08 2E 90 .....*:_...H^.... ... 0080: FA 82 D1 10 4C 1F 4F F4 45 3A BC ....L.O.E:. SESSION KEYGEN: PreMaster Secret: 0000: 03 01 75 A2 2B 37 78 93 75 57 0B AC FE D9 C9 EA ..u.+7x.uW...... 0010: 85 B0 19 B3 80 10 D4 DC 0D FD C1 7A 90 01 99 3F ...........z...? 0020: E3 78 6B 12 0D BF 15 96 A3 0F C3 AF 2D 62 68 34 .xk.........-bh4 CONNECTION KEYGEN: Client Nonce: 0000: 4B 19 97 FE 8B 50 4E 94 20 16 56 79 5E 41 02 56 K....PN. .Vy^A.V 0010: 9B 84 89 03 B9 29 70 49 50 12 00 49 BD FD 3B AC .....)pIP..I..;. Server Nonce: 0000: 4B 19 97 FE 3F 50 E0 D0 3C E0 36 0C 37 B4 A4 7C K...?P..<.6.7... 0010: 3D 68 04 13 88 6C 67 37 7F 36 04 77 CA E6 BF 79 =h...lg7.6.w...y Master Secret: 0000: 86 C3 55 F6 F1 B5 81 DA 58 F9 1C 90 53 20 1F 72 ..U.....X...S .r 0010: 31 1B C7 36 FC 15 D7 71 0B 77 87 73 47 86 EB 55 1..6...q.w.sG..U 0020: B1 11 DC 78 5C 43 1E 39 5C 39 D7 A8 BA 89 D6 98 ...x\C.9\9...... Client MAC write Secret: 0000: 35 52 F7 3D 12 AB 71 FF 9D 23 FA 2F 98 92 E8 14 5R.=..q..#./.... Server MAC write Secret: 0000: 0D 14 A9 24 D6 43 C1 0A 83 4A 7F 81 E2 A2 67 B3 ...$.C...J....g. Client write key: 0000: 7D 16 1D 04 C4 09 33 6E EF C8 0A 7F A2 64 16 F1 ......3n.....d.. Server write key: 0000: B7 9F A7 66 2A 39 24 AD A9 C7 C0 B4 D6 66 15 D5 ...f*9$......f.. ... no IV used for this cipher main, WRITE: TLSv1 Change Cipher Spec, length = 1 [Raw write]: length = 6 0000: 14 03 01 00 01 01 ...... *** Finished verify_data: { 190, 254, 191, 68, 122, 148, 213, 101, 19, 213, 9, 47 } *** [write] MD5 and SHA1 hashes: len = 16 0000: 14 00 00 0C BE FE BF 44 7A 94 D5 65 13 D5 09 2F .......Dz..e.../ Padded plaintext before ENCRYPTION: len = 32 0000: 14 00 00 0C BE FE BF 44 7A 94 D5 65 13 D5 09 2F .......Dz..e.../ 0010: E8 8D 1F BF 04 D0 58 E6 A9 6E F4 41 D3 99 99 A4 ......X..n.A.... main, WRITE: TLSv1 Handshake, length = 32 [Raw write]: length = 37 0000: 16 03 01 00 20 A7 76 57 03 06 3C 3E D3 B0 A5 5B .... .vW..<>...[ 0010: 1E 7E 17 47 DA 94 DD 22 BE F8 8F 85 11 1C FA 9B ...G..."........ 0020: B5 47 16 8F C6 .G... [Raw read]: length = 5 0000: 14 03 01 00 01 ..... [Raw read]: length = 1 0000: 01 . main, READ: TLSv1 Change Cipher Spec, length = 1 [Raw read]: length = 5 0000: 16 03 01 00 20 .... [Raw read]: length = 32 0000: A1 8F D3 24 15 3C 84 A3 F7 0B 17 41 D0 32 DD B0 ...$.<.....A.2.. 0010: 32 BE 87 FD 39 D8 AC 49 85 75 B5 C6 A5 9C 9B 4B 2...9..I.u.....K main, READ: TLSv1 Handshake, length = 32 Padded plaintext after DECRYPTION: len = 32 0000: 14 00 00 0C 65 B8 F8 9D 55 5D 94 EC 89 48 17 38 ....e...U]...H.8 0010: 64 6F A1 FC E9 81 9D 16 C0 93 7A E6 C1 6F EB F2 do........z..o.. *** Finished verify_data: { 101, 184, 248, 157, 85, 93, 148, 236, 137, 72, 23, 56 } *** %% Cached client session: [Session-1, SSL_RSA_WITH_RC4_128_MD5] [read] MD5 and SHA1 hashes: len = 16 0000: 14 00 00 0C 65 B8 F8 9D 55 5D 94 EC 89 48 17 38 ....e...U]...H.8 main, called close() main, called closeInternal(true) main, SEND TLSv1 ALERT: warning, description = close_notify Padded plaintext before ENCRYPTION: len = 18 0000: 01 00 81 45 B7 58 AE 99 A0 85 72 AA D6 ED 7D 5C ...E.X....r....\ 0010: 38 FD 8. main, WRITE: TLSv1 Alert, length = 18 [Raw write]: length = 23 0000: 15 03 01 00 12 46 2C 67 38 BD 8C AD CB C8 0C 57 .....F,g8......W 0010: 1B 86 C2 6E 3A 2A 4B ...n:*K %% Invalidated: [Session-1, SSL_RSA_WITH_RC4_128_MD5] javax.naming.CommunicationException: Failed to get registry service for URL: https://localhost:8443/ [Root exception is java.rmi.ConnectIOException: Failed to create connection; nested exception is: org.exolab.jms.net.connector.ConnectException: Failed to connect to URI=https://localhost:8443/openjms-tunnel/tunnel] at org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContextFactory.java:146) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at TestTunnelClient.connect(TestTunnelClient.java:33) at TestTunnelClient.main(TestTunnelClient.java:58) Caused by: java.rmi.ConnectIOException: Failed to create connection; nested exception is: org.exolab.jms.net.connector.ConnectException: Failed to connect to URI=https://localhost:8443/openjms-tunnel/tunnel at org.exolab.jms.net.orb.Locator.getProxy(Locator.java:137) at org.exolab.jms.net.orb.Locator.getRegistry(Locator.java:103) at org.exolab.jms.net.orb.DefaultORB.getRegistry(DefaultORB.java:285) at org.exolab.jms.client.net.SharedORB.getRegistry(SharedORB.java:121) at org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContextFactory.java:144) ... 6 more Caused by: org.exolab.jms.net.connector.ConnectException: Failed to connect to URI=https://localhost:8443/openjms-tunnel/tunnel at org.exolab.jms.net.http.AbstractHTTPManagedConnection.<init>(AbstractHTTPManagedConnection.java:118) at org.exolab.jms.net.http.HTTPSManagedConnection.<init>(HTTPSManagedConnection.java:74) at org.exolab.jms.net.http.HTTPSManagedConnectionFactory.createManagedConnection(HTTPSManagedConnectionFactory.java:124) at org.exolab.jms.net.connector.DefaultConnectionPool.createManagedConnection(DefaultConnectionPool.java:233) at org.exolab.jms.net.connector.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:140) at org.exolab.jms.net.connector.AbstractConnectionFactory.getConnection(AbstractConnectionFactory.java:167) at org.exolab.jms.net.connector.AbstractConnectionManager.getConnection(AbstractConnectionManager.java:208) at org.exolab.jms.net.orb.Locator.getProxy(Locator.java:131) ... 10 more Is this a problem with my certificates, maybe opejms is misconfigured, but it seems that I don't even get that far.... Thanks, Javier Godinez -- ★ jg |
From: Daniel L. d. S. <dan...@gm...> - 2009-11-30 02:13:11
|
Hello, I am trying to access a open jms server (0.7.6.1 and 0.7.7-beta-1) from an osgi container. I have tried two (knopflerfish and equinox(eclipse)). In both cases when I am trying to obtain a jndi initial context the org.exolab.jms.jndi.InitialContextFactory can't be loaded. Either a class not found exception or a class cast exception occur. (to a javax.naming.spi.InitialContextFactory. Out of the container it runs fine. Is anyone willing to look into this or should I quit open jms and try something else ? I'm putting this very plainly because the test I made to verify these situations assure me that I have not detected no other error in the test that I can blame on something else. I really suspect that there is some incompatibility between the two. I can send the osgi bundle that tests this. |
From: Rajasekhar <p.r...@ro...> - 2009-07-29 12:50:17
|
Will the Open JMS 0.7.7 beta version compatiable with Tomcat 5.5 ? is there any relation between Tomcat versions with Open JMS versions ? |
From: Uruñuela H. S. <sur...@in...> - 2009-04-23 14:00:02
|
Hello, We are now working with a system that uses OpenJMS version 0.77 beta 1 configured to have its database installed in an Oracle database. This is not the problem, the problem is that the database is distributed in a two-host cluster using Oracle RAC, and when we make a balancing test, the few seconds the Oracle RAC is moving the load to the host that is not shutdown the OpenJMS server returns errors while treating incoming and outgoing messages. Any idea?? Someone has encountered this kind of problem?? Is there a way to make the OpenJMS to wait until the RAC responds?? Thank you in advance Regards. Susana Uruñuela Hernández |
From: selvajava <Sel...@he...> - 2009-03-20 10:45:47
|
I am trying to start the adaptor with IBM MQ.. But I am getting following error.. Can Any one help me pn this?? [WARN ][JMSPublisher](JMSPublisher.java:679)[BSSidhu] - org.openadaptor.adaptor.jms.JMSPublisher [Topic=OutputMessageTopic] JMS message delivery mode NON_PERSISTENT is not consistent with ServiceLevel=GUARANTEED <[WARN ][JMSPublisher](JMSPublisher.java:705)[BSSidhu] - org.openadaptor.adaptor.jms.JMSPublisher [Topic=OutputMessageTopic] ServiceLevel=GUARANTEED may not be achievable with the current JMS settings [WARN ][JMSPublisher](JMSPublisher.java:679)[BSSidhu] - org.openadaptor.adaptor.jms.JMSPublisher [Topic=OutputMessageTopic] JMS message delivery mode NON_PERSISTENT is not consistent with ServiceLevel=GUARANTEED [WARN ][JMSPublisher](JMSPublisher.java:705)[BSSidhu] - org.openadaptor.adaptor.jms.JMSPublisher [Topic=OutputMessageTopic] ServiceLevel=GUARANTEED may not be achievable with the current JMS settings [WARN ][AbstractTransporter](AbstractTransporter.java:4993)[Output_MQ_Test_TD_SNK.Topic] - Alternate JNDI Provider is not defined [ERROR][LoggingUtils](LoggingUtils.java:193)[Output_MQ_Test_TD_SNK.Topic] - org.openadaptor.adaptor.transporter.TransporterThread [Topic=OutputMessageTopic] [IbafException: org.openadaptor.adaptor.transporter.AbstractTransporter [Topic=OutputMessageTopic] connect() failed with NamingException: javax.naming.NoInitialContextException: Embedded JNDI server not initialised (If a class could not be instantiated, your JNDI parameters are correct, and the class is in your CLASSPATH, then please check the java version you are using is compatible with the target java VM used when the object was compiled.)] -- View this message in context: http://www.nabble.com/Openjma-and-JNDi-error..-tp22617944p22617944.html Sent from the OpenJMS - User mailing list archive at Nabble.com. |
From: Akshay J. <aks...@tc...> - 2008-12-31 06:22:09
|
Hi Vishal I have downloaded the executable from the site.The version is openjms-0.7.7-beta-1.So created the database for this and started to run the bat file.I am not sure if its a bug. Regards Akshay Jain Tata Consultancy Services Mailto: aks...@tc... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ Vishal Changrani <vis...@ya...> 12/31/2008 11:41 AM Please respond to ope...@li... To ope...@li... cc Subject Re: [openjms-user] Error:urgent Just taking a wild guess..but may be you are closing the connection too early... From: Akshay Jain <aks...@tc...> To: ope...@li... Sent: Tuesday, December 30, 2008 10:05:21 PM Subject: [openjms-user] Error:urgent Hi I am trying to use openJMS to build the application.On running start.bat I am getting the following exception in openjms.bat window. Till now I have created the database in oracle 9.i.Kindly give some suggestions.The exception is as follows. OpenJMS 0.7.7-beta-1 The OpenJMS Group. (C) 1999-2007. All rights reserved. http://openjms.sourceforge.net org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceExc eption: java.lang.NullPointerException at org.apache.commons.dbcp.PoolingConnection.close(PoolingConnection.jav a:78) at org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnecti on.java:151) at org.apache.commons.dbcp.PoolableConnection.reallyClose(PoolableConnec tion.java:95) at org.apache.commons.dbcp.PoolableConnectionFactory.destroyObject(Poola bleConnectionFactory.java:301) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(Bas icDataSource.java:883) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSou rce.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource .java:540) at org.exolab.jms.persistence.DBCPConnectionManager.getConnection(DBCPCo nnectionManager.java:121) at org.exolab.jms.persistence.RDBMSAdapter.getConnection(RDBMSAdapter.ja va:696) at org.exolab.jms.persistence.RDBMSAdapter.<init>(RDBMSAdapter.java:177) at org.exolab.jms.persistence.DatabaseService.createAdapter(DatabaseServ ice.java:311) at org.exolab.jms.persistence.DatabaseService.doStart(DatabaseService.ja va:240) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) Akshay Jain Tata Consultancy Services Mailto: aks...@tc... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you ------------------------------------------------------------------------------ _______________________________________________ openjms-user mailing list ope...@li... https://lists.sourceforge.net/lists/listinfo/openjms-user ForwardSourceID:NT0001309E =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |
From: Vishal C. <vis...@ya...> - 2008-12-31 06:11:38
|
Just taking a wild guess..but may be you are closing the connection too early... ________________________________ From: Akshay Jain <aks...@tc...> To: ope...@li... Sent: Tuesday, December 30, 2008 10:05:21 PM Subject: [openjms-user] Error:urgent Hi I am trying to use openJMS to build the application.On running start.bat I am getting the following exception in openjms.bat window. Till now I have created the database in oracle 9.i.Kindly give some suggestions.The exception is as follows. OpenJMS 0.7.7-beta-1 The OpenJMS Group. (C) 1999-2007. All rights reserved. http://openjms.sourceforge.net org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceExc eption: java.lang.NullPointerException at org.apache.commons.dbcp.PoolingConnection.close(PoolingConnection.jav a:78) at org.apache.commons.dbcp.DelegatingConnection.close(DelegatingConnecti on.java:151) at org.apache.commons.dbcp.PoolableConnection.reallyClose(PoolableConnec tion.java:95) at org.apache.commons.dbcp.PoolableConnectionFactory.destroyObject(Poola bleConnectionFactory.java:301) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(Bas icDataSource.java:883) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSou rce.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource .java:540) at org.exolab.jms.persistence.DBCPConnectionManager.getConnection(DBCPCo nnectionManager.java:121) at org.exolab.jms.persistence.RDBMSAdapter.getConnection(RDBMSAdapter.ja va:696) at org.exolab.jms.persistence.RDBMSAdapter.<init>(RDBMSAdapter.java:177) at org.exolab.jms.persistence.DatabaseService.createAdapter(DatabaseServ ice.java:311) at org.exolab.jms.persistence.DatabaseService.doStart(DatabaseService.ja va:240) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176 ) at org.exolab.jms.service.Service.start(Service.java:97) at org.exolab.jms.server.JmsServer.init(JmsServer.java:146) at org.exolab.jms.server.JmsServer.main(JmsServer.java:178) Akshay Jain Tata Consultancy Services Mailto: aks...@tc... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |