Issue while trying to load SOLR 4.0 admin UI - solr4

I have installed SOLR 4.0 in a linux server under /tmp directory. The SOLR server is started from /example directory using java -jar start.jar . The server has started and listening at port 8983.
Issue:
When I try to load admin UI via URL "//hostname:8983/SOLR" , the static part of page with menu items (dashboard,coreadmin etc.) is loaded but the actual configurations like free memory, used memory etc. are not getting loaded. I just the message "Loading" .
Below are some of the observations and last few entries from the log file. Can anyone advise, what might be wrong?
Regards
Observations:
1. Installed the same SOLR instance on my windows 7 PC and I can access the admin UI without any issues.
2. I do not see any errors in logs when SOLR is started thru java -jar start.jar .
3. When the URL "hostname:8983/SOLR" I can see a log entry for the query but nothing after that
4. When I try "hostname:8983/solr/admin/system?wt=xml" I can see the configuration XML getting loaded with all the values including hostname being populated.
Last few entries in the log
2972 [main] INFO org.apache.solr.servlet.SolrDispatchFilter â user.dir=/tmp/solr-4.4.0/example
2973 [main] INFO org.apache.solr.servlet.SolrDispatchFilter â SolrDispatchFilter.init() done
3008 [main] INFO org.eclipse.jetty.server.AbstractConnector â Started SocketConnector#0.0.0.0:8983
3066 [searcherExecutor-4-thread-1] INFO org.apache.solr.core.SolrCore â [collection1] webapp=null path=null params={event=firstSearcher&q=static+firstSearcher+warming+in+solrconfig.xml&distrib=false} hits=0 status=0 QTime=92
3067 [searcherExecutor-4-thread-1] INFO org.apache.solr.core.SolrCore â QuerySenderListener done.
3067 [searcherExecutor-4-thread-1] INFO org.apache.solr.handler.component.SpellCheckComponent â Loading spell index for spellchecker: default
3068 [searcherExecutor-4-thread-1] INFO org.apache.solr.handler.component.SpellCheckComponent â Loading spell index for spellchecker: wordbreak
3068 [searcherExecutor-4-thread-1] INFO org.apache.solr.core.SolrCore â [collection1] Registered new searcher Searcher#31be0369 main{StandardDirectoryReader(segments_1:1)}
51926 [qtp1798675483-18] INFO org.apache.solr.servlet.SolrDispatchFilter â [admin] webapp=null path=/admin/cores params={indexInfo=false&=1377543032093&wt=json} status=0 QTime=3
52158 [qtp1798675483-13] INFO org.apache.solr.core.SolrCore â [collection1] webapp=/solr path=/admin/system params={=1377543032245&wt=json} status=0 QTime=82
598493 [qtp1798675483-15] INFO org.apache.solr.core.SolrCore â [collection1] webapp=/solr path=/admin/system params={wt=xml} status=0 QTime=75

admin pages are change u have use that
127.0.0.1:8983/solr/collection1/browse?q=
admin to changed collection1 so u just use that

Related

Gerrit plugin-manager doesn't show plugins

