Call EJB in WLS 7.0SP2 from WLS 5.1 SP13

Hello,
I am trying to call an EJB deployed on WLS 7.0SP2 from a WLS 5.1 SP13.
There are issues from 19 Dec 2002 in "weblogic.developer.interest.rmi-iiop" newsgroup
that are supossed to established a summary on this interoperability. The solution
seems to be the same as the interoperability between WLS 6.1SP2 and WLS5.1SP12
with I have been working for several months. I have followed the steps (EJB generated
with "weblogic.ejbc -iiop" in WLS 7.0 and client classes generated with "weblogic.ejbc
-iiop -clienteJar" in WLS5.1) but the only result I obtain is the following exception.
Has anybody really invoked EJBs between this two WLS versions with IIOP?.
javax.naming.NamingException: Unhandled error in lookup. Root exception is java.lang.NullPointerException
at javax.naming.NameImpl.<init>(NameImpl.java:250) at javax.naming.CompositeName.<init>(CompositeName.java:223)
at weblogic.iiop.IIOPInvocationHandlerImpl.getClusteredStub(IIOPInvocationHandlerImpl.java:150)
at weblogic.iiop.IIOPInvocationHandlerImpl.resolveObject(IIOPInvocationHandlerImpl.java:114)
at weblogic.iiop.IIOPReplacer.resolveObject(IIOPReplacer.java:375) at weblogic.iiop.AbstractMsgInput.readRemote(AbstractMsgInput.java:185)
at weblogic.iiop.AbstractMsgInput.readObject(AbstractMsgInput.java:156) at weblogic.cos.naming.NamingContext_WLStub.resolve(NamingContext_WLStub.java:122)
at weblogic.jndi.cosnaming.IIOPInitialContextServer.lookup(IIOPInitialContextServer.java:109)
at javax.naming.InitialContext.lookup(InitialContext.java:345) at jsp_servlet._jsp.__test._jspService(__test.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:946)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:910)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:277)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:403)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:285)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
Thanks for any help,
Rosa

Similar Messages

Call MS com object via SOAP from WLS 6.1

