[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] Gary Quinn closed AS7-1296. --------------------------- Resolution: Rejected Never mind was my stupidity. Installed the correct version of maven and it started up fine. http://maven.apache.org/download.html#Installation -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] Gary Quinn commented on AS7-1296: --------------------------------- Here is the output: gary@gary-desktop:~/data/etc/jboss/jboss-as-7.0.0.Final/bin$ java -version java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) gary@gary-desktop:~/data/etc/jboss/jboss-as-7.0.0.Final/bin$ mvn --version Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200) Maven home: /usr/local/apache-maven/apache-maven-3.0.3 Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_ZA, platform encoding: UTF-8 OS name: "linux", version: "2.6.35-22-generic", arch: "amd64", family: "unix" gary@gary-desktop:~/data/etc/jboss/jboss-as-7.0.0.Final/bin$ ./standalone.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/gary/data/etc/jboss/jboss-as-7.0.0.Final JAVA: java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman ========================================================================= 10:31:00,257 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA 10:31:00,409 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA 10:31:00,452 INFO [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting 10:31:00,966 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1) 10:31:00,975 INFO [org.jboss.as.logging] Removing bootstrap log handlers 10:31:00,985 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2) 10:31:00,992 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem. 10:31:01,065 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem 10:31:01,073 INFO [org.jboss.as.naming] (MSC service thread 1-2) Starting Naming Service 10:31:01,075 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem 10:31:01,088 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem 10:31:01,092 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.0.Beta2 10:31:01,100 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.0.0.Beta3 10:31:01,109 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.0.0.Beta3 10:31:01,230 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-4) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-sun-1.6.0.24/jre/lib/amd64/server:/usr/lib/jvm/java-6-sun-1.6.0.24/jre/lib/amd64:/usr/lib/jvm/java-6-sun-1.6.0.24/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib 10:31:01,240 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-6) Starting remote JMX connector 10:31:01,243 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem 10:31:01,257 INFO [org.jboss.as.remoting] (MSC service thread 1-12) Listening on /127.0.0.1:9999 10:31:01,342 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080 10:31:01,385 INFO [org.jboss.as.connector] (MSC service thread 1-8) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2) 10:31:01,410 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-11) Bound data source [java:jboss/datasources/ExampleDS] 10:31:01,625 INFO [org.jboss.as.deployment] (MSC service thread 1-5) Started FileSystemDeploymentService for directory /home/gary/data/etc/jboss/jboss-as-7.0.0.Final/standalone/deployments 10:31:01,634 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final "Lightning" started in 1522ms - Started 92 of 147 services (55 services are passive or on-demand) 10:31:18,554 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Received an invalid message length of 1347375956 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-1296: ----------------------------------- You don't need Maven to run JBoss AS binary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] a d commented on AS7-1296: -------------------------- Having same issue when starting Jboss 7 09:17:10,373 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] Ramon Rosa da Silva commented on AS7-1296: ------------------------------------------ This bug persists in Release 7.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-1296: ----------------------------- Fix Version/s: 7.1.0.Beta1 Forum Reference: http://community.jboss.org/message/628579#628579, http://community.jboss.org/message/617349#617349 (was: http://community.jboss.org/message/628579#628579, http://community.jboss.org/message/617349#617349) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] Yaro Sheng commented on AS7-1296: --------------------------------- Please reopen, I have same error with jboss 7.1.1 final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1296?page=com.atlassian.jira.plugin.s... ] Mathieu Lachance commented on AS7-1296: --------------------------------------- we had the same problem over there, this issue is fixed. 1. use visual vm script provided in issue : https://issues.jboss.org/browse/AS7-4463 2. the remote address connection string should use the "service pattern : service:jmx:remoting-jmx://remote-host:remote-port -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira