Changing stdoutseverityLevel on weblogic 10.3

Hi,
I need to suppress application warnings while starting the server as we migrating application from 8.1 to 10.3. In 8.1 used stdoutseverityLevel as 16 and suppressed all warnings while starting the server. If i used stdoutseverityLevel as Error in weblogic 10.3 not able to see any notice messages also ( Ex : Server is in Running mode....)
Can we change stdoutseverityLevel for managed server in any startup class. Thanks.

Solved my problem by setting following parameter.
Environment --> Server1--> Logging --> Advanced -->
Set Logger severity properties as EJB=Error
While starting the server it was eliminated all EJB Warnings.
Thanks.

Similar Messages

Change password in Weblogic 10.3

Hi,
I follows change password of weblogic admin for change password,
I have 2 problems:
In step 8, please for me file name to edit WLS_PW (is startManagedWebLogic?)
In step 9, I cannot find gateway.ini file
If in step 8 and 9, I input password, for example password1 then everybody (that permission with my computer) can see my password?
Please help me in step 8 and 9 and explain why password not encryption in step 8 and 9
You are there 1 other way for change password in Weblogic?
Thanks

Hi,
I would suggest you to go through the below link to get the exact steps to change your Weblogic password.
http://weblogic-wonders.com/weblogic/2009/12/15/resetting-admin-username-password/
Hope above information helped you.
Regards,
Ravish Mody

Change locale messages weblogic

Anybody knows how can I change the messages, titles ... Of weblogic, has relationship with fmt locale?

Hi,
You can refer to change your AdminSever Username/Password...
http://weblogic-wonders.com/weblogic/2009/12/15/resetting-admin-username-password/
Thanks
Jay SenSharma

What needs to be changed to run Weblogic as a service and not as an application?

The server is running Windows 2000. Weblogic was installed on the server as an
application and not as a service. We need Weblogic to run as a service, could
someone please provide me with information on the easiest way of doing this, as
we can not re-install the Weblogic at this point. Any assistance would be greatly
appreciated.

hi.
Run the installNtService.cmd script.
Regards,
Michael
Mariet wrote:
The server is running Windows 2000. Weblogic was installed on the server as an
application and not as a service. We need Weblogic to run as a service, could
someone please provide me with information on the easiest way of doing this, as
we can not re-install the Weblogic at this point. Any assistance would be greatly
appreciated.--
Michael Young
Developer Relations Engineer
BEA Support

How to change system password in weblogic 8.1 ?

Hi,
Will you shed some lights on the steps of changing system password ? In weblogic console, I changed the password in Security->User and also in the remote start tab of admin server. When re-starting admin server, got this error : <Jun 17, 2005 1:36:59 PM PDT> <Critical> <Security> <l0065073> <doris811_admin> <main> <<WLS Kernel>> <> <BEA-090052> <Server installed as Windows NT service with incorrect password for user admin; The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.>. Any help is appreciated.
Jessie

I ran the installservice with the new password and received following errors when starting the service :
Program Error : beasvc.exe has generated errors and will be closed by Windows....
Microsoft Management Console : Could not start the beasvc doris_doris_admin service on local computer, Error 1067: The process terminated unexpectedly
Should I change password in weblogic console
security->user prior to re-install service with the new password ?
Any help is greatly appreciated.
Jessie

Weblogic Server 9.2 MP2 - Console hangs on activating changes

Hi,
I have migrated the adminserver to a different server.
After the migration, when we make changes in the weblogic console and try to activate the changes, the console hangs.
The threads are waiting at:
weblogic.management.provider.internal.ActivateTaskImpl
I have tried a few things which include using “Perform Asynchronous Activation”.
But they have not helped.
Environment Details
==============
Operating System : HP-UX Itanium
JDK Version : 1.5
Database Version : Oracle 10g
Any pointers will be highly appreciated.

facing the same problem of console hung
for weblogic 10.3 on Red hat Linux ES 4,
for every change console hangs and restart list shows all managed severs irrespective of changes.
I will appriciate any help to solve this.

Change indicator via trigger (Date/Timestamp)