I generated a WSDL file for a Microsoft com object and can easily write a WL
web service that calls it using Workshop 7.0. But I need to deploy it on a
WLS 6.1 server. (I was hoping that Workshop would simply generate the source
code required for accessing the com object via soap, which I could then cut
and paste into my own source, but it doesn't do that.)
Does anyone have an example of how to do this?

Hi Mel,
You said that you want to "deploy it on WLS 6.1", but I think what you really
meant is that you want a J2EE component (i.e. JSP, Servlet, EJB, etc.) running
in WLS 6.1 to consume the WSDL you created from the COM object, right?
If so, the web services package in WLS 6.1 can be used to do this :-) If you tell
me what type of J2EE component (i.e. JSP, Servlet, EJB, etc.) you want to be the
client, I'll provide you with some sample code. Also, be sure you attach the WSDL
that was generated, because WLS 6.1's WSDL processor isn't as complete as the
one in WLS 7.0 and Workshop :-)
Regards,
Mike Wooten
"Mel Werbow" <[email protected]> wrote:
I generated a WSDL file for a Microsoft com object and can easily write
a WL
web service that calls it using Workshop 7.0. But I need to deploy it
on a
WLS 6.1 server. (I was hoping that Workshop would simply generate the
source
code required for accessing the com object via soap, which I could then
cut
and paste into my own source, but it doesn't do that.)
Does anyone have an example of how to do this?

Message transmission from Wls 7 to Wls 8 and then to Wls10

Hi All,
We are currently doing a POC in which we are using Wls 7, Wls 8.1 and Wls 10 . The basic idea of the POC is that we need to post a message on Wls 7, and from Wls 7 the message should reach Wls 8.1 and inturn from Wls 8.1 it should reach Wls 10. For this communication to take place we have configured message bridges on the respective servers.
But the problem that we are facing is, we are not bale to transmit message from one Wls server to other, from Wls 7 to Wls 8 and also from 8 to 10.
We are gettin the following error:-
<Error> <Security> <090473> <ServerIdentity failed validation, downgrading to anonymous.>
Can anybody please help on this.
Regards,
Rakesh

If this is just a POC, you might try enabling Domain Trust on each of the domains (here is the 10.3 link, probably different in 8.1 and 7.0):
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/security/EnableTrustBetweenDomains.html
In a production environment there are other security implications for doing this willy nilly, that I recommend you read the docs and post questions in the WLS Security forum.

Calling db2 stored procedures from wls 8.1 sp2

Hi,
We noticed strange behaviour when moving customers applications from wls 6.1 to 8.1 sp2. We have a use case where we call db2 stored procedure two times (same prcedure) to make inserts to a database. The first time when procedure is called, everything goes smoothly but at the second time db2 claims that statement is not prepared and gives us sql error sql0518n.
We do see this error only if we use wls prepared statement cache and without cache (size=0) everything seems to work. We also did some db2 level tracing and noticed that statement is not prepared when using wls cache and db2 cannot execute statement which is not prepared....
Why I'm asking this? because this is the first time I had disable wls cache. We have used it and even optimized software performance using prepared statement cache in several projects before this.
Procedure call is done from web container lavel and no EJBs is used. We have tested the use case using autommit option and also committed firts transaction manually and closed connection.
We are using DB2 8.2 fp7 as a database and IBM level 2 JDBC driver without XA support. Honor global transactions support is on at a datasource.
Is this normal behaviour? Db2 problem or maybe WLS problem?
Regards,
Mika

I am getting the same exception about an assertion failed at weblogic.t3.srvr.T3Srvr.checkServerLock. Any ideas?

Error while calling ejb service call from BPM service

Hi,
We are using the Oracle 11.1.1.5.0
We are calling ejb service call from BPM service to update the data to Oracle database.
We are getting the below error when we executing the ejb service call from BPM Service.
<Error> <EJB> <BEA-010026> <Exception occurred du
ring commit of transaction Name=[EJB oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliver
yBean.handleCallback(java.lang.String,java.lang.String,java.lang.String,int,bool
ean)],Xid=BEA1-45B91984D57960994897(30845116),Status=Rolled back. [Reason=javax.
transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a p
articipant in two-phase commit. To force this participation, set the GlobalTrans
actionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhas
eCommit for the Data Source = EBSConnection],numRepliesOwedMe=0,numRepliesOwedOt
hers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[SOADataSource_
base_domain]=(ServerResourceInfo[SOADataSource_base_domain]=(state=rolledback,as
signed=soa_server1),xar=SOADataSource,re-Registered = false),XAServerResourceInf
o[ArCnTaskForms@EBSConnection@EBSConnection_base_domain]=(ServerResourceInfo[ArC
nTaskForms@EBSConnection@EBSConnection_base_domain]=(state=rolledback,assigned=s
oa_server1),xar=weblogic.jdbc.wrapper.JTSEmulateXAResourceImpl@fa5476,re-Registe
red = false),SCInfo[base_domain+soa_server1]=(state=rolledback),properties=({web
logic.jdbc.remote.EBSConnection=t3://192.168.10.114:8001, weblogic.transaction.n
ame=[EJB oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliveryBean.handleCallback(java.la
ng.String,java.lang.String,java.lang.String,int,boolean)]}),local properties=({w
eblogic.jdbc.jta.SOADataSource=[ No XAConnection is attached to this TxInfo ]}),
OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=soa
server1+192.168.10.114:8001+basedomain+t3+, XAResources={eis/tibjms/Queue, eis
/activemq/Queue, WLStore_base_domain_BPMJMSFileStore, WLStore_base_domain__WLS_s
oa_server1, eis/fioranomq/Topic, eis/jbossmq/Queue, eis/Apps/Apps, eis/websphere
mq/Queue, eis/AQ/aqSample, WLStore_base_domain_SOAJMSFileStore, eis/aqjms/Queue,
WSATGatewayRM_soa_server1_base_domain, eis/sunmq/Queue, eis/pramati/Queue, SSCo
nnectionDS_base_domain, eis/tibjms/Topic, eis/tibjmsDirect/Queue, eis/wls/Queue,
eis/tibjmsDirect/Topic, EDNDataSource_base_domain, eis/wls/Topic, eis/aqjms/Top
ic, RL3TST_base_domain, ArCnTaskForms@EBSConnection@EBSConnection_base_domain, S
OADataSource_base_domain, WLStore_base_domain_UMSJMSFileStore_auto_2},NonXAResou
rces={})],CoordinatorURL=soa_server1+192.168.10.114:8001+base_domain+t3+): weblo
gic.transaction.RollbackException: Could not prepare resource 'ArCnTaskForms@EBS
Connection@EBSConnection_base_domain
JDBC driver does not support XA, hence cannot be a participant in two-phase comm
it. To force this participation, set the GlobalTransactionsProtocol attribute to
LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source
= EBSConnection
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
TransactionImpl.java:1881)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
rverTransactionImpl.java:345)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
sactionImpl.java:239)
at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocal
Object.java:622)
at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetr
y(BaseLocalObject.java:455)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(Sess
ionLocalMethodInvoker.java:52)
at oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliveryBean_of8dk6_ICubeDelivery
LocalBeanImpl.handleCallback(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMes
sageHandler.handle(CallbackDeliveryMessageHandler.java:47)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(Dispatc
hHelper.java:140)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatc
hTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTas
k.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.transaction.xa.XAException: JDBC driver does not support XA, he
nce cannot be a participant in two-phase commit. To force this participation, se
t the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended)
or EmulateTwoPhaseCommit for the Data Source = EBSConnection
at weblogic.jdbc.wrapper.JTSXAResourceImpl.prepare(JTSXAResourceImpl.jav
a:83)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:1327)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:513)
at weblogic.transaction.internal.ServerSCInfo$1.run(ServerSCInfo.java:36
8)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
.>
<12 Oct, 2012 12:34:40 PM IST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-00
0000> <failed to handle message
javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot
be a participant in two-phase commit. To force this participation, set the Globa
lTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateT
woPhaseCommit for the Data Source = EBSConnection
at weblogic.jdbc.wrapper.JTSXAResourceImpl.prepare(JTSXAResourceImpl.jav
a:83)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:1327)
at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
sourceInfo.java:513)
at weblogic.transaction.internal.ServerSCInfo$1.run(ServerSCInfo.java:36
8)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<12 Oct, 2012 12:34:40 PM IST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-00
0000> <Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.
message.instance.CallbackDeliveryMessage"; the reported exception is: Error comm
itting transaction:; nested exception is: javax.transaction.xa.XAException: JDBC
driver does not support XA, hence cannot be a participant in two-phase commit.
To force this participation, set the GlobalTransactionsProtocol attribute to Log
gingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = EB
SConnection
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.
message.instance.CallbackDeliveryMessage"; the reported exception is: Error comm
itting transaction:; nested exception is: javax.transaction.xa.XAException: JDBC
driver does not support XA, hence cannot be a participant in two-phase commit.
To force this participation, set the GlobalTransactionsProtocol attribute to Log
gingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = EB
SConnection
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(Dispatc
hHelper.java:207)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatc
hTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTas
k.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
>
Could any body help on this issue.It is little bit urgent for us to resolve.
Thanks in advance.

