Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?

Hello
Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?
Thanks

Hi a,
The short answer is no B or R yet, but stay tuned.
The somewhat longer story is that we are very much engaged with this
emerging binding standard to be used inconjuction with and beyond the
built-in types specified in JAX-RPC 1.1, it should be seen as a
compelling story for J2EE if JAXB could be used as a mechanism for
extending type mapping and offer a vendor neutral way to deal with user
defined types and to easily utilize user types that are developed for
XML applications in web services.
Concerning JAXR, I've experimented with SUN's RI using our UDDI server
and it works fine. As to the arguable merits of JAXR, all I can say is
that it is part of J2EE 1.4.
HTHs,
Bruce
a wrote:
>
Hello
Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?
Thanks

Similar Messages

Does BEA WebLogic 4.2.1 have JSP support

          If so what level
          Thank you


Ashish,
WLI 2.1 does not run on WLS 6.0, only WLS 6.1 SP1.
WLI 2.0 -> WLS 6.0 SP2
WLI 2.1 -> WLS 6.1 SP1
Cheers,
Chris
Ashish Agrawal wrote:
Hi David,
I downloaded WLI2.1 and installed it successfully.
I am using WLS 6.1 SP1 with WL2.1.
Please tell me does WL2.1 supports WLS 6.0 as I am getting error in deploying
a JCA adapter in WL2.1 + WLS 6.0 SP2.
The same adapter was successfully deployed using WL2.1 + WL6.1
Thanx in advance
Ashish Agrawal
ASAP Solutions.
"R J David Burke" <[email protected]> wrote:
Hi all,
BEA WebLogic Integration 2.1 is now available!
Read the press release at
http://www.bea.com/press/releases/2001/1022_portal_wli.shtml
Download the software for evaluation purposes from
http://commerce.bea.com/downloads/weblogic_integration.jsp
Regards, David Burke
ECI Product Management
BEA Systems, Ltd.

JAX-WS SOAPHandler can not deployed in BEA WLS 10.0 - Bug?

Hi,
currently I'm trying tp deploy a simple JAX-WS webservice with JAX-WS SOAPHandler in BEA WLS 10.0.
Therefore I provide a WAR file with the webservice and handler classes.
The SOAP Handler is defined in the webservice via the @HandlerChain(file="handler.xml")
My handler.xml looks as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<javaee:handler-chains xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<javaee:handler-chain>
<javaee:handler> <javaee:handler-class>com.bmw.wss.server.handler.AuthenticationHandler</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</javaee:handler-chains>
This handlers.xml is in the classpath within the WAR file.
If i trying to deploy this WAR file I always get the following exception from BEA WLS 10:
weblogic.application.ModuleException: [HTTP:101216]Servlet: "WSAATestService" failed to preload on startup in Web application: "wsaa-jaxwshandlertest.war".
java.lang.NullPointerException
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsHandlers(WseeRuntimeMBeanManager.java:108)
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsPort(WseeRuntimeMBeanManager.java:80)
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsMBean(WseeRuntimeMBeanManager.java:57)
I seems BEA WLS 10 has some problems with the JAX-WS SOAPHandler. I've deployed the same WAR-file on a Glassfish v2 server... without any problems!
Does anyone already used the JAX-WS handler mechanism in BEA WLS 10? Any ideas?
Thx.