I have a Gerrit v2.15 on a linux machine and I'm the administrator in Gerrit.
I installed the Gerrit plugin-manager under gerrit/plugins with command :
wget https://gerrit-ci.gerritforge.com/view/Plugins-stable-2.15/job/plugin-plugin-manager-bazel-master-stable-2.15/lastSuccessfulBuild/artifact/bazel-genfiles/plugins/plugin-manager/plugin-manager.jar
But nothing uploads in Gerrit UI in tab Plugins. I only see the Installed, as before.
In gerrit/logs/error.log I can read out the following:
[2018-06-15 08:54:26,366] [main] INFO com.google.gerrit.server.plugins.PluginLoader : Loaded plugin plugin-manager, version v2.15-1-g27c3d2935d
[2018-06-15 08:54:26,367] [plugin-manager-preloader] INFO com.googlesource.gerrit.plugins.manager.OnStartStop : Start-up: pre-loading list of plugins from registry
[2018-06-15 08:54:26,902] [main] INFO com.google.gerrit.server.git.GarbageCollectionRunner : Ignoring missing gc schedule configuration
[2018-06-15 08:54:26,902] [main] INFO com.google.gerrit.server.config.ScheduleConfig : accountDeactivation schedule parameter "accountDeactivation.interval" is not configured
[2018-06-15 08:54:26,902] [main] INFO com.google.gerrit.server.change.ChangeCleanupRunner : Ignoring missing changeCleanup schedule configuration
[2018-06-15 08:54:26,946] [main] INFO com.google.gerrit.sshd.SshDaemon : Started Gerrit SSHD-CORE-1.6.0 on *:29418
[2018-06-15 08:54:26,949] [main] INFO org.eclipse.jetty.server.Server : jetty-9.3.18.v20170406
[2018-06-15 08:54:28,040] [main] INFO com.googlesource.gerrit.plugins.gitiles.HttpModule : No /opt/gerrit/etc/gitiles.config; assuming defaults
[2018-06-15 08:54:28,847] [main] INFO org.eclipse.jetty.server.handler.ContextHandler : Started o.e.j.s.ServletContextHandler#62672ad5{/,null,AVAILABLE}
[2018-06-15 08:54:28,869] [main] INFO org.eclipse.jetty.server.AbstractConnector : Started ServerConnector#38503309{HTTP/1.1,[http/1.1]}{127.0.0.1:8081}
[2018-06-15 08:54:28,890] [main] INFO org.eclipse.jetty.server.Server : Started #20170ms
[2018-06-15 08:54:28,893] [main] INFO com.google.gerrit.pgm.Daemon : Gerrit Code Review 2.15.1 ready
[2018-06-15 08:54:44,819] [plugin-manager-preloader] INFO com.googlesource.gerrit.plugins.manager.OnStartStop : 45 plugins successfully pre-loaded
What have i missed?
Is it some permission settings that is wrong or configuration in gerrit.config that has to be done?
Directory gerrit/plugin has permissions set to: drwxr-xr-x
Note : I've tried restarting Gerrit.
Good to know: We are using nginx. That might be useful info.
I know very little about how nginx works.
What it looks like in the UI
The plugin-manager only works in the Old UI. If you're using the new PolyGerrit UI first click on "Switch to Old UI" link at the right/down on the page. Then the plugin-manager can be access at: Plugins > Manage menu.
If you're not able to see the "Manage" option in the Old UI check the following:
. Verify if you're logged in Gerrit with an Admin user (you need to have "Administrate Server" permission in All-Projects project). There're an specific permission to access Plugins > Installed item (called "View Plugins") but this permission doesn't work the same way to Plugins > Manage one.
. Verify if you have the following set in the GERRIT_SITE/etc/gerrit.config file:
[plugins]
allowRemoteAdmin = true
Maybe this can resolve your issue.

neo4j failed to start on my machine

I use brew install neo4j, when i'm trying to start on terminal by neo4j start, it keep loading forever as following.
$ neo4j start Using additional JVM arguments: -server
-XX:+DisableExplicitGC -Dorg.neo4j.server.properties=conf/neo4j-server.properties
-Djava.util.logging.config.file=conf/logging.properties -Dlog4j.configuration=file:conf/log4j.properties -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-OmitStackTraceInFastThrow -Dneo4j.ext.udc.source=homebrew
-Djava.awt.headless=true Starting Neo4j Server...WARNING: not changing user process [9320]... waiting for server to be ready ........................................................................... ........................................................................... ........................................................................... ......................................................................
Failed to start within 120 seconds.
Neo4j Server may have failed to start, please check the logs.
I checked some logs from neo4j already ...but it show nothing error
log messgea from /usr/local/Cellar/neo4j/2.1.6/libexec/data/graph.db/messages.log
2015-05-21 06:46:44.248+0000 INFO [o.n.k.i.n.s.StoreFactory]: [/usr/local/Cellar/neo4j/2.1.6/libexec/data/graph.db/neostore.schemastore.db] brickCount=0 brickSize=0b mappedMem=0b (storeSize=64b)
2015-05-21 06:46:44.248+0000 INFO [o.n.k.i.n.s.StoreFactory]: [/usr/local/Cellar/neo4j/2.1.6/libexec/data/graph.db/neostore.relationshipgroupstore.db] brickCount=0 brickSize=0b mappedMem=0b (storeSize=25b)
2015-05-21 06:46:44.249+0000 INFO [o.n.k.i.n.s.StoreFactory]: [/usr/local/Cellar/neo4j/2.1.6/libexec/data/graph.db/neostore] brickCount=0 brickSize=0b mappedMem=0b (storeSize=81b)
2015-05-21 06:46:44.310+0000 INFO [o.n.k.a.i.i.LuceneLabelScanStore]: No lucene scan store index found, this might just be first use. Preparing to rebuild.
2015-05-21 06:46:44.333+0000 INFO [o.n.k.a.i.i.LuceneLabelScanStore]: No lucene scan store index found, this might just be first use. Preparing to rebuild.
2015-05-21 06:46:44.414+0000 INFO [o.n.k.i.t.x.XaLogicalLog]: Opened logical log [/usr/local/Cellar/neo4j/2.1.6/libexec/data/graph.db/nioneo_logical.log.1] version=0, lastTxId=1 (clean)
2015-05-21 06:46:44.417+0000 INFO [o.n.k.a.i.i.LuceneLabelScanStore]: Rebuilding lucene scan store, this may take a while
2015-05-21 06:46:44.418+0000 INFO [o.n.k.a.i.i.LuceneLabelScanStore]: Lucene scan store rebuilt (roughly -1 nodes)
2015-05-21 06:46:44.421+0000 INFO [o.n.k.i.t.TxManager]: TM new log: tm_tx_log.1
2015-05-21 06:46:44.425+0000 INFO [o.n.k.i.t.KernelHealth]: Kernel health set to OK
log message from /usr/local/Cellar/neo4j/2.1.6/libexec/data/log/console.log
2015-05-21 06:46:43.878+0000 INFO [API] Setting startup timeout to: 120000ms based on -1
2015-05-21 06:57:03.825+0000 INFO [API] Successfully shutdown Neo4j Server.
I try to use brew to re-install neo4j, but it doesn't help.
i'm using mac machine.
java version /Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/bin/java
Can you try to run bin/neo4j console to let it finish the startup.
Probably it is creating / updating an index or an internal structure that takes longer than the 120s timeout?
see
2015-05-21 06:46:44.417+0000 INFO [o.n.k.a.i.i.LuceneLabelScanStore]: Rebuilding lucene scan store, this may take a while
2015-05-21 06:46:44.418+0000 INFO [o.n.k.a.i.i.LuceneLabelScanStore]: Lucene scan store rebuilt (roughly -1 nodes)