Thanks Sudipto Desmukh,
The link is helpful me to resolve this issue.
Thanks,
Narasimha E

Calling EJB from Oracle via IIOP

I've spent the last two days trying to figure out how I can call an
EJB from an Oracle Stored Procedure. I first looked into WLS JNDI
(Using WLInitialContextFactory ), but my collegue recommended I look
into IIOP because it is "less proprietary". I was able to get a WL
example working that does a lookup on an EJB and "narrows" the IIOP
object...so it looked promissing, but then I tried to load the JAR
into Oracle and it said:
"referenced name javax/rmi/PortableRemoteObject could not be found"
So I did a quick check and it looks like this didn't come into
existance until JDK 1.3. By all accounts, Oracle 8.1.6 supports JDK 2
(1.2). So now I'm stuck. I've got a few examples about connecting to
the Oracle ORB using session-iiop, but I don't know if Weblogic will
be able to work with this. I don't know how I'd even call it because
the URL requires an Oracle SID...so now what? I see three options.
Please let me know which would be best (or another option that I'm
missing)
1. Try connecting with Weblogic "T3"
2. Try to get the right combination of classes loaded so 1.2 can work
like 1.3
3. Use the Oracle IIOP (I have no examples for connecting to other
ORBs so I have no idea how to lookup objects).
Chris