I have set up triggers on all my tables to update the 'TIME_STAMP' field whenever a change is made to the row. It works flawlessly in sql*plus as well as in TOAD. However,if I insert a record using a ADF client I can view the record and the trigger provided value using sql*plus. If I update it using the ADF client the data becomes corrupted. I get a "ORA-01877: string is too long for internal buffer" when trying to view it with sql*plus or TOAD and if I dump() the column I get "Typ=180 Len=11: 0,0,0,0,0,0,0,0,0,0,0" (note: this is a dump when I had reset the datatype in my table and entity to a DATE).
The xml file for my entity follows:
Any Ideas?????
<?xml version='1.0' encoding='windows-1252' ?>
<!DOCTYPE Entity SYSTEM "jbo_03_01.dtd">
<Entity
Name="WbsUsers"
DBObjectType="synonym"
DBObjectName="WBS_USERS"
AliasName="WbsUsers"
BindingStyle="Oracle"
UseGlueCode="false"
RowClass="wbs.model.entity.WbsUsersImpl"
CollClass="wbs.framework.entity.EntityObjectCollImpl"
MsgBundleClass="wbs.model.entity.common.WbsUsersImplMsgBundle" >
<DesignTime>
<Attr Name="_isCodegen" Value="true" />
<Attr Name="_version" Value="10.1.2.17.96" />
<Attr Name="_codeGenFlag2" Value="Init|Access|Msg" />
<Attr Name="_superClass" Value="wbs.framework.entity.EntityObjectImpl" />
<Attr Name="_collSuperClass" Value="wbs.framework.entity.EntityObjectCollImpl" />
<AttrArray Name="_publishEvents">
</AttrArray>
</DesignTime>
<Attribute
Name="Id"
IsUpdateable="false"
Precision="32"
ColumnName="ID"
Type="java.lang.String"
ColumnType="CHAR"
SQLType="CHAR"
TableName="WBS_USERS"
PrimaryKey="true"
RetrievedOnUpdate="true"
RetrievedOnInsert="true" >
<DesignTime>
<Attr Name="_DisplaySize" Value="32" />
</DesignTime>
</Attribute>
<Attribute
Name="Username"
IsNotNull="true"
Precision="30"
ColumnName="USERNAME"
Type="java.lang.String"
ColumnType="VARCHAR2"
SQLType="VARCHAR"
TableName="WBS_USERS"
RetrievedOnUpdate="true"
RetrievedOnInsert="true" >
<DesignTime>
<Attr Name="_DisplaySize" Value="30" />
</DesignTime>
</Attribute>
<Attribute
Name="Fname"
IsNotNull="true"
Precision="50"
ColumnName="FNAME"
Type="java.lang.String"
ColumnType="VARCHAR2"
SQLType="VARCHAR"
TableName="WBS_USERS"
RetrievedOnUpdate="true"
RetrievedOnInsert="true" >
<DesignTime>
<Attr Name="_DisplaySize" Value="50" />
</DesignTime>
</Attribute>
<Attribute
Name="Lname"
IsNotNull="true"
Precision="50"
ColumnName="LNAME"
Type="java.lang.String"
ColumnType="VARCHAR2"
SQLType="VARCHAR"
TableName="WBS_USERS"
RetrievedOnUpdate="true"
RetrievedOnInsert="true" >
<DesignTime>
<Attr Name="_DisplaySize" Value="50" />
</DesignTime>
</Attribute>
<Attribute
Name="WbsRoleId"
IsNotNull="true"
Precision="32"
ColumnName="WBS_ROLE_ID"
Type="java.lang.String"
ColumnType="CHAR"
SQLType="CHAR"
TableName="WBS_USERS"
RetrievedOnUpdate="true"
RetrievedOnInsert="true" >
<DesignTime>
<Attr Name="_DisplaySize" Value="32" />
</DesignTime>
</Attribute>
<Attribute
Name="Email"
IsNotNull="true"
Precision="255"
ColumnName="EMAIL"
Domain="wbs.model.entity.emailDomain"
Type="wbs.model.entity.common.emailDomain"
ColumnType="VARCHAR2"
SQLType="VARCHAR"
TableName="WBS_USERS"
RetrievedOnUpdate="true"
RetrievedOnInsert="true" >
<DesignTime>
<Attr Name="_DisplaySize" Value="100" />
</DesignTime>
</Attribute>
<Attribute
Name="TimeStamp"
IsUpdateable="false"
ColumnName="TIME_STAMP"
Type="oracle.jbo.domain.Date"
ColumnType="DATE"
SQLType="TIMESTAMP"
TableName="WBS_USERS"
ChangeIndicator="true"
RetrievedOnUpdate="true"
RetrievedOnInsert="true" >
<DesignTime>
<Attr Name="_DisplaySize" Value="11" />
</DesignTime>
</Attribute>
<AccessorAttribute
Name="WbsRoles"
Association="wbs.model.entity.WbsUserRoleFkAssoc"
AssociationEnd="wbs.model.entity.WbsUserRoleFkAssoc.WbsRoles"
AssociationOtherEnd="wbs.model.entity.WbsUserRoleFkAssoc.WbsUsers"
Type="wbs.model.entity.WbsRolesImpl" >
</AccessorAttribute>
<AccessorAttribute
Name="WbsUserPeriods"
Association="wbs.model.entity.WbsUpUFkAssoc"
AssociationEnd="wbs.model.entity.WbsUpUFkAssoc.WbsUserPeriods"
AssociationOtherEnd="wbs.model.entity.WbsUpUFkAssoc.WbsUsers"
Type="oracle.jbo.RowIterator"
IsUpdateable="false" >
</AccessorAttribute>
<Key
Name="SysC0012735" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.Id" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="SYS_C0012735" />
<Attr Name="_checkCondition" Value=""ID" IS NOT NULL" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="SysC0012736" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.Username" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="SYS_C0012736" />
<Attr Name="_checkCondition" Value=""USERNAME" IS NOT NULL" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="SysC0012737" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.Fname" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="SYS_C0012737" />
<Attr Name="_checkCondition" Value=""FNAME" IS NOT NULL" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="SysC0012738" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.Lname" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="SYS_C0012738" />
<Attr Name="_checkCondition" Value=""LNAME" IS NOT NULL" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="SysC0012739" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.WbsRoleId" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="SYS_C0012739" />
<Attr Name="_checkCondition" Value=""WBS_ROLE_ID" IS NOT NULL" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="SysC0012740" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.Email" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="SYS_C0012740" />
<Attr Name="_checkCondition" Value=""EMAIL" IS NOT NULL" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="SysC0012741" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.TimeStamp" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="SYS_C0012741" />
<Attr Name="_checkCondition" Value=""TIME_STAMP" IS NOT NULL" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="WbsUsersEmailCheck" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.Email" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="WBS_USERS_EMAIL_CHECK" />
<Attr Name="_checkCondition" Value=""EMAIL" IS NOT NULL" />
<Attr Name="_isNotNull" Value="true" />
<Attr Name="_isCheck" Value="true" />
</DesignTime>
</Key>
<Key
Name="WbsUsersPk" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.Id" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="WBS_USERS_PK" />
<Attr Name="_isPrimary" Value="true" />
<Attr Name="_isDeferrableConstraint" Value="true" />
<Attr Name="_isInitiallyDeferredConstraint" Value="true" />
</DesignTime>
</Key>
<Key
Name="WbsUserRoleFk" >
<AttrArray Name="Attributes">
<Item Value="wbs.model.entity.WbsUsers.WbsRoleId" />
</AttrArray>
<DesignTime>
<Attr Name="_DBObjectName" Value="WBS_USER_ROLE_FK" />
<Attr Name="_referencedKey" Value="WBS_ROLES_PK" />
<Attr Name="_isForeign" Value="true" />
<Attr Name="_isDeferrableConstraint" Value="true" />
<Attr Name="_isInitiallyDeferredConstraint" Value="true" />
</DesignTime>
</Key>
</Entity>

