3 Replies Latest reply on Jun 13, 2005 4:45 PM by Andrew Oliver

    Cont: need help running code from HEAD

    Michael Barker Apprentice

      For some reason the forum is not properly displaying the original thread, so I am continuing the thread here.

      OK, deleted the database and it created without error upon deploy; however I still get connection refused from thunderbird. Just for kicks in Thunderbird I changed the server name from 127.0.0.1 (which worked with M2) to localhost.localdomain.com. Instead of the immediate connection refused message, it just timed out. The JBoss server still didn't show any request information in the console though.


      It sounds like you have some form of firewalling preventing you from connectting to the appropriate local port. What OS are you running? Can you confirm that JBMail is properly bound to the pop and smtp ports? You can check that using netstat or TCPMon. Can you try telneting directly to the port.

      Mike.

        • 1. Re: Cont: need help running code from HEAD
          Jeff Headley Newbie

          I'm in Win XP pro. OK, I can telnet to 127.0.0.1 ports 110 and 25, but not 995 for ssl which Thunderbird was set to previously when I had m2 working. It also had TLS selected in the outgoing settings. I turned off SSL so that it was using 110 to receive and 25 to send with no encryption and I'm all good now. I can send myself e-mails. So I think I'm ready to get started helping now. Any suggestions or changes to jboss-service.xml I should make for encryption or is it ok to work on bugs without it? I uncommented the section that said Uncomment for TLS support but then I got these errors when starting the server.

          MBeans waiting for other MBeans:
          ObjectName: jboss.security:domain=Mail+SSL,service=JaasSecurityDomain
           state: FAILED
           I Depend On:
           Depends On Me: java.io.IOException: Too many certificates in chain
          
          MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
          ObjectName: jboss.security:domain=Mail+SSL,service=JaasSecurityDomain
           state: FAILED
           I Depend On:
           Depends On Me: java.io.IOException: Too many certificates in chain
          


          Thanks for the help getting me working. I appreciate it.

          Jeff

          • 2. Re: Cont: need help running code from HEAD
            Michael Barker Apprentice

            You probably won't need encryption to work on bugs, but it's probably worth figuring it out at some point for completness and understanding.

            Mike.

            • 3. Re: Cont: need help running code from HEAD
              Andrew Oliver Master

              original message (jeff87):

              Hi everyone. I would like to start contributing and I am having some problems running the latest code. I need help please. I had M2 running just fine. I was sending myself e-mails. So I get the latest from CVS and do ant dev-deploy and I get some messages during the build. If they matter, it's many of these.

              Code:
              xdoclet:
              [hibernatedoclet] 00:24:07,500 ERROR [findGetterMethod] Method getVerbose not found.
              [hibernatedoclet] 00:24:07,500 ERROR [findGetterMethod] Method getForce not found.
              [hibernatedoclet] 00:24:07,500 ERROR [findGetterMethod] Method getExcludePackageNames not found.
              [hibernatedoclet] 00:24:07,500 ERROR [findGetterMethod] Method isExcludePackageNames not found.
              [hibernatedoclet] 00:24:07,500 ERROR [fillConfigParamsHashMapUsingReflectionFor] Getter method not f
              ound.



              Then when it deploys, the console shows these errors:

              Code:
              00:24:22,265 ERROR [SchemaUpdate] Unsuccessful: create table messageflags (storeid varchar(32) not n
              ull, flagvalue varchar(255), flagindex integer not null, primary key (storeid, flagindex))
              00:24:22,265 ERROR [SchemaUpdate] Table already exists: MESSAGEFLAGS in statement [create table mess
              ageflags]
              00:24:22,265 ERROR [SchemaUpdate] Unsuccessful: create table storedmessages (storeid varchar(32) not
              null, senderaddress varchar(255) not null, createtime timestamp not null, msgsize bigint not null,
              msgbytes varbinary(255), fpath varchar(255), primary key (storeid))
              00:24:22,265 ERROR [SchemaUpdate] Table already exists: STOREDMESSAGES in statement [create table st
              oredmessages]
              00:24:22,265 ERROR [SchemaUpdate] Unsuccessful: create table MAILSTORE (ID bigint generated by defau
              lt as identity (start with 1), LENGTH bigint, PAGESIZE integer, NUMPAGES integer)
              00:24:22,265 ERROR [SchemaUpdate] Table already exists: MAILSTORE in statement [create table MAILSTO
              RE]
              00:24:22,265 ERROR [SchemaUpdate] Unsuccessful: create table PAGES (ID bigint generated by default a
              s identity (start with 1), PAGE_NO integer, DATA varbinary(2147483647), BLOB_ID bigint)
              00:24:22,265 ERROR [SchemaUpdate] Table already exists: PAGES in statement [create table PAGES]
              00:24:22,265 ERROR [SchemaUpdate] Unsuccessful: alter table messageflags add constraint FKB3B6DAE08F
              B051BC foreign key (storeid) references storedmessages
              00:24:22,265 ERROR [SchemaUpdate] Constraint already exists: FKB3B6DAE08FB051BC in statement [alter
              table messageflags add constraint FKB3B6DAE08FB051BC foreign key (storeid) references storedmessages
              ]



              When I go in to Thunderbird, I can no longer send/receive e-mail. I get a connection refused message and nothing shows up in the console that there was a request. Below is my jboss-service.xml if that helps at all.

              Thanks everyone,
              Jeff

              Code:

              <?xml version="1.0" encoding="UTF-8"?>
              <!-- $Id: jboss-service.xml,v 1.117.2.3 2004/10/26 14:57:40 loubyansky Exp $ -->

              <!-- ===================================================================== -->
              <!-- JBoss Server Configuration -->
              <!-- ===================================================================== -->



              <!-- Load all jars from the JBOSS_DIST/server//lib directory. This
              can be restricted to specific jars by specifying them in the archives
              attribute.
              -->



              <!-- ==================================================================== -->
              <!-- JSR-77 Single JBoss Server Management Domain -->
              <!-- ==================================================================== -->

              jboss.system:service=MainDeployer
              jboss.system:service=ServiceDeployer
              jboss.j2ee:service=EARDeployer
              jboss.ejb:service=EJBDeployer
              jboss.jca:service=RARDeployer
              jboss.jca:service=ConnectionFactoryDeployer
              jboss.web:service=WebServer
              jboss:service=Mail
              jboss.mq:service=DestinationManager
              jboss:service=Naming
              jboss:service=TransactionManager
              jboss:service=ClientUserTransaction
              jboss:service=CorbaORB


              <!-- ==================================================================== -->
              <!-- XMBean Persistence -->
              <!-- ==================================================================== -->
              <mbean code="org.jboss.system.pm.AttributePersistenceService"
              name="jboss:service=AttributePersistenceService"
              xmbean-dd="resource:xmdesc/AttributePersistenceService-xmbean.xml">
              <!-- the AttributePersistenceService is persistent, itself -->

              <!--
              org.jboss.system.pm.XMLAttributePersistenceManager

              <data-directory>data/xmbean-attrs</data-directory>

              false

              -->


              <!-- A Thread pool service -->

              JBoss System Threads
              System Threads
              <!-- How long a thread will live without any tasks in MS -->
              60000
              <!-- The max number of threads in the pool -->
              10
              <!-- The max number of tasks before the queue is full -->
              1000
              <!-- The behavior of the pool when a task is added and the queue is full.
              abort - a RuntimeException is thrown
              run - the calling thread executes the task
              wait - the calling thread blocks until the queue has room
              discard - the task is silently discarded without being run
              discardOldest - check to see if a task is about to complete and enque
              the new task if possible, else run the task in the calling thread
              -->
              run


              <!-- Preload all custom editors for VMs that don't use the thread
              context class loader when searching for PropertyEditors. Uncomment
              if your JDK 1.3.0 VM fails to find JBoss PropertyEditors.


              java.math.BigDecimal=org.jboss.util.propertyeditor.BigDecimalEditor
              java.lang.Boolean=org.jboss.util.propertyeditor.BooleanEditor
              java.lang.Class=org.jboss.util.propertyeditor.ClassEditor
              java.util.Date=org.jboss.util.propertyeditor.DateEditor
              java.io.File=org.jboss.util.propertyeditor.FileEditor
              java.net.InetAddress=org.jboss.util.propertyeditor.InetAddressEditor
              java.lang.Integer=org.jboss.util.propertyeditor.IntegerEditor
              javax.management.ObjectName=org.jboss.mx.util.propertyeditor.ObjectNameEditor
              java.util.Properties=org.jboss.util.propertyeditor.PropertiesEditor
              [Ljava.lang.String;=org.jboss.util.propertyeditor.StringArrayEditor
              java.net.URL=org.jboss.util.propertyeditor.URLEditor


              -->

              <!-- ==================================================================== -->
              <!-- Log4j Initialization -->
              <!-- ==================================================================== -->


              resource:log4j.xml
              <!-- Set the org.apache.log4j.helpers.LogLog.setQuiteMode. As of log4j1.2.8
              this needs to be set to avoid a possible deadlock on exception at the
              appender level. See bug#696819.
              -->
              true
              <!-- How frequently in seconds the ConfigurationURL is checked for changes -->
              60


              <!-- ==================================================================== -->
              <!-- JBoss RMI Classloader - only install when available -->
              <!-- ==================================================================== -->

              java.rmi.server.RMIClassLoaderSpi
              org.jboss.system.JBossRMIClassLoader


              <!-- ==================================================================== -->
              <!-- Service Binding -->
              <!-- ==================================================================== -->

              <!-- Automatically activated when generatting the clustering environment -->
              <!-- @TESTSUITE_CLUSTER_CONFIG@ -->

              <!--
              | Binding service manager for port/host mapping. This is a sample
              | config that demonstrates a JBoss instances with a server name 'jboss1'
              | loading its bindings from an XML file using the ServicesStoreFactory
              | implementation returned by the XMLServicesStoreFactory.
              |
              | ServerName: The unique name assigned to a JBoss server instance for
              | lookup purposes. This allows a single ServicesStore to handle mulitiple
              | JBoss servers.
              |
              | StoreURL: The URL string passed to org.jboss.services.binding.ServicesStore
              | during initialization that specifies how to connect to the bindings store.
              | StoreFactory: The org.jboss.services.binding.ServicesStoreFactory interface
              | implementation to create to obtain the ServicesStore instance.


              ports-01
              ../docs/examples/binding-manager/sample-bindings.xml

              org.jboss.services.binding.XMLServicesStoreFactory



              -->


              <!-- ==================================================================== -->
              <!-- Class Loading -->
              <!-- ==================================================================== -->


              8083
              <!-- Should resources and non-EJB classes be downloadable -->
              true
              ${jboss.bind.address}
              ${jboss.bind.address}


              <!-- ==================================================================== -->
              <!-- JNDI -->
              <!-- ==================================================================== -->

              <mbean code="org.jboss.naming.NamingService"
              name="jboss:service=Naming"
              xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
              <!-- The call by value mode. true if all lookups are unmarshalled using
              the caller's TCL, false if in VM lookups return the value by reference.
              -->
              false
              <!-- The listening port for the bootstrap JNP service. Set this to -1
              to run the NamingService without the JNP invoker listening port.
              -->
              1099
              <!-- The bootstrap JNP server bind address. This also sets the default
              RMI service bind address. Empty == all addresses
              -->
              ${jboss.bind.address}
              <!-- The port of the RMI naming service, 0 == anonymous -->
              1098
              <!-- The RMI service bind address. Empty == all addresses
              -->
              ${jboss.bind.address}
              <!-- The thread pool service used to control the bootstrap lookups -->
              <depends optional-attribute-name="LookupPool"
              proxy-type="attribute">jboss.system:service=ThreadPool


              <mbean code="org.jboss.naming.JNDIView"
              name="jboss:service=JNDIView"
              xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">


              <!-- ==================================================================== -->
              <!-- Security -->
              <!-- ==================================================================== -->


              jboss.security:service=XMLLoginConfig


              login-config.xml


              <!-- JAAS security manager and realm mapping -->

              org.jboss.security.plugins.JaasSecurityManager
              anonymous
              <!-- DefaultCacheTimeout: Specifies the default timed cache policy timeout
              in seconds.
              If you want to disable caching of security credentials, set this to 0 to
              force authentication to occur every time. This has no affect if the
              AuthenticationCacheJndiName has been changed from the default value.
              -->
              1800
              <!-- DefaultCacheResolution: Specifies the default timed cache policy
              resolution in seconds. This controls the interval at which the cache
              current timestamp is updated and should be less than the DefaultCacheTimeout
              in order for the timeout to be meaningful. This has no affect if the
              AuthenticationCacheJndiName has been changed from the default value.
              -->
              60


              <!-- ==================================================================== -->
              <!-- Transactions -->
              <!-- ==================================================================== -->
              <!-- The configurable Xid factory. For use with Oracle, set pad to true -->

              <!--attribute name="Pad">true</attribute-->


              <!--
              | The fast in-memory transaction manager.
              -->
              <mbean code="org.jboss.tm.TransactionManagerService"
              name="jboss:service=TransactionManager"
              xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
              300
              <!-- set to false to disable transaction demarcation over IIOP -->
              true
              <depends optional-attribute-name="XidFactory">jboss:service=XidFactory

              <!--
              | UserTransaction support.
              -->
              <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
              name="jboss:service=ClientUserTransaction"
              xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml">


              jboss:service=invoker,type=jrmp
              jboss:service=ClientUserTransaction
              UserTransactionSessionFactory
              org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory


              org.jboss.proxy.ClientMethodInterceptor
              org.jboss.invocation.InvokerInterceptor


              jboss:service=invoker,type=jrmp


              <depends optional-attribute-name="TxProxyName">

              jboss:service=invoker,type=jrmp
              jboss:service=ClientUserTransaction

              org.jboss.tm.usertx.interfaces.UserTransactionSession


              org.jboss.proxy.ClientMethodInterceptor
              org.jboss.invocation.InvokerInterceptor


              jboss:service=invoker,type=jrmp




              <!-- ==================================================================== -->
              <!-- Invokers to the JMX node -->
              <!-- ==================================================================== -->

              <!-- RMI/JRMP invoker -->

              4444
              ${jboss.bind.address}
              <!--
              custom
              custom
              custom
              ssl-domain-name
              -->
              jboss:service=TransactionManager




              jboss:service=TransactionManager



              1
              300
              300
              60000
              ${jboss.bind.address}
              4445
              ${jboss.bind.address}
              0
              false

              <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager


              <!-- ==================================================================== -->
              <!-- Monitoring and Management -->
              <!-- ==================================================================== -->

              <!-- Uncomment to enable JMX monitoring of the bean cache

              -->

              <!-- Uncomment to enable JMX monitoring of the entity bean locking

              -->

              <!-- ==================================================================== -->
              <!-- An MBean that is a registry for JDBC type-mapping metadata -->
              <!-- ==================================================================== -->



              <!-- ==================================================================== -->
              <!-- Deployment Scanning -->
              <!-- ==================================================================== -->

              <!-- An mbean for hot deployment/undeployment of archives.
              -->


              <!-- Uncomment (and comment/remove version below) to enable usage of the
              DeploymentCache
              <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache
              -->
              <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer

              <!-- The URLComparator can be used to specify a deployment ordering
              for deployments found in a scanned directory. The class specified
              must be an implementation of java.util.Comparator, it must be able
              to compare two URL objects, and it must have a no-arg constructor.
              Two deployment comparators are shipped with JBoss:
              - org.jboss.deployment.DeploymentSorter
              Sorts by file extension, as follows:
              "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
              "*"
              - org.jboss.deployment.scanner.PrefixDeploymentSorter
              If the name portion of the url begins with 1 or more digits, those
              digits are converted to an int (ignoring leading zeroes), and
              files are deployed in that order. Files that do not start with
              any digits will be deployed first, and they will be sorted by
              extension as above with DeploymentSorter.
              -->
              org.jboss.deployment.DeploymentSorter
              <!--
              org.jboss.deployment.scanner.PrefixDeploymentSorter
              -->

              <!-- The Filter specifies a java.io.FileFilter for scanned
              directories. Any file not accepted by this filter will not be
              deployed. The org.jboss.deployment.scanner.DeploymentFilter
              rejects the following patterns:
              "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
              "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
              ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
              "TAGS", "core", "tags"
              -->
              org.jboss.deployment.scanner.DeploymentFilter

              5000

              <!-- URLs are comma separated and resolve relative to the server home URL
              unless the given path is absolute. If the URL ends in "/" it is
              considered a collection and scanned, otherwise it is simply deployed;
              this follows RFC2518 convention and allows discrimination between
              collections and directories that are simply unpacked archives.

              URLs may be local (file:) or remote (http:). Scanning is supported
              for remote URLs but unpacked deployment units are not.

              Example URLs:
              deploy/
              scans ${jboss.server.url}/deploy/, which is local or remote
              depending on the URL used to boot the server
              ${jboss.server.home}/deploy/
              scans ${jboss.server.home)/deploy, which is always local
              file: formErrors = 'You must enter a message before posting.';
              }
              if (formErrors) {
              alert(formErrors);
              return false;
              } else {
              return true;
              }
              }

              I'm deleteing the original thread since it seems to cause misbehavior on jbportal's part.