[email protected] (Chris Snyder) writes:
Andy Piper <[email protected]> wrote in message news:<[email protected]>...
[email protected] (Chris Snyder) writes:
1. Try connecting with Weblogic "T3"It depends on what version of WLS you are using. If you are using 6.1
then you are out-of-luck because this only support JDK 1.3.1.We are using WLS 6.1 and Oracle 8.1.6. There's got to be a way to
connect what is essentially a 1.2 JVM to a 1.3.1 JVM. On my way home
yesterday I was wondering if just straight RMI would work...although
we need to encrypt the connection. I've seen several people talk
about calling EJB's from stored procedures so it seems like there is a
way. Any other ideas?The really gross way is HTTP. In a previous life I had a customer use
oracle's HTTP plug-in to do this. You could probably invert the
problem also. I.e. write CORBA objects that sit inside an Orb hosted
in WLS and invoke on those using oracle's CORBA support. But HTTP is
probably the way most likely to work. You probably couldn't use RMI
over HTTP either - you would have to write a servlet that delegated to
your beans.
andy

Upgrading of WLS 6.1 from SP3 to SP5

Can anyone help me.
I am going to upgrade WLS 6.1 from SP3 to SP5.
How can i do this ?
From where do i download the ServicePack (SP5) ?
Is there someting i have to be aware off, about the license ?

Hi Paul
This is a JVM bug, Upgrade to 1.3.1_08 jvm from sun
Contact weblogic support for temporary workaround
Paul Wilson wrote:
We've a client running 6.1 sp2 on Solaris, who is experiencing
Weblogic hanging for roughly 10 minutes at a time. On resumption they
get:
####<06-May-03 16:28:50 BST> <Critical> <WebLogicServer> <edox>
<Mendel> <ListenThread> <system> <> <000204> <Failed to listen on port
80, failure count: 1, failing for 1,052,234,928 seconds,
java.net.SocketException: Software caused connection abort>
####<06-May-03 16:28:51 BST> <Notice> <WebLogicServer> <edox> <Mendel>
<ListenThread> <system> <> <000205> <After having failed to listen,
the server is now listening on port 80>
The last time it occurred, I got them to take a thread dump and all
but one execution thread and the listener threads were idle. One
execution thread was busy reloading (or loading) a class from the war.
I've asked them to ensure that the reload period is -1, but that
shouldn't cause a 10 minute hang; plus nothing had changed. Red
herring?
As an experiment I wrote a servlet that just blocks its execution
thread: after about a thousand calls to this on our dev box, we get
<May 14, 2003 5:45:42 PM BST> <Critical> <WebLogicServer> <Failed to
listen on port 6001, failure count: 3, failing for 1,052,930,739
seconds, java.net.SocketException: Too many open files>
AFAIK this means that we've run out of file descriptors. Our client
doesn't get this, so I don't think that is happening to them.
A number of people on weblogic.* groups reported similar problems
about a year ago, but without any really definitive resolutions.
Anyone solved this, even by upgrading?

Excessive LDAP Queries from WLS 6.0 SP2 RP3

We have an application served from WLS 6.0. Our current version of WLS is:
Service Pack 2 05/24/2001 11:55:28 #117037 RP3 for 6.0 SP2 02/21/2002 17:46:45
#167070
WLS has been configured to query an LDAP server for user authentication. The issue
we are experiencing is that WLS performs the LDAP query on EVERY page load in
the application. This is resulting in excessive calls to the LDAP server, and
increased response times.
We have attempted to change the caching realm settings such that the cache is
refreshed every 15 minutes as follows:
<CachingRealm AuthenticationCacheSize="601"
AuthenticationCacheTTLPositive="900" BasicRealm="X_LDAP"
CacheCaseSensitive="true" GroupMembershipCacheTTL="900"
Name="X_CACHE" UserCacheSize="601" UserCacheTTLPositive="900"/>
This has not improved the situation. What else could be causing the excessive
calls? How can we reduce the number of calls?
thanks
Bavini

"Bavini Naidoo" <[email protected]> wrote in message
news:3fc741c1$[email protected]..
>
We have an application served from WLS 6.0. Our current version of WLS is:
Service Pack 2 05/24/2001 11:55:28 #117037 RP3 for 6.0 SP2 02/21/200217:46:45
#167070
WLS has been configured to query an LDAP server for user authentication.The issue
we are experiencing is that WLS performs the LDAP query on EVERY page loadin
the application. This is resulting in excessive calls to the LDAP server,and
increased response times.
We have attempted to change the caching realm settings such that the cacheis
refreshed every 15 minutes as follows:
<CachingRealm AuthenticationCacheSize="601"
AuthenticationCacheTTLPositive="900" BasicRealm="X_LDAP"
CacheCaseSensitive="true" GroupMembershipCacheTTL="900"
Name="X_CACHE" UserCacheSize="601" UserCacheTTLPositive="900"/>
This has not improved the situation. What else could be causing theexcessive
calls? How can we reduce the number of calls?
Turn on weblogic.security.ldaprealm.verbose and see if the debugging output
indicates
the operation that the ldap realm is performing.