Hi all,
I am a dope. I was having so may problems with the TIMESTAMP datatype in ADF and in TOAD I decided to just go with a DATE datatype for a change indicator. I did all the changes in the build scripts and model but forgot to run the build script so the errors I was getting were based on the old datatype.
BTW, Steve Muench had published a workaround to the issue in October that I found after I did all my changes. (http://radio.weblogs.com/0118231/2004/10/07.html#a394)

Why weblogic-cmp-rdbms-jar.xml.old gets created in Weblogic 7?

Hi all,
I use the build.bat file for creating the jar file
build.bat
==========
mkdir build build\META-INF
copy *.xml build\META-INF
@REM Compile EJB classes into the build directory (jar preparation)
javac -d build *.java
@REM Make a EJB jar file, including XML deployment descriptors
cd build
jar cv0f std_ejb_accountcmp.jar META-INF ejb
cd ..
@REM Run EJBC on jar file
java -classpath %WL_HOME%/lib/weblogic.jar weblogic.ejbc -convertDDs -verbose -keepgenerated -compiler javac build\std_ejb_accountcmp.jar d:\ejb_accountcmp.jar
=============================================================
Any ideas why when u unjar the jar file created for deployment in Weblogic 7.0, it creates an old copy of the xml files used
For example :
weblogic-ejb-jar.xml has weblogic-ejb-jar.xml.old
ejb-jar.xml has ejb-jar.xml.old
Why does it replace the weblogic-cmp-rdbms-jar.xml to weblogic-cmp-rdbms-jar.xml.old?
Rgds,
Seetesh

Hi Indra,
Thanks for ur post.
I have now renamed the weblogic-cmp-rdbms-jar.xml to weblogic-cmp20-rdbms-jar.xml and made the changes in the weblogic-ejb-jar.xml file in the type-storage parameter.
Now after executing the foll cmd
java ..... weblogic.ejbc old.jar new.jar
The new.jar file contains the generated stub/skeleton along with the additional old files for the 2 xml's ejb-jar.xml and weblogic-ejb-jar.xml.
Using the Weblogic builder utility, while opening the new.jar file, it discards the old xml deployment descriptors and creates new ones in its place.
Cld u give me some hints on using the Deployment tool? I use it to deploy the new.jar file.
Rgds,
Seetesh

Injest XML (JAXB) with Apache CXF on Weblogic 9.2.3

I have tried all of the suggestions I can find out there, but still can not get Weblogic and CXF to play along when injesting XML.
CXF is deployed and working in production.
Now that I want add a method to XML results, I declared with JAX-RS like this:
@POST
@Consumes( "application/xml")
@Path( "{order_id}/" + ANALYSE_PARAM )
public void reportResult( @PathParam( "order_id") int orderId, AnalyseResults analyseResults ) {
// NOTE: AnalyseResults is a JAXB object which we've created (i.e. mappings to Java provided)
However, when this method is invoked, I get this:
, I get this:
2011-10-26 14:02:46,766 WARN org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper - WebApplicationException has been caught : no cause is available
java.lang.IllegalArgumentException: Unable to access unsupported property javax.xml.stream.supportDTD
at weblogic.xml.stax.ConfigurationContextBase.check(ConfigurationContextBase.java:60)
at weblogic.xml.stax.ConfigurationContextBase.setProperty(ConfigurationContextBase.java:54)
at weblogic.xml.stax.XMLStreamInputFactory.setProperty(XMLStreamInputFactory.java:280)
at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:195)
at org.apache.cxf.staxutils.StaxUtils.getXMLInputFactory(StaxUtils.java:166)
at org.apache.cxf.staxutils.StaxUtils.createXMLStreamReader(StaxUtils.java:1164)
at org.apache.cxf.jaxrs.provider.JAXBElementProvider.unmarshalFromInputStream(JAXBElementProvider.java:214)
at org.apache.cxf.jaxrs.provider.JAXBElementProvider.doUnmarshal(JAXBElementProvider.java:180)
at org.apache.cxf.jaxrs.provider.JAXBElementProvider.readFrom(JAXBElementProvider.java:149)
at org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1013)
at org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:594)
at org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:559)
at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:230)
at org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118)
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:208)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:166)
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:113)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:184)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:163)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3244)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
I've done all the reading out there and taken all the suggestions:
- the woodstox and stax2 JARs are on my classpath
- the weblogic-application.xml file has been modified to include (a number of varieties have been tried):
<prefer-application-packages>
          <package-name>javax.jws.*</package-name>
          <package-name>javax.xml.*</package-name>
          <package-name>org.apache.*</package-name>
