Suppose I'm running a pyspark shell against a Mesos cluster. I'd like to occupy just 12 CPU cores. So I launch it like this:
uu#r4:~$ pyspark --master mesos://e3.test:5050 --total-executor-cores 12
And then goes the usual stuff:
Python 2.7.13 |Anaconda 2.5.0 (64-bit)| (default, Dec 20 2016, 23:09:15)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io/thanks and https://anaconda.org
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
17/01/31 08:16:31 INFO SparkContext: Running Spark version 1.6.2
17/01/31 08:16:31 INFO SecurityManager: Changing view acls to: uu
17/01/31 08:16:31 INFO SecurityManager: Changing modify acls to: uu
17/01/31 08:16:31 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(uu); users with modify permissions: Set(uu)
17/01/31 08:16:31 INFO Utils: Successfully started service 'sparkDriver' on port 53336.
17/01/31 08:16:31 INFO Slf4jLogger: Slf4jLogger started
17/01/31 08:16:32 INFO Remoting: Starting remoting
17/01/31 08:16:32 INFO Remoting: Remoting started; listening on addresses :[akka.tcp://sparkDriverActorSystem#r4.test:59860]
17/01/31 08:16:32 INFO Utils: Successfully started service 'sparkDriverActorSystem' on port 59860.
17/01/31 08:16:32 INFO SparkEnv: Registering MapOutputTracker
17/01/31 08:16:32 INFO SparkEnv: Registering BlockManagerMaster
17/01/31 08:16:32 INFO DiskBlockManager: Created local directory at /var/tmp/spark/blockmgr-6b16ff11-b0bc-4a71-82f5-c69a363c8c1a
17/01/31 08:16:32 INFO MemoryStore: MemoryStore started with capacity 511.1 MB
17/01/31 08:16:32 INFO SparkEnv: Registering OutputCommitCoordinator
17/01/31 08:16:32 INFO Utils: Successfully started service 'SparkUI' on port 4040.
17/01/31 08:16:32 INFO SparkUI: Started SparkUI at http://r4.test:4040
I0131 08:16:32.582038 24965 sched.cpp:226] Version: 1.1.0
I0131 08:16:32.586931 24958 sched.cpp:330] New master detected at master#192.168.0.15:5050
I0131 08:16:32.587162 24958 sched.cpp:341] No credentials provided. Attempting to register without authentication
I0131 08:16:32.596922 24956 sched.cpp:743] Framework registered with 075ef8d0-de21-472d-8198-80805006b93d-0051
17/01/31 08:16:32 INFO CoarseMesosSchedulerBackend: Registered as framework ID 075ef8d0-de21-472d-8198-80805006b93d-0051
17/01/31 08:16:32 INFO Utils: Successfully started service 'org.apache.spark.network.netty.NettyBlockTransferService' on port 51135.
17/01/31 08:16:32 INFO NettyBlockTransferService: Server created on 51135
17/01/31 08:16:32 INFO BlockManagerMaster: Trying to register BlockManager
17/01/31 08:16:32 INFO BlockManagerMasterEndpoint: Registering block manager r4.test:51135 with 511.1 MB RAM, BlockManagerId(driver, r4.test, 51135)
17/01/31 08:16:32 INFO BlockManagerMaster: Registered BlockManager
17/01/31 08:16:32 INFO CoarseMesosSchedulerBackend: SchedulerBackend is ready for scheduling beginning after reached minRegisteredResourcesRatio: 0.0
17/01/31 08:16:32 INFO CoarseMesosSchedulerBackend: Mesos task 0 is now TASK_RUNNING
Welcome to
____ __
/ __/__ ___ _____/ /__
_\ \/ _ \/ _ `/ __/ '_/
/__ / .__/\_,_/_/ /_/\_\ version 1.6.2
/_/
Using Python version 2.7.13 (default, Dec 20 2016 23:09:15)
SparkContext available as sc, HiveContext available as sqlContext.
but it ends up with only one executor registered:
>>> 17/01/31 08:16:35 INFO CoarseMesosSchedulerBackend: Registered executor NettyRpcEndpointRef(null) (r5.test:42965) with ID 023af0f2-fc60-4d9d-a3db-301ab34764c9-S3
17/01/31 08:16:35 INFO BlockManagerMasterEndpoint: Registering block manager r5.test:33239 with 511.1 MB RAM, BlockManagerId(023af0f2-fc60-4d9d-a3db-301ab34764c9-S3, r5.test, 33239)
meaning that the whole Spark app is about to run on the single node. And this is not the scheduling I want (primarily due to data locality considerations). What I was expecting is more like Spark standalone setup way: --total-executor-cores spread more or less evenly across the cluster.
Any way to achieve this? Remaining options mentioning executors/cores numbers do not seem to have any effect (and are related to standalone and Yarn configurations only).
Why exactly does Spark with Mesos employ this placement strategy of filling up nodes one by one rather than distributing work?
UPD: Conf entries mentioned in the docs do not work either:
pyspark --master mesos://e3.test:5050 --conf spark.executor.cores=2 --conf spark.cores.max=12
version 1.6.2
is the problem. In the more recent versions there is an option spark.cores.max capping the number of cores per executor.
in my compilation even though i am placing twitter jar files in the src/main/resources folder ,but SBT compilation is not picking them up and compiles and package without errors but at run time gives me error as "class not found twitterUtils"
my question is why SBT is not including the jar files from resource folder in the compilation ?
people are telling me to do all these complex steps of getting the Git utility and then doing a sbt assembly which I did but since iam behind proxy Git is not working even though all the http_proxy setup.
I have also tried putting these twitter jar files in the CLASSPATH with no luck.
I am stuck with this issue so any help is highly appreciated.
please see the details below
[root#hadoop1 TwitterPopularTags]# pwd
/root/TwitterPopularTags
[root#hadoop1 TwitterPopularTags]# sbt compile
[info] Set current project to TwitterPopularTags (in build file:/root/TwitterPopularTags/)
[info] Updating {file:/root/TwitterPopularTags/}twitterpopulartags...
[info] Resolving jline#jline;2.12.1 ...
[info] Done updating.
[info] Compiling 2 Scala sources to /root/TwitterPopularTags/target/scala-2.11/classes...
[success] Total time: 14 s, completed Sep 16, 2016 9:55:20 AM
[root#hadoop1 TwitterPopularTags]# sbt package
[info] Set current project to TwitterPopularTags (in build file:/root/TwitterPopularTags/)
[info] Packaging /root/TwitterPopularTags/target/scala-2.11/twitterpopulartags_2.11-1.0.jar ...
[info] Done packaging.
[success] Total time: 1 s, completed Sep 16, 2016 9:56:20 AM
[root#hadoop1 TwitterPopularTags]# spark-submit /root/TwitterPopularTags/target/scala-2.11/twitterpopulartags_2.11-1.0.jar
16/09/16 09:57:06 INFO SparkContext: Running Spark version 1.6.2
16/09/16 09:57:06 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
16/09/16 09:57:06 INFO SecurityManager: Changing view acls to: root
16/09/16 09:57:06 INFO SecurityManager: Changing modify acls to: root
16/09/16 09:57:06 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(root); users with modify permissions: Set(root)
16/09/16 09:57:07 INFO Utils: Successfully started service 'sparkDriver' on port 53967.
16/09/16 09:57:07 INFO Slf4jLogger: Slf4jLogger started
16/09/16 09:57:07 INFO Remoting: Starting remoting
16/09/16 09:57:07 INFO Remoting: Remoting started; listening on addresses :[akka.tcp://sparkDriverActorSystem#10.100.44.17:57877]
16/09/16 09:57:07 INFO Utils: Successfully started service 'sparkDriverActorSystem' on port 57877.
16/09/16 09:57:07 INFO SparkEnv: Registering MapOutputTracker
16/09/16 09:57:07 INFO SparkEnv: Registering BlockManagerMaster
16/09/16 09:57:07 INFO DiskBlockManager: Created local directory at /tmp/blockmgr-47a89077-0926-447c-ada7-fdb4a9aa1b83
16/09/16 09:57:07 INFO MemoryStore: MemoryStore started with capacity 511.5 MB
16/09/16 09:57:07 INFO SparkEnv: Registering OutputCommitCoordinator
16/09/16 09:57:08 INFO Server: jetty-8.y.z-SNAPSHOT
16/09/16 09:57:08 INFO AbstractConnector: Started SelectChannelConnector#0.0.0.0:4040
16/09/16 09:57:08 INFO Utils: Successfully started service 'SparkUI' on port 4040.
16/09/16 09:57:08 INFO SparkUI: Bound SparkUI to 0.0.0.0, and started at http://10.100.44.17:4040
16/09/16 09:57:08 INFO HttpFileServer: HTTP File server directory is /tmp/spark-d56628b6-fdbf-4d89-bbd2-a96603000607/httpd-ee499eb3-00ae-4276-b163-423e3b81f0b4
16/09/16 09:57:08 INFO HttpServer: Starting HTTP Server
16/09/16 09:57:08 INFO Server: jetty-8.y.z-SNAPSHOT
16/09/16 09:57:08 INFO AbstractConnector: Started SocketConnector#0.0.0.0:56067
16/09/16 09:57:08 INFO Utils: Successfully started service 'HTTP file server' on port 56067.
16/09/16 09:57:08 INFO SparkContext: Added JAR file:/root/TwitterPopularTags/target/scala-2.11/twitterpopulartags_2.11-1.0.jar at http://10.100.44.17:56067/jars/twitterpopulartags_2.11-1.0.jar with timestamp 1474034228091
16/09/16 09:57:08 INFO Executor: Starting executor ID driver on host localhost
16/09/16 09:57:08 INFO Utils: Successfully started service 'org.apache.spark.network.netty.NettyBlockTransferService' on port 49715.
16/09/16 09:57:08 INFO NettyBlockTransferService: Server created on 49715
16/09/16 09:57:08 INFO BlockManagerMaster: Trying to register BlockManager
16/09/16 09:57:08 INFO BlockManagerMasterEndpoint: Registering block manager localhost:49715 with 511.5 MB RAM, BlockManagerId(driver, localhost, 49715)
16/09/16 09:57:08 INFO BlockManagerMaster: Registered BlockManager
16/09/16 09:57:08 WARN DomainSocketFactory: The short-circuit local reads feature cannot be used because libhadoop cannot be loaded.
16/09/16 09:57:08 INFO EventLoggingListener: Logging events to hdfs:///spark-history/local-1474034228122
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/spark/streaming/twitter/TwitterUtils$
at dot.state.fl.us.PrintTweets$.main(PrintTweets.scala:29)
at dot.state.fl.us.PrintTweets.main(PrintTweets.scala)
my question is why SBT is not including the jar files from resource folder in the compilation ?
Because that's not what resource folder is for. If you want to manage the dependencies manually, put them into lib folder instead. But in this case you also need to do the same with all dependencies of those dependencies, their dependencies, etc. Using managed dependencies, as described in the linked documentation, is a much better idea in general.
10:52:16,587 INFO [stdout] (http--0.0.0.0-8080-3) Hibernate:
10:52:16,587 INFO [stdout] (http--0.0.0.0-8080-3) select
10:52:16,587 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.age_band_age_id as age_band4_5_0_,
10:52:16,587 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.age_band_age_share_id as age_band1_6_0_,
10:52:16,587 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.age_band_age_share_id as age_band1_6_1_,
10:52:16,587 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.age_band_age_id as age_band4_6_1_,
10:52:16,588 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.is_active as is_activ2_6_1_,
10:52:16,588 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.share_amount as share_am3_6_1_,
10:52:16,588 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.tier_id as tier_id5_6_1_
10:52:16,588 INFO [stdout] (http--0.0.0.0-8080-3) from
10:52:16,588 INFO [stdout] (http--0.0.0.0-8080-3) eba_age_band_age_share agebandage0_
10:52:16,589 INFO [stdout] (http--0.0.0.0-8080-3) where
10:52:16,589 INFO [stdout] (http--0.0.0.0-8080-3) agebandage0_.age_band_age_id=?
I want to log sql query in following manner :
10:52:16,588 INFO [stdout] (http--0.0.0.0-8080-3)
Hibernate:
SELECT
agebandage0_.age_band_age_id AS age_band4_5_0_,
agebandage0_.age_band_age_share_id AS age_band1_6_0_,
agebandage0_.age_band_age_share_id AS age_band1_6_1_,
agebandage0_.age_band_age_id AS age_band4_6_1_,
agebandage0_.is_active AS is_activ2_6_1_,
agebandage0_.share_amount AS share_am3_6_1_,
agebandage0_.tier_id AS tier_id5_6_1_
FROM
eba_age_band_age_share agebandage0_
WHERE
agebandage0_.age_band_age_id=?
Hibernate query logging writes to stdout, System.out, which is wrapped by a logger in JBoss AS 7. The wrapped stream processes each line separately logging each line separately which is why you see the prefix on each line.
There is no way to turn this off. You could create a logger called stdout and assign a handler to it that doesn't for any formatting. Just give it a pattern of %s%n. That would print each line with no formatting.
I recently began working with Sitecore on a fresh system. I installed IIS, configured it, and was able to get the project to build and load on IIS just fine. While trying to figure out why the startup time was so slow, it began to give me this error.
Value cannot be null.
Parameter name: message
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: message
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ArgumentNullException: Value cannot be null.
Parameter name: message]
Sitecore.Diagnostics.Log.Info(String message, Object owner) +309
Sitecore.Nexus.Web.HttpModule.Init(HttpApplication app) +557
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +530
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475
[HttpException (0x80004005): Value cannot be null.
Parameter name: message]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12966756
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12806561
I have tried the following:
Doing a full get (overriding all) for TFS and re-building
Pulling down an exact copy of the files that are on the dev environment (which works)
Disabling logging in Sitecore
Deleting the project from my local system and pulling it down again from TFS, rebuilding
Deleting the inetpub www folder IIS was pointing to and re-building
Removing and re-adding the IIS site and app pool
Uninstalling IIS and reinstalling it
Deleting temporary ASP.NET files from the .NET framework folders
Clearing out IIS config files (along with a reinstall)
Clearing out .NET machine.config files and repairing .NET
Re-registering .NET with IIS
Changing the app pool user
Granting very liberal permissions to the inetpub folder, .NET framework folders (C:\Windows\Microsoft.NET...)
Adding the app pool user to Performance Log Users, Performance Monitor Users
Removing all config files from /App_Config/Include/
I'm not sure what else to try at this point.
Any ideas?
One of the first things that Sitecore does is to start writing out a message that says "HttpModule is being initialized". Before you get the exception, do you see this message in the logs? The exception you have seems to indicate that initial loadup is trying to extract details for the message to log but is not receiving any.
If you examine your log file, you should hopefully be able to see how far the logging can get before it is getting a 'null' message and blowing up. From there, it will be easier to identify what the next typical information line would be and track down what is happening.
For example, here is a typical 6.6 INFO block from the start of a log file:
10024 10:26:13 INFO HttpModule is being initialized
10024 10:26:13 INFO
10024 10:26:13 INFO **********************************************************************
10024 10:26:13 INFO **********************************************************************
10024 10:26:13 INFO Sitecore started
10024 10:26:13 INFO Sitecore.NET 6.6.0 (rev. 130529)
10024 10:26:13 INFO
10024 10:26:13 INFO C:\Src\TFS\Path\Website\bin\Sitecore.Client.dll (Sitecore CMS, Sitecore Client Application, 6.6.0 rev. 130529)
10024 10:26:13 INFO C:\Src\TFS\Path\Website\bin\Sitecore.Kernel.dll (Sitecore CMS, Sitecore CMS Kernel Library, 6.6.0 rev. 130529)
10024 10:26:13 INFO C:\Src\TFS\Path\Website\bin\Sitecore.Nexus.dll (Sitecore.Nexus)
10024 10:26:13 INFO
10024 10:26:13 INFO Operating system Microsoft Windows NT 6.1.7601 Service Pack 1
10024 10:26:13 INFO
10024 10:26:13 INFO Microsoft.NET version 4.0.30319.18444
10024 10:26:13 INFO
10024 10:26:13 INFO Process id: 12132
10024 10:26:13 INFO Windows identity used by the process: IIS APPPOOL\MyAppPoolUser. Impersonation: True
10024 10:26:13 INFO Managed pipeline mode: Integrated
10024 10:26:13 INFO
10024 10:26:13 INFO EventQueues enabled: False
10024 10:26:13 INFO Instance Name:MyInstanceName
10024 10:26:13 INFO
10024 10:26:13 INFO Threshold settings
10024 10:26:13 INFO Show threshold warnings: False
10024 10:26:13 INFO
10024 10:26:13 INFO Databases
10024 10:26:13 INFO core
10024 10:26:13 INFO master
10024 10:26:13 INFO web
10024 10:26:13 INFO filesystem
10024 10:26:13 INFO
10024 10:26:13 INFO Domains
10024 10:26:13 INFO Heartbeat - Initializing
10024 10:26:13 INFO Heartbeat - Interval set to: 00:00:02
10024 10:26:13 INFO Heartbeat - Worker thread started
10024 10:26:13 INFO Trying to load XML configuration /App_Config/Security/Domains.config
10024 10:26:13 INFO sitecore
10024 10:26:13 INFO extranet
10024 10:26:13 INFO default
10024 10:26:13 INFO **********************************************************************
10024 10:26:13 INFO **********************************************************************
10024 10:26:13 INFO Attempting to get ASP.NET process history
10024 10:26:13 WARN No process history available
I'm trying to get a web app up and running on jboss 5 in eclipse and i'm not getting any errors in the log and when i hit http://localhost:8080/WebDataViewer, i just get the default http 404 error page.
When i hit http://localhost:8080/ i get the default jboss page with some links on it.
I've not worked with jboss before, but can anyone help figure out how i can access my app or how i can troubleshoot this?
10:07:39,706 INFO [ServerImpl] Starting JBoss (Microcontainer)...
10:07:39,707 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)
10:07:39,707 INFO [ServerImpl] Bootstrap URL: null
10:07:39,707 INFO [ServerImpl] Home Dir: C:\jboss-5.1.0.GA
10:07:39,708 INFO [ServerImpl] Home URL: file:/C:/jboss-5.1.0.GA/
10:07:39,708 INFO [ServerImpl] Library URL: file:/C:/jboss-5.1.0.GA/lib/
10:07:39,708 INFO [ServerImpl] Patch URL: null
10:07:39,708 INFO [ServerImpl] Common Base URL: file:/C:/jboss-5.1.0.GA/common/
10:07:39,708 INFO [ServerImpl] Common Library URL: file:/C:/jboss-5.1.0.GA/common/lib/
10:07:39,709 INFO [ServerImpl] Server Name: default
10:07:39,709 INFO [ServerImpl] Server Base Dir: C:\jboss-5.1.0.GA\server
10:07:39,709 INFO [ServerImpl] Server Base URL: file:/C:/jboss-5.1.0.GA/server/
10:07:39,709 INFO [ServerImpl] Server Config URL: file:/C:/jboss-5.1.0.GA/server/default/conf/
10:07:39,709 INFO [ServerImpl] Server Home Dir: C:\jboss-5.1.0.GA\server\default
10:07:39,709 INFO [ServerImpl] Server Home URL: file:/C:/jboss-5.1.0.GA/server/default/
10:07:39,709 INFO [ServerImpl] Server Data Dir: C:\jboss-5.1.0.GA\server\default\data
10:07:39,709 INFO [ServerImpl] Server Library URL: file:/C:/jboss-5.1.0.GA/server/default/lib/
10:07:39,710 INFO [ServerImpl] Server Log Dir: C:\jboss-5.1.0.GA\server\default\log
10:07:39,710 INFO [ServerImpl] Server Native Dir: C:\jboss-5.1.0.GA\server\default\tmp\native
10:07:39,710 INFO [ServerImpl] Server Temp Dir: C:\jboss-5.1.0.GA\server\default\tmp
10:07:39,710 INFO [ServerImpl] Server Temp Deploy Dir: C:\jboss-5.1.0.GA\server\default\tmp\deploy
10:07:40,279 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
10:07:40,898 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
10:07:40,900 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
10:07:41,132 INFO [CopyMechanism] VFS temp dir: C:\jboss-5.1.0.GA\server\default\tmp
10:07:41,133 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
10:07:42,399 INFO [ServerInfo] Java version: 1.6.0_35,Sun Microsystems Inc.
10:07:42,399 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
10:07:42,399 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.10-b01,Sun Microsystems Inc.
10:07:42,399 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
10:07:42,399 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dfile.encoding=Cp1252
10:07:42,425 INFO [JMXKernel] Legacy JMX core initialized
10:07:44,183 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey#2ee634bf[domain=default, server=default, name=default]
10:07:45,435 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
10:07:50,839 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
10:07:50,839 INFO [NativeServerConfig] 3.1.2.GA
10:07:51,473 INFO [AttributeCallbackItem] Owner callback not implemented.
10:07:52,334 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl#5de82b72[ defaultDomain='jboss' ]
10:08:06,536 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:06,536 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:06,537 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:06,537 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:08,928 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
10:08:09,029 INFO [MailService] Mail Service bound to java:/Mail
10:08:11,006 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 installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
10:08:11,020 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
10:08:11,073 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
10:08:11,111 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
10:08:11,111 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
10:08:11,312 INFO [TransactionManagerService] Initializing recovery manager
10:08:11,436 INFO [TransactionManagerService] Recovery manager configured
10:08:11,436 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
10:08:11,457 INFO [TransactionManagerService] Starting transaction recovery manager
10:08:12,016 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_35\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jdk1.6.0_35/bin/../jre/bin/server;C:/Program Files/Java/jdk1.6.0_35/bin/../jre/bin;C:/Program Files/Java/jdk1.6.0_35/bin/../jre/lib/amd64;c:\program files\apache-maven-3.0.x\bin;C:\Ruby192\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\sybase15_0_7\OCS-15_0\bin;C:\sybase15_0_7\OCS-15_0\dll;C:\sybase15_0_7\OCS-15_0\lib3p;C:\sybase15_0_7\DataAccess\ADONET\dll;C:\sybase15_0_7\DataAccess\ODBC\dll;C:\sybase15_0_7\DataAccess\OLEDB\dll;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\MySQL\MySQL Server 5.5\bin;c:\Program Files\Stellent\IBPM;C:\PROGRA~2\IBM\SQLLIB\BIN;C:\PROGRA~2\IBM\SQLLIB\FUNCTION;C:\PROGRA~2\IBM\SQLLIB\bin;%JAVA_HOME%\bin;C:\Program Files\apache-maven-3.0.4\bin;C:\Oracle_Instant_Client(32bit)\instantclient_11_2;C:\Program Files (x86)\Git\cmd;C:\Program Files\TortoiseSVN\bin;C:\Program Files\eclipse;;.
10:08:12,087 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
10:08:12,089 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
10:08:12,122 INFO [StandardService] Starting service jboss.web
10:08:12,130 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA
10:08:12,235 INFO [Catalina] Server startup in 145 ms
10:08:12,258 INFO [TomcatDeployment] deploy, ctxPath=/web-console
10:08:12,993 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
10:08:13,068 INFO [TomcatDeployment] deploy, ctxPath=/invoker
10:08:13,242 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
10:08:13,285 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
10:08:13,310 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
10:08:13,324 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
10:08:13,353 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
10:08:13,422 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
10:08:13,442 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
10:08:13,445 INFO [RAMJobStore] RAMJobStore initialized.
10:08:13,446 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
10:08:13,446 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
10:08:13,446 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
10:08:13,769 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
10:08:14,145 INFO [ServerPeer] JBoss Messaging 1.4.3.GA server [0] started
10:08:14,220 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
10:08:14,269 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
10:08:14,269 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#4bb8e77c started
10:08:14,271 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
10:08:14,272 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
10:08:14,272 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#28062593 started
10:08:14,272 INFO [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
10:08:14,282 INFO [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
10:08:14,283 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
10:08:14,283 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#30726eca started
10:08:14,419 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
10:08:14,705 INFO [JBossASKernel] Created KernelDeployment for: profileservice-secured.jar
10:08:14,712 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
10:08:14,712 INFO [JBossASKernel] with dependencies:
10:08:14,712 INFO [JBossASKernel] and demands:
10:08:14,712 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
10:08:14,712 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
10:08:14,713 INFO [JBossASKernel] and supplies:
10:08:14,713 INFO [JBossASKernel] Class:org.jboss.profileservice.spi.ProfileService
10:08:14,713 INFO [JBossASKernel] jndi:SecureProfileService/remote
10:08:14,713 INFO [JBossASKernel] jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
10:08:14,713 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profileservice-secured.jar
10:08:14,714 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
10:08:14,714 INFO [JBossASKernel] with dependencies:
10:08:14,714 INFO [JBossASKernel] and demands:
10:08:14,714 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
10:08:14,714 INFO [JBossASKernel] and supplies:
10:08:14,714 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager
10:08:14,714 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management.deploy.DeploymentManager
10:08:14,714 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote
10:08:14,714 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profileservice-secured.jar
10:08:14,715 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
10:08:14,715 INFO [JBossASKernel] with dependencies:
10:08:14,715 INFO [JBossASKernel] and demands:
10:08:14,715 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
10:08:14,715 INFO [JBossASKernel] and supplies:
10:08:14,715 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
10:08:14,715 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management.ManagementView
10:08:14,715 INFO [JBossASKernel] jndi:SecureManagementView/remote
10:08:14,715 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar
10:08:14,722 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData#6cdc5f76{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
10:08:14,723 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData#240c5895{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
10:08:14,723 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData#1cfd0695{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
10:08:14,877 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
10:08:14,887 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager
10:08:15,010 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface
SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface
10:08:15,055 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
10:08:15,056 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView
10:08:15,064 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureManagementView/remote - EJB3.x Default Remote Business Interface
SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface
10:08:15,107 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
10:08:15,108 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
10:08:15,150 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureProfileService/remote - EJB3.x Default Remote Business Interface
SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
10:08:15,778 INFO [TomcatDeployment] deploy, ctxPath=/admin-console
10:08:15,930 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
10:08:19,678 INFO [TomcatDeployment] deploy, ctxPath=/
10:08:23,577 INFO [TomcatDeployment] deploy, ctxPath=/WebDataViewer
10:08:23,825 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/WebDataViewer'
10:08:24,812 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
10:08:25,069 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
10:08:25,093 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
10:08:25,099 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 45s:387ms
Snippet from web.xml
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.xhtml</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
The address http://localhost:8080/WebDataViewer just points to the context root of the application, so it will just work if you've a default page defined (such as index.jsp). If you've no default resource for the context root WebDataViewer, you'll have to especify a resource name (a resource can be a servlet, a jsp, jsf ...), for example: http://localhost:8080/WebDataViewer/myservlet.
Usually you can look at the resources defined for your application in the WEB-INF/web.xml of your application, for example:
<servlet-mapping>
<servlet-name>MyServlet</servlet-name>
<url-pattern>/myservlet</url-pattern>
</servlet-mapping>
In your case, according to your web.xml, it seems you're using JSF. So I guess that you should have some xhtml files in the root of your war (or at least in any subdirectory). For example if your war is like:
WebDataViewer.war
|
|--page.xhtml
|
|--WEB-INF
| |
| |- web.xml
| |- ...
|- ...
A valid address would be: http://localhost:8080/WebDataViewer/page.xhtml.