WebLogic Debugging thru Multiple EjBs using VCafe 3.1
Here is my problem:
We are trying to use use WebLogic 4.5.1 and Visual Cafe 3.1 and debug
with break points within multiple EjBs. However, this is not going so well.
My first question is this, is what we are trying to do even possible with
the versions we are using. From all I have read I gather now it is possible
to debug using the aforementioned versions of WL and VC with special
handling. Or is it necessary to use different versions. The problem with
that would be that there is no Enterprise relase of Cafe past 3.1 yet.
Further we want to use Java 1.2 and that means we have to use WL 4.5.1 (so
4.0.3 is not an option although it works well with Debugging with VC 3.1)
Any help or direction would really be appreciated. Thank you.
Mark,
Please post this in the weblogic.developer.interest.general newsgroup
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Mark Hartnett" <[email protected]> wrote in message
news:3f57a4a3$[email protected]..
>
I am having a problem debugging using Eclipse 2.1 and the weblogic serverplugin
provided by this site.
If I start the server and run the application everything works fine.
If I put a breakpoint into my code and then run the application I do notsee the
application breaking at all. I am in debug view of Eclipse. The browserjust
hangs and will not respond. I can take the breakpoint off and refresh thebrowser
and it works fine again.
Do I need to have anything special in a configuration file for weblogic toenable
debugging ?
Do I need to start the JVM with any special parms. I am currently usingthe following
startup options. I have tried a number of configurations on the startupoptions
and nothing works.
-hotspon
-ms64m
-mx256m
-Xdebug
-Djava.compiler=none
-Xnoagent
-Dweblogic.ProductionModeEnabled=false
I am using Weblogic 6.1 and JDK 1.3.1_09
Thanks in advance for any help...
Similar Messages
-
How to debug serlvet and EJB using IDE
Anybody knows how to debug Servlet and EJB through standard IDE, like
Symantec or VisualAge? Does the attach to process works?
Thanks.1) Download and install the jpda package from sun (Java Platform Debugger
Architecture, it contains the jdwp.dll, this has to be in your %PATH%
variable).
2) Start weblogic with something like this:
%JDK_HOME%\bin\java -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y
,address=8000 -ms64m -mx64m -Xbootclasspath:%JAVACLASSPATH% -classpath
%WEBLOGICHOME%\classes\boot -Dweblogic.class.path=%WEBLOGICCLASSPATH% -Dwebl
ogic.home=%WEBLOGICHOME% -Dweblogic.system.name=MyServer -Djava.security.man
ager -Djava.security.policy==%WEBLOGICHOME%\weblogic.policy weblogic.Server
3) address is the portnumber (in this example 8000) for the remote debugger.
Attach to the VM with arguments -host <hostname> -port <address>
-Falk
"test" <[email protected]> wrote in message
news:8frkq6$ru5$[email protected]..
Anybody knows how to debug Servlet and EJB through standard IDE, like
Symantec or VisualAge? Does the attach to process works?
Thanks. -
Remote debugging (jboss deployed) ejb using JDeveloper
Hi there
Does anyone know how to remote debug an ejb deployed in JBoss using JDeveloper (or perhaps know of a link?)? All I can find is this from Oracle:
http://www.oracle.com/technology/products/jdev/howtos/appservers/debug_in_jboss.html
But the cmd to replace in the $bin\run.bat file to enable remote debugging doesn't exist in my version of JBoss (jboss-4.0.1RC1).
Can anyone shed some light here?
Thanks very much in advance...JonIn run batch file add
set JAVA_OPTS= -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS% -
Connection to multiple databases using a single EJB
How can I connect to multiple Databases (using @PersistenceContext) using an EJB?
Did I need to connect various Entity Managers corresponding to the each database and simply send my Queries?
I am using Glassfish Application Server
Netbeans IDE
Java Derby Database
Oracle Database
Java Persistence API
Thanks in AdvanceYes, you need a persistence context and thus entity manager per database. Depending on what you want to achieve you may also need to go to the next level in your skill set and learn all about distributed transactions.
-
Lookup on multiple ejb instances accross servers using servicelocator
Hi all,
i have a weird problem. I have to hit multiple ejbs hosted in diffrent server.
The problem is with the lookup and accessing..
some server's components have username and passwords and other server donot have.
So though i create a new Initial context instance with diffrent parameters.. it
is getting messed up inside. ie it is passing server A username and password to
server B's method call as for B i donot set username and password there is no
need of username and password.
the service locator will server for only one server's objects lookup. but here
we have multiple components in diffrent so different provider_URL INITIAL_CONTEXT_FACTORY,
SECURITY_PRINCIPAL, SECURITY_CREDENTIALS
and the for each i have a seperate sericelocator.. like each one for componet
A, B, C etc. in diffrent servers
and they inturn have InitialContext instance of their own. .. and these are initilized
with the factory, url, username and credentials...
this can be set as the system property also using -D option. thatz why .. when
i create for one component.... the already created Initial context factory is
getting affected with the new values. ;(((
one solution is every time create the Initial context... do not hold the reference
of contexts and donot hold reference of home handles..
but i need to cache atleast the home handles, if i am not caching.. the performance
is really bad.
on the cached handle if i call method i get a java.rmi.AccessException: Security
violation: insufficient permission to access method, though it worked for first
time,
and on the servers it which does not need passwords, method call is throwing java.lang.SecurityException:
Authentication for user ServerAUser denied in realm wl_realm
but the serverAUser belongs to server A, i get this error when i call a componets
method on Server B.
Is this a bug, or the Initial Context working it self is this way, the behind
the scence provider class is messing up. bea guys please reply if u know to solve
this problem, it will be of real help.
reagrds,
Arun.NProblem resolved as this is an stateless session bean issues.
-
FCP to export thru Compressor to multiple computers using Qmaster
Hello all,
I just wanted to confirm, can you from FCP export thru Compressor to multiple computers using Qmaster?
ThanksSort of... you can set up a render farm using Qmaster so the files are worked on by all of your CPUs... If that's what you are talking about the answer is yes.
Jerry -
I tried to ask this question a few months ago, but I must not have given enough
details
for anyone to even guess what my problem might be. So I created a simple example
to
demonstrate what's happening.
I have a cluster of 2 WL servers (7.0) running on Linux. When I call an EJB multiple
times at once from different threads in a client application, sometimes all the
threads
finish in a few milliseconds, but other times at least one of the threads will
pause
for 60 seconds before finishing. There are no error or warning indicators in any
server
log files. I'm trying to do something very simple: add one to a number in a database
table without letting any two clients get the same number.
I'm using DB2 as my database and COM.ibm.db2.jdbc.app.Driver as my driver. I have
a
JDBC connection pool and a DataSource, which I'm using in a stateless session
bean.
I lock the table in exclusive mode, query the current number, and add one to it.
I'm
using container-managed transactions, so I'm relying on the container to commit
the
update when the method ends. (I tried using a bean-managed transaction, and I
got the
same results.)
For a long time I believed the problem must be with DB2, but when I put the exact
same
code in a JSP, it works just fine. So I know that DB2 can do what I'm asking it
to do.
I also tried it on a Windows NT server, and it behaves exactly the same. Comparing
thread dumps of the two servers in the cluster taken during one of these 60 second
wait periods doesn't show any obvious problems: the two servers both have exactly
the
same threads going, and they all seem pretty reasonable to me.
Here is the code for my EJB:
package com.davisvision.cv;
import java.sql.*;
import javax.ejb.*;
public class SimpleBean implements SessionBean {
SessionContext ctx;
public void ejbCreate() {
public void ejbPostCreate() {
public void ejbRemove() {
public void ejbActivate() {
public void ejbPassivate() {
public void setSessionContext(SessionContext c) {
ctx = c;
public int nextNumber() {
String tableName = "TEST.PROVIDER_SPAWN";
Connection con = null;
int num = 0;
try {
con = CvDatabase.getConnection();
con.setAutoCommit(false);
Statement stmt = con.createStatement();
stmt.executeUpdate("LOCK TABLE " + tableName + " IN EXCLUSIVE MODE");
ResultSet rs = stmt.executeQuery("SELECT NEXT_OFFICE_NUM FROM "
+ tableName + " WHERE PROVIDER_TYPE = 'DAVIS2'");
if (rs.next()) {
num = rs.getInt(1);
num++;
int updated = stmt.executeUpdate("UPDATE " + tableName
+ " SET NEXT_OFFICE_NUM = " + num
+ " WHERE PROVIDER_TYPE = 'DAVIS2'");
catch(Exception e) {
num = -1;
Logger.writeDated(Logger.FATAL, "SimpleBean.nextNumber: " + e);
finally {
CvDatabase.close(con);
return num;
And here is my client application:
package test;
import com.davisvision.cv.*;
import java.util.*;
import javax.ejb.*;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
public class TestSimpleBean implements Runnable {
static InitialContext ctx;
public int taskNum;
static void getContext() {
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://weblogictest:7055");
try {
ctx = new InitialContext(env);
catch(NamingException e) {
System.out.println("Unable to obtain an initial JNDI context:
" + e);
public void run() {
System.out.println("Thread " + taskNum + " started.");
try {
Object obj = ctx.lookup("ejb-cv-Simple");
SimpleHome h = (SimpleHome) PortableRemoteObject.narrow(obj, SimpleHome.class);
SimpleRemote r = h.create();
int n = r.nextNumber();
System.out.println("Thread " + taskNum + " next number = " + n);
catch(Exception e) {
System.out.println("Error in thread " + taskNum + ": " + e);
System.out.println("Thread " + taskNum + " ended.");
public static void main(String[] args) {
getContext();
int n = 3;
TestSimpleBean x = null;
Thread t = null;
// start each thread
for (int i = 0; i < n; i++) {
x = new TestSimpleBean();
x.taskNum = i;
t = new Thread(x);
t.start();
System.out.println("" + n + " threads started.");
My deployment descriptors are as simple as I could make them:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>Simple</ejb-name>
<home>com.davisvision.cv.SimpleHome</home>
<remote>com.davisvision.cv.SimpleRemote</remote>
<ejb-class>com.davisvision.cv.SimpleBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>Simple</ejb-name>
<method-name>
</method-name>
</method>
<trans-attribute>
Required
</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
"-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Simple</ejb-name>
<jndi-name>ejb-cv-Simple</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
This is from part of a production application, so to make sure our users aren't
getting
random 60-second pauses, I have the production bean deployed on just one server
in the
cluster with just one bean in the pool. But I really need to find the solution
to this
problem before development goes much further. Any guesses, sugestions, or conjectures
would be most welcome.
- garyOops, I didn't notice that I only attached one file last time. The thread dump
from the other server in the cluster is attached.
My (off-topic) Linux problem must be something else: Signaling the parent
java process was one of the first things I tried. It may have to do with the
way that we start WL (in the background with nohup).
- gary
Rob Woollen <[email protected]> wrote:
Gary Bradshaw wrote:
Thanks for your response, Rob. I've attached the thread dumps, hopingthat they
will be easier to read that way. They are from a Windows NT system:Thanks. Are you sure this is the right dump? The server looks
completely idle in this dump.
I haven't
yet found a way to get a thread dump on my Linux system. (I know Ishould say
"kill -3 <processId>", but each WLS has at least 72 process IDs. MaybeI just
haven't found the right one yet.)Try ps -ef --forest . It'll show you graphically with a little ascii
art the parent process/thread.
-- Rob
Your suggestion to do the update first would work for this particularexample
since I know I always want to add 1 to the number, but in other similarsituations
I will want to vary the update based on the values I find in the row.I'm looking
for a clean way to safely do multi-user updates with JDBC. (For larger,more important
tables I'm using entity beans).
- gary
Rob Woollen <[email protected]> wrote:
Can you post the thread dumps?
Also usually people do something like this:
update mytable set count = count + 1
select count from mytable
-- Rob
Gary Bradshaw wrote:
I tried to ask this question a few months ago, but I must not havegiven enough
details
for anyone to even guess what my problem might be. So I created a
simple
example
to
demonstrate what's happening.
I have a cluster of 2 WL servers (7.0) running on Linux. When I callan EJB multiple
times at once from different threads in a client application, sometimesall the
threads
finish in a few milliseconds, but other times at least one of the
threads
will
pause
for 60 seconds before finishing. There are no error or warning indicatorsin any
server
log files. I'm trying to do something very simple: add one to a numberin a database
table without letting any two clients get the same number.
I'm using DB2 as my database and COM.ibm.db2.jdbc.app.Driver as mydriver. I have
a
JDBC connection pool and a DataSource, which I'm using in a statelesssession
bean.
I lock the table in exclusive mode, query the current number, and
add
one to it.
I'm
using container-managed transactions, so I'm relying on the containerto commit
the
update when the method ends. (I tried using a bean-managed transaction,and I
got the
same results.)
For a long time I believed the problem must be with DB2, but when
I
put the exact
same
code in a JSP, it works just fine. So I know that DB2 can do what
I'm
asking it
to do.
I also tried it on a Windows NT server, and it behaves exactly thesame. Comparing
thread dumps of the two servers in the cluster taken during one ofthese 60 second
wait periods doesn't show any obvious problems: the two servers bothhave exactly
the
same threads going, and they all seem pretty reasonable to me.
Here is the code for my EJB:
package com.davisvision.cv;
import java.sql.*;
import javax.ejb.*;
public class SimpleBean implements SessionBean {
SessionContext ctx;
public void ejbCreate() {
public void ejbPostCreate() {
public void ejbRemove() {
public void ejbActivate() {
public void ejbPassivate() {
public void setSessionContext(SessionContext c) {
ctx = c;
public int nextNumber() {
String tableName = "TEST.PROVIDER_SPAWN";
Connection con = null;
int num = 0;
try {
con = CvDatabase.getConnection();
con.setAutoCommit(false);
Statement stmt = con.createStatement();
stmt.executeUpdate("LOCK TABLE " + tableName + " IN EXCLUSIVEMODE");
ResultSet rs = stmt.executeQuery("SELECT NEXT_OFFICE_NUM
FROM "
+ tableName + " WHERE PROVIDER_TYPE = 'DAVIS2'");
if (rs.next()) {
num = rs.getInt(1);
num++;
int updated = stmt.executeUpdate("UPDATE " + tableName
+ " SET NEXT_OFFICE_NUM = " + num
+ " WHERE PROVIDER_TYPE = 'DAVIS2'");
catch(Exception e) {
num = -1;
Logger.writeDated(Logger.FATAL, "SimpleBean.nextNumber:" + e);
finally {
CvDatabase.close(con);
return num;
And here is my client application:
package test;
import com.davisvision.cv.*;
import java.util.*;
import javax.ejb.*;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
public class TestSimpleBean implements Runnable {
static InitialContext ctx;
public int taskNum;
static void getContext() {
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://weblogictest:7055");
try {
ctx = new InitialContext(env);
catch(NamingException e) {
System.out.println("Unable to obtain an initial JNDIcontext:
" + e);
public void run() {
System.out.println("Thread " + taskNum + " started.");
try {
Object obj = ctx.lookup("ejb-cv-Simple");
SimpleHome h = (SimpleHome) PortableRemoteObject.narrow(obj,SimpleHome.class);
SimpleRemote r = h.create();
int n = r.nextNumber();
System.out.println("Thread " + taskNum + " next number= " + n);
catch(Exception e) {
System.out.println("Error in thread " + taskNum +
" + e);
System.out.println("Thread " + taskNum + " ended.");
public static void main(String[] args) {
getContext();
int n = 3;
TestSimpleBean x = null;
Thread t = null;
// start each thread
for (int i = 0; i < n; i++) {
x = new TestSimpleBean();
x.taskNum = i;
t = new Thread(x);
t.start();
System.out.println("" + n + " threads started.");
My deployment descriptors are as simple as I could make them:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>Simple</ejb-name>
<home>com.davisvision.cv.SimpleHome</home>
<remote>com.davisvision.cv.SimpleRemote</remote>
<ejb-class>com.davisvision.cv.SimpleBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>Simple</ejb-name>
<method-name>
</method-name>
</method>
<trans-attribute>
Required
</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
"-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Simple</ejb-name>
<jndi-name>ejb-cv-Simple</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
This is from part of a production application, so to make sure ourusers aren't
getting
random 60-second pauses, I have the production bean deployed on justone server
in the
cluster with just one bean in the pool. But I really need to find
the
solution
to this
problem before development goes much further. Any guesses, sugestions,or conjectures
would be most welcome.
- gary------------------------------------------------------------------------
Full thread dump:
"Thread-7" daemon prio=5 tid=0x868400 nid=0x1f8 waiting on monitor[0x136ff000..0x136ffdc0]
at java.lang.Thread.sleep(Native Method)
at com.davisvision.cv.CvProperties.run(CvProperties.java:153)
at java.lang.Thread.run(Thread.java:479)
"ListenThread.Default" prio=5 tid=0x8647d0 nid=0x1f0 runnable [0x136bf000..0x136bfdc0]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:263)
"ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=5 tid=0x84d220nid=0x1e9 waiting on monitor [0x1312f000..0x1312fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=5tid=0x84c040 nid=0x1e8 waiting on monitor [0x130ef000..0x130efdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=5tid=0x84c580 nid=0x1e7 waiting on monitor [0x130af000..0x130afdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=5tid=0x84cec0 nid=0x1a1 waiting on monitor [0x1306f000..0x1306fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=5tid=0x84b370 nid=0x1a0 waiting on monitor [0x1302f000..0x1302fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"CoreHealthMonitor" daemon prio=5 tid=0x829e30 nid=0x1e6 waiting onmonitor [0x12fef000..0x12fefdc0]
at java.lang.Thread.sleep(Native Method)
at weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:114)
"ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x820420nid=0x1e5 waiting on monitor [0x12faf000..0x12fafdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81f2d0nid=0x1e4 waiting on monitor [0x12f6f000..0x12f6fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81fec0nid=0x1e3 waiting on monitor [0x12f2f000..0x12f2fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81eac0nid=0x1e2 waiting on monitor [0x12eef000..0x12eefdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81d6c0nid=0x1e1 waiting on monitor [0x12eaf000..0x12eafdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81c2d0nid=0x1e0 waiting on monitor [0x12e6f000..0x12e6fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81cec0nid=0x1df waiting on monitor [0x12e2f000..0x12e2fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81bac0nid=0x1de waiting on monitor [0x12def000..0x12defdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x81a6c0nid=0x1dd waiting on monitor [0x12daf000..0x12dafdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x8192d0nid=0x1dc waiting on monitor [0x12d6f000..0x12d6fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x819ec0nid=0x1db waiting on monitor [0x12d2f000..0x12d2fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x818990nid=0x1da waiting on monitor [0x12cef000..0x12cefdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x817630nid=0x1d9 waiting on monitor [0x12caf000..0x12cafdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x816150nid=0x1d8 waiting on monitor [0x12c6f000..0x12c6fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x816690nid=0x1d7 waiting on monitor [0x12c2f000..0x12c2fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5 tid=0x811cc0 nid=0x1d6 waiting on monitor [0x12bef000..0x12befdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5 tid=0x8104c0 nid=0x1d5 waiting on monitor [0x12baf000..0x12bafdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5 tid=0x80f020 nid=0x1d4 waiting on monitor [0x12b6f000..0x12b6fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"Thread-4" prio=5 tid=0x80e440 nid=0x1d3 waiting on monitor [0x12b2f000..0x12b2fdc0]
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:427)
at java.util.TimerThread.run(Timer.java:380)
"ExecuteThread: '1' for queue: 'DRS'" daemon prio=5 tid=0x80d700 nid=0x1d2waiting on monitor [0x12aef000..0x12aefdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: 'DRS'" daemon prio=5 tid=0x80b160 nid=0x1d1waiting on monitor [0x12aaf000..0x12aafdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: 'Multicast'" daemon prio=5 tid=0x80a8b0nid=0x1d0 waiting on monitor [0x12a6f000..0x12a6fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '1' for queue: 'Replication'" daemon prio=5 tid=0x8072f0nid=0x1cf waiting on monitor [0x12a2f000..0x12a2fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: 'Replication'" daemon prio=5 tid=0x807430nid=0x1c9 waiting on monitor [0x129ef000..0x129efdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"LDAPConnThread 10.1.7.26:7001" daemon prio=5 tid=0x7f56c0 nid=0x1cdrunnable [0x1296f000..0x1296fdc0]
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:85)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:181)
at java.io.BufferedInputStream.read(BufferedInputStream.java:199)
at netscape.ldap.ber.stream.BERElement.getElement(BERElement.java:101)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:420)
"LDAPConnThread 10.1.7.26:7001" daemon prio=5 tid=0x7f35c0 nid=0x1cbrunnable [0x128ef000..0x128efdc0]
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:85)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:181)
at java.io.BufferedInputStream.read(BufferedInputStream.java:199)
at netscape.ldap.ber.stream.BERElement.getElement(BERElement.java:101)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:420)
"LDAPConnThread 10.1.7.26:7001" daemon prio=5 tid=0x7edc70 nid=0x1carunnable [0x128af000..0x128afdc0]
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:85)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:181)
at java.io.BufferedInputStream.read(BufferedInputStream.java:199)
at netscape.ldap.ber.stream.BERElement.getElement(BERElement.java:101)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:420)
"VDE Transaction Processor Thread" prio=2 tid=0x7e21c0 nid=0x1c5 waitingon monitor [0x1282f000..0x1282fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:306)
at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:192)
"ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x7a7020 nid=0x1c4 waiting on monitor [0x127df000..0x127dfdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x7d7750 nid=0x1c3 waiting on monitor [0x1279f000..0x1279fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemonprio=5 tid=0x7c26b0 nid=0x1c2 waiting on monitor [0x1273f000..0x1273fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemonprio=5 tid=0x7c2bf0 nid=0x1c1 waiting on monitor [0x126ff000..0x126ffdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"TimeEventGenerator" daemon prio=5 tid=0x7c00d0 nid=0x1c0 waiting onmonitor [0x126bf000..0x126bfdc0]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=5tid=0x7bfac0 nid=0x1bf waiting on monitor [0x1267f000..0x1267fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=5tid=0x7be5c0 nid=0x1be waiting on monitor [0x1263f000..0x1263fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"HighPriority TimeEventGenerator" daemon prio=9 tid=0x7bee10 nid=0x1bdwaiting on monitor [0x125ff000..0x125ffdc0]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=5 tid=0x7bc270 nid=0x1bc waitingon monitor [0x125bf000..0x125bfdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:60)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x7b9050nid=0x1bb runnable [0x1257f000..0x1257fdc0]
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:534)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
"ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x7b8050nid=0x1ba runnable [0x1253f000..0x1253fdc0]
at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:534)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
"ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x7b8840nid=0x1b9 runnable [0x124ff000..0x124ffdc0]
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:387)
at weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:158)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:336)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
"ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x7b7360nid=0x1b8 waiting on monitor [0x124bf000..0x124bfdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x7b7ec0nid=0x1b7 waiting on monitor [0x1247f000..0x1247fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x7b6ac0nid=0x1b6 waiting on monitor [0x1243f000..0x1243fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x7b56c0nid=0x1b5 waiting on monitor [0x123ff000..0x123ffdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x7b4360nid=0x1b4 waiting on monitor [0x123bf000..0x123bfdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
"ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x7b4ec0nid=0x1b3 waiting on monitor [0x1237f000..0x1237fdc0]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread. -
Hi All:
I am trying to create multiple profiles, using unified profile types, to
store multiple values for same properties. Here my intention of using
'unified profile types' is to create multiple profiles (to store multiple
values for a property). All the properties are stored in the same database
maintained by Personalization server. Also, I am trying to use the same
'USER' ejb as profile class/home/pk/jndi.
The scenerio is,
define unified profile types (Business, Vacation) using Personalization
admin tools, using com.beasys.commerce.axiom.contact.User,
com.beasys.commerce.axiom.contact.UserHome,
com.beasys.commerce.axiom.contact.UserPk,
com.beasys.commerce.axiom.contact.User for Profile Class, Home, Pk class,
JNDI name respectively.
Define Property set 'HotelCommerce' with property
HotelProp as single, restricted, text (valid values Single, Double)
Now you can use the attached jsp files to login as a user and try to set the
property value for HotelProp for each profile. As per my understanding, I
was expecting that I can set different values for the property 'HotelProp'
for each profiles. But unexpectedly, all the profiles get the same value.
Question. is it the correct behavior? if yes, how can I achieve this
functionality?
if not, do you see any problem in my scripts?
your answer asap is appreciated. we need to make decision on using
Personalization server v/s developing our own Personalization server!!!:)
thanks,
-rajesh
PS: I have tried 'Unified Profile Example' type too, but that did not work.
[propsettest.jsp]
[home.jsp]I am trying to create multiple profiles, using unified profile types, to
store multiple values for same properties. Here my intention of using
'unified profile types' is to create multiple profiles (to store multiple
values for a property). All the properties are stored in the same database
maintained by Personalization server. Also, I am trying to use the same
'USER' ejb as profile class/home/pk/jndi.Hello Rajesh,
This is not the purpose of the UUP. The UUP is used to allow existing
database schemas to be aggregated with the existing Weblogic Personalization
Server database schema to provide a single, customized user profile with which
to maintain the user properties (
http://e-docs.bea.com/wlcs/p13n/users.htm#1068901 )
If you want to have properties that change value based on some "profile" or
classification of a user, then you should use classifier rules to change the
user from "OnVacation" to "AtWork" or "AtHome". You can use these classifier
rules to select content for the user or conditionally execute logic (
http://e-docs.bea.com/wlcs/p13n/rules.htm )
Ture Hoefner
BEA Systems, Inc.
1655 Walnut Street; suite 200
Boulder, CO 80302
www.beasys.com -
Hi,
I have 2 weblogic startup scripts (startWebLogic.sh and
startWebLogic_recovery.sh) for the same domain.
startWebLogic.sh uses config.xml file.
I would like to use config_recovery.xml as the configuration file for startWebLogic_recovery.sh
How would I do this ?
I am using WebLogic Server 6.1 on SunOS 5.8 / HP-UX 11.0.
Appreciate any help.
Regards
Gunaseelan VenkateswaranI guess you're using Weblogic 6.1 with WLCS 3.5. I think you're supposed to work with one config.xml for the same domain, and not have a different config.xml.
To start up different applications or EJBs, use the "target" property to control which applications to start up for the particular instance.
YY -
How to get the TransactionManager in a stateful EJB (using JPA toplink)
I use weblogic 10.3
This is my stateful EJB and I need to get the TransactionManager because I want to suspend my transaction...
Here it is ok for the UserTransaction ut but I got an error with the TransactionManager
EJB Code
//@Stateless(name = "MyFacadeEJB", mappedName = "MyFacadeEJB")
@Stateful(name = "MyFacadeEJB", mappedName = "MyFacadeEJB")
@TransactionManagement(TransactionManagementType.BEAN)
@Remote
@Local
public class MyFacadeEJBBean implements MyFacadeEJB, MyFacadeEJBLocal, Serializable {
@Resource javax.transaction.UserTransaction ut;
@Resource javax.transaction.TransactionManager tm;
Error Message at the deploy EJB
Unable to deploy EJB: MyFacadeEJB from PocJTA-PEJB-ejb:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'test.ejb.MyFacadeEJBBean/tm' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.
at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:639)
at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:247)Chpruvos,
Hi, I ran into a similar issue when specifying WebLogic specific descriptors in ejb-jar.xml and the corresponding weblogic-ejb-jar.xml. I no longer use this approach in our example code - we just use annotations. see: http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#Tutorial_Source
My session bean is stateless - I don't know how much it will help with your statefull bean managed config but here are copies of the ejb.jar configuration xml I used to use. All the resource*ref elements (see the resource-description* element) ended up in the weblogic specific weblogic-ejb-jar.xml descriptor file.
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee [http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd]" version="3.0">
*<enterprise-beans>*
*<session>*
*<ejb-name>ApplicationService</ejb-name>*
*<ejb-class>org.eclipse.persistence.example.unified.business.ApplicationService</ejb-class>*
*<session-type>Stateless</session-type>*
+<!-- default to CMP Container managed transations not BMP -->+
+<!-- transaction-type>Bean</transaction-type-->+
+<!-- resource-env-ref id="ResourceEnvRef_1080980284303">+
+<resource-env-ref-name>localOracle10RemoteDS</resource-env-ref-name>+
+<resource-env-ref-type>javax.sql.DataSource</resource-env-ref-type>+
+</resource-env-ref-->+
+<!-- resource-ref>+
+<res-ref-name>localOracle10RemoteDS</res-ref-name>+
+<res-type>javax.sql.DataSource</res-type>+
+<res-auth>Application</res-auth>+
+</resource-ref-->+
*</session>*
*</enterprise-beans>*
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0"?>
<weblogic-ejb-jar>
*<weblogic-enterprise-bean>*
*<ejb-name>ApplicationService</ejb-name>*
*<stateless-session-descriptor>*
*<pool>*
*<max-beans-in-free-pool>8</max-beans-in-free-pool>*
*<initial-beans-in-free-pool>2</initial-beans-in-free-pool>*
*</pool>*
*</stateless-session-descriptor>*
{color:#008000}<resource-description>
<res-ref-name>localOracle10RemoteDS</res-ref-name>
<jndi-name>localOracle10RemoteDS</jndi-name>
</resource-description>
<resource-env-description>
<resource-env-ref-name>localOracle10RemoteDS</resource-env-ref-name>
<jndi-name>localOracle10RemoteDS</jndi-name>
</resource-env-description>
{color}+<!-- jndi-name>localOracle10RemoteDS</jndi-name-->+
*</weblogic-enterprise-bean>*
</weblogic-ejb-jar>
thank you
/michael
[http://www.eclipselink.org|http://www.eclipselink.org/]
Edited by: michael_obrien on Feb 26, 2009 9:56 AM -
How to send multiple Recipients using the mail.jar and activation.jar
hi!
could somebody help me. how do i send multiple Recipient using mail.jar. when i would input 2email address in to Recipient
(example: [email protected], [email protected])
i get a DEBUG: setDebug: JavaMail version 1.3.2
but if i send a single email it just works properly.
heres my code
import java.io.*;
import java.util.*;
import javax.mail.*;
import javax.mail.event.*;
import javax.mail.internet.*;
public class SendMail
public SendMail(String to, String from, String subject, String body)
//public SendMail(String to)
String message_recip = to;
String message_subject = subject;
String message_cc = "";
String message_body = body;
//The JavaMail session object
Session session;
//The JavaMail message object
Message mesg;
// Pass info to the mail server as a Properties, since JavaMail (wisely) allows room for LOTS of properties...
Properties props = new Properties( );
// LAN must define the local SMTP server as "mailhost" to be able to send mail...
//props.put("mail.smtp.host","true");
props.put("mail.smtp.host", "mailhost");
// Create the Session object
session = Session.getDefaultInstance(props, null);
session.setDebug(true);
try
// create a message
mesg = new MimeMessage(session);
// From Address - this should come from a Properties...
mesg.setFrom(new InternetAddress(from));
// TO Address
InternetAddress toAddress = new InternetAddress(message_recip);
mesg.addRecipient(Message.RecipientType.TO, toAddress);
// CC Address
InternetAddress ccAddress = new InternetAddress(message_cc);
mesg.addRecipient(Message.RecipientType.CC, ccAddress);
// The Subject
mesg.setSubject(message_subject);
// Now the message body.
mesg.setText(message_body);
// XXX I18N: use setText(msgText.getText( ), charset)
// Finally, send the message!
Transport.send(mesg);
}//end of try
catch (MessagingException ex)
while ((ex = (MessagingException)ex.getNextException( )) != null)
ex.printStackTrace( );
}//end of while
}//end of catch
}//end of SendMail
public static void main(String[] args)
//String t = "[email protected], [email protected]"; - this I think causes error
String t = "[email protected]";
String f = "[email protected]";
String s = "Hello World";
String b = "the quick brown fox jumps over the lazy dog";
SendMail sm = new SendMail(t,f,s,b);
}//end of main
}//end of class
could someone please help me im stuck-up with this. thanx!i need it ASAP
i am a beginner in java and jsp
Need to knw how can I parse the addresss field
Below
is the code
<code>
package
public class EMailBean {
private String smtp,username,password,from,bcc,subject,body,attachments,cc;
/*setter*/
public void setSmtp(String str){this.smtp=str;}
public void setUsername(String str){this.username=str;}
public void setPassword(String str){this.password=str;}
public void setFrom(String str){this.from=str;}
public void setTo(String str){this.to=str;}
public void setCc(String str){this.cc=str;}
public void setBcc(String str){this.bcc=str;}
public void setSubject(String str){this.subject=str;}
public void setBody(String str){this.body=str;}
public void setAttachments(String str){this.attachments=str;}
/*getter*/
public String getSmtp( ){return this.smtp;}
public String getUsername( ){return this.username;}
public String getPassword( ){return this.password;}
public String getFrom( ){return this.from;}
public String getTo( ){return this.to;}
public String getCc( ){return this.cc;}
public String getBcc( ){return this.bcc;}
public String getSubject( ){return this.subject;}
public String getBody( ){return this.body;}
public String getAttachments( ){return this.attachments;}
</code>
Session session = Session.getDefaultInstance(props, null);
session.setDebug(true);
try {
MimeMessage msg = new MimeMessage(session);
msg.setFrom(new InternetAddress(mail.getFrom()));
msg.addRecipients(Message.RecipientType.TO, InternetAddress.parse(to, false));
msg.addRecipient(Message.RecipientType.TO,new InternetAddress(mail.getTo()));
msg.addRecipient(Message.RecipientType.CC, new InternetAddress(mail.getCc()));
msg.addRecipient(Message.RecipientType.CC, new InternetAddress("[email protected]"));
msg.setSubject(mail.getSubject());
// Create the message part
BodyPart messageBodyPart = new MimeBodyPart();
// Fill the message
messageBodyPart.setText(mail.getBody());
Multipart multipart = new MimeMultipart();
multipart.addBodyPart(messageBodyPart);
// Part two is attachment
messageBodyPart = new MimeBodyPart();
DataSource source = new FileDataSource(mail.getAttachments());
messageBodyPart.setDataHandler(new DataHandler(source));
messageBodyPart.setFileName(source.getName());
multipart.addBodyPart(messageBodyPart);
msg.setContent(multipart);
msg.setSentDate(new Date());
Transport t = session.getTransport("smtp");
try {
t.connect(mail.getUsername(), mail.getPassword());
t.sendMessage(msg, msg.getAllRecipients());
} finally {
t.close();
result = result + "<FONT SIZE='4' COLOR='blue'><B>Success!</B>"+"<FONT SIZE='4' COLOR='black'> "+"<HR><FONT color='green'><B>Mail was successfully sent to </B></FONT>: "+mail.getTo()+"<BR>";
if (!("".equals(mail.getCc())))
result = result +"<FONT color='green'><B>CCed To </B></FONT>: "+mail.getCc()+"<BR>";
if (!("".equals(mail.getBcc())))
result = result +"<FONT color='green'><B>BCCed To </B></FONT>: "+mail.getBcc() ;
result = result+"<BR><HR>";
} catch (MessagingException mex) {
result = result + "<FONT SIZE='4' COLOR='blue'> <B>Error : </B><BR><HR> "+"<FONT SIZE='3' COLOR='black'>"+mex.toString()+"<BR><HR>";
} catch (Exception e) {
result = result + "<FONT SIZE='4' COLOR='blue'> <B>Error : </B><BR><HR> "+"<FONT SIZE='3' COLOR='black'>"+e.toString()+"<BR><HR>";
e.printStackTrace();
finally {
return result;
} -
Multiple DataSource using single Connection Pool
Previously using Weblogic 6.1 we had a configuration where multiple Datasources used a single connection pool. Now that we are in the process of upgrading to Weblogic 9.1, we are attempting to recreate the same configuration.
The Weblogic 9.1 upgrade wizard appears to have created the relevent datasource & connection pool configuration files but when attempting to use these I am receiving the following errors:
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901758> <BEA-001508> <Destroying Connection Pool TestDSLegacyPool.>
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901758> <BEA-001155> <The following exception has occurred:
weblogic.common.ResourceException: Unknown Data Source TestDSLegacyPool
at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:419)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:251)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<30-Jan-2007 11:18:21 o'clock GMT> <Error> <Deployer> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901773> <BEA-149205> <Failed to initialize the application 'TestDSLegacyPool' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:239)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
at weblogic.jdbc.common.internal.DataSourceManager.verifyPoolDeployment(DataSourceManager.java:607)
at weblogic.jdbc.common.internal.DataSourceManager.checkDSConfig(DataSourceManager.java:594)
at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:236)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
++++++++++++++++++++++++++++++++++++++++++++++++++
The configuration files content is :
TestDSLegacyPool-9290-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>TestDSLegacyPool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>3</value>
</property>
<property>
<name>LegacyPoolName</name>
<value>Beach Brochure Browse Pool</value>
</property>
</internal-properties>
<jdbc-data-source-params>
<jndi-name>beachBrochureBrowseDS</jndi-name>
<global-transactions-protocol>None</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
CP-Beach_Brochure_Browse_Pool-1043-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>Beach Brochure Browse Pool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>1</value>
</property>
</internal-properties>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@aserver:1522:adb</url>
<driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>gf_user</value>
</property>
<property>
<name>dll</name>
<value>ocijdbc9</value>
</property>
<property>
<name>protocol</name>
<value>thin</value>
</property>
</properties>
<password-encrypted>{3DES}4UT5899x/Z4=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>3</max-capacity>
</jdbc-connection-pool-params>
</jdbc-data-source>
Would anyone be able to point me in the right direction with this? Configuring the Datasources through the Admin Console creates a single Datasource configuration file that contains its relevent connection pool configuration, but the Weblogic Upgrade wizard creates a Datasource config file and a separate connection pool config file. What would I need to do to use the config files generated by the Weblogic Upgrade wizard?
Any help appreciated
Thanks
AndrewAndrew Harrison wrote:
Previously using Weblogic 6.1 we had a configuration where multiple Datasources used a single
connection pool. Now that we are in the process of upgrading to Weblogic 9.1, we are attempting
to recreate the same configuration.Hi, sorry to say, that is no longer possible:
http://e-docs.bea.com/wls/docs90/jdbc_admin/jdbc_intro.html#1044158
Simplified JDBC Resource Configuration
In WebLogic Server 9.0, the number of JDBC resource types was reduced to simplify JDBC configuration and to reduce the likelihood
of configuration errors. Instead of configuring a JDBC connection pool and then configuring a data source or tx data source to
point to the connection pool and bind to the JNDI tree, you configure a data source that encompasses a connection pool.
Note: Because of the new configuration design, you can no longer have multiple data sources that point to a single connection
pool. Instead, you can create additional data sources, each with its own pool of connections, or you can bind a single data source
to the JNDI tree with multiple names. See Binding a Data Source to the JNDI Tree with Multiple Names for more information.
Joe
>
The Weblogic 9.1 upgrade wizard appears to have created the relevent datasource & connection pool
configuration files but when attempting to use these I am receiving the following errors:
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
<1170155901758> <BEA-001508> <Destroying Connection Pool TestDSLegacyPool.>
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
<1170155901758> <BEA-001155> <The following exception has occurred:
weblogic.common.ResourceException: Unknown Data Source TestDSLegacyPool
at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:419)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:251)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
####<30-Jan-2007 11:18:21 o'clock GMT> <Error> <Deployer> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901773> <BEA-149205> <Failed to initialize the application 'TestDSLegacyPool' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:239)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
at weblogic.jdbc.common.internal.DataSourceManager.verifyPoolDeployment(DataSourceManager.java:607)
at weblogic.jdbc.common.internal.DataSourceManager.checkDSConfig(DataSourceManager.java:594)
at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:236)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
++++++++++++++++++++++++++++++++++++++++++++++++++
The configuration files content is :
TestDSLegacyPool-9290-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>TestDSLegacyPool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>3</value>
</property>
<property>
<name>LegacyPoolName</name>
<value>Beach Brochure Browse Pool</value>
</property>
</internal-properties>
<jdbc-data-source-params>
<jndi-name>beachBrochureBrowseDS</jndi-name>
<global-transactions-protocol>None</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
CP-Beach_Brochure_Browse_Pool-1043-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>Beach Brochure Browse Pool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>1</value>
</property>
</internal-properties>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@aserver:1522:adb</url>
<driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>gf_user</value>
</property>
<property>
<name>dll</name>
<value>ocijdbc9</value>
</property>
<property>
<name>protocol</name>
<value>thin</value>
</property>
</properties>
<password-encrypted>{3DES}4UT5899x/Z4=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>3</max-capacity>
</jdbc-connection-pool-params>
</jdbc-data-source>
Would anyone be able to point me in the right direction with this? Configuring the Datasources
through the Admin Console creates a single Datasource configuration file that contains its relevent
connection pool configuration, but the Weblogic Upgrade wizard creates a Datasource config file and
a separate connection pool config file. What would I need to do to use the config files generated
by the Weblogic Upgrade wizard?
Any help appreciated
Thanks
Andrew -
Error compiling single ejb using appc/ejbc (long)
This may be related to my earlier post ("no longer able to build ejb
using appc (WLS 8.1)", posted this morning), but the error and the way I
encountered it were different enough that I thought I'd post as a new
topic. I've been trying to build a project using weblogic 8.1, but I've
been running into some problems.
As a test, I tried compiling a single ejb from the command line using
the new appc compiler. I compiled the source files and moved them to a
clean build directory, along with the deployment descriptors. From the
command line, I set the system classpath to the bare minimum necessary
to build the ejb-- the jdk tools.jar, the jre rt.jar, the weblogic.jar
file, the project bin directory, the log4j.jar, and my database driver
jar (see [1] and the echoed resulting classpath at [2] below). I then
invoked appc, specifying the output and source paths ([3]). The
resulting error ([4]) shows a much larger classpath, which abruptly ends
with a "?". I ran the same test using ejbc instead of appc, and I get
the very same problem (same error message). I've never encountered
problems like these before, and other than upgrading to weblogic 8.1, my
system configuration hasn't changed. Any ideas or suggestions would be
greatly appreciated!
system:
weblogic 8.1
sun jdk 1.4.1_02 (bundled with weblogic)
win 2k
Test and resulting error message:
[1] SETTING CLASSPATH...
D:\workspace\TRIPS\deployment\build>set classpath=D:\bea\jdk141_02\jre
\lib\rt.jar;D:\bea\jdk141_02\lib\tools.jar;D:\bea\weblogic81\server\lib
\weblogic.jar;D:\workspace\TRIPS\bin;D:\workspace\TRIPS\lib\log4j.jar;D:
\workspace\TRIPS\lib\ifxjdbc.jar
[2] ECHOING CLASSPATH...
D:\workspace\TRIPS\deployment\build>set classpath
classpath=D:\bea\jdk141_02\jre\lib\rt.jar;D:\bea\jdk141_02\lib
\tools.jar;D:\bea\weblogic81\server\lib\weblogic.jar;D:\workspace\TRIPS
\bin;D:\workspace\TRIPS\lib\log4j.jar;D:\workspace\TRIPS\lib\ifxjdbc.jar
[3] INVOKING APPC...
D:\workspace\TRIPS\deployment\build>java weblogic.appc -output D:
\workspace\TRIP
S\deployment\build\VASKeyGenerator.jar D:\workspace\TRIPS\deployment
\build
[4] ERROR MESSAGE...
java.io.IOException: CreateProcess: javac -classpath "C:\temp\appcgen;C:
\Program
Files\Java\j2re1.4.1_01\lib\rt.jar;C:\Program Files\Java\j2re1.4.1_01
\lib\i18n.
jar;C:\Program Files\Java\j2re1.4.1_01\lib\sunrsasign.jar;C:\Program
Files\Java\
j2re1.4.1_01\lib\jsse.jar;C:\Program Files\Java\j2re1.4.1_01\lib
\jce.jar;C:\Prog
ram Files\Java\j2re1.4.1_01\lib\charsets.jar;C:\Program Files\Java
\j2re1.4.1_01\
classes;D:\bea\jdk141_02\jre\lib\rt.jar;D:\bea\jdk141_02\lib
\tools.jar;D:\bea\we
blogic81\server\lib\weblogic.jar;D:\bea\weblogic81\server\lib
\wlcipher.jar;D:\be
a\weblogic81\server\lib\webservices.jar;D:\bea\weblogic81\server\lib
\xmlx.jar;D:
\bea\weblogic81\server\lib\ojdbc14.jar;D:\bea\weblogic81\server\lib
\EccpressoAsn
1.jar;D:\bea\weblogic81\server\lib\EccpressoCore.jar;D:\bea\weblogic81
\server\li
b\EccpressoJcae.jar;D:\bea\weblogic81\server\lib\ant\ant.jar;D:\bea
\weblogic81\s
erver\lib\ant\optional.jar;D:\bea\weblogic81\server\lib\ant\jakarta-oro-
2.0.4.ja
r;D:\bea\weblogic81\server\lib\ant\xml-apis.jar;D:\bea\weblogic81\server
\lib\ant
\xerc?
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:63)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at java.lang.Runtime.exec(Runtime.java:491)
at java.lang.Runtime.exec(Runtime.java:457)
at weblogic.utils.Executable.exec(Executable.java:227)
at weblogic.utils.Executable.exec(Executable.java:156)
at weblogic.utils.Executable.exec(Executable.java:142)
at weblogic.utils.compiler.CompilerInvoker.execCompiler
(CompilerInvoker.
java:246)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit
(CompilerInvo
ker.java:463)
at weblogic.utils.compiler.CompilerInvoker.compile
(CompilerInvoker.java:
364)
at weblogic.utils.compiler.CompilerInvoker.compile
(CompilerInvoker.java:
372)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile
(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB
(EJBCompiler.java:468)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB
(EJBCompiler.java:387)
at weblogic.appc.compileEJB(appc.java:735)
at weblogic.appc.compileEJB(appc.java:709)
at weblogic.appc.compileInput(appc.java:446)
at weblogic.appc.runBody(appc.java:167)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.appc.main(appc.java:961)
Exec failed .. exiting
D:\workspace\TRIPS\deployment\build>Hi Tim,
I just got past a similar problem by specifying the full path to javac
in build.xml. Like:
<wlappc source="${dest.dir}" compiler="C:\bea\jdk141_02\bin\javac"
/>
Tim Perrigo <[email protected]> wrote in message news:<[email protected]>...
This may be related to my earlier post ("no longer able to build ejb
using appc (WLS 8.1)", posted this morning), but the error and the way I
encountered it were different enough that I thought I'd post as a new
topic. I've been trying to build a project using weblogic 8.1, but I've
been running into some problems.
As a test, I tried compiling a single ejb from the command line using
the new appc compiler. I compiled the source files and moved them to a
clean build directory, along with the deployment descriptors. From the
command line, I set the system classpath to the bare minimum necessary
to build the ejb-- the jdk tools.jar, the jre rt.jar, the weblogic.jar
file, the project bin directory, the log4j.jar, and my database driver
jar (see [1] and the echoed resulting classpath at [2] below). I then
invoked appc, specifying the output and source paths ([3]). The
resulting error ([4]) shows a much larger classpath, which abruptly ends
with a "?". I ran the same test using ejbc instead of appc, and I get
the very same problem (same error message). I've never encountered
problems like these before, and other than upgrading to weblogic 8.1, my
system configuration hasn't changed. Any ideas or suggestions would be
greatly appreciated!
system:
weblogic 8.1
sun jdk 1.4.1_02 (bundled with weblogic)
win 2k
Test and resulting error message:
[1] SETTING CLASSPATH...
D:\workspace\TRIPS\deployment\build>set classpath=D:\bea\jdk141_02\jre
\lib\rt.jar;D:\bea\jdk141_02\lib\tools.jar;D:\bea\weblogic81\server\lib
\weblogic.jar;D:\workspace\TRIPS\bin;D:\workspace\TRIPS\lib\log4j.jar;D:
\workspace\TRIPS\lib\ifxjdbc.jar
[2] ECHOING CLASSPATH...
D:\workspace\TRIPS\deployment\build>set classpath
classpath=D:\bea\jdk141_02\jre\lib\rt.jar;D:\bea\jdk141_02\lib
\tools.jar;D:\bea\weblogic81\server\lib\weblogic.jar;D:\workspace\TRIPS
\bin;D:\workspace\TRIPS\lib\log4j.jar;D:\workspace\TRIPS\lib\ifxjdbc.jar
[3] INVOKING APPC...
D:\workspace\TRIPS\deployment\build>java weblogic.appc -output D:
\workspace\TRIP
S\deployment\build\VASKeyGenerator.jar D:\workspace\TRIPS\deployment
\build
[4] ERROR MESSAGE...
java.io.IOException: CreateProcess: javac -classpath "C:\temp\appcgen;C:
\Program
Files\Java\j2re1.4.1_01\lib\rt.jar;C:\Program Files\Java\j2re1.4.1_01
\lib\i18n.
jar;C:\Program Files\Java\j2re1.4.1_01\lib\sunrsasign.jar;C:\Program
Files\Java\
j2re1.4.1_01\lib\jsse.jar;C:\Program Files\Java\j2re1.4.1_01\lib
\jce.jar;C:\Prog
ram Files\Java\j2re1.4.1_01\lib\charsets.jar;C:\Program Files\Java
\j2re1.4.1_01\
classes;D:\bea\jdk141_02\jre\lib\rt.jar;D:\bea\jdk141_02\lib
\tools.jar;D:\bea\we
blogic81\server\lib\weblogic.jar;D:\bea\weblogic81\server\lib
\wlcipher.jar;D:\be
a\weblogic81\server\lib\webservices.jar;D:\bea\weblogic81\server\lib
\xmlx.jar;D:
\bea\weblogic81\server\lib\ojdbc14.jar;D:\bea\weblogic81\server\lib
\EccpressoAsn
1.jar;D:\bea\weblogic81\server\lib\EccpressoCore.jar;D:\bea\weblogic81
\server\li
b\EccpressoJcae.jar;D:\bea\weblogic81\server\lib\ant\ant.jar;D:\bea
\weblogic81\s
erver\lib\ant\optional.jar;D:\bea\weblogic81\server\lib\ant\jakarta-oro-
2.0.4.ja
r;D:\bea\weblogic81\server\lib\ant\xml-apis.jar;D:\bea\weblogic81\server
\lib\ant
\xerc?
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:63)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at java.lang.Runtime.exec(Runtime.java:491)
at java.lang.Runtime.exec(Runtime.java:457)
at weblogic.utils.Executable.exec(Executable.java:227)
at weblogic.utils.Executable.exec(Executable.java:156)
at weblogic.utils.Executable.exec(Executable.java:142)
at weblogic.utils.compiler.CompilerInvoker.execCompiler
(CompilerInvoker.
java:246)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit
(CompilerInvo
ker.java:463)
at weblogic.utils.compiler.CompilerInvoker.compile
(CompilerInvoker.java:
364)
at weblogic.utils.compiler.CompilerInvoker.compile
(CompilerInvoker.java:
372)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile
(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB
(EJBCompiler.java:468)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB
(EJBCompiler.java:387)
at weblogic.appc.compileEJB(appc.java:735)
at weblogic.appc.compileEJB(appc.java:709)
at weblogic.appc.compileInput(appc.java:446)
at weblogic.appc.runBody(appc.java:167)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.appc.main(appc.java:961)
Exec failed .. exiting
D:\workspace\TRIPS\deployment\build> -
Send/Receive multiple attachments using SwA (no MTOM)
Hello all,
I would appreciate if someone can put me in the right direction about the following implementation:
- web service method able to receive multiple attachment using weblogic tools (wsdlc, jwsc) without MTOM.
I tried JAXRPC and JAXWS, starting from code and from wsdl, using bytearrayholder, DataHandler array ... without success.
Better solution for my own goal would be using JAXRPC and Array of attachments.
Actually I don't know what I can add again: I've done multiple tests and I cannot add all the used code/wsdl/build/... of course.
I'm using WLS 10.0 (p3)
I'm just a bit confused! So, I will thank if someone can suggest the right road and, in case, I'll post more details about the related test I've done.
Thanks,
PepeHello all,
I would appreciate if someone can put me in the right direction about the following implementation:
- web service method able to receive multiple attachment using weblogic tools (wsdlc, jwsc) without MTOM.
I tried JAXRPC and JAXWS, starting from code and from wsdl, using bytearrayholder, DataHandler array ... without success.
Better solution for my own goal would be using JAXRPC and Array of attachments.
Actually I don't know what I can add again: I've done multiple tests and I cannot add all the used code/wsdl/build/... of course.
I'm using WLS 10.0 (p3)
I'm just a bit confused! So, I will thank if someone can suggest the right road and, in case, I'll post more details about the related test I've done.
Thanks,
Pepe -
URGENT: Is it possible to upload multiple files using STRUTS
Hi,
Is it possible to upload multiple files using STRUTS.
I am able to upload a single file. But how do i upload multiple files ??
upload.jsp
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
<%@ taglib uri="/WEB-INF/struts-template.tld" prefix="template" %>
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
<html:html>
<head>
<title>New Page 1</title>
</head>
<body>
<html:form action="/secure/uploadFile.do" enctype="multipart/form-data" method="POST" type="com.smartstream.webconnect.user.actions.UploadActionForm">
<p>File to upload
<html:file property="fileUpload" size="20"/></p>
<p><html:submit/></p>
</html:form>
</body>
</html:html>
UploadAction.java
public class UploadAction extends BaseAction {
Logger log = Logger.getLogger(AttachMessageAction.class);
public ActionForward executeAction(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws ActionException {
System.out.println("executeAction of UploadAction");
UploadActionForm uploadActionForm = (UploadActionForm) form;
int fileSize = uploadActionForm.getFileUpload().getFileSize();
System.out.println("uploadActionForm.getFileUpload().getFileSize() = " + uploadActionForm.getFileUpload().getFileSize());
byte buffer[] = new byte[1024];
try {
BufferedInputStream bufferedInputStream = new BufferedInputStream(uploadActionForm.getFileUpload().getInputStream());
FileOutputStream fos = new FileOutputStream("s:\\uploaded\\" + uploadActionForm.getFileUpload().getFileName());
int read;
while ( (read = bufferedInputStream.read(buffer,0,buffer.length)) != -1) {
fos.write(buffer, 0, read);
fos.flush();
fos.close();
bufferedInputStream.close();
return mapping.findForward("success");
} catch (IOException e) {
e.printStackTrace();
return mapping.findForward("error");
}catch(OutOfMemoryError o){
o.printStackTrace();
System.out.println("o.getMessage() " + o.getMessage());
return mapping.findForward("error");
UploadActionForm.java
public class UploadActionForm extends ActionForm{
private FormFile fileUpload;
private byte[] fileContent;
public FormFile getFileUpload() {
org.apache.struts.taglib.html.FormTag _jspx_th_html_form_0;
return fileUpload;
public byte[] getFileContent() {
return fileContent;
public void setFileUpload(FormFile fileUpload) {
this.fileUpload = fileUpload;
public void setFileContent(byte[] fileContent) {
this.fileContent = fileContent;
}--Bhupendra MahajanYes, you could try using the multipart handler...
But I have a better idea...
Determine the maximum number of file uploads that the
user can do at one time. I mean, you can't
realistically have the user upload a million files at
one time. So say the max is 20. So you create your
action form class with 20 FormFile fields called file1
to file20.
Then when you dynamically create your page, you
dynamically create the specified number of file fields
and 1 hidden field called "totalFiles" which contains
the number of file fields you created. This should be
an int field in the form bean.
Then when you do your action processing, you just loop
thru the totalFiles... Or well, actually, you may not
need that at all. You could just check all the
FormFile fields and whatever ones aren't null contain
files.But what about UploadActionForm.java[b]
How do i have exact mapping of the HTML form in this file ??
--[b]Bhupendra Mahajan
Maybe you are looking for
-
Material stock received and issued for a given period of time
HOW to get the material stock received and issued for a given period of time including the open orders. if there is any BAPI Available then please tell me. or give me the table relations thaks. thanks inadvance
-
Hi, we have the need to supress bank/payment data in the vendor master (MK03, FK03, XK03) as well is in invoices (MIR4). I know this can be done via Define Screen Layout per Activty in the IMG. The problem this presents is that there are some users
-
CONVERT_OTF_2_PDF_ARCHIVELINK
Hi Do anybody knows how to use this function? I have a field named ls_output_info( type otf_t_itcoo) and I have to convert it as type TDOTFLO to give it to the FM. How can I convert this field? Any suggestion? Regards Karim
-
Template Installer JDI NW2004s SP05
HI all, I have installed NW2004s and updated to SP05 and try to run the template installer for usage type DI. However when I run the template installer with template "DI_Postinstallation", I got an error seems related to localization problem on step
-
Error message and crashing of LabVIEW 5 when controlling K-Teams Khepera robot
I have the gripper turret attached to K-Team's Khepera 1 Robot and use the K-Team provided LabVIEW VI's to control the arm movement or gripper. Every so often I get an error message after the VI runs and LabVIEW has to shut down. Does anyone know why