Calling ejb of wl6 from VAJ

Can i run inside visual age 3.0 a java application program that calls
EJB residing
on a weblogic 6.0 server?
thanks
OHAD

No, there are certain server features that require 1.3 to operate, but
it's not every weblogic class. JDK 1.2 is supported for clients of 6.0,
see:
http://e-docs.bea.com/wls/platforms/index.html#mix
-- Jim
OHAD wrote:
>
The problem is that the clients needs classes of weblogic server and
therefore
also require jdk 1.3. Isn't it correct?
OHAD
Jim Edwards-Hewitt wrote:
Probably. While the server requires JDK 1.3 (which VAJ doesn't have
yet), clients can run with earlier Java versions.
-- Jim
OHAD wrote:
Can i run inside visual age 3.0 a java application program that calls
EJB residing
on a weblogic 6.0 server?
thanks
OHAD

Calling EJB 3.0 from ALBPM

Hi,
I tried calling EJB 2.1 from ALBPM and it worked.
But I was nto able to call EJB 3.0.
Is calling EJB 3.0 supported from ALBPM 6.0.2?
If yes, how to call a business method in EJB 3.0?

Frank,
Thanks. The @LOB annotations are missing.
Create table with:
CREATE TABLE TestBlob (id number PRIMARY KEY, xmlCol BLOB);
INSERT INTO TestBlob VALUES(1, EMPTY_BLOB());
The following is the complete listing for the EJB 3 class generated from table TestBlob.
package ejb3;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.Id;
import javax.persistence.NamedQueries;
import javax.persistence.NamedQuery;
@Entity
@NamedQueries({
@NamedQuery(name = "Testblob.findAll", query = "select o from Testblob o")
public class Testblob implements Serializable {
@Id
@Column(nullable = false)
private Long id;
private byte[] xmlCol;
public Testblob() {
public Testblob(Long id) {
this.id = id;
public Long getId() {
return id;
public void setId(Long id) {
this.id = id;
public byte[] getXmlCol() {
return xmlCol;
public void setXmlCol(byte[] xmlCol) {
this.xmlCol = xmlCol;
}

Enterprise application conversion problem from WLS 10.3.0 to WLS 10.3.2

Hi all,
I'm posting this just to document a problem I had when converting an Enterprise Application from WLS 10.3.0 across to WLS 10.3.2 environment.
Upon deployment of the application I was getting this error:
Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.ApplicationParamBeanImpl@b720894d(/ApplicationParams[webapp.encoding.default])"
     at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:227)
     at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setApplicationParams(WeblogicApplicationBeanImpl.java:560)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:536)
     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
     at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:329)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:181)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
It turns out this was an issue with the META-INF/weblogic-application.xml having duplicate entries for the "webapp.encoding.default" parameter.
This obviously got duplicated when my app was re-imported into the Eclipse OPEP environment for WLS 10.3.2
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd">


<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
</wls:weblogic-application>
Removing the duplicate entry resolved this problem.
I hope this helps anyone else that experiences this issue.
Regards,
Paul

Below link might be helpful.
http://kr.forums.oracle.com/forums/thread.jspa?threadID=1049509&tstart=0
Regards,
Anandraj
http://weblogic-wonders.com/

Migrating apps from WLS 10.3.0 to SOA Suite 11g-- WLS 10.3.3

Hi,
We want to migrate our apps from WLS 10.3.0 to SOA Suite 11g-->WLS 10.3.3. While deploying the apps on WLS 10.3.3 (SOA Suite Domain 11g), it is throwing exception as below. This exception is common for almost all apps. Kindly help.
Caused by: weblogic.utils.compiler.ToolFailureException: Unable to load your custom module provider's module-factory-class com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory
at weblogic.application.compiler.FlowDriver.handleStateChangeException(FlowDriver.java:53)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:37)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169)
... 67 more
Caused by: weblogic.management.DeploymentException: Unable to load your custom module provider's module-factory-class com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory
at weblogic.application.internal.flow.CustomModuleHelper.loadModuleFactory(CustomModuleHelper.java:82)
at weblogic.application.internal.flow.CustomModuleHelper.initFactories(CustomModuleHelper.java:52)
at weblogic.application.utils.CustomModuleManager.createScopedCustomModules(CustomModuleManager.java:119)
at weblogic.application.utils.CustomModuleManager.<init>(CustomModuleManager.java:39)
at weblogic.application.compiler.WARModule.merge(WARModule.java:466)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:41)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
... 72 more

Below link might be helpful.
http://kr.forums.oracle.com/forums/thread.jspa?threadID=1049509&tstart=0
Regards,
Anandraj
http://weblogic-wonders.com/

JMS Bridge from WLS to OAS not working; automatic redirection to JMS Port

We have setup a JMS Bridge inbetween Weblogic Server 10.3.0 and Oracle App Server 10.1.3. In our test environment it is working fine. But, in LIVE, we are facing a problem. Firewall is there inbetween OAS and WLS.
1. OAS Admin port 6003, is blocked by firewall. So, from outside environment we can't connect to this port.
2. OAS Port 12401 (RMI Port) is not-blocked
3. OAS Port 12601 (JMS Port) is blocked by firewall
4. We created credential "JMS_USER" while configuring QueueConnFactory at OAS end and used it while setting up WLS JMS Bridge
We are using ormi://172.24.255.59:12401/default as Provider URL from Weblogic while creating JMS Bridge.
Problem
========
While connecting from WLS we are getting the following error from WLS end:
javax.jms.JMSException: Unable to create a connection to "apgst366/172.24.255.59:12,601" as user "JMS_USER".
     at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1050)
     at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1130)
     at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:132)
     at com.evermind.server.jms.EvermindQueueConnection.<init>(EvermindQueueConnection.java:71)