Migrate app in openshift with "create --from-app" doesn't load my old application [Grails]

I have a Grails application in Openshift and I've recently upgraded my plan from free to silver and I need to migrate my application from non scalable to scalable, to do this I used the command rhc create-app --from-app app --scaling. After a while the new app is created but when I run it, it doesn't load the app, just the by default tomcat first screen.
Update: The logs of the new app show this:
==> app-root/logs/haproxy_ctld.log <==
I, [2015-04-18T01:02:28.949500 #163665] INFO -- : Starting haproxy_ctld
I, [2015-04-18T08:28:39.200616 #496980] INFO -- : Starting haproxy_ctld
==> app-root/logs/haproxy.log <==
[WARNING] 107/010224 (167630) : config : log format ignored for proxy 'express' since it has
no log address.
[WARNING] 107/012317 (167630) : Server express/local-gear is DOWN for maintenance.
[ALERT] 107/012317 (167630) : proxy 'express' has no server available!
[WARNING] 107/082838 (496963) : config : log format ignored for proxy 'stats' since it has n
o log address.
[WARNING] 107/082838 (496963) : config : log format ignored for proxy 'express' since it has
no log address.
[WARNING] 107/082838 (496963) : Server express/local-gear is DOWN, reason: Layer4 connection
problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers lef
t. 0 sessions active, 0 requeued, 0 remaining in queue.
[ALERT] 107/082838 (496963) : proxy 'express' has no server available!
[WARNING] 107/082851 (496963) : Server express/local-gear is UP, reason: Layer7 check passed
, code: 200, info: "HTTP status check returned code <3C>200<3E>", check duration: 2ms. 1 act
ive and 0 backup servers online. 0 sessions requeued, 0 total in queue.
[WARNING] 107/085928 (496963) : Server express/local-gear is DOWN for maintenance.
[ALERT] 107/085928 (496963) : proxy 'express' has no server available!
==> app-root/logs/jbossews.log <==
Apr 18, 2015 8:28:47 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3727 ms
Apr 18, 2015 8:59:28 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-127.7.39.1-8080"]
Apr 18, 2015 8:59:28 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Apr 18, 2015 8:59:28 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-127.7.39.1-8080"]
Apr 18, 2015 8:59:28 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-127.7.39.1-8080"]
b

Unable to load webadmin for Neo4j High Availability

I have installed 3 instances of neo4j version 1.9.4 on a linux machine, in 3 different directories: Neo4j01, neo4j02, neo4j03.
I have updated the configuration files neo4j.properties and neo4j-server.properties as mentioned in the link (http://docs.neo4j.org/chunked/milestone/ha-setup-tutorial.html).
When I start all the neo4j instances one after the other, they are successfully installing, but after some time 2 of the 3 neo4j process/instances are automatically disappearing. I noticed it via ps -aef | grep neo4j.
When I checked console logs then i found below errors:
2013-11-12 16:37:32.512+0000 INFO [Cluster] Checking store consistency with master
2013-11-12 16:37:33.174+0000 INFO [Cluster] Store is consistent
2013-11-12 16:37:33.176+0000 INFO [Cluster] Catching up with master
2013-11-12 16:37:33.276+0000 INFO [Cluster] Now consistent with master
2013-11-12 16:37:34.442+0000 INFO [Cluster] ServerId 2, successfully moved to slave for master ha://localhost.localdomain:6363?serverId=1
2013-11-12 16:37:34.689+0000 INFO [Cluster] Instance 1 is available as backup at backup://localhost.localdomain:6366
2013-11-12 16:37:34.798+0000 INFO [Cluster] Instance 2 (this server) is available as slave at ha://localhost.localdomain:6364?serverId=2
2013-11-12 16:37:35.036+0000 INFO [Cluster] Database available for write transactions
2013-11-12 16:37:35.360+0000 INFO [API] Successfully started database
2013-11-12 16:37:36.079+0000 INFO [API] Starting HTTP on port :7474 with 10 threads available
2013-11-12 16:37:40.596+0000 INFO [Cluster] Instance 3 has failed
2013-11-12 16:37:43.654+0000 INFO [API] Enabling HTTPS on port :7473
2013-11-12 16:38:01.081+0000 INFO [API] Mounted REST API at: /db/manage/
2013-11-12 16:38:01.158+0000 INFO [API] Mounted discovery module at [/]
2013-11-12 16:38:02.375+0000 INFO [API] Loaded server plugin "CypherPlugin"
2013-11-12 16:38:02.449+0000 INFO [API] Loaded server plugin "GremlinPlugin"
2013-11-12 16:38:02.462+0000 INFO [API] Mounted REST API at [/db/data/]
2013-11-12 16:38:02.534+0000 INFO [API] Mounted management API at [/db/manage/]
2013-11-12 16:38:03.568+0000 INFO [API] Mounted webadmin at [/webadmin]
2013-11-12 16:38:06.189+0000 INFO [API] Mounting static content at [/webadmin] from [webadmin-html]
2013-11-12 16:38:30.844+0000 DEBUG [API] Failed to start Neo Server on port [7474], reason [org.mortbay.util.MultiException[java.net.BindException: Address already in use, java.net.BindException: Address already in use]]
2013-11-12 16:38:30.880+0000 DEBUG [API] org.neo4j.server.ServerStartupException: Starting Neo4j Server failed: org.mortbay.util.MultiException[java.net.BindException: Address already in use, java.net.BindException: Address already in use]
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:211) ~[neo4j-server-1.9.4.jar:1.9.4]
at org.neo4j.server.Bootstrapper.start(Bootstrapper.java:86) [neo4j-server-1.9.4.jar:1.9.4]
at org.neo4j.server.Bootstrapper.main(Bootstrapper.java:49) [neo4j-server-1.9.4.jar:1.9.4]
Caused by: java.lang.RuntimeException: org.mortbay.util.MultiException[java.net.BindException: Address already in use, java.net.BindException: Address already in use]
at org.neo4j.server.web.Jetty6WebServer.startJetty(Jetty6WebServer.java:334) ~[neo4j-server-1.9.4.jar:1.9.4]
at org.neo4j.server.web.Jetty6WebServer.start(Jetty6WebServer.java:154) ~[neo4j-server-1.9.4.jar:1.9.4]
at org.neo4j.server.AbstractNeoServer.startWebServer(AbstractNeoServer.java:344) ~[neo4j-server-1.9.4.jar:1.9.4]
at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:187) ~[neo4j-server-1.9.4.jar:1.9.4]
... 2 common frames omitted
Caused by: org.mortbay.util.MultiException: Multiple exceptions
at org.mortbay.jetty.Server.doStart(Server.java:188) ~[jetty-6.1.25.jar:6.1.25]
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) ~[jetty-util-6.1.25.jar:6.1.25]
at org.neo4j.server.web.Jetty6WebServer.startJetty(Jetty6WebServer.java:330) ~[neo4j-server-1.9.4.jar:1.9.4]
... 5 common frames omitted
2013-11-12 16:38:30.894+0000 DEBUG [API] Failed to start Neo Server on port [7474]
Now, only neo4j01 process is running and neo4j02 and neo4j03 processes are disappeared. But even though neo4j01 process is up and running I am unable to access the webadmin page at http://htname:7474/webadmin/#/info/org.neo4j/High%20Availability/.
Please, can someone shed some light on this?
You might want to take a look at https://github.com/neo-technology/neo4j-enterprise-local-qa. This contains a rakefile that automates a local setup of 3 instances. Clone the repo locally, and use
rake setup_cluster start_cluster
to bring a locally running cluster online. Shutdown can be done via
rake stop_cluster
Find the configs in machine[ABC]/conf/.

