You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by "Tawfik, Sameh E" <Sa...@fairisaac.com> on 2008/01/29 02:40:34 UTC
Continuum 1.1 standalone run-time error on Windows server 2003.
I just installed Continuum 1.1 on Windows Server 2003 - Enterprise
Edition with Service Pack 1, by extracting all the files from
apache-continuum-1.1.zip
Next, I run C:\continuum-1.1\bin\windows-x86-32\run.bat
When run.bat runs, it generated the following error:
[ERROR] Error while deploying appserver
continuum-plexus-application-1.1.jar.
Does anyone know what causes this problem and how to fix it?
Thanks,
Here is the full output:
------------------------
C:\continuum-1.1\bin\windows-x86-32>run.bat
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights
Reserved.
jvm 1 |
jvm 1 | [INFO] Loading on start [role,roleHint]:
[org.codehaus.plexus.naming.Naming,dataSources]
jvm 1 | [INFO] Loading on start [role,roleHint]:
[org.codehaus.plexus.contextualizer.Contextualizer,jettyConfiguration]
jvm 1 | [INFO] Services will be deployed in:
'C:\continuum-1.1\bin\windows-x86-32\..\..\services'.
jvm 1 | [INFO] Applications will be deployed in:
'C:\continuum-1.1\bin\windows-x86-32\..\..\apps'.
jvm 1 | [INFO] Service Supervisor is deploying
plexus-appserver-service-jetty-2.0-alpha-8.
jvm 1 | [DEBUG] Found 1 components to load on start
jvm 1 | [INFO] Loading on start [role,roleHint]:
[org.codehaus.plexus.appserver.service.PlexusService,jetty]
jvm 1 | Jan 28, 2008 4:09:55 PM org.mortbay.http.HttpServer doStart
jvm 1 | INFO: Version Jetty/5.1.10
jvm 1 | Jan 28, 2008 4:09:55 PM org.mortbay.util.Container start
jvm 1 | INFO: Started org.mortbay.jetty.Server@42552c
jvm 1 | [INFO] Application Supervisor is deploying
continuum-plexus-application-1.1.
jvm 1 | [INFO] Extracting
C:\continuum-1.1\bin\windows-x86-32\..\..\apps\continuum-plexus-applicat
ion-1.1.jar to 'C:\continuum-1.1\apps\continuum'.
jvm 1 | [INFO] Deploying application 'continuum' at
'C:\continuum-1.1\apps\continuum'.
jvm 1 | [INFO] Using application configurator file
C:\continuum-1.1\bin\windows-x86-32\..\..\apps\continuum\conf\applicatio
n.xml.
jvm 1 | [INFO] Using appDir =
C:\continuum-1.1\bin\windows-x86-32\..\..\apps\continuum
jvm 1 | [DEBUG] appserver.home =
C:\continuum-1.1\bin\windows-x86-32\..\..
jvm 1 | [DEBUG] appserver.base =
C:\continuum-1.1\bin\windows-x86-32\..\..
jvm 1 | [INFO] Deploying C:\continuum-1.1\apps\continuum\webapp with
context path of /continuum
jvm 1 | [INFO] Using standard webapp classloader for webapp.
jvm 1 | [INFO] Deploying appserver 'continuum'.
jvm 1 | [INFO] Adding HTTP listener on *8080
jvm 1 | Jan 28, 2008 4:10:06 PM org.mortbay.util.ThreadedServer start
jvm 1 | WARNING: Failed to start: SocketListener0@0.0.0.0:8080
jvm 1 | [ERROR] Error while deploying appserver
continuum-plexus-application-1.1.jar.
jvm 1 | org.codehaus.plexus.appserver.ApplicationServerException:
Error in the app server lifecycle post-app-container-init-service-call
phase.
jvm 1 | at
org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo
yer.deployJar(DefaultApplicationDeployer.java:119)
jvm 1 | at
org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo
yer.deploy(DefaultApplicationDeployer.java:88)
jvm 1 | at
org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase
$1.onJarDiscovered(ApplicationDeploymentPhase.java:44)
jvm 1 | at
org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scanDirectory
(DefaultSupervisor.java:100)
jvm 1 | at
org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scan(DefaultS
upervisor.java:73)
jvm 1 | at
org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase
.execute(ApplicationDeploymentPhase.java:58)
jvm 1 | at
org.codehaus.plexus.appserver.DefaultApplicationServer.start(DefaultAppl
icationServer.java:218)
jvm 1 | at
org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execut
e(StartPhase.java:33)
jvm 1 | at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:128)
jvm 1 | at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:142)
jvm 1 | at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:132)
jvm 1 | at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g
etComponent(ClassicSingletonComponentManager.java:90)
jvm 1 | at
org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponen
tLookupManager.java:147)
jvm 1 | at
org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponen
tLookupManager.java:69)
jvm 1 | at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:297)
jvm 1 | at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:291)
jvm 1 | at
org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicat
ionHost.java:155)
jvm 1 | at
org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicat
ionHost.java:85)
jvm 1 | at
org.codehaus.plexus.appserver.PlexusApplicationHost.main(PlexusApplicati
onHost.java:289)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
jvm 1 | at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
jvm 1 | at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
jvm 1 | at java.lang.reflect.Method.invoke(Method.java:597)
jvm 1 | at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launche
r.java:289)
jvm 1 | at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:2
29)
jvm 1 | at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launc
her.java:408)
jvm 1 | at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351
)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
jvm 1 | at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
jvm 1 | at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
jvm 1 | at java.lang.reflect.Method.invoke(Method.java:597)
jvm 1 | at
org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:24
0)
jvm 1 | at java.lang.Thread.run(Thread.java:619)
jvm 1 | Caused by:
org.codehaus.plexus.appserver.application.deploy.lifecycle.AppDeployment
Exception: Error calling service in pre-app init phase.
jvm 1 | at
org.codehaus.plexus.appserver.application.deploy.lifecycle.phase.AfterAp
pStartServiceSetupPhase.execute(AfterAppStartServiceSetupPhase.java:32)
jvm 1 | at
org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo
yer.deployJar(DefaultApplicationDeployer.java:107)
jvm 1 | ... 32 more
jvm 1 | Caused by:
org.codehaus.plexus.appserver.service.PlexusServiceException: Error
while adding httpListener on address: 'null', port: 8080.
jvm 1 | at
org.codehaus.plexus.service.jetty.JettyPlexusService.processWebContextCo
nfiguration(JettyPlexusService.java:349)
jvm 1 | at
org.codehaus.plexus.service.jetty.JettyPlexusService.afterApplicationSta
rt(JettyPlexusService.java:217)
jvm 1 | at
org.codehaus.plexus.appserver.application.deploy.lifecycle.phase.AfterAp
pStartServiceSetupPhase.execute(AfterAppStartServiceSetupPhase.java:28)
jvm 1 | ... 33 more
jvm 1 | Caused by:
org.codehaus.plexus.jetty.ServletContainerException: Error while adding
httpListener on address: 'null', port: 8080.
jvm 1 | at
org.codehaus.plexus.jetty.AbstractJettyServletContainer.addListener(Abst
ractJettyServletContainer.java:119)
jvm 1 | at
org.codehaus.plexus.service.jetty.JettyPlexusService.processWebContextCo
nfiguration(JettyPlexusService.java:345)
jvm 1 | ... 35 more
jvm 1 | Caused by: java.net.BindException: Address already in use:
JVM_Bind
jvm 1 | at java.net.PlainSocketImpl.socketBind(Native Method)
jvm 1 | at
java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
jvm 1 | at java.net.ServerSocket.bind(ServerSocket.java:319)
jvm 1 | at java.net.ServerSocket.<init>(ServerSocket.java:185)
jvm 1 | at
org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:391)
jvm 1 | at
org.mortbay.util.ThreadedServer.open(ThreadedServer.java:477)
jvm 1 | at
org.mortbay.util.ThreadedServer.start(ThreadedServer.java:503)
jvm 1 | at
org.mortbay.http.SocketListener.start(SocketListener.java:203)
jvm 1 | at
org.codehaus.plexus.jetty.AbstractJettyServletContainer.addListener(Abst
ractJettyServletContainer.java:115)
jvm 1 | ... 36 more
jvm 1 | [INFO] The appserver server has been initialized.
jvm 1 | [INFO] The appserver server has started.
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
Re: How to adjust the screen size of the output
Posted by Jesse McConnell <je...@gmail.com>.
I would suggest openning a jira issue with this information as well as
browser versions and snapshots of the problem
jesse
On Jan 31, 2008 6:52 PM, Tawfik, Sameh E <Sa...@fairisaac.com> wrote:
>
>
> After the build is complete, when I click on Build History icon followed
> by clicking on the Result icon, the output screen is too big! The output
> screen is behind Continuum main screen, and the output screen is much
> bigger in size than Continuum screen, so its scroll bars are hidden
> behind Continuum screen, and I've to do lots of scrolling to the right
> and to the bottom of Continuum screen to be able to reach the output
> screen scroll bars so I can view the output! It is very cumbersome to
> view the results.
>
> Is there is a way to adjust the size of the output screen so it would
> fit inside the parent Continuum screen, so it would be easy to scroll
> and view?
>
>
> This email and any files transmitted with it are confidential, proprietary
> and intended solely for the individual or entity to whom they are
> addressed.
> If you have received this email in error please delete it immediately.
>
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
RE: Continuum renamed and moved my projects?
Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.
Wendy,
I created two project groups "project group A" and "Project group B". In
"project group A", I added a maven2 project "abc-r4", and in "Project
group B", I added maven2 project "abc-r3".
Both projects represent the same product, but each project represents
different code, so project "abc-4" represents the main code of the trunk
and "abc-r3" project represents the code from a branch in Subversion.
After I did the above, when I attempted to build project "abc-3" that
represents the branch, Continuum did the following:
1. It moved "abc-r4" project from project group "project group A" to the
second project group "Project group B". When I opened "project group A"
it was empty!
2. In project group "Project group B", Continuum renamed both projects
to have the same name? So now, the two projects are called "abc". When I
click on each project to see the properties, I see each project SCM URL
is set correctly to the point to the right line of code inside
Subversion repository, one is set to the trunk, and the other is set to
a branch.
I think there must be some configuration that I need to set inside
Continuum to allow it to maintain the structure that I set? I'm not sure
yet what do I need to set to accomplish this goal? Maybe it's something
I need to set under the Administration choices?
What I'm trying to do is simple, I just want to add two projects of the
same product, one represents the main line of code and the other one
represents a branch.
Sameh
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: Friday, February 01, 2008 6:03 PM
To: continuum-users@maven.apache.org
Subject: Re: Continuum renamed and moved my projects?
On Feb 1, 2008 6:38 PM, Tawfik, Sameh E <Sa...@fairisaac.com>
wrote:
> Now when I run a build, Continuum did the following:
>
> 1. It moved the project under the trunk code group to be under the
> second group that is I set to point to the branch?
>
> 2. In the group that points to the branch, Continuum renamed both
> projects to have the same name?
What do you mean when you say Continuum "moved" and "renamed" the
projects?
--
Wendy
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
Re: Continuum renamed and moved my projects?
Posted by Wendy Smoak <ws...@gmail.com>.
On Feb 1, 2008 6:38 PM, Tawfik, Sameh E <Sa...@fairisaac.com> wrote:
> Now when I run a build, Continuum did the following:
>
> 1. It moved the project under the trunk code group to be under the
> second group that is I set to point to the branch?
>
> 2. In the group that points to the branch, Continuum renamed both
> projects to have the same name?
What do you mean when you say Continuum "moved" and "renamed" the projects?
--
Wendy
Continuum renamed and moved my projects?
Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.
I created two project groups and added to each group a maven2 project,
one is set to a branch and the other one is set to point to the trunk in
Subversion. Both projects represent the same product, but as specified
each project represents different code.
I renamed each project to reflect the code type one as main and the
other as a branch.
Now when I run a build, Continuum did the following:
1. It moved the project under the trunk code group to be under the
second group that is I set to point to the branch?
2. In the group that points to the branch, Continuum renamed both
projects to have the same name?
Does anyone know what is wrong?
Sameh
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
How to adjust the screen size of the output
Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.
After the build is complete, when I click on Build History icon followed
by clicking on the Result icon, the output screen is too big! The output
screen is behind Continuum main screen, and the output screen is much
bigger in size than Continuum screen, so its scroll bars are hidden
behind Continuum screen, and I've to do lots of scrolling to the right
and to the bottom of Continuum screen to be able to reach the output
screen scroll bars so I can view the output! It is very cumbersome to
view the results.
Is there is a way to adjust the size of the output screen so it would
fit inside the parent Continuum screen, so it would be easy to scroll
and view?
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
RE: Continuum 1.1 standalone run-time error on Windows server 2003.
Posted by "Tawfik, Sameh E" <Sa...@fairisaac.com>.
Thanks Wendy, I used port 8085 and that fixed it.
Sameh
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: Monday, January 28, 2008 5:52 PM
To: continuum-users@maven.apache.org
Subject: Re: Continuum 1.1 standalone run-time error on Windows server
2003.
On Jan 28, 2008 6:40 PM, Tawfik, Sameh E <Sa...@fairisaac.com>
wrote:
>
> I just installed Continuum 1.1 on Windows Server 2003 - Enterprise
> Edition with Service Pack 1, by extracting all the files from
> apache-continuum-1.1.zip
>
> Next, I run C:\continuum-1.1\bin\windows-x86-32\run.bat
...
jvm 1 | Caused by: java.net.BindException: Address already in use:
JVM_Bind
Looks like you already have something running on port 8080. You can
change the port number in one of the xml files, I think you'll find it
if you search for 'jetty.port', or check the docs.
--
Wendy
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
Re: Continuum 1.1 standalone run-time error on Windows server 2003.
Posted by Wendy Smoak <ws...@gmail.com>.
On Jan 28, 2008 6:40 PM, Tawfik, Sameh E <Sa...@fairisaac.com> wrote:
>
> I just installed Continuum 1.1 on Windows Server 2003 - Enterprise
> Edition with Service Pack 1, by extracting all the files from
> apache-continuum-1.1.zip
>
> Next, I run C:\continuum-1.1\bin\windows-x86-32\run.bat
...
jvm 1 | Caused by: java.net.BindException: Address already in use:
JVM_Bind
Looks like you already have something running on port 8080. You can
change the port number in one of the xml files, I think you'll find it
if you search for 'jetty.port', or check the docs.
--
Wendy