Hi,
thx for your answer. Now I've found the problem. The BEA WLS don't accept null return value of the SOAPHandler method getHeaders(). If I return a dummy object everything wotks fine:
public Set<QName> getHeaders() {
return new TreeSet<QName>();
However I think this behaviour of the BEA WLS 10 is some kind of strange. Why do I have to implement the method getHeaders() if I don't want to use it.
Sun's Glassfish allows a null return value like expected.

BEA WLS and OraclePoolConnection

Hi,
Using the Oracle (9i) JDBC OCI driver, i am trying to get a proxy
connection going in BEA WLS.
If i define the connection pool using the Oracle classes in my program
everything is fine (i can get a connection and then proxy as as another
user). But if I define the pool using the Weblogic console then I have a
ClassCastException after doing a the lookup().
InitialContext initial = new InitialContext();
// HERE the classcastexception :
OracleOCIConnectionPool ds =
(OracleOCIConnectionPool) initial.lookup("jdbc/OracleOciDS");
oracle.jdbc.OracleConnection conn = null;
Properties p = new Properties();
p.setProperty(PROXY_USER_NAME, username);
conn = ds.getProxyConnection( PROXYTYPE_USER_NAME, p);
OracleOciDS is an OCI Connection pool (defined via the WLS console) and it's
working ok if I don't try to use the ProxyConnection mechanism of the JDBC
OCI.
If I do everything "by hand" without defining the Datasource in the BEA WLS console (using Oracle example), it's ok but the best would be to use the BEA console to do the administration and monitoring of the pool.
Thanks.
Real Gagnon from Quebec, Canada
* Looking for Java or PowerBuilder snippets ? Visit Real's How-to
* http://www.rgagnon.com/howto.html
* http://www.rgagnon.com/bigindex.html

Hi,
I am facing the same problem. Any luck on this?

What BEA WLS for Oracle 10.2.0.4?

Hi,
I'm going migration DB from 9.2.0.6 with BEA WLS 8.1 SP2 to 10.2.0.4 and I would like what's the certificate version of BEA WLS target.
Thanks!

You have already posted this in the correct forum - Upgrade Oracle DB from 9.2.0.6 to 10.2..0.4
This forum is meant for issues related to database upgrades - pl clarify your question in your other post. AFAIK, there is no co-relation between database upgrades and WLS upgrades - but I have no expertise in WLS
HTH
Srini

BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

Hello anybody,
learnt XA being necessary if more than one sql command in transaction, so I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now I receive the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
start() failed on resource 'OracleDB' Unexpected error during start for XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Hi Klaus,
if you want to implement a global transaction over two different JDBC Resource Managers
(update on both + 2PC) they have to be both XA compliant.
Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
and configuring a TXDataSource with "enable two-phase commit" = true (but only one
non-XA JDBC driver at a time can participate in a distributed transaction).
Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
transactions or distributed transactions without XA drivers as well (using a single
resource manager).
But if you want to update multiple resource managers in the same transaction using
EJBs, this is a "global" transaction, and WL server fully supports it.
But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
Sergi
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
>
Hi Sergi, hello world,
thanks a lot for this message. So the conclusion is that I hava no chance
at all
to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
a prerequisite
for EJB are XA-transactions.
Is this conclusion correct.
Many thanks again
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
distributed transaction (XA) features require version
Oracle8i release 8.1.6 or later of the Oracle server.
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hi Sergi,
1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
2.) I didn´t use a special driver but that that was delivered with thewls
server
in the package "weblogic.jar".
Could I enable you helping me with this information?
Best wishes
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
which
1) Oracle server version (I don't think it's a 8.3.2.)
2) Oracle JDBC driver version
are you you using ?
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hello anybody,
learnt XA being necessary if more than one sql command in transaction,so
I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now
I
receive
the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating itsSQL
Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction
branch
start() failed on resource 'OracleDB' Unexpected error during start
for
XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Autonomy integration in BEA WLS 9.2

I am trying to use the Autonomy portlets with BEA WLS 9.2. To do so I have followed the instructions at
http://edocs.bea.com/wlp/docs92/search/searchdev.html.
After successfully going through the indicated steps, the portlets do not deploy because of unmet dependencies for the following packages:
* com.autonomy.client
* com.autonomy.portlet
* com.autonomy.APSL
Where can I find the jar file that contains these packages?

Seems like you might have missed step 4 in the Autonomy Portlet installation instructions at http://edocs.bea.com/wlp/docs92/search/searchdev.html#wp1026209
These classes are found in AutonomyPiB.jar, which inside of the AutonomyPortlets.zip file. This jar file should be placed in your EAR's APP-INF/lib directory.
I hope this helps.

Does BEA have JDBC 2.0 compliant drivers for MS-SQL 7?

Does BEA have JDBC 2.0 compliant drivers for MS-SQL 7?Thanks in advance for your reply.

No. You might want to look at the MERANT JDBC drivers. They might help.
Shiva.
Anil Nair wrote:
Does BEA have JDBC 2.0 compliant drivers for MS-SQL 7?Thanks in advance for your reply.

Which BEA WLS version (+ service packs) used which JDK/JRockit-JDK version