</prefer-application-packages>
I understand the root of the issue: the System properties / JAR files which are first read by Weblogic force the loading of the weblogic.xml.stax.XMLStreamInputFactory as "the way" to create StAX InputFactories.
But ... that Factory (for whatever reason) is incompatible with the way that CXF invokes it.
So ... is there ANY way to get WebLogic to allow CXF to use an alternate parser?

A support ticket (SR 3-4866617511) with Oracle has confirmed that the Weblogic StAX parser has a defect. A patch is available for WLS 10mp2 (and possibly for 9.2.4).
However, it is also possible to work around with a different StAX implementation.
Our choice was Woodstox and after putting the JARs (Woodstox and StaX2 mentioned below plus the xml-apis.jar and a xerces implementation JAR) in WEB-INF/lib and removing the changes to weblogic-application.xml (below), the magic was changing WEB-INF/weblogic.xml file (as described in http://download.oracle.com/docs/cd/E13222_01/wls/docs92/programming/classloading.html )to include:
<container-descriptor>
<servlet-reload-check-secs>-1</servlet-reload-check-secs>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
Why does this work?
By using the "prefer-web-inf-classes" node, the WL Classloader looks first in the JAR files of the Web Application (rather than it's own classes). In this case it finds the META-INF/services/javax.xml.stream.XMLInputFactory from the Woodstox JAR (rather than the one from weblogic.jar). Note how this is not just about loading classes from the WEB-INF/lib JARs first ... it also affects how Weblogic interacts with the JAR Service Provider Interface (SPI ... http://docs.oracle.com/javase/tutorial/sound/SPI-intro.html).
However, the XercesImpl.jar is becomes necessary because when running without it, the following error occurs:
javax.xml.datatype.FactoryFinder:Using context class loader: weblogic.utils.classloaders.ChangeAwareClassLoader@1a3c1d6 finder: weblogic.utils.classloaders.CodeGenClassFinder@488280 annotation: appsdirtbiis_dir@btb-ws/ic
javax.xml.datatype.FactoryFinder:found null in $java.home/jaxp.properties
javax.xml.datatype.FactoryFinder:loaded from fallback value: org.apache.xerces.jaxp.datatype.DatatypeFactoryImpl
<Nov 8, 2011 11:58:41 AM EST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@e02837 - appName: '_appsdir_tbiis_dir', name: '/btb-ws/ic', context-path: '/btb-ws/ic'] Root cause of ServletException.
java.lang.Error: javax.xml.datatype.DatatypeConfigurationException: Provider org.apache.xerces.jaxp.datatype.DatatypeFactoryImpl not found
Truncated. see log file for complete stacktrace
>
THAT issue is due to the fact that the javaee-5.0.5-api.jar's implementation of javax.xml.datatype.DatatypeFactory provides org.apache.xerces.jaxp.datatype.DatatypeFactoryImpl (rather than com.sun.org.apache.xerces.internal.jaxp.datatype.DatatypeFactoryImpl which is the fallback for the JDK 1.5 implementation that ships with WL 9.2) as the fallback value.
However, this mechanism is only used because none of the JARs (either in my app or in the standard WL distro) contain an file named "META-INF/services/java.xml.datatype.DatatypeFactory" which points to an existing Xerces implementation.
The xml-apis.jar was necessary because of unit test I was running on the package. YMMV with the xml-apis.jar.

Data source JNDI lookup fails in Weblogic 12.1.2

What is changed in the Weblogic 12.1.2 JNDI handling?
My EJB 2.1 application has been working fine with Weblogic versions up to 12.1.1, but with version 12.1.2 it is giving the following error at startup:
weblogic.application.ModuleException: javax.naming.NameNotFoundException: remaining name: comp/env/jdbc/DataSourceAlias
where jdbc/DatasourceAlias is the res-ref-name of the actual datasource named jdbc/APP_DATASOURCE which is set through the admin console.
The discovery of the datasource is performed by this piece of code :
ds = initialContext.lookup ("java:comp/env/" + refName)
This is what is failing with Weblogic 12. After some research I found out that in order for the datasource lookup to succeed, I have to :
1) ignore the subcontext "comp/env" and
2) use the actual JNDI name "jdbc/APP_DATASOURCE" instead of the reference "jdbc/DataSourceAlias"
However for the EJBs, nothing is changed, they are found in the comp/env subcontext.
Hope this helps someone, or let someone tell me how the migration to Weblogic 12.1.2 is supposed to be done.