Question
=========
1) We are requesting for 12401; then why the JMS Port 12601 is being referred?
2) Is there any automatic redirection from OAS end?
3) Will unblocking the 12601 port by Firewall help?
Please help me, as this has become a burning issue for us.
Thanks in advance.

Can anybody please help me?

How to Call EJB from coldfusion

I need to call EJB that's created in JBoss from coldfusion.
I'm getting different errors depending on how I set the home object
and provider url.
If I prefix provider url with jnp://, then I get the
following error
The connection to the remote JNDI server on host jnp at port
1099 has failed (as have all backup hosts listed, if any) - please
verify that the server is running and the NamingService is
available
If I take the jnp out and keep just the ip address and port,
then i get the following error
null (no security manager: RMI class loader disabled).
So I'm not sure what the issue is and I haven't used this
feature before.
Here's my code

I tries to call custom EJBfrom custom component received
follwong error
ERROR [STDERR] javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException:
No ClassLoaders found for: com.mycom.myapp.action.interfaces.pm.ejb.PmFacadeRemote
(no security manager: RMI class loader disabled)]
any idea?
Thanks
YogLC

How can I call EJB from JSP/Servlets in iWS?

Hi!!
My JSP/Servlets are on iWS, and I deploy EJB on iAS.
In this case, I don't know how JSP/Servlet call EJb on iAS.
I'd like to know how I can set JNDI name in JSP/Servlet on iWS.
I will thank you if you give me a simple example source using JSP/Servlet
and EJB.
Thanks in advance!!!
- Park-

Park,
Why Are you running your JSP/Servlets in iWS instead of iAS? For whatever
reason,
look at the Converter sample from iAS. You will be doing RMI/IIOP in this
case and the sample explains in detail what to do.
hth,
-robert
"SungHyun, Park" <[email protected]> wrote in message
news:9jpfmt$[email protected]..
Hi!!
My JSP/Servlets are on iWS, and I deploy EJB on iAS.
In this case, I don't know how JSP/Servlet call EJb on iAS.
I'd like to know how I can set JNDI name in JSP/Servlet on iWS.
I will thank you if you give me a simple example source using JSP/Servlet
and EJB.
Thanks in advance!!!
- Park-

Call EJB in WLS 7.0SP2 from WLS 5.1 SP13

Similar Messages

Maybe you are looking for