unable to figure jboss error

can someone figure out whats the error in jboss. when i enter localhost:8080 in url it says INVALID REQUEST. PLEASE CHECK URL.
I am using jboss 5.0.1
JBOSS_HOME: D:\Jboss\jboss-5.0.1.GA
JAVA: C:\Program Files\Java\jdk1.6.0_13\bin\java
JAVA_OPTS: -Dfile.encoding=UTF-8 -Dprogram.name=run.bat -server -Xms512m -Xmx1024m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: D:\Jboss\jboss-5.0.1.GA\bin\run.jar
===============================================================================
20:46:16,640 INFO [ServerImpl] Starting JBoss (Microcontainer)...
20:46:16,640 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)
20:46:16,640 INFO [ServerImpl] Bootstrap URL: null
20:46:16,656 INFO [ServerImpl] Home Dir: D:\Jboss\jboss-5.0.1.GA
20:46:16,656 INFO [ServerImpl] Home URL: file:/D:/Jboss/jboss-5.0.1.GA/
20:46:16,656 INFO [ServerImpl] Library URL: file:/D:/Jboss/jboss-5.0.1.GA/lib/
20:46:16,656 INFO [ServerImpl] Patch URL: null
20:46:16,656 INFO [ServerImpl] Common Base URL: file:/D:/Jboss/jboss-5.0.1.GA/common/
20:46:16,656 INFO [ServerImpl] Common Library URL: file:/D:/Jboss/jboss-5.0.1.GA/common/lib/
20:46:16,656 INFO [ServerImpl] Server Name: default
20:46:16,656 INFO [ServerImpl] Server Base Dir: D:\Jboss\jboss-5.0.1.GA\server
20:46:16,671 INFO [ServerImpl] Server Base URL: file:/D:/Jboss/jboss-5.0.1.GA/server/
20:46:16,671 INFO [ServerImpl] Server Config URL: file:/D:/Jboss/jboss-5.0.1.GA/server/default/conf/
20:46:16,671 INFO [ServerImpl] Server Home Dir: D:\Jboss\jboss-5.0.1.GA\server\default
20:46:16,671 INFO [ServerImpl] Server Home URL: file:/D:/Jboss/jboss-5.0.1.GA/server/default/
20:46:16,671 INFO [ServerImpl] Server Data Dir: D:\Jboss\jboss-5.0.1.GA\server\default\data
20:46:16,671 INFO [ServerImpl] Server Library URL: file:/D:/Jboss/jboss-5.0.1.GA/server/default/lib/
20:46:16,671 INFO [ServerImpl] Server Log Dir: D:\Jboss\jboss-5.0.1.GA\server\default\log
20:46:16,671 INFO [ServerImpl] Server Native Dir: D:\Jboss\jboss-5.0.1.GA\server\default\tmp\native
20:46:16,687 INFO [ServerImpl] Server Temp Dir: D:\Jboss\jboss-5.0.1.GA\server\default\tmp
20:46:16,687 INFO [ServerImpl] Server Temp Deploy Dir: D:\Jboss\jboss-5.0.1.GA\server\default\tmp\deploy
20:46:17,296 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/D:/Jboss/jboss-5.0.1.GA/server/default/conf/bootstrap.xml
20:46:17,859 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
20:46:17,859 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
20:46:18,140 INFO [CopyMechanism] VFS temp dir: D:\Jboss\jboss-5.0.1.GA\server\default\tmp
20:46:18,156 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
20:46:20,218 INFO [ServerInfo] Java version: 1.6.0_13,Sun Microsystems Inc.
20:46:20,234 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
20:46:20,234 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 11.3-b02,Sun Microsystems Inc.
20:46:20,234 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
20:46:20,265 INFO [JMXKernel] Legacy JMX core initialized
20:46:22,593 INFO [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository#126c5a5(root=D:\Jboss\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.Pro
fileKey#143b82c3[domain=default,server=default,name=default])
20:46:22,593 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository#126c5a5(root=D:\Jboss\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.ProfileKey#143b82c3[doma
in=default,server=default,name=default])
20:46:22,593 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl#1e779a7{key=org.jboss.profileservice.spi.ProfileKey#143b82c3[domain=default,server=default,name=default]}
20:46:24,421 INFO [WebService] Using RMI server codebase: http://127.0.0.1:9283/
20:46:30,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
20:46:30,671 INFO [NativeServerConfig] 3.0.5.GA
20:46:42,218 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:2290/jmxconnector
20:46:42,375 INFO [MailService] Mail Service bound to java:/Mail
20:46:44,015 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installat
ion default. Please see the JBoss Messaging user guide for instructions on how to do this.
20:46:44,031 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
20:46:44,203 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
20:46:44,203 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
20:46:44,656 INFO [TransactionManagerService] Initializing recovery manager
20:46:44,843 INFO [TransactionManagerService] Recovery manager configured
20:46:44,843 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
20:46:44,875 INFO [TransactionManagerService] Starting transaction recovery manager
20:46:45,453 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
20:46:45,453 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8218
20:46:45,453 INFO [StandardService] Starting service jboss.web
20:46:45,453 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
20:46:45,531 INFO [Catalina] Server startup in 146 ms
20:46:45,562 INFO [TomcatDeployment] deploy, ctxPath=/invoker
20:46:46,156 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
20:46:46,203 INFO [TomcatDeployment] deploy, ctxPath=/web-console
20:46:46,265 INFO [[/web-console]] SystemFolder: Failed to init plugin, Resource not found: SystemFolder.bsh
20:46:46,296 INFO [[/web-console]] J2EEFolder: Failed to init plugin, Resource not found: J2EEFolder.bsh
20:46:46,421 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Jboss/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
20:46:46,531 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Jboss/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
20:46:46,578 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Jboss/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
20:46:46,609 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Jboss/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
20:46:46,640 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Jboss/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
20:46:46,796 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
20:46:46,843 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
20:46:46,843 INFO [RAMJobStore] RAMJobStore initialized.
20:46:46,843 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
20:46:46,843 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
20:46:46,843 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
20:46:47,531 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
20:46:48,062 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
20:46:48,296 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4657 has leasing enabled, lease period 10000 milliseconds
20:46:48,296 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#3dc250 started
20:46:48,359 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4657 has leasing enabled, lease period 10000 milliseconds
20:46:48,359 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#188ef97 started
20:46:48,406 INFO [QueueService] Queue[/queue/A] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,406 INFO [QueueService] Queue[/queue/ex] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,406 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,406 INFO [QueueService] Queue[/queue/B] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,406 INFO [QueueService] Queue[/queue/C] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,421 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory wil
l *not* support failover
20:46:48,421 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factor
y will *not* support load balancing
20:46:48,421 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4657 has leasing enabled, lease period 10000 milliseconds
20:46:48,421 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#2de670 started
20:46:48,421 INFO [QueueService] Queue[/queue/D] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,421 INFO [QueueService] Queue[/queue/MailQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,421 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,421 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,437 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,437 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,437 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
20:46:48,640 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
20:46:48,703 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=PostgresDSDYPK' to JNDI name 'java:PostgresDSDYPK'
20:46:48,734 INFO [TomcatDeployment] deploy, ctxPath=/
20:46:50,312 INFO [TomcatDeployment] deploy, ctxPath=/ap
20:46:50,406 WARN [JAXWSDeployerHookPreJSE] Cannot load servlet class: org.jboss.jmx.adaptor.html.HtmlAdaptorServlet
20:46:50,406 WARN [JAXWSDeployerHookPreJSE] Cannot load servlet class: org.jboss.jmx.adaptor.html.ClusteredConsoleServlet
20:46:50,421 INFO [TomcatDeployment] deploy, ctxPath=/jmx-conso1e
20:46:50,500 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
20:46:50,531 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8218
20:46:50,546 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 33s:859ms
You will also have to specify the binding address for the jboss server. For jboss5.x, the command will be like
Jboss\jboss-5.0.1.GA\bin\run.jar -b0.0.0.0
Check your port number under /deploy/jbossweb.sar/server.xml, I think the problem is right there.
It should be like this ==>
<!-- A HTTP/1.1 Connector on port 8080 -->
<Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}"
maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
emptySessionPath="true"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"/>
Check the port number!

Resources