Hi,
If it is war then try to apply following Patch 13893259.
Regards,
Kal

Using Axis2 webservices in WebLogic 10.3 - weblogic.xml

Hi,
I am facing an issue while trying the following:
I am using a webservices webapp in WebLogic 10.3. The web-app uses Axis2 for the webservices. To fix a logging issue, I had to add the following to my weblogic.xml:
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
After adding this change to the weblogic.xml- I am now getting an error in weblogic server log files, which is as follows -
]] Root cause of ServletException.
java.lang.LinkageError: loader constraint violation: when resolving interface method "org.apache.xmlbeans.SchemaTypeLoader.parse(Ljavax/xml/stream/XMLStreamReader;Lorg/apache/xmlbeans/SchemaType;Lorg/apache/xmlbeans/XmlOptions;)Lorg/apache/xmlbeans/XmlObject;"
the class loader (instance of org/apache/axis2/deployment/DeploymentClassLoader) of the current class, com/arcot/schemas/regfort/v2/types/GetArcotIdDocument$Factory, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, org/apache/xmlbeans/SchemaTypeLoader, have different Class objects for the type javax/xml/stream/XMLStreamReader used in the signature
I have tried over 6 hours of debugging but to no avail. If there are any suggestions anyone came make- as to the possible cause of this problem, it would be much appreciated!
thank you,
ronak

