Re: [JBoss-user] Problems running Jboss
I had the same problem today (19 September 2001) I solve it by deleting lib directory in jboss/deploy. Tomcat/JSP behaviour seems OK to me. However I didn't have the time to check EJB behaviour maybe tommorow. - Original Message - From: Menz, Matthias [EMAIL PROTECTED] To: JBoss Mailgroup (E-Mail) [EMAIL PROTECTED] Sent: Wednesday, September 19, 2001 3:04 PM Subject: [JBoss-user] Problems running Jboss Hello, has anybody got any idea why I cant get Jboss started. Do I have to have any jars included in my classpath. I use a JBoss Version 2.4.0 with JDK 1.3.0 on a Digital(Compaq) UNIX V4.0F (Alpha). Included is the log of the session. The Script runs fine for a while and then terminates with a segmentation violation. Any help would be apreciated. Greetings Matt ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Problems running Jboss
I had the same problem today (19 September 2001) I solve it by deleting lib directory in jboss/deploy. Tomcat/JSP behaviour seems OK to me. However I didn't have the time to check EJB behaviour maybe tommorow. - Original Message - From: Menz, Matthias [EMAIL PROTECTED] To: JBoss Mailgroup (E-Mail) [EMAIL PROTECTED] Sent: Wednesday, September 19, 2001 3:04 PM Subject: [JBoss-user] Problems running Jboss Hello, has anybody got any idea why I cant get Jboss started. Do I have to have any jars included in my classpath. I use a JBoss Version 2.4.0 with JDK 1.3.0 on a Digital(Compaq) UNIX V4.0F (Alpha). Included is the log of the session. The Script runs fine for a while and then terminates with a segmentation violation. Any help would be apreciated. Greetings Matt ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Problems running Jboss
What JVM are you using? (Sun 1.3.1 works OK for me in Win2k) Cheers - Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Menz, Matthias Sent: 19 September 2001 09:05 To: JBoss Mailgroup (E-Mail) Subject: [JBoss-user] Problems running Jboss Hello, has anybody got any idea why I cant get Jboss started. Do I have to have any jars included in my classpath. I use a JBoss Version 2.4.0 with JDK 1.3.0 on a Digital(Compaq) UNIX V4.0F (Alpha). Included is the log of the session. The Script runs fine for a while and then terminates with a segmentation violation. Any help would be apreciated. Greetings Matt ./run.sh JBOSS_CLASSPATH=:run.jar:../lib/crimson.jar jboss.home = /usr/users/nsuser/jboss_tomcat/jboss Using JAAS LoginConfig: file:/usr/users/nsuser/jboss_tomcat/jboss/conf/default/auth.conf Using configuration default [root] Started Log4jService, config=file:/usr/users/nsuser/jboss_tomcat/jboss/conf/default/log4j.properti es [Info] Java version: 1.3.0,Compaq Computer Corp. [Info] Java VM: Classic VM 1.3.0-1,Compaq Computer Corp. [Info] System: OSF1 V4.0,alpha [Shutdown] Shutdown hook added [Service Control] Initializing 27 MBeans [WebService] Initializing [WebService] Initialized [NamingService] Initializing [NamingService] Initialized [JNDIView] Initializing [JNDIView] Initialized [TransactionManagerService] Initializing [TransactionManagerService] Initialized [ClientUserTransactionService] Initializing [ClientUserTransactionService] Initialized [JaasSecurityManagerService] Initializing [JaasSecurityManagerService] Initialized [JdbcProvider] Initializing [JdbcProvider] Loaded JDBC-driver:org.hsql.jdbcDriver [JdbcProvider] Loaded JDBC-driver:org.enhydra.instantdb.jdbc.idbDriver [JdbcProvider] Initialized [HypersonicDatabase] Initializing [HypersonicDatabase] Initialized [XADataSourceLoader] Initializing [XADataSourceLoader] Initialized [XADataSourceLoader] Initializing [XADataSourceLoader] Initialized [ServerDataCollector] Initializing [ServerDataCollector] Initialized [ContainerFactory] Initializing [ContainerFactory] Initialized [JBossMQService] Initializing [JBossMQService] Initialized [JMSProviderLoader] Initializing [Default] queue factory name: XAQueueConnectionFactory [Default] topic factory name: XATopicConnectionFactory [JMSProviderLoader] Initialized [ServerSessionPoolLoader] Initializing [ServerSessionPoolLoader] Initialized [J2eeDeployer] Initializing [J2eeDeployer] Initialized [RARDeployer] Initializing [RARDeployer] Found a temp directory left over from a previous run - deleting it. [RARDeployer] Initialized [ConnectionManagerFactoryLoader] Initializing [ConnectionManagerFactoryLoader] Initialized [ConnectionManagerFactoryLoader] Initializing [ConnectionManagerFactoryLoader] Initialized [ConnectionManagerFactoryLoader] Initializing [ConnectionManagerFactoryLoader] Initialized [ConnectionFactoryLoader] Initializing [ConnectionFactoryLoader] Initialized [ConnectionFactoryLoader] Initializing [ConnectionFactoryLoader] Initialized [AutoDeployer] Initializing [AutoDeployer] Initialized [JMXAdaptorService] Initializing [JMXAdaptorService] Initialized [RMIConnectorService] Initializing [RMIConnectorService] Initialized [MailService] Initializing [MailService] Initialized [Service Control] Initialized 27 services [Service Control] Starting 27 MBeans [WebService] Starting [Default] Started on port 8083 [Webserver] Codebase set to http://monolith.messerknecht.de:8083/ [Webserver] Started webserver on port 8083 [WebService] Started [NamingService] Starting [NamingService] Starting jnp server [NamingService] Started jnpPort=1099, rmiPort=0, Client SocketFactory=null, Server SocketFactory=null [NamingService] InitialContext Environment: [NamingService] key=java.naming.factory.initial, value=org.jnp.interfaces.NamingContextFactory [NamingService] key=java.naming.factory.url.pkgs, value=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interface s [NamingService] Naming started on port 1099 [NamingService] Started [JNDIView] Starting [JNDIView] Started [TransactionManagerService] Starting [TransactionManagerService] Started [ClientUserTransactionService] Starting [ClientUserTransactionService] Started [JaasSecurityManagerService] Starting [Default] JAAS.startService, cachePolicy=null [Default] JAAS.startService, SecurityProxyFactory=org.jboss.security.SubjectSecurityProxyFactory@ff31519e [JaasSecurityManagerService] Started [JdbcProvider] Starting [JdbcProvider] Started [HypersonicDatabase] Starting [HypersonicDatabase] Database started [HypersonicDatabase] Started [XADataSourceLoader] Starting [InstantDB] XA Connection pool InstantDB bound to java:/InstantDB [Default] Enhydra InstantDB - Version 3.26 [Default] [Default] The Initial Developer of the Original Code is Lutris Technologies Inc. Portions created by Lutris are Copyright (C) 1997-2001 Lutris Technologies, Inc. All Rights Reserved. [XADataSourceLoader] Started [XADataSourceLoader
Re: [JBoss-user] Problems running jboss 2.2 embedded Tomcat
On 2001.04.14 13:53:19 -0400 Todd Chaffee wrote: I installed the latest jboss 2.2 + tomcat binaries and am getting an error in tomcat when requesting any jsp page: [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111 [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1 The error is in the mod_jk.log file. I'm not an apache/tomcat expert, but maybe I can point you in a fruitfull direction. Make sure that apache and tomcat agree on the port that that protocol should be listening on. You probably have apache's conf file including a 'mod-jk.auto' (or something like that). Take a look in that auto file and make sure that the ajp connection handler setup in (I believe) the server.xml that is included in the JBoss/tomcat distribution uses the same port. Tomcat + apache work fine if I start apache and then tomcat so I believe that apache tomcat are communicating just fine. The problem is when I start apache and then jboss + embedded tomcat. It seems like the connection between apache and tomcat is handled differently in jboss and I'm not sure what to do to get this working. Does jboss work with mod_jk? It looks like jboss is trying to use ajp12 and I thought that mod_jk uses ajp13. The sample pet store on the jboss.org site uses apache/jboss/tomcat so I guess it is possible to get it working. Is there anyone that could provide sample config files from that server so I could compare them to my own? - Todd Chaffee ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Problems running jboss 2.2 embedded Tomcat
Just wanted to let everyone know I got this working by making the CLASSPATH blank before running JBoss. I don't know why having something in my classpath was a problem, but it's working now. Hopefully this will help someone save a little time in the future. BTW, I didn't see this anywhere in the docs. If I'm wrong, please point me in the right direction. If not, I'd be happy to update the documentation so that this is mentioned. - Todd Chaffee On 2001.04.16 11:21:58 -0400 Todd Chaffee wrote: On 2001.04.14 13:53:19 -0400 Todd Chaffee wrote: I installed the latest jboss 2.2 + tomcat binaries and am getting an error in tomcat when requesting any jsp page: [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111 [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1 The error is in the mod_jk.log file. I'm not an apache/tomcat expert, but maybe I can point you in a fruitfull direction. Make sure that apache and tomcat agree on the port that that protocol should be listening on. You probably have apache's conf file including a 'mod-jk.auto' (or something like that). Take a look in that auto file and make sure that the ajp connection handler setup in (I believe) the server.xml that is included in the JBoss/tomcat distribution uses the same port. Tomcat + apache work fine if I start apache and then tomcat so I believe that apache tomcat are communicating just fine. The problem is when I start apache and then jboss + embedded tomcat. It seems like the connection between apache and tomcat is handled differently in jboss and I'm not sure what to do to get this working. Does jboss work with mod_jk? It looks like jboss is trying to use ajp12 and I thought that mod_jk uses ajp13. The sample pet store on the jboss.org site uses apache/jboss/tomcat so I guess it is possible to get it working. Is there anyone that could provide sample config files from that server so I could compare them to my own? - Todd Chaffee ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Problems running jboss 2.2 embedded Tomcat
I'm reposting this 'cause I got no response. Please somebody, help (see original messages below). I will be using this for a b2c site for a major wine retailer and will be happy to share it as a success story for jboss if I can get it working. I'm sure other folks have used the binary jboss+tomcat succesfully - what am I doing wrong? Thanks in advance for any help. - Todd Chaffee On 2001.04.14 13:53:19 -0400 Todd Chaffee wrote: I installed the latest jboss 2.2 + tomcat binaries and am getting an error in tomcat when requesting any jsp page: [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111 [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1d the latest jboss + tomcat binaries and am getting a tomcat error The error is in the mod_jk.log file. I am using tomcat with apache 1.3.12 and was using tomcat just fine before trying to run it embedded with jboss. Any suggestions? Thanks, Todd Chaffee On 2001.04.14 14:25:12 -0400 Todd Chaffee wrote: Additional info: I can run tomcat + apache from the "jboss tomcat" installation as long as I run it without jboss. I modified my classpath to include the necessary jboss jar files (xml, jboss, tomcat-service, etc) and started tomcat using the tomcat.sh startup script and it works fine. So it seems the mod_jk error has something to do with the way jboss is running / starting. Once again, any help is appreciated. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Problems running jboss 2.2 embedded Tomcat
Todd Chaffee wrote: I'm reposting this 'cause I got no response. Please somebody, help (see original messages below). I will be using this for a b2c site for a major wine retailer and will be happy to share it as a success story for jboss if I can get it working. I'm sure other folks have used the binary jboss+tomcat succesfully - what am I doing wrong? Thanks in advance for any help. - Todd Chaffee On 2001.04.14 13:53:19 -0400 Todd Chaffee wrote: I installed the latest jboss 2.2 + tomcat binaries and am getting an error in tomcat when requesting any jsp page: [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111 [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1d the latest jboss + tomcat binaries and am getting a tomcat error The error is in the mod_jk.log file. I'm not an apache/tomcat expert, but maybe I can point you in a fruitfull direction. Make sure that apache and tomcat agree on the port that that protocol should be listening on. You probably have apache's conf file including a 'mod-jk.auto' (or something like that). Take a look in that auto file and make sure that the ajp connection handler setup in (I believe) the server.xml that is included in the JBoss/tomcat distribution uses the same port. -danch ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user