2 things: webapps / module whosloggedin
I have 2 questions; 1. Is it possible to count one field in a web apps item? For example, I have 2 different web apps; members and groups. Each member is connected to a group. In the members web app there is a field where you can choose which group. And then I would like a field in the groups that counts how many members that have selected this group. 2. Is it possible to show who - or how many that is logged in to admin console. I tried to use {module whosloggedin}, but that doesn't work.
None of those things are possible at this stage. That many-to-many relationship between web apps can not be created with the current framework and you can not show the number of people logged in. Maybe with the new development to the web app module this may become available. We just have to wait and see.
Cheers,
-m
Similar Messages
-
Parsing in Weblogic/jsp doesn't work; application-mode (command-line) works
Hello-
Parsing my XML file in Weblogic/jsp doesn't work, whereas it works
in application-mode... (albeit on two different machines)
Here are the parameters:
server1:
weblogic 6.0
win2k server
jre1.3
my personal machine:
***no weblogic***
win2k server
jre1.3
When I run my code as an application (command-line style) on my machine,
parsing in my xml file works fine, and I can do a root.toString() and it
dumps out the entire xml file, as desired.
However, running my code inside weblogic (on server1) in JSP, parsing in
my file and doing a root.toString() results in the following: [dmui: null]
(where dmui is my root)
(even though i'm running it on two different machines, i'm positive its the
same code (the servers share a mapped drive)...
So, I think its probably because I'm using a different parser, as
specified by weblogic? There are no exceptions being thrown. Here's my
(abbreviated) code, which is called either command line style or in a JSP:
// Imports
import org.w3c.dom.*;
import org.w3c.dom.Document;
import javax.xml.parsers.*;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
DocumentBuilderFactory docBuilderFactory =
DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
mDocument = docBuilder.parse (inFile);
myRoot.toString()
-END
Doing a System.getProperty("javax.xml.parsers.DocumentBuilderFactory")
results in:
server1 (weblogic/jsp):
"weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
my machine (application-mode):
null
Does anyone have any ideas about how to get this work? Do I try to set it
up so that they both use the same parser? Do I change the Weblogic parser?
If so, to what? And how?
Am I even close?
Any help would be appreciated..
Thanks, Clint
"[email protected]" <[email protected]> wrote in message
news:[email protected]...
No problem, glad you got it worked out :)
~Ryan U.
Jennifer wrote in message <[email protected]>...
I completely missed setting the property(:-o), foolish mistake. That wasit. Thanks.
"j.upton" <[email protected]> wrote:
Jennifer,
Personally I would get rid of import com.sun.xml.parser.* and use xerces
which comes with WLS 6.0 now, unless like I said earlier you have a need
to
use the sun parser :) Try something like this with your code --I've put
things to watch for as comments in the code.
import javax.xml.parsers.*;
import org.xml.sax.SAXException;
import org.w3c.dom.*;
import java.io.FileInputStream;
public class BasicDOM {
public BasicDOM (String xmlFile) {
try{
FileInputStream inStream;
Document document;
/*You must specify a parser for jaxp. You can in a simple view
think
of this as being analogous to a driver used by JDBC or JNDI. If you are
using this in the context of a servlet or JSP and have set an XML
registry
with the console this happens automatically. You can also invoke it in
the
context of an application on the command line using the -D switch. */
System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
>>>
"weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
// create a document factory
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
// specify validating or non-validating parser
dbf.setValidating(true);
// obtain a factory
DocumentBuilder db = dbf.newDocumentBuilder();
// create a document from the factory
inStream = new FileInputStream(xmlFile);
document = db.parse(inStream);
}//try
catch (Exception e)
System.out.println("Unexpected exception reading document!"
+e);
System.exit (0);
}//catch
}//BasicDom
// Main Method
public static void main (String[] args) {
if (args.length < 1)
System.exit(1); file://or you can be more verbose
new BasicDOM(args[0]);
}//class
=============================================
That will give you a basic DOM you can manipulate and parse it fromthere.
BTW this code
compiled and ran on WLS 6.0 under Windows 2000.
Let me know if this helped or you still are having trouble.
~Ryan U.
"Jennifer" <[email protected]> wrote in message
news:[email protected]...
Actually I included com.sun.xml.parser.* as one last febble attempt toget
it working.
And as for source code, I included the code. If I just put that oneline
of code
in, including the imports, it fails giving me an error listed above inthe
subject
line. Here is the code again:
package examples.xml.http;
import javax.xml.parsers.*;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.w3c.dom.*;
import java.util.*;
import java.net.*;
import org.xml.sax.*;
import java.io.*;
public class BasicDOM {
static Document document;
public BasicDOM (String xmlFile) {
try {
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
} catch (FactoryConfigurationError e){
System.err.println(e.getException());
e.printStackTrace();
// Main Method
public static void main (String[] args) {
BasicDOM basicDOM = new BasicDOM (args[0]);Hi, Rob
Does it work in WL9.2?
It seems I do it exactly as the explained at http://edocs.bea.com/wls/docs81/programming/classloading.html - and it fails :o(.
I try to run my app.ear with WL9.2 There are 2 components in it: webapp and mdb. The webapp/WEB-INF contains weblogic.xml:
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
Mdb is expected to run in the same mode, i.e. to prefer the webapp/WEB-INF/*.jar over the parent Weblogic classloader. To do so I add the weblogic-application.xml to the app.ear!/META-INF:
<weblogic-application>
<classloader-structure>
<module-ref>
<!-- reminder: this webapp contains
prefer-web-inf-classes -->
<module-uri>webapp</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>mdb.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
Now, when classloader-structure specified, both webabb and mdb prefer the weblogic root loader as if prefer-web-inf-classes not defined at all. -
Have anyone made a wsgen task in a build.xml file for use with an original Ant-distribution?
(not using org.apache.tools.ant.Main located in weblogic.jar)
I get a non-informing build error when running the wsgen-task. (The ejbc-task
completes successfully).
java.lang.NoSuchMethodError
at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.<init>(DocumentBuilderImpl.java:136)
at weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumen...bla
bla...
(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
If anyone could tell me what to do - that would really make my day(!)
Regards,
Henning StorhaugThere is a little bit of situation using taskdef and a classpath from inside
a build.xml. The problem is that ant creates a custom classloader (which
loads classes the same way ant finds files, ie. replacing /->\, :->;, using
the correct basedir, etc. etc.). Ant uses this classloader to load the class
implementing the task.
Mainly this creates two problems:
- This classloader does not 100% implement the correct protocol of a
classloader, especially when it comes to finding resources. (no disrespect
intended, ant is a great tool!)
- Many classes in Weblogic is not really used to being loaded from a
classloader and doesn't behave very well. (for example: using the
system-classloader directly, assuming that they are located at the
java.system.classpath etc. etc)
This makes it almost impossible to use any weblogic-tasks without loading
weblogic-classes from the system-classpath. And that is why the "trick of
the external build.xml" works, because antcall starts the new ant with a
system-classpath including weblogic.jar.
Don't really now what the best solution to this is. I think that BEA has to
be better writing code that behaves nicer to custom classloaders, and I
think the ant team needs to fix their class-loader a little better.
(especially in respect to resources)
In the meantime use the "external build.xml"-trick or use the ant included
with weblogic.
"Chris" <[email protected]> wrote in message
news:[email protected]...
>
We are actually using Ant 1.4 with Weblogic 6.1 and the wsgen tasksuccessfully..
although I haven't tested myself , I was told that there might be problemsif
the wsgen task is run from the same build.xml file (which might be thereason
for your problem as well)... so what I have done is created a second buildxml
file that includes the wsgen task (and some staging tasks) and I call itfrom
my main build.xml (using antcall).
A couple of things to note is that you have to make sure that you put antin front
of the weblogic.jar in the classpath.. Additionally (and you were rightabout
this) you have to use the taskdef to define the wsgen task as ant will notfind
it by itself..
Here is a sample of the wsgen task I use.
<wsgendestpath="${dir.dsn-build}/webservices_staging/${module.name.Report}WS.ear"
>
context="/${module.name.Report}"
host="localhost"
port="8081"
protocol="http"
webapp="${module.name.Report}-web-services.war">
<rpcservices path="${dir.ear_staging}/ReportEntryEJB.jar">
<rpcservice bean="ReportEntry" uri="/${module.name.Report}uri"/>
</rpcservices>
</wsgen>
"Simon Spruzen" <[email protected]> wrote:
I tried this, and defined a taskdef to allow standalone ant to locate
the WLS ant
wsgen task:
<!-- wsgen - build web services -->
<taskdef name="wsgen" classname="weblogic.ant.taskdefs.ejb.WSGen">
<classpath refid="bea.class.path"/>
</taskdef>
bea.class.path was defined to ensure that weblogic.jar came first.
However, I got a curious error when running wsgen target - can't
remember,
and
don't have, the full details - but it involved a message along the lines
of something
"...violating loader constraints...".
So I just gave up and used the version of Ant that ships with WLS 6.1,
and it
works and I am happy and content.
(But you're stuffed if you want to move to ant 1.4)
"Henning Storhaug" <[email protected]> wrote:
To be a bit more specific:
The wsgen ant-task runs when using the ant-distribution within
weblogic.jar,
but
not using the jakarta-ant-1.3 distribution. I've checked the versions,
and they
are the same.
If you need more info, please ask. -
I need to control resultsPerPage without hardcoding the value
I need to be able to setup the resultsPerPage parameter in the webapps module line as a variable rather than a constant.
e.g.
{module_webapps,ID ,filter,itemID,notUsed,targetFrame,useBackup,resultsPerPage,hideEmptyMessage,rowLength,So rt}
I have two webapps displayed on a page - one showing news, one showing events. At times I need 2 news items and 4 events while at other times I might need 1 news item and 5 events.
I thought that if there was a way I could store the numbers (e.g. in files that could be included, in content holders, in web apps etc) then it would be easier to change than getting into the template and making the change there - which is fraught with danger should the wrong bit be changed.
But I can't see a way of doing it. Obviously javascript is no use since it needs to happen server side before the {module... invocation occurs.
Is there a way? Or am I going to have to setup five separate templates and use this method to select the numbers. I don't really want to do this because it means five templates to keep syncronized in the event of changes but changing a '2' to '3' in the middle of a very user unfriendly template is far less attractive...Darn. But I suspected as much.
We have a home page which displays a bunch of stuff - including an area shared between two web apps (News and Events). Because it is a limited amount of real estate, we can essentially fit 6 'items' in the space - i.e. a combination of X news items and Y event items where X+Y equals 6. So I am having to go into the template and change the two lines for these two web apps to reflect the correct values. Finding the appropriate area in the template is a bit of a pain and making sure I change the exact piece of the line (i.e. don't accidentally delete/insert commas etc) is also a pain. It's worse if someone else is called to make the change because at least I am familiar with it. SO I hoped to find a more parameter driven solution...
Ideally, the web apps could have a DEFAULT RESULTS value and the parameter 'resultsPerPage' could be set to -1 to use that default. Then at least it would mean just updating that field in Business Catalyst...
The only other solution is for me to have the five different versions of the template which is probably going to be safer all things considered...
Thanks for you help though -
Does anyone have a good server.xml file for tomcat?
I am trying to link apache and tomcat on a RedHat 9 computer. I previously posted a message stating that I could not get tomcat to "automagically" make the configuration files (mod_jk.conf-auto) that all the manuals promised it would. However, I found that my problem was the lack of an ApacheConfig tag in the server.xml file. After looking at my server.xml file, I found that it was much more simplistic than I would hoped = it did not have enough comments or commented out options. It had none of the directives that the manuals said it included by default.
In short, does anyone who has apache and tomcat linked have a server.xml file that I can look at so that I can figure out what I must add to mine to get tomcat working with apache? I would greatly appreciate it if you could copy and paste the whole thing here.
Thank you very much in advance.
Edward S. RiceHi!
I am having the Apache-Tomcat4.0 version installed on a Win2000 machine. I am pasting here my server.xml. Hope it will be useful to you. I even didnot do much modifications to my server.xml except for adding a context.
Please come back if problem persists.
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 4.0 documentation bundle for more detailed
instructions):
* Download and install JSSE 1.0.2 or later, and put the JAR files
into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="60000"/>
<!-- Note : To disable connection timeouts, set connectionTimeout value
to -1 -->
<!-- Define an SSL HTTP/1.1 Connector on port 8443 -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0" scheme="https" secure="true">
<Factory className="org.apache.catalina.net.SSLServerSocketFactory"
clientAuth="false" protocol="TLS"/>
</Connector>
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!--
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
-->
<!-- Define a Proxied HTTP/1.1 Connector on port 8081 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8081" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0" connectionTimeout="60000"
proxyPort="80"/>
-->
<!-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 -->
<!--
<Connector className="org.apache.catalina.connector.http10.HttpConnector"
port="8082" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0"/>
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Standalone" defaultHost="localhost" debug="0">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.3
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<Realm className="org.apache.catalina.realm.MemoryRealm" />
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority?user=test;password=test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL?user=scott;password=tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!-- Define the default virtual host -->
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true">
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across all web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn"
debug="0"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common"/>
<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.-->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true"/>
<!-- Define properties for each web application. This is only needed
if you want to set non-default properties, or have web application
document roots in places other than the virtual host's appBase
directory. -->
<!-- Tomcat Root Context -->
<!--
<Context path="" docBase="ROOT" debug="0"/>
-->
<Context path="/vijay" docBase="D:\Java\servlets" debug="0"/>
<!-- Tomcat Manager Context -->
<Context path="/manager" docBase="manager"
debug="0" privileged="true"/>
<!-- Tomcat Examples Context -->
<Context path="/examples" docBase="examples" debug="0"
reloadable="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_examples_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>
<!-- PersistentManager: Uncomment the section below to test Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
limits this. -1 means unlimited sessions are allowed.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
maxActiveSessions. This avoids thrashing when the site is
highly active. -1 or 0 means there is no minimum - sessions
can be swapped out at any time.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the Store,
but left in active memory) if idle for this long (in seconds),
and all sessions found in the Store will be loaded on startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then restart
Catalina.
-->
<!--
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/EmployeeAppDb">
<parameter><name>user</name><value>sa</value></parameter>
<parameter><name>password</name><value></value></parameter>
<parameter><name>driverClassName</name>
<value>org.hsql.jdbcDriver</value></parameter>
<parameter><name>driverName</name>
<value>jdbc:HypersonicSQL:database</value></parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
</Context>
</Host>
</Engine>
</Service>
<!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt file coming with
the WebApp Module distribution on how to build it.
(Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
To configure the Apache side, you must ensure that you have the
"ServerName" and "Port" directives defined in "httpd.conf". Then,
lines like these to the bottom of your "httpd.conf" file:
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
The next time you restart Apache (after restarting Tomcat, if needed)
the connection will be established, and all applications you make
visible via "WebAppDeploy" directives can be accessed through Apache.
-->
<!-- Define an Apache-Connector Service -->
<Service name="Tomcat-Apache">
<Connector className="org.apache.catalina.connector.warp.WarpConnector"
port="8008" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0"/>
<!-- Replace "localhost" with what your Apache "ServerName" is set to -->
<Engine className="org.apache.catalina.connector.warp.WarpEngine"
name="Apache" debug="0" appBase="webapps">
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="apache_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<Realm className="org.apache.catalina.realm.MemoryRealm" />
</Engine>
</Service>
</Server> -
Problems in configuring deployment descriptors to use EJB in JSP
Hello,
I've been trying to use an EJB in a JSP on Weblogic 8.1. The relevent part of
my web.xml and weblogic.xml look like this:
=====================================
web.xml -
<ejb-ref>
<description>Purchase order bean deployed</description>
<ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>mypackage2.PurchaseorderHome</home>
<remote>mypackage2.Purchaseorder</remote>
<ejb-link>/PO.jar#Purchaseorder</ejb-link>
</ejb-ref>
<ejb-local-ref>
<description>purchase order</description>
<ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>mypackage2.PurchaseorderLocalHome</local-home>
<local>mypackage2.PurchaseorderLocal</local>
<ejb-link>/PO.jar#Purchaseorder</ejb-link>
</ejb-local-ref>
=====================================
weblogic.xml -
<ejb-reference-description>
<ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
<jndi-name>Purchaseorder</jndi-name>
</ejb-reference-description>
</reference-descriptor>
=================================
My ejb-jar.xml file looks like this (this EJB jar is already deployed on Weblogic):
<description>Entity Bean ( CMP )</description>
<display-name>Purchaseorder</display-name>
<ejb-name>Purchaseorder</ejb-name>
<home>mypackage2.PurchaseorderHome</home>
<remote>mypackage2.Purchaseorder</remote>
<local-home>mypackage2.PurchaseorderLocalHome</local-home>
<local>mypackage2.PurchaseorderLocal</local>
<ejb-class>mypackage2.PurchaseorderBean</ejb-class>
==============================================
Finally, my weblogic-ejb-jar.xml looks like this:
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Purchaseorder</ejb-name>
<jndi-name>Purchaseorder</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
===============================================
But despite many many efforts, I keep getting the following error:
Could not setup environment - with nested exception: [weblogic.deployment.EnvironmentException:
[J2EE:160101]Error: The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref
or ejb-local-ref 'ejb/Purchaseorder' in the application module 'public_html' could
not be resolved. The target EJB for the ejb-ref could not be found. Please ensure
the link is correct.] weblogic.deployment.EnvironmentException: [J2EE:160101]Error:
The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref or ejb-local-ref
'ejb/Purchaseorder' in the application module 'public_html' could not be resolved.
The target EJB for the ejb-ref could not be found. Please ensure the link is correct.
at
I have changed around a lot of things. I've a classes directory under web-inf
where I have mypackage2\all-the-class-files. I've also made available PO.jar file
(which contains Purchaseorder) at various levels to ensure that the class can
be found. I've changed the "/PO.jar#Purchaseorder" value of <ejb-link> tag accordingly
to try various things. (e.g ejb/Purchaseorder, mypackage2.Purchaseorder, and a
lot of other things) but of no avail. I keep getting the same error over and over
again. (Do you think banging my head on the wall would do the trick?)
Any help would be greatly appreciated. Thanks.
Sam, thanks for the explanation. It makes sense now that why it's not working.
But is this specific to Weblogic? I'm actually using JDevloper to develop my
EJB (CMP) and JSP. Within JSP, I can use the tag library ejbtag provided by Oracle
to specify home, create instance, and get collection back from an EJB. I've specify
the tag lib URI in the web.xml but I kept getting the error message in Weblogi
when running the test to load JSP saying that it could not find the EJB (Purchaseorder)
specified. That led me to do some research and I came accross the <ejb-ref> and
<ejb-link> tags.
If it is a restriction only posed by Weblogic then I guess I'll have to create
a JavaBean to interact with EJB first and then get the collection.
Thanks.
Sam Pullara <[email protected]> wrote:
>You can only use ejb-links when connecting to EJBs that are in the same
>
>application (ear). If you want to have them separate you will have to
>
>use a global JNDI name for the EJB and look up that.
>
>Sam
>
>A Roman wrote:
>> Michael,
>>
>> I'm not deploying EJB as an .ear application that'd include web app
>and .jar.
>> Instead I have deployed .jar as stand alone EJB and want to deploy
>.war (exploded
>> directory structure) as a seperate web app. Both .jar and .war will
>be deployed
>> on the same server. That's exactly why I cannot use the syntax that's
>used in
>> the samples.
>>
>> Thanks.
>>
>> "Michael Kovacs" <[email protected]> wrote:
>>
>>>I guess to start off with I'm making the assumption that your PO.jar
>>>is your
>>>EJB module
>>>and that it is contained in the same EAR as your webapp module, looking
>>>something like
>>>this:
>>>
>>>myEAR.ear
>>> |_ PO.jar
>>> |_ webapp
>>> |_ jspCallingEJB.jsp
>>>
>>>If this is correct, the first thing I'd suggest trying is to remove
>your
>>>"/"
>>
>>>from the front of your <ejb-link> and
>>
>>>just make the value <ejb-link>PO.jar#Purchaseorder</ejb-link>
>>>
>>>The EJB example that ships with 8.1 platform makes use of an EJB from
>>>a jsp
>>>page so you could
>>>look to that example for some guidance, which references the EJB in
>this
>>>same way in the web.xml ejb-local-ref element.
>>>hope that helps.
>>>--
>>>Michael Kovacs
>>>Senior Software Engineer
>>>BEA Systems
>>>"ARoman" <[email protected]> wrote in message
>>>news:[email protected]...
>>>
>>>>Hello,
>>>>
>>>>I've been trying to use an EJB in a JSP on Weblogic 8.1. The relevent
>>>
>>>part
>>>of
>>>
>>>>my web.xml and weblogic.xml look like this:
>>>>=====================================
>>>>web.xml -
>>>>
>>>> <ejb-ref>
>>>> <description>Purchase order bean deployed</description>
>>>> <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
>>>> <ejb-ref-type>Entity</ejb-ref-type>
>>>> <home>mypackage2.PurchaseorderHome</home>
>>>> <remote>mypackage2.Purchaseorder</remote>
>>>> <ejb-link>/PO.jar#Purchaseorder</ejb-link>
>>>>
>>>> </ejb-ref>
>>>>
>>>> <ejb-local-ref>
>>>> <description>purchase order</description>
>>>> <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
>>>> <ejb-ref-type>Entity</ejb-ref-type>
>>>> <local-home>mypackage2.PurchaseorderLocalHome</local-home>
>>>> <local>mypackage2.PurchaseorderLocal</local>
>>>> <ejb-link>/PO.jar#Purchaseorder</ejb-link>
>>>> </ejb-local-ref>
>>>>=====================================
>>>>
>>>>weblogic.xml -
>>>><ejb-reference-description>
>>>><ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
>>>><jndi-name>Purchaseorder</jndi-name>
>>>></ejb-reference-description>
>>>></reference-descriptor>
>>>>=================================
>>>>My ejb-jar.xml file looks like this (this EJB jar is already deployed
>>>
>>>on
>>>Weblogic):
>>>
>>>>
>>>> <description>Entity Bean ( CMP )</description>
>>>> <display-name>Purchaseorder</display-name>
>>>> <ejb-name>Purchaseorder</ejb-name>
>>>> <home>mypackage2.PurchaseorderHome</home>
>>>> <remote>mypackage2.Purchaseorder</remote>
>>>> <local-home>mypackage2.PurchaseorderLocalHome</local-home>
>>>> <local>mypackage2.PurchaseorderLocal</local>
>>>> <ejb-class>mypackage2.PurchaseorderBean</ejb-class>
>>>> ==============================================
>>>>Finally, my weblogic-ejb-jar.xml looks like this:
>>>>
>>>><weblogic-ejb-jar>
>>>> <weblogic-enterprise-bean>
>>>> <ejb-name>Purchaseorder</ejb-name>
>>>> <jndi-name>Purchaseorder</jndi-name>
>>>> </weblogic-enterprise-bean>
>>>></weblogic-ejb-jar>
>>>>===============================================
>>>>
>>>>But despite many many efforts, I keep getting the following error:
>>>>
>>>>Could not setup environment - with nested exception:
>>>
>>>[weblogic.deployment.EnvironmentException:
>>>
>>>>[J2EE:160101]Error: The ejb-link '/PO.jar#Purchaseorder' declared
>in
>>>
>>>the
>>>ejb-ref
>>>
>>>>or ejb-local-ref 'ejb/Purchaseorder' in the application module
>>>
>>>'public_html' could
>>>
>>>>not be resolved. The target EJB for the ejb-ref could not be found.
>>>
>>>Please
>>>ensure
>>>
>>>>the link is correct.] weblogic.deployment.EnvironmentException:
>>>
>>>[J2EE:160101]Error:
>>>
>>>>The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref or
>>>
>>>ejb-local-ref
>>>
>>>>'ejb/Purchaseorder' in the application module 'public_html' could
>not
>>>
>>>be
>>>resolved.
>>>
>>>>The target EJB for the ejb-ref could not be found. Please ensure the
>>>
>>>link
>>>is correct.
>>>
>>>>at
>>>>
>>>>I have changed around a lot of things. I've a classes directory under
>>>
>>>web-inf
>>>
>>>>where I have mypackage2\all-the-class-files. I've also made available
>>>
>>>PO.jar file
>>>
>>>>(which contains Purchaseorder) at various levels to ensure that the
>>>
>>>class
>>>can
>>>
>>>>be found. I've changed the "/PO.jar#Purchaseorder" value of <ejb-link>
>>>
>>>tag
>>>accordingly
>>>
>>>>to try various things. (e.g ejb/Purchaseorder, mypackage2.Purchaseorder,
>>>
>>>and a
>>>
>>>>lot of other things) but of no avail. I keep getting the same error
>>>
>>>over
>>>and over
>>>
>>>>again. (Do you think banging my head on the wall would do the trick?)
>>>>
>>>>Any help would be greatly appreciated. Thanks.
>>>>
>>>
>>>
>>
>
>
-
Logic 9 corrupts EXS insts created/edited in Logic 8
OK, I thought this issue was limited only to EXS instruments that used the VSL Performance Tool, but I'm finding that many (if not all) instruments I created or edited in Logic 8 are corrupted in Logic 9.
Something fishy is going on in the EXS architecture between these versions. To be specific, it seems that EXS in Logic 9 doesn't recall certain parameters that I've set in version 8: zone loop on/off, start & end points, crossfade, LFO settings and on and on.
This is an absolute show-stopper: I have HUNDREDS of custom EXS patches I created in Logic 8 alone that are unusable in Logic 9!
Anybody else experiencing this?Specifically, mod matrix parameters do not recall properly. On some mod/matrix slots, values known to have been saved with non-zero values are recalled as zero. See the following link for an insight:
http://www.logicprohelp.com/viewtopic.php?t=45379
"Logic Expert", I admire your optimism though I may note entirely share it. I post feedback because it's one of the few channels we have to report bugs. The value in the forums -- as Jim said -- is to make others aware of problems, get confirmation from other users experiencing the bugs, and, dare I say, vent on occasion. And, of course, to occasionally have a laugh.
For bugs there's also the ADC Bug Reporter, but there isn't enough time in the day to write up reports in the format they (understandably) request. If you're going to go the ADC route you're basically agreeing to be an unpaid beta tester. And the reality of using the Bug Reporter is that you won't necessarily get confirmation of the bugs you report. So you're feeding information into a system that promises basically nothing in return, not confirmation, not a 'thank you'. Only if you're really lucky will you get a response or a request for additional info.
What I don't quite understand is what is so inappropriate about people occasionally expressing their anger because the software they just paid hundreds of dollars for doesn't work as advertised or as expected. Not saying that continual rant-fests is the way to go... far from it. But the frustration is there. It's visible everyday, world-wide on the 'Net vis a vis news articles, blogs, forums, on any number of issues related to Apple products, from laptop batteries blowing up to über-buggy software titles. And Apple's reputation for non-response is legendary.
So what is it about Apple that they should be approached walking on eggshells, or not apprised of the tens of thousands of cumulative man-hours of wasted time and frustration assumed by customers unwitting of the beta-like software they just paid good money for? What is clearly not understood by some power-that-is (and I would also opine that the Emapple guys are not at fault here) is that _people make their living using these wares_. Logic is not a toy! But to advertise it as ready for public consumption and then to see things like this EXS mod matrix bug literally prevent people from making their living is reprehensible.
You speculate that Apple reads the feedback. Sure, I think sending feedback is very important. However, I speculate that the Emapple guys are already aware of some (but not all) of these bugs. But I can't help but think that their hand was forced in putting Logic 9.0.0 out to market when it really should have been put out to pasture with a lot of other RC's.
In terms of being hopeful, yes, let's hope that 9.0.1 comes out REAL quick and fixes, amongst other things:
• EXS modulation matrix recall bug
• UNDO history non-recall bug
• no way to avoid creating take folders when punching into a track bug
• remainder of punched-into MIDI region shortened when coming out of record
• tempo event behavior that's vastly different from L8 (a confirmed bug with a fix purportedly in the works)
• using "select unused" removes BIP files from the Arrange area
• global track display doesn't function properly in the score editor
• video thumbnail doesn't display in any Global tracks except those enabled in the Arrange page
The bugs are real, but the rest is my opinion, which may differ from your opinion, YMMV, etc. etc. -
Payment block if material is quality stock(MM &QM)
Hi Group,
My client requirement is like
While receiving material against a purchase order to quality stock , the vendor payment should be block(it will not allow for payment or posting invoice). One more thing QM module is not implemented in this client.Is there any such control in MM or any moment type by which we can block payment for the vendor while receiving material.
Thanks
sp sahuHi
First let me know, if QM is not implemented, how stock is moving out from QI to Unrestricted?
You can use QM Procurement key in material master Quality View. There may be standard procurment key (0007 - Delivery release and Invoice block). Otherwise you have your own key and assign it in Material master, quality view, Then Invoice will beblocked as long as material is lying in QI.
For this setting, you need not implement whole QM module.
please check and let me know how it goes.
regards
Srinivas -
Has anyone run the connection pooling for mysql & tomcat successfully?
I'm trying to set up connection pooling. I'm following the how-to page at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
But when i test the DBTest/test.jsp file, tomcat displays an error =
could not load jdbc driver class 'null'(msdos)
i have placed all the required .jar files in the tomcat lib.
below is the cofiguration i did to the server.xml file
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<!-- Uncomment these entries to enable JMX MBeans support -->
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 4.0 documentation bundle for more detailed
instructions):
* Download and install JSSE 1.0.2 or later, and put the JAR files
into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to -1 -->
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" scheme="https" secure="true"
useURIValidationHack="false" disableUploadTimeout="true">
<Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
clientAuth="false" protocol="TLS" />
</Connector>
-->
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!--
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
-->
<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8082" minProcessors="5" maxProcessors="75"
enableLookups="true" disableUploadTimeout="true"
acceptCount="100" debug="0" connectionTimeout="20000"
proxyPort="80" useURIValidationHack="false" />
-->
<!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8083" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
<!--
<Connector className="org.apache.catalina.connector.http10.HttpConnector"
port="8084" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Standalone" defaultHost="localhost" debug="0">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.3
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<Realm className="org.apache.catalina.realm.MemoryRealm" />
-->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!-- Define the default virtual host -->
<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<Context path="/my-jsp" docBase="c:\JSP-Files" debug="0"
privileged="true" reloadable="true" />
<Context path="" docBase="c:\Inetpub\wwwroot" debug="0" privileged="true" />
<Context path="/sharon" docBase="C:\Tomcat 4.1\webapps\sharon" debug="0" privileged="true" />
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across all web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn"
debug="0"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.-->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true"/>
<!-- Define properties for each web application. This is only needed
if you want to set non-default properties, or have web application
document roots in places other than the virtual host's appBase
directory. -->
<!-- Tomcat Root Context -->
<!--
<Context path="" docBase="ROOT" debug="0"/>
-->
<!-- Tomcat Examples Context -->
<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>
<!-- If you wanted the examples app to be able to edit the
user database, you would uncomment the following entry.
Of course, you would want to enable security on the
application as well, so this is not done by default!
The database object could be accessed like this:
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
UserDatabase database =
(UserDatabase) envCtx.lookup("userDatabase");
-->
<!--
<ResourceLink name="userDatabase" global="UserDatabase"
type="org.apache.catalina.UserDatabase"/>
-->
<!-- PersistentManager: Uncomment the section below to test Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
limits this. -1 means unlimited sessions are allowed.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
maxActiveSessions. This avoids thrashing when the site is
highly active. -1 or 0 means there is no minimum - sessions
can be swapped out at any time.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the Store,
but left in active memory) if idle for this long (in seconds),
and all sessions found in the Store will be loaded on startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then restart
Catalina.
-->
<!--
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<Resource name="jdbc/TestDB"
auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/TestDB">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<!-- Maximum number of dB connections in pool. Make sure you
configure your mysqld max_connections large enough to handle
all of your db connections. Set to 0 for no limit.
-->
<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>
<!-- Maximum number of idle dB connections to retain in pool.
Set to 0 for no limit.
-->
<parameter>
<name>maxIdle</name>
<value>30</value>
</parameter>
<!-- Maximum time to wait for a dB connection to become available
in ms, in this example 10 seconds. An Exception is thrown if
this timeout is exceeded. Set to -1 to wait indefinitely.
-->
<parameter>
<name>maxWait</name>
<value>10000</value>
</parameter>
<!-- MySQL dB username and password for dB connections -->
<parameter>
<name>user</name>
<value>javauser</value>
</parameter>
<parameter>
<name>password</name>
<value>javadude</value>
</parameter>
<!-- Class name for mm.mysql JDBC driver -->
<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>
<!-- The JDBC connection url for connecting to your MySQL dB.
The autoReconnect=true argument to the url makes sure that the
mm.mysql JDBC Driver will automatically reconnect if mysqld closed the
connection. mysqld by default closes idle connections after 8 hours.
-->
<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
</parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource"
global="simpleValue"
type="java.lang.Integer"/>
</Context>
</Host>
</Engine>
</Service>
<!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt file coming with
the WebApp Module distribution on how to build it.
(Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
To configure the Apache side, you must ensure that you have the
"ServerName" and "Port" directives defined in "httpd.conf". Then,
lines like these to the bottom of your "httpd.conf" file:
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
The next time you restart Apache (after restarting Tomcat, if needed)
the connection will be established, and all applications you make
visible via "WebAppDeploy" directives can be accessed through Apache.
-->
<!-- Define an Apache-Connector Service -->
<!--
<Service name="Tomcat-Apache">
<Connector className="org.apache.catalina.connector.warp.WarpConnector"
port="8008" minProcessors="5" maxProcessors="75"
enableLookups="true" appBase="webapps"
acceptCount="10" debug="0"/>
<Engine className="org.apache.catalina.connector.warp.WarpEngine"
name="Apache" debug="0">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="apache_log." suffix=".txt"
timestamp="true"/>
<Realm className="org.apache.catalina.realm.MemoryRealm" />
</Engine>
</Service>
-->
</Server>
Pleas4 help!!!you have your driver jar in Tomcat\common\lib?
if so, check your classpath, it could be that. -
Error when deploying ADF application to new WebLogic Server
Hello,
My java-free workplace is getting into ADF development. We've purchased Fusion Applications but don't have the hardware or software yet. I am trying to get a development machine set up ASAP so I can play around with ADF and later SOA Suite.
I have never dealt with WebLogic Server before. I have just taken some training on ADF and SOA Suite and want to play around with what I've learned quickly, as it will be a while until we get our real environment set up and I don't want to forget anything. During the training the environment was already set up for us, so everything just worked. So at this point, I'm fine having everything entirely localized to this machine for the sake of playing around.
I've taken a brand new VM image of a 32-bit Win7 machine and installed:
-Python
-jDeveloper 11.1.2.3.0
-Oracle Database Express (for the sake of having some data to play around with)
-WLS 10.3
-ADF for Oracle Fusion Middleware 11.1.1.7
With WLS, I created a new domain and gave it some credentials.
I can create a ADF application, make connections to my db tables, and build the business components I need based on them. I've created a simple jsf page with the word "test" as my default page.
Then I go to deploy. It can find the WLS domain fine, builds the WAR, but always fails when trying to deploy it and then start it. My error, which I've googled for hours and cannot find a solution to (because of my little understanding of WLS) is:
*Unresolved Webapp Library references for "ServletContext@29372801[app:webapp module:webapp.war path:/TorDemoApplication-DemoUI-context-root spec-version:2.5]", defined in weblogic.xml [Extension-Name: adf.oracle.domain.webapp, exact-match: false]*_
Is there a common step I am missing?
Thanks
TorTor, you didn't miss a step but you used the wrong turn in the middle.
JDev version are tidily coupled to wls versions. Read my blog http://tompeez.wordpress.com/2011/09/14/jdeveloper-versions-vs-weblogic-server-versions/ to get more info on that. So the first decision to take is if you want to use SOA, BPMN and stuff like that, then use JDev 11.1.1.7.0 or if you like to use JSF2.0 and faclets withotu SOA, then use JDev 11.1.2.3.0.
As you said you are working with SOA later on 11.1.1.7.0 is the right version for you. WebLogic server 10.3.6 with the right adf runtime installed and there should be no problem.
Timo -
Hi Guy's,
creation of new infotype we are using Transation code:PM01, when we enter this TS it displays differnt tabs like : Create infotype,infotype version, Screen structure.. presnt require ment is to enhance the one tab to that TS.(Ex: create the one custom infotype like Employee Details, when ever we press the Eployeedetails tab it displays the related field list). Pease help me how to proceed this senario.
Thanks and Regrads,
Sai.
Edited by: sai shanhu on Apr 7, 2008 8:44 AMSai shanhu,
Creating Infotypes for PA and PD using PM01.
1. Infotypes should be started between 9000 9999
2. Go to transaction code PM01.->select Create infotype
3. Give the Infotype number on the screen 9010
4. Click on the Button Generate Objects right to the Infotype input field.
5. It asks for the Creation of the PS9010 structure for infotype. Create, save and activate and come back remaining things will be created automatically. Remaining things means Module pool program, User interface, BADI.
6. Maintain infotype characteristics ex: Time constraints, Subtype, assigning single screen & list screen and save.
7. Select Screen radio button and give 2000 on input field and press edit button .It takes you to the SE51 screen painter. Here we have to write logic for the validations for the fields on the Infotype screen.
Creating subtypes for the infotype
1. Create subtype field in the PS structure of the infotype table.
2. Go to PM01 and press on technical attributes button and select infotype for which subtype should be maintained and display in change mode and enter Subtype field, T591A (Subtype table), T591T (Subtype text table), T591A (Time constraint table) tables and save and exit.
3. Go to SM30 and enter V_T591A and press maintain. Enter subtype numbers and its text and save.
I hope that it helps u .
Regards,
Venkat.O -
Hi, Ive installed tomcat to develop with jsp pages, but I want to use my apache webserver with it. Basically i want to use my http://localhost/~myuser/some_site with jsp files. Ive seen references to mod_jk, but not found a good up to date step by step installation instruction. The most recent one apple has is from 2002, 6 years old now. Anyone know of any up to date mod_jk installation instructions?
thanksThe Tomcat 4 has different settings compared to the previous releases (Tomcat 3.3.x and Tomcat 3.2.x). If the previous releases use mod_jk.dll and/or mod_jk.so, the version 4 uses different modules. I have obtained the following from the server.xml file from Tomcat 4.0.3.
The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt file coming with
the WebApp Module distribution on how to build it.
(Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
To configure the Apache side, you must ensure that you have the
"ServerName" and "Port" directives defined in "httpd.conf". Then,
lines like these to the bottom of your "httpd.conf" file:
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
The next time you restart Apache (after restarting Tomcat, if needed)
the connection will be established, and all applications you make
visible via "WebAppDeploy" directives can be accessed through Apache. -
Hi how to add new folders under root for jsp in tomcat4.1.18
hi,
previsously i used tomcat3.3 and tomcat4.1.12 run sucessfully.
now i downloed jakartha_tomcat4.1.18,
i am running sample succesfuly direcly under root.
now i want my some jsp appilcationes to run under xyz,pqr folders
here my jsp files are abc.jsp,fgh.jsp while running file url like this
http://localhost:8080/xyz/abc.jsp
http://localhost:8080/pqr/fgh.jsp
while running url server not locate the files.
where i add these xyz and pqr folders in server.xml.
here my server.xml like this any one can modify this
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<!-- Comment these entries out to disable JMX MBeans support -->
<!-- You may also configure custom components (e.g. Valves/Realms) by
including your own mbean-descriptor file(s), and setting the
"descriptors" attribute to point to a ';' seperated list of paths
(in the ClassLoader sense) of files to add to the default list.
e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"
-->
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 4.0 documentation bundle for more detailed
instructions):
* Download and install JSSE 1.0.2 or later, and put the JAR files
into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to -1 -->
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" scheme="https" secure="true"
useURIValidationHack="false" disableUploadTimeout="true">
<Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
clientAuth="false" protocol="TLS" />
</Connector>
-->
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="0"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!--
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
-->
<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8082" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" connectionTimeout="20000"
proxyPort="80" useURIValidationHack="false"
disableUploadTimeout="true" />
-->
<!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8083" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
<!--
<Connector className="org.apache.catalina.connector.http10.HttpConnector"
port="8084" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :
<Engine name="Standalone" defaultHost="localhost" debug="0" jmvRoute="jvm1">
-->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Standalone" defaultHost="localhost" debug="0">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.3
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<Realm className="org.apache.catalina.realm.MemoryRealm" />
-->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!-- Define the default virtual host -->
<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across all web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn"
debug="0"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.-->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true"/>
<!-- Define properties for each web application. This is only needed
if you want to set non-default properties, or have web application
document roots in places other than the virtual host's appBase
directory. -->
<!-- Tomcat Root Context -->
<Context path="" docBase="ROOT" debug="0"/>
<!-- Tomcat Examples Context -->
<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_examples_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>
<!-- If you wanted the examples app to be able to edit the
user database, you would uncomment the following entry.
Of course, you would want to enable security on the
application as well, so this is not done by default!
The database object could be accessed like this:
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
UserDatabase database =
(UserDatabase) envCtx.lookup("userDatabase");
-->
<!--
<ResourceLink name="userDatabase" global="UserDatabase"
type="org.apache.catalina.UserDatabase"/>
-->
<!-- PersistentManager: Uncomment the section below to test Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
limits this. -1 or 0 means unlimited sessions are allowed.
If it is not possible to swap sessions new sessions will
be rejected.
This avoids thrashing when the site is highly active.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
activity.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the Store,
but left in active memory) if idle for this long (in seconds),
and all sessions found in the Store will be loaded on startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then restart
Catalina.
-->
<!--
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/EmployeeAppDb">
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value></value></parameter>
<parameter><name>driverClassName</name>
<value>org.hsql.jdbcDriver</value></parameter>
<parameter><name>url</name>
<value>jdbc:HypersonicSQL:database</value></parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource"
global="simpleValue"
type="java.lang.Integer"/>
</Context>
</Host>
</Engine>
</Service>
<!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt file coming with
the WebApp Module distribution on how to build it.
(Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
To configure the Apache side, you must ensure that you have the
"ServerName" and "Port" directives defined in "httpd.conf". Then,
lines like these to the bottom of your "httpd.conf" file:
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
The next time you restart Apache (after restarting Tomcat, if needed)
the connection will be established, and all applications you make
visible via "WebAppDeploy" directives can be accessed through Apache.
-->
<!-- Define an Apache-Connector Service -->
<!--
<Service name="Tomcat-Apache">
<Connector className="org.apache.catalina.connector.warp.WarpConnector"
port="8008" minProcessors="5" maxProcessors="75"
enableLookups="true" appBase="webapps"
acceptCount="10" debug="0"/>
<Engine className="org.apache.catalina.connector.warp.WarpEngine"
name="Apache" debug="0">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="apache_log." suffix=".txt"
timestamp="true"/>
<Realm className="org.apache.catalina.realm.MemoryRealm" />
</Engine>
</Service>
-->
</Server>
==========
any one may modify above one
thanks
pullareddyjAs the server.xml is big enough, I took the minimum portion of it. Hope u can proceed with it.
<!-- Tomcat Root Context -->
<Context path="" docBase="ROOT" debug="0"/>
<!-- New contexts -->
<Context path="/xyz" docBase="pathTo_xyz" debug="0" crossContext="true"/>
<Context path="/pqr" docBase="pathTo_pqr" debug="0" crossContext="true"/>
<!-- Tomcat Examples Context -->
<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
You should also provide a WEB-INF folder under pqr or xyz folder.
You should also provide a web.xml file under each WEB-INF folder.
The minimal web.xml is
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/j2ee/dtd/web-app_2_3.dtd">
<web-app>
</web-app>
That's it. Try it out. Hope it is OK.
Hafizur Rahman
SCJP -
Issue after deploying war file???
We are moving from a windows box to a unix box...
We had installed jdeveloper - jdev11113install.exe (along with weblogic server and adf libraries) earlier version on the windows box and deployed a ADF application war file on that box which worked fine.
Now i have installed jdevloper -jdev11115install.jar (along with weblogic server and adf libraries) a newer version. Now if i deploy my adf war file on this weblogic server its not fully functional. I have some bars and charts which dont load on one tab but loads on the other.
Here are my logs :
AdminServer-Diagnostic .log
[2011-05-13T00:59:05.835-07:00] [AdminServer] [WARNING] [J2EE JMX-46041] [oracle.as.jmx.framework.MessageLocalizationHelper] [tid: JMX FRAMEWORK Domain Runtime MBeanServer pooling thread] [userId: <anonymous>] [ecid: 0000IzcNPGiEGRG5yz_AiW1DnEIq000002,0] The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.
[2011-05-13T01:00:11.288-07:00] [AdminServer] [ERROR] [] [org.apache.beehive.netui.pageflow.internal.AdapterManager] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IzcNfGTEGRG5yz_AiW1DnEIq000003,0] [APP: consoleapp] ServletContainerAdapter manager not initialized correctly.
[2011-05-13T01:14:04.821-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [STANDBY].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000015,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:14:05.208-07:00] [AdminServer] [NOTIFICATION] [] [oracle.security.jps.wls.util.JpsWlsUtil] [tid: [STANDBY].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000015,0] [APP: STUsageApp] JPS-00126
[2011-05-13T01:15:17.280-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:15:19.989-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:15:26.200-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:17:22.266-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] MBean: oracle.mds.lcm:name=MDSAppRuntime,type=MDSAppRuntime,Application=STUsageApp already exists
[2011-05-13T01:17:22.275-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] MBean: oracle.mds.lcm:name=MDSAppRuntime,type=MDSAppRuntime,Application=STUsageApp deregistered
[2011-05-13T01:17:22.278-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:17:42.347-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:17:42.598-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:17:46.568-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:20:34.868-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:20:35.142-07:00] [AdminServer] [NOTIFICATION] [] [oracle.security.jps.wls.util.JpsWlsUtil] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038,0] [APP: STUsageApp] JPS-00126
[2011-05-13T01:21:07.963-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:21:08.177-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:21:11.460-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:23:52.056-07:00] [AdminServer] [NOTIFICATION] [] [oracle.jbo.uicli.mom.CpxUtils$Visitor] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004a,0] [APP: STUsageApp] zip:/usr/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/STUsageApp/aszvbi/war/WEB-INF/lib/_wl_cls_gen.jar!/st/view/DataBindings.cpx
[2011-05-13T01:23:53.108-07:00] [AdminServer] [NOTIFICATION] [ADFC-54008] [oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImpl] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004a,0] [APP: STUsageApp] ADFc: Initializing ADF Page Lifecycle for the JSF environment, LifecycleContextBuilder is 'oracle.adfinternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
[2011-05-13T01:23:58.753-07:00] [AdminServer] [WARNING] [] [oracle.adf.share.jndi.ReferenceStoreHelper] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004c,0] [APP: STUsageApp] Incomplete connection reference object for connection:oc
[2011-05-13T01:25:08.181-07:00] [AdminServer] [WARNING] [] [org.apache.myfaces.trinidad.webapp.ResourceServlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-00000000000000d2,0] [APP: STUsageApp] ResourceServlet._setHeaders(): Content type for /bi/jsLibs/engine_20110409.swf is NULL![[
Cause: Unknown file extension
]]basedomain.log
n.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: AdsTimerManager is already bound; remaining name 'app/webapp/STUsage-ViewController-context-root/15580269/comp/env/tm'
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
at weblogic.deployment.BaseEnvironmentBuilder.addTimerManager(BaseEnvironmentBuilder.java:843)
at weblogic.deployment.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:164)
at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:138)
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<13-May-2011 1:17:50 o'clock AM PDT> <Error> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002c> <1305274670833> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'STUsageApp'.>
####<13-May-2011 1:17:50 o'clock AM PDT> <Warning> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002f> <1305274670836> <BEA-149004> <Failures were detected while initiating start task for application 'STUsageApp'.>
####<13-May-2011 1:17:50 o'clock AM PDT> <Warning> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002f> <1305274670837> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Could not setup environment
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1495)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: AdsTimerManager is already bound; remaining name 'app/webapp/STUsage-ViewController-context-root/15580269/comp/env/tm'
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
at weblogic.deployment.BaseEnvironmentBuilder.addTimerManager(BaseEnvironmentBuilder.java:843)
at weblogic.deployment.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:164)
at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:138)
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<13-May-2011 1:18:32 o'clock AM PDT> <Warning> <netuix> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000030> <1305274712736> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppDeploymentsControlPage.>
####<13-May-2011 1:19:47 o'clock AM PDT> <Warning> <Socket> <server_name> <AdminServer> <ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000011> <1305274787906> <BEA-000450> <Socket 21 internal data record unavailable (probable closure due idle timeout), event received -32>
####<13-May-2011 1:20:34 o'clock AM PDT> <Warning> <J2EE> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038> <1305274834453> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application STUsageApp is not versioned.>
####<13-May-2011 1:21:22 o'clock AM PDT> <Notice> <HTTP> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000042> <1305274882683> <BEA-101352> <There are no active sessions. The webapp module STUsage-ViewController-context-root of application STUsageApp is ready to go into admin mode.> -
prefer-web-inf-classes in weblogic.xml doesn't work
When I try to use <prefer-web-inf-classes>true</prefer-web-inf-classes> it works fine with default classloaders structure. But after I changed classloaders hierarhy by means of <classloader-structure> in weblogic-application.xml classes from web app are ignored and classes from outside web app are loaded.
Here is classloaders structure I use
<weblogic-application>
<classloader-structure>
<module-ref>
<module-uri>mywar.war</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>myejb.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
Has anybody encountered this before?Hi, Rob
Does it work in WL9.2?
It seems I do it exactly as the explained at http://edocs.bea.com/wls/docs81/programming/classloading.html - and it fails :o(.
I try to run my app.ear with WL9.2 There are 2 components in it: webapp and mdb. The webapp/WEB-INF contains weblogic.xml:
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
Mdb is expected to run in the same mode, i.e. to prefer the webapp/WEB-INF/*.jar over the parent Weblogic classloader. To do so I add the weblogic-application.xml to the app.ear!/META-INF:
<weblogic-application>
<classloader-structure>
<module-ref>
<!-- reminder: this webapp contains
prefer-web-inf-classes -->
<module-uri>webapp</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>mdb.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
Now, when classloader-structure specified, both webabb and mdb prefer the weblogic root loader as if prefer-web-inf-classes not defined at all.
Maybe you are looking for
-
Purchase Order text in Material Master
Hi experts, A material code ( for ex 10000000 ) is opened in plant X and is also extended to plant Y. We want to enter purchase order text in the same material code 10000000 ( thru tcode MM02 ) for plant X only. At present, the purchase order te
-
Hello friends, Can some help me to understand how to implement cascaded prompts in OBIEE 10g? My situation is: I have three Prompts P1,P2 and P3 P1: Values are comming from a table P2: Shows the value from a Stored Procedure, such that one stored pro
-
Table maintainance generator: Event 01
Hi colleagues, I created a maintenance dialog for a user table a while ago. For administrative purposes I used event 01 'Before Saving the Data in the Database' to add some data automatically to new and changed records. This worke fine until last wee
-
I'm trying to record a new track in an existing project, and every time a hit the record button I get an I/O Error Result Code -36. This is only happening in this particular project. If I open a new project I can record just fine. What does this mean
-
I want to sync my ipad with my computer but there's no option to do so