hi david,
thank you for the suggestion. The interesting thing is the error goes away as soon as I remove the weblogic.xml entry- and everything works fine. Except, when I dont have the prefer-web-inf-classes I get a log4j issue where my logs from different apps merge into a single file. That problem got resolved by adding the weblogic.xml change, but now it is this error.
Do you think there is anything that can be done in the weblogic-application.xml <prefer-application-packages> that might help in solving this problem?
thank you

Cmp bean - change to the database column not accepting

Hi,
I have a CMP Entity bean defined within the application. I had to change the column size of one of the table defined database. It was changed for 1 character to 3. But while inserting the records through the application the EJB still seems to consider the column with 1 character and not 3. I'm not sure if there is something to be changed in the weblogic-cmp-rdbms-jar.xml file. Can someone tell me if I have to change something, so that the entity bean recognizes the column size as 3 and not as 1 ?
thank you very much in advance.
-Harish

here is the rdbms-bean.jar.xml setting for the particular table. i do not think there is any special settings like dbms-column-type.
<weblogic-rdbms-bean>
<ejb-name>OrderItem</ejb-name>
<data-source-name>Order.DataSource</data-source-name>
<table-map>
<table-name>ORDER_ITEM</table-name>
<field-map>
<cmp-field>itemId</cmp-field>
<dbms-column>item_id</dbms-column>
</field-map>
<field-map>
<cmp-field>lenderPoolCode</cmp-field>
<dbms-column>lender_pool_code</dbms-column>
</field-map>
</table-map>
<weblogic-query>

Need help in upgrading weblogic portal 8.1.4 to 8.1.6

Hi,
I have recently upgraded weblogic portal domain for an application. I have used bsu.sh present at app/wlp814/utils/bsu.
I have one concern, if i run bsu.sh, its going to just update my weblogic portal 8.1.4 binaries and its not going to do any changes to my weblogic domain right. Because, i recently upgraded my weblogic portal domain from 814 to 816 and want to move it to production.
Location to binaries: /app/wlp814
Domain location: /app/user_projects/<domain>
I have successfully upgraded my staging server, but I want to move it to production, so its just ok to copy the binaries i.e wlp814 (which is upgraded to 8.1.6) from stage to my production server and i don't have to make any changes in production domains right.
Thanks in advance.

Can some one help me regarding this............................

Weblogic 8.1 server : Nullpointer exception and clascast exception ?

We are getting this Nullpointer and class cast exception from Weblogic and our application fails.Any idea why we are getting and how to resolve it.
After we restart the server everything is good,but it comes back after 4 or 5 days.
com.telus.api.TelusAPIException:
     at com.telus.provider.account.TMAccountManager.findSubscriberByPhoneNumber(TMAccountManager.java:743)
     at com.telus.offermanagement.cmd.subscriber.impl.RetrieveSubscriberByMobileCmdImpl.execute(RetrieveSubscriberByMobileCmdImpl.java:49)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
