Trouble starting J2EE1.3 Server
hey after setting my java_home to jdk1.2.2 and my j2ee_home to j2sdkee1.3,i tried starting the J2ee server using the j2ee batch file.
but its' giving the following exception....
Exception in thread "main" java.lang.NoClassDefFoundError: javax/naming/Context
at com.sun.enterprise.server.J2EEServer.<clinit>(J2EEServer.java:59)
can anybody help out in this
thanx
Josh
j2sdkee is designed to work with JDK 1.3. Then it will start without a problem.I mean
j2sdkee 1.3 is designed to work with JDK 1.3. Then it will start without a problem.
Similar Messages
-
Trouble starting managed weblogic server on another machine in acluster
Hi,
I was having trouble starting managed weblogic server on another machine in a cluster from the command prompt
I have following setup:
1) BEA weblogic is installed on 2 machines - local machine A with ip address 172.17.2.219 and another machine B with ip address 172.17.2.201
2)node manager is running on both machines
3)An admin server myserver on the local machine at port 7001
4)In the admin tree under Machines a new machine is created 'Machine1' with Node manager Listen Address: 172.17.2.201
5) The managed server 'BEAServerMan1 ' instance is created with listen Address 172.17.2.201 and port 7705. This Server is assigened to Machine1. The server also belongs to a cluster 'Cluster1' where the 172.17.2.201:7705 is part of the Cluster Address.
I can start 'BEAServerMan1 from http://172.17.2.16:7001/console/
But I am unable to start BEAServerMan1 from the console using the command :
startManagedWebLogic BEAServerMan1 http://172.17.2.219:7001
startManagedWebLogic.sh BEAServerMan1 http://172.17.2.219:7001
CLASSPATH=/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/BEA/weblogic81/server/lib/weblogic_sp.jar:/opt/BEA/weblogic81/server/lib/weblogic.jar:/opt/BEA/weblogic81/server/lib/ojdbc14.jar::/opt/BEA/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/opt/BEA/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/BEA/j2sdk1.4.1_03/jre/lib/rt.jar:/opt/BEA/weblogic81/server/lib/webservices.jar:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/oracle/OraHome1/jdbc/lib/classes111.jar:/opt/oracle/OraHome1/jdbc/lib/nls_charset11.jarx:/opt/BEA/user_projects/domains/mydomain/myserver/stage/_appsdir_dyn_ear/dyn.war:/opt/BEA/user_projects/domains/mydomain/./myserver/.wlnotdelete/extract/myserver__appsdir_dyn_ear_dyn/jarfiles/WEB-INF/lib/dspjspTaglib1_036773.jar:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11:/usr/bin/j2sdk1_3_1_11/lib/tools.jar
PATH=/opt/BEA/weblogic81/server/bin:/opt/BEA/j2sdk1.4.1_03/jre/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/ATG6.2.0/home/bin:/usr/xpg4/bin:/opt/bmc/Patrol3/Solaris28-sun4/bin:/usr/bin::/usr/openwin/bin:/bin:/usr/ucb:/usr/local/sbin:/usr/dt/bin:/opt/RICHPse/bin:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://<hostname>:<port>/console *
<13-Jan-2005 3:22:20 o'clock PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.1_03-b02 from Sun Microsystems Inc.>
<13-Jan-2005 3:22:21 o'clock PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://172.17.2.219:7001 to check if there exists a running admin server at this URL.>
<13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
WebLogic XMLX Module 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009>
<13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://172.17.2.219:7001 to retrieve the initial configuration.>
<13-Jan-2005 3:22:27 o'clock PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /opt/BEA/user_projects/domains/mydomain/BEAServerMan1 /BEAServerMan1 .log is opened. All server side log events will be written to this file.>
<13-Jan-2005 3:22:37 o'clock PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<13-Jan-2005 3:22:38 o'clock PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "BEAServerMan1 " for domain "mydomain">
<13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster Cluster1 on 237.0.0.1:7001.>
<13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster1.>
<13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000350> <Unable to create a server socket on Channel Default for: 172.17.2.201, port: 7705. java.net.BindException: Cannot assign requested address Perhaps the address 172.17.2.201 is incorrect or another process is using port 7705.>
<13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <Security> <BEA-090085> <Server failed to bind to the configured port. The port may already be used by another process.>
<13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Server failed to bind to the requested port. See preceeding log message for details.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.server.ServerLifecycleException: Server failed to bind to the requested port. See preceeding log message for details.'
Reason: Server failed to bind to the requested port. See preceeding log message for details.
***************************************************************************Hi
i am also facing the same problem.kindly reply for th solution if you got.
D:\bea1\user_projects_cluster\mydomain>startManagedWebLogic server2 10.16.96.21:
7001
D:\bea1\user_projects_cluster\mydomain>echo off
CLASSPATH=d:\bea1\jdk131_03\lib\tools.jar;d:\bea1\weblogic700\server\lib\weblogi
c_sp.jar;d:\bea1\weblogic700\server\lib\weblogic.jar;F:\bea\weblogic81\server\li
b;D:\;c:\
PATH=.;d:\bea1\weblogic700\server\bin;d:\bea1\jdk131_03\bin;E:\oracle\product\10
.2.0\client_1\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:
\WINDOWS;C:\WINDOWS\System32\Wbem;F:\bea\jdk142_05\bin;C:\PROGRA~1\IBM\CLIENT~1;
C:\PROGRA~1\IBM\CLIENT~1\Shared;C:\PROGRA~1\IBM\CLIENT~1\Emulator;
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
D:\bea1\user_projects_cluster\mydomain>"d:\bea1\jdk131_03\bin\java" -hotspot -Xm
s32m -Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore=d:\bea1\weblogic700\serv
er\lib\cacerts -Dweblogic.Name="server2" -Dbea.home="d:\bea1" -Dweblogic.managem
ent.username= -Dweblogic.management.password= -Dweblogic.management.server="10.1
6.96.21:7001" -Dweblogic.ProductionModeEnabled= -Djava.security.policy="d:\bea1\
weblogic700\server\lib\weblogic.policy" weblogic.Server
<Sep 20, 2007 1:47:13 PM IST> <Info> <Security> <090065> <Getting boot identity
from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
Starting WebLogic Server...
Connecting to http://10.16.96.21:7001...
<Sep 20, 2007 1:47:25 PM IST> <Notice> <Security> <090082> <Security initializin
g using realm myrealm.>
<Sep 20, 2007 1:47:25 PM IST> <Notice> <WebLogicServer> <000328> <Starting WebLo
gic Managed Server "server2" for domain "mydomain">
Starting Cluster Service...
<Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000138> <Listening for announc
ements from cluster mycluster on 237.0.0.1:7777>
<Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000133> <Waiting to synchroniz
e with other running members of mycluster>
<Sep 20, 2007 1:48:16 PM IST> <Notice> <Cluster> <000134> <Discovered and synchr
onized with 1 other running members of mycluster>
<Sep 20, 2007 1:48:17 PM IST> <Emergency> <WebLogicServer> <000350> <Unable to c
reate a server socket on Channel Default for: 10.16.96.24/10.16.96.24, port: 900
1. java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
address 10.16.96.24/10.16.96.24 is incorrect or another process is using port 9
001.>
<Sep 20, 2007 1:48:18 PM IST> <Emergency> <Security> <090085> <Server failed to
bind to any port such that it is not reachable from the console.>
<Sep 20, 2007 1:48:18 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to i
nitialize the server: Fatal initialization exception>
The WebLogic Server did not start up properly.
Reason: Fatal initialization exception
D:\bea1\user_projects_cluster\mydomain>goto finish
D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
D:\bea1\user_projects_cluster\mydomain> -
Hard trouble starting a managed server
Hi,
First, I know many have posted similar questions, but I've read them all,
and none of the solutions seem to help me :-(
On a WLS6.1SP1 on Solaris, I have a setup with one administration server
and one managed server. The two server instances are on the same physical
machine, and they are configured in the same domain, only on different
ports. When I start the managed server, it gets a
"weblogic.net.http.HttpUnauthorizedException: 401]" exception.
Here are some further information:
- I use a RDBMSRealm for all security checking.
- The administration server is started by:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atadmin -Dbea.home=/opt/bea
-Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==/opt/bea/wlserver6.1/lib/weblogic.policy
weblogic.Server
- The managed server is started with:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atserver1 -Dweblogic.management.server=192.168.26.196:7441
-Dbea.home=/opt/bea -Dweblogic.management.username=system
-Dweblogic.management.password=xxxxx -Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==$WL_HOME/lib/weblogic.policy weblogic.Server
- Both the admin server and the managed server is bound to listen to
192.168.26.196 (someone reported problems with using localhost, so I tried
this, no help).
- I've created a password.ini file, with the password for user "system" in.
- Some information on the ACLs and permissions for booting:
In RDBMSRealm, I've defined:
acl: weblogic.server.atadmin
acl: weblogic.server.atserver1
group: "wlsadmin" with permission "boot" on the two ACLs
user: "system" which is defined to be in group wlsadmin
- At boot of administration server I can see, in debugging output, that the
following ACL is checked and found OK: User "system", permission "boot" on
ACL "weblogic.server.atadmin".
- At boot of managed server, I can see in the debugging output, that the
following ACL is checked: User "system", permission "boot" on ACL
"weblogic.server.atserver1".
NOW: The realm implementation returns, that user "system" do have the
needed permission (which is correct), but regardless of this, the
adminstration server logs:
<Dec 28, 2001 2:10:39 PM CET> <Info> <Security> <Access failed (Thread =
Thread[ExecuteThread: '4' for queue: 'default',5,Thread Group for Queue:
'default']), caused java.lang.SecurityException: User "system" does not
have Permission "boot" based on ACL "weblogic.server.atserver1".>
- I've got the same realm, and security data in it, running on my
development machine. This machine only has ONE server, so I don't have the
added managed server setup there. In this setup, all works fine, so the
ACLs are correctly defined.
- If I disable the RDBMS realm, and use the fileRealm, I must define the
exact same ACLs and permissions to boot, but in this setup, it does work
with an administration server and a managed server.
- So, I try a RDBMS realm setup, with fallback on a fileRealm which have
been verified to work, ... same problem.
Hope someone got through the long talk above, and have some suggestion
for what to do, because I'm at a loss here :-(
Regards, Per OlesenHi again,
I managed to solve this one myself.
Here is what I finally found out:
- WLS admin server can only be started as user "system".
- If using RDBMS realm and administration server+managed server setup in
conjunction, the permissions needed for booting any server (managed or
administration) must be set using fileRealm.
- All other permissions can come for RDBMSRealm.
Hmm, so my final setup became:
1. RDBMSRealm with a caching realm.
2. fileRealm with user "system" and needed ACLs+permissions at boot time.
Be sure not to define the information from the fileRealm.properties in your
RDBMSRealm. It will not work.
While you can define all your permissions in a fileRealm and use for
booting any servers in a similar setup, you cannot define all your
permissions in a RDBMSRealm and none in a fileRealm :-(
Regards, Per -
Trouble starting a managed server
Hi,
First, I know many have posted similar questions, but I've read them all,
and none of the solutions seem to help me :-(
On a WLS6.1SP1 on Solaris, I have a setup with one administration server
and one managed server. The two server instances are on the same physical
machine, and they are configured in the same domain, only on different
ports. When I start the managed server, it gets a
"weblogic.net.http.HttpUnauthorizedException: 401]" exception.
Here are some further information:
- I use a RDBMSRealm for all security checking.
- The administration server is started by:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atadmin -Dbea.home=/opt/bea
-Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==/opt/bea/wlserver6.1/lib/weblogic.policy
weblogic.Server
- The managed server is started with:
java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=atdomain
-Dweblogic.Name=atserver1 -Dweblogic.management.server=192.168.26.196:7441
-Dbea.home=/opt/bea -Dweblogic.management.username=system
-Dweblogic.management.password=xxxxx -Dweblogic.ProductionModeEnabled=true
-Djava.security.policy==$WL_HOME/lib/weblogic.policy weblogic.Server
- Both the admin server and the managed server is bound to listen to
192.168.26.196 (someone reported problems with using localhost, so I tried
this, no help).
- I've created a password.ini file, with the password for user "system" in.
- Some information on the ACLs and permissions for booting:
In RDBMSRealm, I've defined:
acl: weblogic.server.atadmin
acl: weblogic.server.atserver1
group: "wlsadmin" with permission "boot" on the two ACLs
user: "system" which is defined to be in group wlsadmin
- At boot of administration server I can see, in debugging output, that the
following ACL is checked and found OK: User "system", permission "boot" on
ACL "weblogic.server.atadmin".
- At boot of managed server, I can see in the debugging output, that the
following ACL is checked: User "system", permission "boot" on ACL
"weblogic.server.atserver1".
NOW: The realm implementation returns, that user "system" do have the
needed permission (which is correct), but regardless of this, the
adminstration server logs:
<Dec 28, 2001 2:10:39 PM CET> <Info> <Security> <Access failed (Thread =
Thread[ExecuteThread: '4' for queue: 'default',5,Thread Group for Queue:
'default']), caused java.lang.SecurityException: User "system" does not
have Permission "boot" based on ACL "weblogic.server.atserver1".>
- I've got the same realm, and security data in it, running on my
development machine. This machine only has ONE server, so I don't have the
added managed server setup there. In this setup, all works fine, so the
ACLs are correctly defined.
- If I disable the RDBMS realm, and use the fileRealm, I must define the
exact same ACLs and permissions to boot, but in this setup, it does work
with an administration server and a managed server.
- So, I try a RDBMS realm setup, with fallback on a fileRealm which have
been verified to work, ... same problem.
Hope someone got through the long talk above, and have some suggestion
for what to do, because I'm at a loss here :-(
Regards, Per OlesenHi Per,
I just wanted to comment really briefly on this.
You can define very nearly everything in the RDBMSRealm rather than the
fileRealm.
The only things that absolutely must exist in the fileRealm are:
"system" user (which can be redundantly declared in the RDBMSRealm, if you
wish)
acl.boot.weblogic.admin=system
If you like, you can declare all other users,groups, and acls in your
RDBMSRealm -- just dup everything you see in the fileRealm and move it to your
RDBMSRealm. I've tried this myself and it works.
But you're right. You can never entirely rid yourself of the fileRealm. :(
Joe Jerry
Per Olesen wrote:
Hi again,
I managed to solve this one myself.
Here is what I finally found out:
- WLS admin server can only be started as user "system".
- If using RDBMS realm and administration server+managed server setup in
conjunction, the permissions needed for booting any server (managed or
administration) must be set using fileRealm.
- All other permissions can come for RDBMSRealm.
Hmm, so my final setup became:
1. RDBMSRealm with a caching realm.
2. fileRealm with user "system" and needed ACLs+permissions at boot time.
Be sure not to define the information from the fileRealm.properties in your
RDBMSRealm. It will not work.
While you can define all your permissions in a fileRealm and use for
booting any servers in a similar setup, you cannot define all your
permissions in a RDBMSRealm and none in a fileRealm :-(
Regards, Per -
Having trouble starting the J2EE Server... for hours and hours...
Hi:
I am having problem starting the J2EE Server.
I have looked through this page where lots of people had similar problem:
http://forum.java.sun.com/thread.jsp?forum=136&thread=468079
but the solutions provided there could not solve my problem...
My problem, specifically, is that when I try to start the sever, I get:
com.sun.enterprise.admin.servermgmt.DomainException: ...
CLI156 Could not start the domain domain1.
I am using Windows XP Professional on IBM ThinkPad X30.
Does anyone have some idea how to solve the problem?
Thanx!bsankararao,
Thanks for the quick response. I am currently using the latest IE6.0 XPXP2 version and yes I doe have a successful start of the domain1 process. Here is the startup log for verification:
[#|2004-02-02T15:03:04.765-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-02T15:03:12.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-02T15:03:12.436-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-02T15:03:14.649-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-02T15:03:15.470-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-02T15:03:15.491-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-02T15:03:15.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-02T15:03:32.084-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-02T15:03:34.338-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-02T15:03:34.938-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-02T15:03:36.391-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-02T15:03:36.421-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|autoDeployment status dir missing, creating a new one|#]
[#|2004-02-02T15:03:36.451-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.471-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.481-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:38.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:38.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
[#|2004-02-02T15:03:48.818-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:49.549-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 12728 msec, Total EJB Compiler Module Time: 10775 msec, Portion spent EJB Compiling: 84%
Breakdown of EJBC Module Time: Total Time for EJBC: 10775 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 10605 msec (98%), JAX-RPC Generation: 20 msec (0%),
|#]
[#|2004-02-02T15:03:49.750-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-02-02T15:03:50.571-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:51.292-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.029-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.309-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5688 msec, Total EJB Compiler Module Time: 4737 msec, Portion spent EJB Compiling: 83%
Breakdown of EJBC Module Time: Total Time for EJBC: 4737 msec, CMP Generation: 2674 msec (56%), Java Compilation: 1933 msec (40%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-02-02T15:03:56.339-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-02-02T15:03:56.810-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-02T15:03:57.210-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-02T15:03:57.461-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-02T15:03:57.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-02T15:03:57.721-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-02T15:03:59.924-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-02T15:04:00.315-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.355-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.936-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.946-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.966-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:00.986-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:01.266-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075755841276|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-02T15:18:13.512-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T15:18:13.522-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T15:18:39.119-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T15:18:39.119-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:27:40.443-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:41.174-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:27:49.076-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:49.076-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:31:57.022-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:31:57.022-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:32:08.869-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:32:08.869-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T20:00:22.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T20:00:22.424-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-03T08:30:22.556-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T08:30:23.808-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T08:30:23.998-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T08:30:26.422-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T08:30:27.143-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T08:30:27.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T08:30:27.253-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T08:30:31.509-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T08:30:33.462-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T08:30:33.963-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T08:30:34.914-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T08:30:36.036-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T08:30:37.027-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T08:30:37.428-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T08:30:37.618-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T08:30:37.638-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T08:30:37.798-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T08:30:39.901-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T08:30:40.202-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.242-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.402-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.412-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.442-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.452-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.732-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075818640752|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T08:48:32.383-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\domains\domain1\autodeploy\hello.war ] for autodeployment.|#]
[#|2004-02-03T08:48:33.785-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello]|#]
[#|2004-02-03T08:48:33.835-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello]|#]
[#|2004-02-03T08:48:34.606-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 1862 msec, Total EJB Compiler Module Time: 50 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 50 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (20%),
|#]
[#|2004-02-03T08:48:34.807-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello]|#]
[#|2004-02-03T08:48:35.007-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T08:48:36.719-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-03T08:48:36.729-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\domains\domain1\autodeploy\hello.war.|#]
[#|2004-02-03T14:53:47.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T14:53:48.718-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T14:53:48.929-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T14:53:51.222-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T14:53:52.003-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T14:53:52.033-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T14:53:52.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T14:53:56.449-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T14:53:58.492-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T14:53:58.983-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T14:53:59.985-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T14:54:01.206-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T14:54:02.188-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T14:54:02.678-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T14:54:02.899-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T14:54:02.919-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T14:54:02.939-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T14:54:03.119-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T14:54:05.563-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T14:54:05.883-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:05.943-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:06.083-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.093-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.123-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.133-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075841646434|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T23:32:20.272-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T23:32:22.004-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T23:32:22.234-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T23:32:24.608-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T23:32:25.629-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T23:32:25.659-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T23:32:25.689-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T23:32:31.237-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T23:32:33.781-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T23:32:34.332-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T23:32:35.453-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T23:32:37.156-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T23:32:38.317-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T23:32:38.948-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T23:32:39.179-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T23:32:39.199-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T23:32:39.229-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T23:32:39.439-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T23:32:42.343-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T23:32:42.724-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.764-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.944-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.954-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.994-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.014-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.315-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075872763335|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-04T08:31:44.681-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02 -
Trouble starting Managed Server
I'm having trouble starting a managed server.
I have 'myomain' running on 7001, and attempt to start 'examples' on 7006
as a managed server pointing to 7001 as the admin server.
I've modified a copy of startWebLogic.sh to include the following -D parameters:
weblogic.management.server=127.0.0.1:7001
weblogic.management.password = <password for mydomain>
weblogic.management.username=system
When run, the 7001 access.log contains the following entry, so I know the reqest
is getting to the mydomain server:
127.0.0.1 - - [13/Nov/2000:14:06:13 -0700] "GET /Bootstrap HTTP/1.1" 200 125docs60/notes/issues.html
The terminal session that is attempting to start 'examples' barfs with the following:
<Mon Nov 13 14:12:25 MST 2000> <Error> <Configuration Management> <Error connecting to admin server to boo
tstrap via URL: http://127.0.0.1:7001/Bootstrap, user: system
java.lang.ClassCastException: java.lang.String
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:756)
at weblogic.management.Admin.initialize(Admin.java:275)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
Full Text is attached.
I noticed the post on 27-Oct by Sanjeev Chopra related to a known bug on this subject, but my
error text is quite different and I wasn't sure if this is the same problem.
Please advise.
Thanks
joeI'm having trouble starting a managed server.
I have 'myomain' running on 7001, and attempt to start 'examples' on 7006
as a managed server pointing to 7001 as the admin server.
I've modified a copy of startWebLogic.sh to include the following -D parameters:
weblogic.management.server=127.0.0.1:7001
weblogic.management.password = <password for mydomain>
weblogic.management.username=system
When run, the 7001 access.log contains the following entry, so I know the reqest
is getting to the mydomain server:
127.0.0.1 - - [13/Nov/2000:14:06:13 -0700] "GET /Bootstrap HTTP/1.1" 200 125docs60/notes/issues.html
The terminal session that is attempting to start 'examples' barfs with the following:
<Mon Nov 13 14:12:25 MST 2000> <Error> <Configuration Management> <Error connecting to admin server to boo
tstrap via URL: http://127.0.0.1:7001/Bootstrap, user: system
java.lang.ClassCastException: java.lang.String
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:756)
at weblogic.management.Admin.initialize(Admin.java:275)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
Full Text is attached.
I noticed the post on 27-Oct by Sanjeev Chopra related to a known bug on this subject, but my
error text is quite different and I wasn't sure if this is the same problem.
Please advise.
Thanks
joe -
SQL Server Service won't start on SQL Server 2008
Hi everyone,
I'm having trouble starting SQL Server service after stopping and starting the service. Before this happened, I created a Stored Procedure for marking all tables at once along with a maintenance plan for differential backup on all my databases based on the
recommendation from this link, http://msdn.microsoft.com/en-us/library/ms253070.aspx.
When I realized that the differential backup failed with some databases displaying (Restoring...) post-fix to the database name, I decided to stop SQL Server service and start it up. That is when I won't be able to start the service again.
Is there a fix for starting the SQL Server service? Any help is very much appreciated.
Additional information:
- With administrator permission granted.
- Service Pack 1 for SQL Server 2008 installed.
- Using default database instance.
- Tried C:\Program Files\Microsoft SQL Server\MSSQL.....\Binn>net start MSSQLSERVER /T3608 ( return msg: System error 5 has occurred. Access is denied.
- When I start SQL Server service, I keep getting this dialog msg:
"Windowns could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1814."
The event log does not explain or provide any hint on how to fix the problem.
- Log msg:
2010-07-22 10:30:25.09 Server (c) 2005 Microsoft Corporation.
2010-07-22 10:30:25.09 Server All rights reserved.
2010-07-22 10:30:25.09 Server Server process ID is 6076.
2010-07-22 10:30:25.10 Server Authentication mode is MIXED.
2010-07-22 10:30:25.10 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2010-07-22 10:30:25.11 Server This instance of SQL Server last reported using a process ID of 5708 at 7/21/2010 3:27:01 PM (local) 7/21/2010 10:27:01 PM (UTC). This is an informational message only; no user action is required.
2010-07-22 10:30:25.11 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2010-07-22 10:30:25.14 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-07-22 10:30:25.14 Server Detected 4 CPUs. This is an informational message; no user action is required.
2010-07-22 10:30:25.23 Server Using locked pages for buffer pool.
2010-07-22 10:30:25.43 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2010-07-22 10:30:25.73 Server Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2010-07-22 10:30:25.81 spid7s Starting up database 'master'.
2010-07-22 10:30:26.14 spid7s CHECKDB for database 'master' finished without errors on 2010-07-19 21:15:02.823 (local time). This is an informational message only; no user action is required.
2010-07-22 10:30:26.18 spid7s Resource governor reconfiguration succeeded.
2010-07-22 10:30:26.18 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.18 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.19 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2010-07-22 10:30:26.28 spid7s SQL Trace ID 1 was started by login "sa".
2010-07-22 10:30:26.29 spid7s Starting up database 'mssqlsystemresource'.
2010-07-22 10:30:26.31 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2010-07-22 10:30:26.43 spid10s Starting up database 'model'.
2010-07-22 10:30:26.43 spid7s Server name is 'XXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
2010-07-22 10:30:26.47 spid10s The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2010-07-22 10:30:26.47 spid10s Error: 927, Severity: 14, State: 2.
2010-07-22 10:30:26.47 spid10s Database 'model' cannot be opened. It is in the middle of a restore.
2010-07-22 10:30:26.59 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in
the event log that may indicate why the tempdb files could not be initialized.
2010-07-22 10:30:26.59 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.Hello,
Could you please copy the model.mdf and modellog.ldf from
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\Templates
To
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
Rebuilding the system databases you will lose lose logins, jobs, SSIS packages. You may have to restore or attach user databases.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Having trouble with the HTTP Server vi
I'm having trouble using the HTTP Server program to view the front panel of my program remotely.
When I initially start the server program everything works fine. However, the program hasn't been able to run for more than one or two days at a time before it freezes and won't display the front panel.
The only clue I can see as to what is going on is that there are always several pending connections and active connections listed in the HTTP Server front panel when it isn't working properly. Stopping the server and starting it again fixes the problem temporarily and it works fine for another day or two.
Any ideas about what might be causing this problem?Which OS do you have? Win95 and 98 are not very stable systems, so you might want to try with WinNT. You should be able to run the HTTP server for few days on WinNT.
Since restarting the server solves the problem, maybe you can try to programmatically restart the server every 24 hours. This can be done within LabVIEW with the HTTP Server Control.vi. Be aware that this will close all the connections, not just the pending ones.
Does this problem happen every couple of days, or are you able to run it sometimes for a longer period time? Is it related to how many clients request control?
Also, take a look at the Access Log, and see if you notice anything strange at the time when the problem happens.
I hope this helps.
Have a pleasant day.
Zvezdana S.
Nat
ional Instruments -
I have Oracle 10.2 installed on Mac OS X 10.5. The database was working at one point (I didn't use it much) but now I'm having trouble starting it.
First I log in as the Oracle user:
su - oracle
Then I start the listener and it appears to start up correctly:
localhost:~ oracle$ lsnrctl start
LSNRCTL for MacOS X Server: Version 10.2.0.4.0 - Production on 24-SEP-2009 11:17:01
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Starting /Users/oracle/oracle/product/10.2.0_db_1/bin/tnslsnr: please wait...
TNSLSNR for MacOS X Server: Version 10.2.0.4.0 - Production
System parameter file is /Users/oracle/oracle/product/10.2.0_db_1/network/admin/listener.ora
Log messages written to /Users/oracle/oracle/product/10.2.0_db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for MacOS X Server: Version 10.2.0.4.0 - Production
Start Date 24-SEP-2009 11:17:01
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /Users/oracle/oracle/product/10.2.0_db_1/network/admin/listener.ora
Listener Log File /Users/oracle/oracle/product/10.2.0_db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Then I log into SQL Plus and try to start the database and it fails with the message shown:
localhost:~ oracle$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Thu Sep 24 11:17:15 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/Users/oracle/oracle/product/10.2.0_db_1/dbs/initXE.ora'
The SID of my database is ORCL, not XE. I'm not sure where the XE in "initXE.ora" comes from, and I'm not sure if that's part of the problem. When I look in the /Users/oracle/oracle/product/10.2.0_db_1/dbs/ directory this is what is there:
localhost:~ oracle$ cd /Users/oracle/oracle/product/10.2.0_db_1/dbs/
localhost:dbs oracle$ ls
alert_ORCL.log init.ora lkORCL spfileorcl.ora
hc_orcl.dat initdw.ora orapworcl sqlnet.log
localhost:dbs oracle$
So apparently there is no initXE.ora file.
h1. My Question:
Why is it looking for initXE.ora, and how can I fix it? Like I said I had this database working before (SID or ORCL) so I don't know what changed.
h3. Thank you!!!!!Follow these steps:
startup pfile='<pfile location of initORCL.ora>';
then logging as SYSDBA
create spfile from pfile;
Check the spfile in $ORACLE_HOME/dbs/ directory.
then shutdown the database and startup the database.
Don't forget to export the ORACLE_HOME,ORACLE_SID,PATH environment variables.
Regards
Asif Kabir -
Failed to start remote debug server
I'm having trouble getting xcode to play nicely with my provisioned iPhone under beta 7. When I change my default target to "Device Debug" and do a clean build the following occurs:
1) The code compiles and links
2) The application is installed on the iPhone
3) XCode tries to start the remote debug server and fails with the following message:
Failed to start remote debug server for test.app on Keith's iPhone
The application does get installed on my phone, but I am unable to use xcode to view the logs and perform other debugging related activities.
Has anyone seen this before and know how to fix it?
Thank you,
-KeithThanks for the reply, but it didn't seem to help. Maybe I didn't do it right. I did:
- Delete app from iPhone
- Clean project
- Close project
- Xcode->Empty Caches
- Close Xcode
- Disconnect and reconnect device (via iTunes eject)
- Open project
- Build & Go
Still the same 'please disconnect and reconnect the device' when starting debugserver
I am able to run the app just fine, but can't use Instruments or the debugger -
[solved] how to start the rabbitmq-server with systemctl
I got the rabbitmq package from https://aur.archlinux.org/packages/rabbitmq/. Upon installing with 'pacman -U', I got the message
==> WARNING:
==> This systemd unit executes rabbitmq as rabbitmq user. This is *DIFFERENT*
==> from the legacy sysvinit scripts included in the package that
==> default on using the "root" user. DO NOT MIX usage of this systemd unit
==> with rc.d initscripts, or permission problems may arise.
==> To fix those, use the following command (as root):
chown -R rabbitmq.rabbitmq /var/lib/rabbitmq
==> DO NOT DELETE anything manually, that may make your rabbitmq install
==> unusable, until deletion of everything under /var/lib/rabbitmq
I did the 'chown' thing as advised, but I'm not sure if there is something more I should be doing (or not doing).
I can start the server with
sudo rabbitmq-server
and then in another terminal I can do
sudo /usr/sbin/rabbitmqctl status
and the output seems to show everything working.
The trouble starts if instead of directly running rabbit-server, I do
sudo systemctl enable rabbitmq
sudo systemctl start rabbitmq
It seems to start fine and then I get (when I do systemctl status rabbitmq)
rabbitmq.service - RabbitMQ Messaging Server
Loaded: loaded (/usr/lib/systemd/system/rabbitmq.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2014-12-29 02:03:25 GMT; 4s ago
Process: 25657 ExecStop=/usr/bin/rabbitmqctl stop (code=exited, status=2)
Process: 25549 ExecStart=/usr/bin/rabbitmq-server (code=exited, status=1/FAILURE)
Main PID: 25549 (code=exited, status=1/FAILURE)
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: * epmd reports: node 'rabbit' not running at all
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: no other nodes on brunnhilde
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: * suggestion: start the node
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: current node details:
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: - node name: 'rabbitmqctl-25657@brunnhilde'
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: - home dir: /var/lib/rabbitmq
Dec 29 02:03:25 brunnhilde rabbitmq[25657]: - cookie hash: 59JWXfWlAKuxru4vaTbvBQ==
Dec 29 02:03:25 brunnhilde systemd[1]: rabbitmq.service: control process exited, code=exited status=2
Dec 29 02:03:25 brunnhilde systemd[1]: Unit rabbitmq.service entered failed state.
Dec 29 02:03:25 brunnhilde systemd[1]: rabbitmq.service failed.
I presume this failure has something to do with the systemd warning that I got when installing, but I am not really sure what to do.
Has anyone got rabbitmq server working using systemctl?
Last edited by mjandrews (2014-12-29 20:25:13)I seem to have fixed it now.
I changed /etc/rabbitmq/rabbitmq-env.conf from
NODENAME=rabbit
NODE_IP_ADDRESS=0.0.0.0
NODE_PORT=5672
LOG_BASE=/var/log/rabbitmq
MNESIA_BASE=/var/lib/rabbitmq/mnesia
to
NODENAME=rabbit
NODE_IP_ADDRESS=127.0.0.1
NODE_PORT=5672
HOME=/var/lib/rabbitmq
LOG_BASE=/var/log/rabbitmq
MNESIA_BASE=/var/lib/rabbitmq/mnesia
and that seems to have done the trick. -
JoltConnectionPool can not start in weblogic server
Hi
I am trying to run the sample Tuxedo provided application which uses Servlets or Ejb.
Now the Tuxedo Server has been configured and running properly.
I have WebLogic Server installed and had created the JoltSessionPool with name "MAJoltConnectionPool" and had also defined the StartupClass & ShutdonClass.
While defining the JoltSessionPool i had given min services as 1 and max services as 5 and others as default,
and the JoltSessionPool's target is a weblogic managed server which named ct2.
Then i tryed to start the ct2 server on command line such as:
startManagedWebLogic.cmd ct2 http://localhost:7001
I got an error in starting "MAJoltConnectionPool" but the server ct2 is starting normally.
Anyone who can help me to find out the reason? Thanks a lot.
The Command Line window shown following in the Log:
Failed to invoke startup class "MAJoltPoolStart", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool :
Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
The Entire Trace from the Log file is:
####<Mar 16, 2011 11:58:35 AM CST> <Notice> <Log Management> <HXU49> <ct2> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915024> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<Mar 16, 2011 11:58:35 AM CST> <Info> <Diagnostics> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915070> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
####<Mar 16, 2011 11:58:35 AM CST> <Info> <WebLogicServer> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915078> <BEA-000256> <Invoking bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(null)>
####<Mar 16, 2011 11:58:35 AM CST> <Critical> <WebLogicServer> <HXU49> <ct2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1300247915239> <BEA-000286> <Failed to invoke startup class "MAJoltPoolStart", java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool : Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
java.lang.Exception: Errors in starting the following connection pools :
com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool : Access to sensitive attribute in clear text is not allowed due to the setting of ClearTextCredentialAccessEnabled attribute in SecurityConfigurationMBean. Attr: UserPassword, MBean name: com.bea:Name=MAJoltConnectionPool,Type=JoltConnectionPool
at bea.jolt.pool.servlet.weblogic.impl.PoolManagerStartUpJMX.startup(PoolManagerStartUpJMX.java:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.main(PoolManagerStartUp.java:38)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:186)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppAdminState(ClassDeploymentManager.java:162)
at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
>
####<Mar 16, 2011 11:58:35 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247915288> <BEA-000365> <Server state changed to ADMIN>
####<Mar 16, 2011 11:58:35 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247915313> <BEA-000365> <Server state changed to RESUMING>
####<Mar 16, 2011 11:58:36 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247916769> <BEA-000365> <Server state changed to RUNNING>
####<Mar 16, 2011 11:58:36 AM CST> <Notice> <WebLogicServer> <HXU49> <ct2> <main> <<WLS Kernel>> <> <> <1300247916770> <BEA-000360> <Server started in RUNNING mode>
With Regards
HanHi
To resolve this problem , you have 2 solutions:
- modify the config.xml file to add in the tag <security-configuration> the following line :
<clear-text-credential-access-enabled>true</clear-text-credential-access-enabled>
or
- check the checkbox "Clear Text Credential Access Enabled" in the settings for the domain / security / general / advanced
restart the weblogic server to activate this change if necessary (Normaly, no restarts are necessary with weblogic server v10.3.5.0)
Hope this reponse help you (if it's not too late ;-) )
Laurent. -
Facing Problem in Starting Weblogic Managed Server
Hi,
While starting a managed server through Weblogic Console it is giving "nodemanager is not running" related error. I am not sure what is happening here. It was working fine earlier.
Thanks
PawanHi,
Please check wheather node manager is running inside the server. Please check the nodemanager listen port in nodemanager.properties file and issue below command from your server.
netstat -a |grep "port"
Regards,
Kishore -
Error while starting Soa Managed server on weblogic11g
Hi All,
I am facing one issue while starting the soa managed server on weblogic11g.
it gives error like :
"<Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
What can be done to get over this issue & start the soa server ???
Thanks & Regards,
NupurHi,
Full stack trace of log is :
<Apr 12, 2011 7:04:19 AM IST> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
at jrockit.ext.epoll.EPoll.epollCtl0(Native Method)
at jrockit.ext.epoll.EPoll.epollEnableOneshot(EPoll.java:87)
at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:84)
at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:302)
at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
Truncated. see log file for complete stacktrace
>
<Apr 12, 2011 7:04:41 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'soademoDatabase1' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: ORA-28001: the password has expired
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:479)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:173)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:244)
Truncated. see log file for complete stacktrace
Apr 12, 2011 7:05:49 AM IST> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
at jrockit.ext.epoll.EPoll.epollCtl0(Native Method)
at jrockit.ext.epoll.EPoll.epollEnableOneshot(EPoll.java:87)
at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:84)
at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:302)
at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
Truncated. see log file for complete stacktrace
<Apr 12, 2011 7:05:53 AM IST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-26024> <Registration of driver Email-Driver did not complete; will retry periodically until messaging server responds.>
<Apr 12, 2011 7:05:56 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'FtpAdapter' due to error weblogic.application.ModuleException: weblogic.connector.exception.RAException: Jndi Name is null or empty..
weblogic.application.ModuleException: weblogic.connector.exception.RAException: Jndi Name is null or empty.
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:224)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
No this is not a clustered environment.
yeah but under domains there are two domains we have created.
i.e. domains/ domain1 domain2
both are having soa servers as managed server.
in one domain soa is up but in domain2 it is not getting up causing above errors while starting.
FYI : It is causing problem now only.. before this , soa server on both the server have been up & running simultaneously.
Regards,
Nupur -
Error in starting the BPEL Server
Hi All ,
I am new to the BPEL technology and facing problem when I try to start BPEL Server through the "Start BPEL Server" menu.
This is the error that I get after a few minutes :
OraBPEL "default" BPEL domain loaded.
<2007-12-24 18:13:20,317> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700
<2007-12-24 18:13:35,868> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://DWUS1B018:9700/orabpel
<2007-12-24 18:13:51,404> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://10.10.10.10:9700/orabpel
<2007-12-24 18:14:07,205> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700/orabpel
<2007-12-24 18:14:22,741> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://localhost:9700/orabpel
<2007-12-24 18:14:22,741> <ERROR> <collaxa> <ProcessJob::execute> Attempt (1/15)
... failed to connect ... retrying in 5 seconds ...
<2007-12-24 18:15:01,415> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700
<2007-12-24 18:15:57,390> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://10.10.10.10:9700/orabpel
<2007-12-24 18:16:27,133> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700/orabpel
<2007-12-24 18:17:01,908> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://localhost:9700/orabpel
Earlier in the begining it reported that the network name and the localhost name are different so I installed a loopback adapter also. Now this problem is no more there but still the server does not boots and when I click on the BPEL Console then I get this message
"Network Error (dns_unresolved_hostname)
Your requested host "dwus1b018.msc.com" could not be resolved by DNS.
For assistance, contact your network support team."
Please guys help me out , I am badly stuck..........Hi ,
I am badly stuck now . I have the system RAM now 1 GB and when I start the BPEM server then this is the snapshot of netstat command that I get
H:\>netstat
Active Connections
Proto Local Address Foreign Address State
TCP DWUS1B018:2083 dwus1b018.hsc.com:9700 ESTABLISHED
TCP DWUS1B018:9700 dwus1b018.hsc.com:2083 ESTABLISHED
TCP DWUS1B018:1077 DWUS1B018.hsc.com:2084 ESTABLISHED
TCP DWUS1B018:1531 localhost:2075 ESTABLISHED
TCP DWUS1B018:2072 localhost:2073 ESTABLISHED
TCP DWUS1B018:2073 localhost:2072 ESTABLISHED
TCP DWUS1B018:2075 localhost:1531 ESTABLISHED
TCP DWUS1B018:1353 ggns1wfs01.hsc.com:microsoft-ds ESTABLISHED
TCP DWUS1B018:2060 ggnmail01.hsc.com:https CLOSE_WAIT
TCP DWUS1B018:2062 ggns1wis02.hsc.com:1026 TIME_WAIT
TCP DWUS1B018:2077 ggns1wis02.hsc.com:microsoft-ds TIME_WAIT
TCP DWUS1B018:2084 205.177.95.136:ftp ESTABLISHED
TCP DWUS1B018:2086 205.177.95.136:ftp SYN_SENT
*********************But soon there is error in the BPEL prompt :****************
<2007-12-31 12:11:35,304> <INFO> <default.collaxa.cube.engine> <CubeEngine::init>
OraBPEL "default" BPEL domain loaded.
<2007-12-31 12:11:57,317> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.hsc.com:9700
2007-12-31 12:12:12.933 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}userObject to javax.xml.soap.SO
APElement userObject. Reason for not creating a custom Java type: use of an unimplemented feature.
2007-12-31 12:12:12.963 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}groupObject to javax.xml.soap.S
OAPElement groupObject. Reason for not creating a custom Java type: use of an unimplemented feature.
2007-12-31 12:12:12.963 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}roleObject to javax.xml.soap.SO
APElement roleObject. Reason for not creating a custom Java type: use of an unimplemented feature.
2007-12-31 12:12:12.979 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}userObjects to javax.xml.soap.S
OAPElement userObjects. Reason for not creating a custom Java type: use of an unimplemented feature.
**************AND then the prompt hangs at this place :****************************
0 processes have been loaded for BPEL domain "default".
<2007-12-31 12:12:34,752> <INFO> <collaxa> <ServerManager::loadProcesses> Done loading processes for all domains
<2007-12-31 12:12:38,021> <INFO> <default.collaxa.cube.compiler> validating "C:\product\10.1.3.1\OraBPEL_1\bpel\domains\default\tmp\.bp
el_TaskManager_1.0_63ee83a3d1166eef2f9e56a17e1de896.tmp\TaskManager.bpel" ...
<2007-12-31 12:12:38,099> <INFO> <default.collaxa.cube.compiler> validating "C:\product\10.1.3.1\OraBPEL_1\bpel\domains\default\tmp\.bp
el_TaskActionHandler_1.0_5edb841c8a9e176e18a0fe3ad7114fb7.tmp\TaskActionHandler.bpel" ...
<2007-12-31 12:12:50,635> <INFO> <default.collaxa.cube.engine.deployment> <CubeProcessFactory::generateProcessClass>
Process "TaskManager" (revision "1.0") successfully compiled.
<2007-12-31 12:12:51,283> <INFO> <default.collaxa.cube.engine.deployment> <CubeProcessFactory::generateProcessClass>
Process "TaskActionHandler" (revision "1.0") successfully compiled.
<2007-12-31 12:12:51,314> <INFO> <default.collaxa.cube.engine.deployment> Process "TaskManager" (revision "1.0") successfully loaded.
07/12/31 12:12:51 @#############@##@ CLOB = oracle.lite.poljdbc.CLOB@8433bb
<2007-12-31 12:12:51,776> <INFO> <default.collaxa.cube.engine.deployment> Process "TaskActionHandler" (revision "1.0") successfully loa
ded.
07/12/31 12:12:51 @#############@##@ CLOB = oracle.lite.poljdbc.CLOB@6fdb4b
************************At this if I run the BPEL Prompt then this message I get at the explorer Window :************************
Network Error (dns_unresolved_hostname)
Your requested host "dwus1b018.msc.com" could not be resolved by DNS. For assistance, contact your network support team.
*********************At this moment the Netstat command gives this output *********
H:\>netstat
Active Connections
Proto Local Address Foreign Address State
TCP DWUS1B018:2083 dwus1b018.hsc.com:9700 CLOSE_WAIT
TCP DWUS1B018:2089 dwus1b018.hsc.com:9700 CLOSE_WAIT
TCP DWUS1B018:9700 dwus1b018.hsc.com:2083 FIN_WAIT_2
TCP DWUS1B018:9700 dwus1b018.hsc.com:2089 FIN_WAIT_2
TCP DWUS1B018:1531 localhost:2075 TIME_WAIT
TCP DWUS1B018:1531 localhost:2095 TIME_WAIT
TCP DWUS1B018:2072 localhost:2073 ESTABLISHED
TCP DWUS1B018:2073 localhost:2072 ESTABLISHED
TCP DWUS1B018:2093 localhost:9700 CLOSE_WAIT
TCP DWUS1B018:2096 localhost:1531 TIME_WAIT
TCP DWUS1B018:9700 localhost:2093 FIN_WAIT_2
*********Please can anybody help me figure out this error****************
Maybe you are looking for
-
I have tried using the set in system of trying to update an app and being prompted to agree, but every single time Apple's gay system keeps telling me that my session has timed out and I should try again. I have tried multiple times to have it sent
-
I bought a video and it says i have no videos to watch on my laptop
hi i bought some videos from i tunes and it was from i tunes i logg on throught my computer and it says i have no videos but when i logg on with my phone it says there still on my account i wanna watch it through my computer thou how can i fix this
-
Moving Sync from one computer to another.
Hi Folks! I have been using an old Mac Mini to sync my iPhone 3G to and want to move it to an older G5. When I first plugged the iPhone into the G5 I got the expected warning about loosing all the data currently on the phone. I can, and have, moved m
-
Formatting Failed- Device not Supported
Hi. I'm new to DVDSP and hope this isn't a stupid question. (No hits when I searched for the same problem.) I have a project that started as FCS HD. I sent it to Compressor and created a QT H.264.mov file that is 5.96GB. Built a DVDSP project that en
-
Hi, For OPEN DATASET statement, I get error OPEN 004 error in UCCHECK. Can you please let me know what addition should be used to solve this problem? ENCODING DEFAULT ?? ENCODING UTF-8 ?? ENCODING NON_UNICODE ?? As per SAP Help, I have added EN