Hello,
I'm looking for an overview about the JDK and JRockit JDK versions which are used in the different BEA WLS versions.
Specialy im interested on all BEA WLS server versions (incl. the different Service Packs) starting with version 7.0.
The overview should contain the following information if possible:
- BEA WLS Version Number including SP
- Plattform (Windows, HPUX, Solaris, ...)
- JDK version
- JRockit JDK version
Here is an example (??? = I do not know currently):
WLS vers. (incl. SP)|Plattf.|JDK vers.|JRockit vers.
7.0.1 |Solaris|??? |???
8.1.5 |Windows|1.4.2_08 |rockit81sp5_142_08
9.2 MP1 |HPUX |??? |???
Thanks a million if somebody could provide me those information. :-x
Cheers,
Markus Jessl

Please check :
http://edocs.bea.com/platform/suppconfigs/index.html
Jin

BEA WLS 6.0 Install Error

Thanks Charlie,
I hadn't subscribed to the 'install' group and therefore didn't know it
existed.
Mica
"Charlie Therit" <[email protected]> wrote in message
news:[email protected]..
It seems like this problem would be better addressed under the "install"
newsgroup as it doesn't seem to pertain to our Enterprise product.
We'll see what happens.
-Charlie
Mica Cooper wrote:
I am trying to install the WLS 6.0 Beta on a test machine and it fails.
As
soon as InstallAnywhere is done doing its 'preparing to install', the
install completely disappears. What should I do? I tried running the
install.exe but that fails also.
The test machine is a dual 500 NT4sp6 machine. It has a running copy of4.52
on it that I am going to transfer over.
Thanks,
Mica Cooper

ANNOUNCE: BEA WLS 6.0 Beta available

ANNOUNCE: BEA WLS 6.0 Beta available
We are proud to announce that the BEA WebLogic Server version 6.0 public
beta has begun. You can download the Beta at http://commerce.BEA.com. The
Beta is free and open to anyone.
More information can be found at the above URL.
Thanks,
Michael
Michael Girdley
BEA Systems Inc

Hi,
          why wasn't that email sent to weblogic.announce??
          I'm starting to believe weblogic.annouce is truly useless since neither
          service packs nor betas are announced there. What is the official way of
          monitoring releases of SP,etc. from bea?
          Mathieu
          Michael Girdley wrote:
          >
          > ANNOUNCE: BEA WLS 6.0 Beta available
          >
          > We are proud to announce that the BEA WebLogic Server version 6.0 public
          > beta has begun. You can download the Beta at http://commerce.BEA.com. The
          > Beta is free and open to anyone.
          >
          > More information can be found at the above URL.
          >
          > Thanks,
          > Michael
          >
          > --
          > ----
          > Michael Girdley
          > BEA Systems Inc

Com.bea.wls.EJBGenException

Hi All,
I have recently started to work on ejb's,I have created a project that has 2 modules
and ejb and a web module.
I am trying to use ANT to build my application.But here is the problem that I don't understand..
when I try to compile using ANT,I get the following error
com.bea.wls.EJBGenException:Error:Couldn't determine the type of the EJB 'xx.xx.path..XXBean'
Please make sure that :
-Its an Enterprise Java Bean
-Its superclass is in your classpath
Now as far as I can see I know that its an entity bean..
here is tags
* @ejbgen:entity
* ejb-name = "LoginBean"
* data-source-name = "DevDataSource"
* table-name = "LOGIN"
* prim-key-class="java.lang.Long"
* enable-call-by-reference = True
* default-transaction = Required
I know the parent class is accesible totherwise my IDE would scream that it can not extend it....
Please some one help me and elaborate what exactly is missing thats causing this

I have a totaly seprate question to put forward to you so I hope you dont mind. I was rather interested in this posting that you made sometime ago:
http://forum.java.sun.com/thread.jsp?thread=454215&forum=31&message=2070364
Is there any chance I could get a sample of the complete code you have done?
I would greatly appreciate it.
Many thanks -

Com.bea.wls.ejbgen.EJBGenException

Hi,
Am trying to generate sources for a message bean using ant generate task :
contents of generate task are:
<target name="generate">
<mkdir dir="${build}" />
<java classname="weblogic.tools.ejbgen.EJBGen" fork="yes" failonerror="yes" >
<arg value="-source"/>
<arg value="${sourceVersion}"/>
<arg value="-classpath"/>
<arg value="${java.class.path};${build}"/>
<arg value="-sourcepath"/>
<arg value="${source}"/>
<arg value="-d"/>
<arg value="${gen}"/>
     <arg value="-noValueClasses"/>