----- Caused by -----
java.lang.NullPointerException
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:290)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:248)
2009-08-17 11:45:40,265 DEBUG [ExecuteThread: '55' for queue: 'weblogic.kernel.Default'] com.telus.offermanagement.webapp.action.InitClientAction - Kowbility authentication start:23075
2009-08-17 11:45:40,388 ERROR [ExecuteThread: '55' for queue: 'weblogic.kernel.Default'] com.telus.offermanagement.webapp.action.InitClientAction - TelusAPI authentication failed:TelusAPIException:23075
com.telus.api.TelusAPIException:
     at com.telus.provider.TMProvider.<init>(TMProvider.java:348)
     at com.telus.provider.TMProvider.<init>(TMProvider.java:212)
     at sun.reflect.GeneratedConstructorAccessor163.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
----- Caused by -----
java.lang.ClassCastException
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:290)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:248)
     at com.telus.eas.utility.ejb.ReferenceDataHelper_cegd99_EOImpl_816_WLStub.authenticate(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Edited by: Manjit on Aug 21, 2009 3:51 PM

But here is the issue.We had same weblogic server installed before and after our deployment.The only thing that has changed is our marketing application.Hence wondering if our new changes has made weblogic to crash.Our older version of application has been running in the server for 6 years without any issue !!
Before I open a defect again Weblogic support I want to be 100% sure that our team (our application) is not responsible for crash.

Weblogic & EJB

Hi, everyone
I am a freshman .There is a problem to me .I need your help. thanks.
the detail as following:
InitialContext ctx=new InitialContext();
Object objRef = ctx.lookup("java:comp/env/Hello"); ---when i want to call ejb module and the application run to this line,it will throw a javax.naming.NamingException.
the detailed error info :
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:640)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:280)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at Test.main(Test.java:9)
others：
1.Weblogic is as ejb container.
2.There is no warning and error when I start weblogic server ,so i can confirm that there is no problem in the ejb module. And there is no problem in the file of "ejb-jar.xml" either.
<2004-8-23 03:53:27 PM> <Notice> <Application Poller> <149400> <Activating
application: appsdirHello_jar>
<2004-8-23 03:53:27 PM> <Notice> <Application Poller> <149404> <Activate ap
plication appsdirHello_jar on rickyserver - Running>
<2004-8-23 03:53:29 PM> <Notice> <Application Poller> <149404> <Activate ap
plication appsdirHello_jar on rickyserver - Completed>
THE ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!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>
     <description>
          This is Hello EJB example
     </description>
     <display-name>HelloBean</display-name>
     <enterprise-beans>
          <session>
               <display-name>Hello</display-name>
               <ejb-name>Hello</ejb-name>
               <home>HelloHome</home>
               <remote>Hello</remote>
               <ejb-class>HelloEJB</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
          </session>
     </enterprise-beans>
</ejb-jar>
question：
where is error? plz tell me, thanks very much.

Check your weblogic-ejb-jar.xml file and add following...
I am assuming you are using weblogic 8.1, if not then refer respective .dtd and make change accordingly.
<weblogic-enterprise-bean>
<ejb-name>Hello</ejb-name>
<local-jndi-name>Hello</local-jndi-name>
</weblogic-enterprise-bean>
Following is the sample code for lookup...
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, "t3://localhost:7001");
h.put(Context.SECURITY_PRINCIPAL, "username");
h.put(Context.SECURITY_CREDENTIALS, "password");
InitialContext initialContext = new InitialContext(h);
HelloLocalHome helloLocalHome = (HelloLocalHome)initialContext.lookup("Hello");
Note : You need to provide valid username and password of the weblogic.
h.put(Context.SECURITY_PRINCIPAL, "username");
h.put(Context.SECURITY_CREDENTIALS, "password");
Here dummy values are written; replace these values by valid username and password.
+ Mihir

Changing stdoutseverityLevel on weblogic 10.3

Similar Messages

Maybe you are looking for