JPDA and J2EE server
Hi,
The document says:
The Java Platform Debugger Architecture (JPDA) consists of three interfaces designed for use by debuggers in development environments for desktop systems.
So, it is for desktop systems only. Why it can not be used in J2EE environment?
Any information would be appreciated. Thanks in advance.
In a servlet i use the below code:
response.setHeader("Arun","Prasath");
RequestDispatcher rd=request.getRequestDispatcher("index.jsp");
rd.forward(request,response);
the above header i set in the servlet,then i use RequestDispatcher
to forward it to a jsp.There i give the following code to retrieve the header value.
ie,In index.jsp i give the below code:
String ss=(String)request.getHeader("Arun");
out.println(ss);
The result is null when i print the String ss,instead of prasath.
If u find the answer or where is the problem reply me,please
Similar Messages
-
What is their difference betwwen Sun ONE Application Server and J2EE serv
Sun ONE Application Server is Sun implementation of J2EE server.
But it seems even no Sun ONE Application Server, use J2EE SDK command
j2ee -verbose
we still can launch an Application Server that support EJB, JSP....
what is their difference betwwen Sun ONE Application Server and J2EE server provided by J2EE SDK ?
Thanks,Sun ONE generally refers to the Sun ONE Application Server version 7.x. This is a J2EE 1.3 compliant application server from Sun. Sun also released a Reference Implementation version (RI) as a requirement of the J2ee 1.3 spec. This is the J2EE server you are refering too. The Sun ONE Application Server 7 is a more robust production ready App Server.
Going forward, Sun combined the 2 seperate groups to include just 1 release. The J2EE 1.4 Reference Implementation is the Sun Java System Application Server Platform Edition version 8. SJS AS 8 PE is both free and production ready. Other version will include High Availability, Managing and Monitoring features.
-Jeff -
Error while starting NW server and j2ee server is getting stopped.
Hi,
I am working in NW04s. It contains ABAP sp5 and java sp9 versions. The server was working find till ten days back. After the gap of ten days, when i started to work on this SAP system, i was not able to start the j2ee server. During the startup of the server itself, j2ee server is getting stopped and dispatcher also. Following is the error bunch I got in trace. If any one has any idea about this, please reply this soon.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=garden SYSNR=00 GWHOST=garden GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR connection to partner '15.70.176.191:sapgw00' broken
TIME Mon Nov 13 12:45:30 2006
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -6
MODULE nixxi.cpp
LINE 4207
DETAIL NiIRead
SYSTEM CALL recv
ERRNO 10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER 4
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
#1.5#000E7FFD8B5D001D00000011000008540004221BAAB8047C#1163402130490#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_54##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#> ceException: Connect to SAP gateway failed
> Connect_PM TYPE=A ASHOST=garden SYSNR=00
> GWHOST=garden GWSERV=sapgw00 PCS=1
>
> LOCATION CPIC (TCP/IP) on local host with Unicode
> ERROR connection to partner
> '15.70.176.191:sapgw00' broken
You can ping this machine from your portal-nodes and you can connect to the port "sapgw00" (should be 3300) ?
> ##0#0#Fatal#1#/System/Server#Plain###Critical
> shutdown was invoked. Reason is: Core service
> com.sap.security.core.ume.service failed. J2EE Engine
> cannot be started.#
This is the reason why your j2ee-server stops - the portal can't connect to the ume. What did you configured as the ume - the portal database, a ldap-server or a r3-system ?
Regards
Norman -
Need help:Urgent:MS SQL Server and J2EE Server
Hello,
i am developing simple bean managed persistence bean. i want to know how could i use microsoft SQL Server as my database with ejb's in J2EE. i don't want to use cloudscape rather i want to connect through jdbc bridge with sql server. can any body help me out ?
i have developed DSN for my database with the name of DsnProduct and user name for DB is guest and password is guest123.
so do i have to change configuration is my J2EE server . or put some additional code. so far i have added the following line in my implementation class
private String dbName= "java:comp/env/jdbc/ProductDB";
DataSource ds = (DataSource) ic.lookup(dbName);
con = ds.getConnection("guest","guest123");
moreover in server configuration i have added driver
sun.jdbc.odbc.JdbcOdbcDriver
and also provide the following JNDI Name
jdbc/ProductDB
and
it's url is
jdbc:odbc:DsnProduct
i am thankfull for your support.
[email protected]hi llturro,
Thanks for answering my question. I have tried out what you suggested, but I still can't fix my problem. The following are the messages that display when I try to run my servlet. It seems that the DataSource, Connection and Statement are ok, however when it comes to the ResultSet the error message appear. What's wrong with my ResultSet coding ?
ResultSet rs = stat.executeQuery("SELECT ISBN FROM BOOKSINFO WHERE ISBN='"+primarykey+"'");
setEntityContext Method
Find by primary key
DataSource OK
Connection OK
Primary Key = 013-00-675721-9
Statement OK
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.lang.NullPointerException
<<no stack trace available>> -
CPA Cache and J2EE server issues
Hi Experts,
I am having a File to File scenario where the sender channel picks up csv files ( around 3MB each). Once I finished the configuration of the scenario, the J2EE server started to restart continuously five times and stops with a out of memory error.
After going through the defaultTrace.trc file in logviewer, this is the first error that I could see after starting the J2EE server.
CPA Cache not updated with directory data, due to: Couldn't open Directory URL (http://pi-dev:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.pid.pi-dev), due to: HTTP 503: Not Ready
Source Name: com.sap.aii.service.cpa.impl.cache.CacheManager.I checked the RFC destination of INTEGRATION_DIRECTORY_HMI and also checked if PIDIRUSER and PIAFUSER are locked or not. But they are not locked.
After the above error, the errors just build up probably because of the adapter framework not firing up. One of the error is:
Failed to lookup object from JNDI for name localejbs/AFWListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at localejbs, the whole lookup name is localejbs/AFWListener.
Source: com.sap.aii.af.ra.ms.runtime.Resources
I also increased the max thread count in the Application Thread Manager to 250 in the Config tool. I kept the heap sizes as posted above.
Any help will be greatly appreciated.
RegardsHey,
>the J2EE server started to restart continuously five times and stops with a out of memory error.
Strange, Can you test with less than 1 MB file and let us know the status, Is SAP PI & ECC are installed in the same Server.
Cheers
Agasthuri -
I am not shure, I thought that you don't hav to have a j2ee server installed for every client who wants to send and receive messages with the Help of JMS, but in the JMS tutorial stands on page that 57 that "JMS client programms can communilate with each other when they are running on different systems in a network. These systems must be visible to each other by name and must both running the j2ee server"
I wantet to make an Applet wich is a JMS Client, who communikates with the server, is this possible? And if yes, does every person who wants to use the applet have to have installed the j2ee server?in this case, j2eeserver is used for the jndi lookup, not the cloudscape, jsp, webserver, and all that other crup.
there is no reason not to connect to a remote jndi listener, rather than going thru a local listener which passes you off to the remote one.
i have avoided jndi recently, and can help in websphere MQ, otherwise i am not sure.
i would like also like to know. -
BACK button difference between Weblogic and J2EE server
Hi Everyone,
I have a J2EE application implemented mainly with JSP and EJB, which can run on
both J2EE and Weblogic Servers seperately. When running on either of them, the
server acts as both a web and application server.
It is my understanding that it first goes to the cache in the browser when you
try to revisit the previous page (JSP files) by clicking the BACK button in the
browser. If the page is there, it just displays that page from the cache. If not,
it will go to the server to retrive (execute) that page.
When I run my application over J2EE server and try to visit the previous page
by using the BACK button in the browser, it does this way correctly. But when
I run my
application over Weblogic server, it always goes to the server and execute the
JSP file again in the server, rather than simply retriving that page from the
cache. If your JSP file is simply doing data retriving, that is fine. But if it
is doing data inserting, it will insert your data again. This is not good.
I know that the Weblogic server is mainly an application server. But I am not
sure when it acts as a web server,
why it works differently from J2EE which also can acts as both an pplication and
a web server. Does anyone have any ideas or suggestions about this?
Thanks a lot.
-John
I believe that the correct behaviour is to rerun the .jsp page unless the
user specifically sets the header to allow the browser to cache it. That
being said... You should never make a web application that can be broken by
the user hitting "reload" or the browser automatically retrying. An
application like this is very fragile and will probably break in practice.
I suggest that you either make all your pages idempotent or you keep track
through a hidden form field a transaction id and only allow the execution of
any particular transaction once. As far as WebLogic not being a good web
server, I would say that with 6.1 you get most of the management advantages
of using a separate web server and also most of the static file performance
you will find with apache or IIS.
Sam
"John Wang" <[email protected]> wrote in message
news:[email protected]...
>
> Hi Bruno,
>
> Thank you for your prompt reply.
>
> I think I might not explain my problem clearly. My application
> is in developing stage now. So we are just working on a single
> serevr which can acts as both a web and an application server.
> Later we are going to distribute our application into a web and an
application
> seperately.
>
> As you said, it seems that my problem is because the weblogic server is
mainly
> an application server and does not act as a web server very well. So if I
distribute
> my application into both a web and an application servers, it should be
fine,
> since it is ok when I run it over the J2EE server. Is this correct?
>
> In other words, I can say that the J2EE server is configured better in its
role
> as a web server than the weblogic server, isn't it?
>
> In addition, all my JSP files are only dealing with catching
> data from user input and displaying data. Data inserting is done
> by EJB and JavaBeans through the JSP files. Because those JavaBeans in the
JSP
> files, each time when I use the BACK button, it will invoke those
JavaBeans and
> EJBs through the JSP files and do things like inserting in the background.
That
> is what I mean in my previous message.
>
> Thanks.
>
> -John
>
> "Bruno" <[email protected]> wrote:
> >
> >Hi John,
> >
> >You should use a real Web Server on the front side of your application.
> >Weblogic
> >is mainly an application server that has to be used in middle tier. But
> >it's not
> >a good Web Server. Like almost all J2EE application. You should use a
> >separate
> >web server like apache, optimised to serve static file. Furthemore, this
> >approach
> >will enable you to physically separate the two servers for a better
security.
> >Anyway, usually jsp files are dynamic files and are not intended to be
> >totally
> >cached (except in special cases). I think you should just use JSP to
> >display data.
> >If you want to do data inserting, you should use EJB or JavaBeans for
> >that rather
> >than JSP.
> >
> >Hope it helps
> >
> >Regards
> >
> >"John Wang" <[email protected]> wrote:
> >>
> >>Hi Everyone,
> >>
> >>I have a J2EE application implemented mainly with JSP and EJB, which
> >>can run on
> >>both J2EE and Weblogic Servers seperately. When running on either of
> >>them, the
> >>server acts as both a web and application server.
> >>
> >>It is my understanding that it first goes to the cache in the browser
> >>when you
> >>try to revisit the previous page (JSP files) by clicking the BACK button
> >>in the
> >>browser. If the page is there, it just displays that page from the
cache.
> >>If not,
> >>it will go to the server to retrive (execute) that page.
> >>
> >>When I run my application over J2EE server and try to visit the previous
> >>page
> >>by using the BACK button in the browser, it does this way correctly.
> >>But when
> >>I run my
> >>application over Weblogic server, it always goes to the server and
execute
> >>the
> >>JSP file again in the server, rather than simply retriving that page
> >>from the
> >>cache. If your JSP file is simply doing data retriving, that is fine.
> >>But if it
> >>is doing data inserting, it will insert your data again. This is not
> >>good.
> >>
> >>I know that the Weblogic server is mainly an application server. But
> >>I am not
> >>sure when it acts as a web server,
> >>why it works differently from J2EE which also can acts as both an
pplication
> >>and
> >>a web server. Does anyone have any ideas or suggestions about this?
> >>
> >>Thanks a lot.
> >>
> >>-John
> >>
> >
>
-
NWDS and J2ee server Installation
Hi all,
Iam new to web dynpro java .To download the necessary software for it i went to sap downloads page in SCN . i entered into Netweaver main releases. I am not understanding which version to down load . I want only web dynpro java and portal server.my system is having window xp Sp3 OS with 1 GB ram and 50 Gb freespace in hard drive. in some blogs i saw that only 1 gb is necessary for installing but in some it is 2GB min . what are the correct system requirements and
which version of Netweaver is more suitable for installing in my system and right place to download sufficient software .when
i download also it is asking for going sap service market place. is there any other way to download necessary soft ware for practicing webdynpro java and portal server.......
Thanks and Regards
PrasadFor learning Web Dynpro Java and Portal you should download the CE release: http://www.sdn.sap.com/irj/scn/nw-ce-downloads. From there you can download 7.1 and 7.2 trials. I would go for the 7.2 trial ("SAP NetWeaver Composition Environment 7.2 Trial Version").
br,
Tobias -
ABAP and J2EE-Stacks in SAP WEB AS
Hi,
I have two questions about the technical architecture of SAP WebAS, particularly about the ABAP- and J2EE-Server.
Can someone recommend detailed papers/guides (besides help.sap.com)describing:
1) the management of processes and resources in two parts (ABAP and Java)
and
2) The communication mechanisms between J2EE- and ABAP-server.
What are the problems with JCo?
Is there other possibilities to communicate between 2EE- and ABAP-server.(besides JCO), what is the performance in this case compares with JCO?
Thank you!
Peter HnekeHi
please have a look in to this Pdf Doc . might be of soem help to you .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b52456bd-0a01-0010-6d9b-f153bf15a82f
Apart from JCO communication between JAVA and ABAP can also be handled using ESA services .
please have a llok at these blogs
/people/scott.campbell/blog/2005/05/16/the-esa-is-coming-the-esa-is-coming
/people/kevin.liu/blog/2005/10/17/esa-soa-es
/people/harsh.chauhan/blog/2005/08/27/building-esa-and-delivering-it-through-caf
/people/sap.user72/blog/2005/10/28/the-fundamental-problem-solved-by-esa
Hope this helps . pelase do not forget to reward points , if helpful
regards
rajeshkr -
Hi All,
I was installed the Netweaver server on windows 2003 server over sqlserver database. The jlaunch and sqlserver process is taking too much memory.
I would like to decouple the ABAP and J2EE server ......how can i approch this. Is there any way to reduce the memory usage of sqlserver and jlaunch process....?
Is there any solution to that problem...please let me know.
Thanks & Regards,
Sridhar M.I would like to decouple the ABAP and J2EE server
I didnt understand the term decouple over here for ABAP and JAVA instance. But however, if you dont want the JAVA instance to start along with ABAP, you can control it through the profile parameter rdisp/j2ee_start.
More info:
http://help.sap.com/saphelp_sm32/helpdata/en/9a/b9b09d57aba54ca6d010b82b9119e4/content.htm
Hope this helps..
Cheers,
Jazz -
How to install and configure configure IGS for J2EE server 700
Hi,
Please help me in installing and configuring IGS for J2EE server700 as i need it to run Business Graphics for my Web DynPro application. Earlier i had installed J2EE server 640 and i didnt have to do any separate installation for IGS. I just had to configure the IGS URL from Visual Admin. But i can't find any igswd.exe running on my J2EE700 engine.
Please let me know the procedure for this.
Thanks an Regards,
Smriti.Hi,
Check the below link,
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/17/86c039c7811f11e10000000a114084/frameset.htm">About IGS Configuration and Adminisatration</a>
Regards,
Suresh.T -
Pros and cons of installing a local J2EE server
Hi,
We are about to start developing portal applications with Web Dynpro and will use NWDI (DTR/CBS/CMS). I would like to know what SAP recommends for team development, each developer installs a local J2EE server or they all deploy and test on a central server?
From my past experiences, using only one central server can cause problems with debugging, deployment and collisions of a DC tested simultanously by two developers. Running a local server can solve these problems but this could be costly; first because PCs often don't have enough CPU/RAM to run it, and second to support all these complex installations.
I have read Benny's two blogs and some SAP documentation but it is still not clear to me which option is best. If you have lived good or bad experiences with one or the other please let me know!
Thanks,
MartinI would strongly suggest you avoid having a single runtime environment for multiple developers. The nature of Java development makes working in a runtime environment such as this very difficult. It's far too easy to have multiple developers working on the same component making changes that result in different versions of the same component getting deployed to the same runtime environment. Unless communication is very good, you're developers will end up clobbering each others changes. Obviously not good, since the developers will spend time trying to debug problems which really don't exist!
At the other end of the spectrum, each developer can have their own Java stack running locally on their desktop PC. This was the solution that we first tested out, but due to the amount of virus scanning and the overall 'weight' of the other software tools on our desktop PC's, this didn't work too well - performance wasn't all that good. It was also too easy for the developer to clobber their own environment by accidentally removing files, or by making changes to the configuration that would render their engine unusable.
What we opted for was something in the middle: a dedicated multi-cpu system with lots of RAM that runs multiple J2EE instances, each of which is assigned to a single developer. What you get from this sort of configuration is this: only a single operating system to patch when you are required to do upgrades; a controlled environment where the developer doesn't have file system access to the system (which they don't need anyways); if you're lucky, basis support to perform installation and patching duties.
We've been using this environment for about a year now, and it works well. I have full access to the J2EE container via the Visual Admin, and since the dev instances are configured as single server debuggable instances, I can restart the server via the Dev Studio with just two clicks.
Hope that gives you an idea of another possible config. -
How to read the J2EE server hostname and port programmatically
Is there any API to read the J2EE server host and port programmatically? I am looking for the hostname where the components are deployed so that I can append the wsdl path to the server and create an URL.
Hi Larry,
there is a standard J2EE Servlet API for your case.
In a servlet or jsp file you can get the host and prot from the request object.
For example in a JSP file :
request.getScheme();
request.getServerName()
request.getServerPort()
You can check the whole API here :
http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/ServletRequest.html#getServerName()
Bets Regards
Bojidar -
Our J2EE server is not starting due to following error :
Severe error in network I/O of centralserver. Please restart DTR server application. If the problem occurs again, please refer to SAP note 774339 for more details on how to analyse the error condition
we want to restart DTR server.
since J2ee engine is not started, we are not able to logon to Visual Admin.
can anyone tell me about any other way to restart the DTR server.
or
else how to start j2ee engine for above error.
appropriate points will be awarded.
thanks and regards,
Aditya DeshpandeDouble post: DTR server problem
Please continue in the other thread. -
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
Maybe you are looking for
-
Why can't I get a personal hotspot on my iPhone 5 with iOS 7
I can't seem to get the personal hotspot that I paid for already on my phone. We have tried absolutely everything and so has our carrier which is sprint. They contacted apple and there is still no fix for it. This problem causes the personal hotspot
-
TCODE TO DOWNLOAD IDOC INTO A FLAT FILE
Hi All, Please let me know if there is any tcode to download IDOC into a flat file.. Regards, Kaveri
-
Rear Camera has horizontal white line across screen
Hi, I was given a playbook for Christmas and I love it but it has developed a horizontal white line on the rear camera which makes the camera and video unusable. I have customized my Playbook so am reluctant to take it back to the shop. Is there anyt
-
Why do my contacts have such large print? How can i reduce the Size?
mmy contacts are appearing in large print, which means I do,not easily see the whole phone number. How can alter the size of the print?
-
How can I sort properties in KM?
Hi! Can someone tell me, how can I sort properties in a table (KM) - for example the propertie modified in the default-Table Thanks in advance! Emma