<arg value="-descriptorDir"/>
<arg value="${build}/META-INF"/>
<arg value="-ignorePackage"/>
     <arg line="source\com\communication\messagebeans\VIICMessageBean.java" />
<classpath>
<pathelement path="${java.class.path};${build}"/>
</classpath>
</java>
</target>
mesage beans has this annotation :
@MessageDriven( maxBeansInFreePool = "200",
destinationType = "javax.jms.Queue",
initialBeansInFreePool = "20",
transTimeoutSeconds = "0",
defaultTransaction = MessageDriven.DefaultTransaction.REQUIRED,
durable = Constants.Bool.FALSE,
               ejbName = "VIICMessageBean",
               destinationJndiName = "VIICQueue")
but am getting this error whie executing generate task:
[java] Exception in thread "main" com.bea.wls.ejbgen.EJBGenException: ejbName is a required attribute
[java] at com.bea.wls.ejbgen.Bean.createBeanSpecificTags(Bean.java:202)
[java] at com.bea.wls.ejbgen.Bean.<init>(Bean.java:127)
[java] at com.bea.wls.ejbgen.MessageDrivenBean.<init>(MessageDrivenBean
.java:29)
[java] at com.bea.wls.ejbgen.EJBFactory.createBean(EJBFactory.java:138)
[java] at com.bea.wls.ejbgen.EJBFactory.createBean(EJBFactory.java:99)
[java] at com.bea.wls.ejbgen.EJBGenSGen.initModule(EJBGenSGen.java:106)
[java] at com.bea.sgen.SGen.run(SGen.java:205)
[java] at com.bea.wls.ejbgen.EJBGen.main(EJBGen.java:212)
[java] at com.bea.wls.ejbgen.EJBGen.main(EJBGen.java:238)
[java] at weblogic.tools.ejbgen.EJBGen.main(EJBGen.java:21)
BUILD FAILED
D:\VIICApplication\build.xml:44: Java returned: 1
any help in resolving this issue will be greatly apprectiate.
Thanks

Just busted my brains on this same problem.
My solution was changing the value of ${sourceVersion} from "1.5 " into "1.5". That is removing the extra space from the source version variable.
Cheers,
Rene

XA transactions with JMS connector (with BEA WLS)

Hello,
are XA transactions supported by JMS connector when communicating with BEA WLS (version 8.1)?
Thanks
Tomas

Hi
Yes
Check this JMS FAQ
http://www.google.com/url?sa=t&ct=res&cd=1&url=https%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fgo%2Fportal%2Fprtroot%2Fdocs%2Flibrary%2Fuuid%2F604e2b64-e689-2910-64b3-ffd650f83756&ei=LcmERubLL4fgsALL6snWDw&usg=AFQjCNHbiooj-7G5g6w4tVVZQiRuQ5XQ_A&sig2=tpxbhUpIKR5oSe3aab8h4w
regards
krishna

BEA-149218 Attempted to report an exception to DRS and received an error

I am using Weblogic81 SP2. I have two Managed servers. I am trying to
start a managed server through Node Manager and I get the following
error
####<Nov 20, 2003 10:09:14 AM EST> <Error> <Deployer> <iolaus>
<iolaus110> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'>
<<WLS Kernel>> <> <BEA-149218> <Attempted to report an exception to DRS
and received an error.
NotificationException due to underlying exception
weblogic.drs.internal.InvalidStateException: Slave update for
DataIdentifier DataIdentfierID: 1 received a commitFailed() call - this
can only be called if update is in AwaitingCommitCompletion state
at
weblogic.drs.internal.statemachines.slave.SlaveState.commitFailed(SlaveState.java:89)
at
weblogic.drs.internal.DataReplicationService.notifyCommitFailure(DataReplicationService.java:375)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:581)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at
weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Does anybody know a solution or a work around please?
Dharmesh

Not sure if this applies to all instances, but in our case this issue was caused by an incorrect startup script for the admin node. We had neglected to include the -server flag. Adding the flag resolved the issue for us.

Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?

Similar Messages

Maybe you are looking for