Wls 8.1 sp4 jms store
Hi,
I need to move the jms store (for jms server) from file based to db based.
Server has:
Distributed Queue Members
Distributed Topic Members
Durable Topic Subscriber
Persistent Messages (potentially un-consumed) for Member Queues and Topics.
1Any recommendations on the approach for going abt. this ?
2.Any utilities I could use ?
Thanx'
Unless you can upgrade to a newer version, I know of no such utility - even then, I'm not sure I'd recommend it.
Your topic durable subscribers will be automatically recreated in the new store when they first attempt to connect but they won't have any messages (even if you could xfer the messages, a subscription ignores messages that are older than when the subscription was created anyway).
Depending on the use case, a solution that uses a messaging bridge or a hand-coded client might apply, where the bridge/client is used to xfer the message to a destination with a different name, and then is used to xfer the message on to the new destination.
Regardless, I still highly recommend simply draining all of your messages first, in which case the conversion becomes trivial.
Tom
Similar Messages
-
Persistent messages are not deleted from JMS store
Hi,
I'm experiencing some unexperienced JMS store behaviour with WLS 6.1 sp 4. I have
a servlet that posts a message to persistent JMS queue, which will be eventually
consumed by an MDB. Even though consumption is successful, the message is not
deleted from JMS store.
The message will be redelivered after server restart and is still not deleted
from JMS store. I verified this using file store and JDBC store. The messages
actually stay in the JMSSTORE table till doom's day.
I couldn't reproduce the case with WLS 6.1 sp 3. Exactly the application code
was used in all cases.
Subsequently I ran the same case with various ServerDebug DebugJMSXXX-flags set,
and discovered that WLS 6.1 sp3 logs 'asyncDeleteL' and 'ZZZDelete' for the consumed
message. WLS 6.1 sp4 didn't log this information.
I'm running WLS 6.1 on WinNT and Win2000.
Comments?
b r
Juha Räsänen
I've am having exactly this problem with wl 5.1....
I first saw it with 5.1 sp8....
In the release notes for 5.1 sp10, the following CR was fixed, which seemed
like it might have been my problem:
CR 45915
Fixed a JMS problem with messages begin left in the queue after received messages had been acknowledged. When a high volume of
messages was sent to a queue and a consumer retrieved those messages and sent them to another queue, the messages were not being
removed from the first queue even though they were acknowledged.
We upgraded to 5.1 sp12, and it appeared that the incidence of that problem was reduced.
However it still occurs once or twice a week, with 5.1 sp12....
My situation is a little bit different, in that my consumer retieves a message, and sends another
message to the SAME queue instead of another queue as described in the CR above...
It does happen under heavy load, etc....
Don't know if this has been reported and identified for wl 5.1 sp12 or not...
It is of course a really difficult to deal with bug....
Jason
"Juha Räsänen" <[email protected]> wrote in message news:[email protected]...
>
> Hi,
> I'm experiencing some unexperienced JMS store behaviour with WLS 6.1 sp 4. I have
> a servlet that posts a message to persistent JMS queue, which will be eventually
> consumed by an MDB. Even though consumption is successful, the message is not
> deleted from JMS store.
>
> The message will be redelivered after server restart and is still not deleted
> from JMS store. I verified this using file store and JDBC store. The messages
> actually stay in the JMSSTORE table till doom's day.
>
> I couldn't reproduce the case with WLS 6.1 sp 3. Exactly the application code
> was used in all cases.
>
> Subsequently I ran the same case with various ServerDebug DebugJMSXXX-flags set,
> and discovered that WLS 6.1 sp3 logs 'asyncDeleteL' and 'ZZZDelete' for the consumed
> message. WLS 6.1 sp4 didn't log this information.
>
> I'm running WLS 6.1 on WinNT and Win2000.
>
> Comments?
>
> b r
> Juha Räsänen
-
Problem with JMS stores in 8.1 sp2
Hi
Everytime I use the wizard to create a JMS server/Queue and a store I get this
kind of error. Am not able to figure out why this happens - why is the store assigned
to this
<WSReliableDeliveryPolicy Name="RMDefaultPolicy" Store="clsstore"
DefaultRetryCount="10" DefaultTimeToLive="60000"/>
guy? I never configured it! I am attaching the config.xml with this mail. Can
anyone tell me what I doing wrong?
error trace---------------------------
<Mar 10, 2004 12:37:18 PM EST> <Notice> <Management> <BEA-140005> <Loading domai
n configuration from configuration repository at C:\bea8\user_projects\domains\m
yclsdomain\.\config.xml.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Set
ting attribute Targets with values
myclsdomain:Name=merlin_1,Type=Server
for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested exception:
[javax.management.InvalidAttributeValueException: One of the stores configured
f
or JMS Server "clsjmsserver" is already configured for use by a reliable deliver
y policy on a different server (A JMS store may only be used once).]'
Reason: weblogic.management.configuration.ConfigurationException: Setting attrib
ute Targets with values
myclsdomain:Name=merlin_1,Type=Server
for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested exception:
[javax.management.InvalidAttributeValueException: One of the stores configured
f
or JMS Server "clsjmsserver" is already configured for use by a reliable deliver
y policy on a different server (A JMS store may only be used once).]
thanks
Anamitra
[config.xml]
Hi Dongbo
I didnt configure any WS reliable messaging - it got the entry by default and
am not sure whether this is a bug of the configure app or anything related to
JMS config. But this happens consistently - I have tried on several different
installation of WLS 8.1 sp2 and happens everywhere. What do I have to do to not
have it?
Also in ur reply I didnt quite get what u meant by this----------------
This would be fine if the JMSServer and
>the Web Services
>policy is on the same server. The problem is that they are on two different
>WebLogic
>Servers.
do let me know if this is a bug as all I am doing is setting up a Queue using
the config wizard.
thanks
Anamitra
Dongbo Xiao <[email protected]> wrote:
>Hi Anamitra,
>
>I don't know how you instructed the wizard, however, it looks like that
>the wizard
>somehow configured the same JMS file to be used for both a JMSServer
>and a policy for Web
>Service's Reliable Messaging. This would be fine if the JMSServer and
>the Web Services
>policy is on the same server. The problem is that they are on two different
>WebLogic
>Servers.
>Thanks,
>Dongbo
>
>Anamitra wrote:
>
>> Hi
>> Everytime I use the wizard to create a JMS server/Queue and a store
>I get this
>> kind of error. Am not able to figure out why this happens - why is
>the store assigned
>> to this
>>
>> <WSReliableDeliveryPolicy Name="RMDefaultPolicy" Store="clsstore"
>> DefaultRetryCount="10" DefaultTimeToLive="60000"/>
>>
>> guy? I never configured it! I am attaching the config.xml with this
>mail. Can
>> anyone tell me what I doing wrong?
>>
>> error trace---------------------------
>>
>> <Mar 10, 2004 12:37:18 PM EST> <Notice> <Management> <BEA-140005> <Loading
>domai
>> n configuration from configuration repository at C:\bea8\user_projects\domains\m
>> yclsdomain\.\config.xml.>
>> ***************************************************************************
>> The WebLogic Server did not start up properly.
>> Exception raised: 'weblogic.management.configuration.ConfigurationException:
>Set
>> ting attribute Targets with values
>> myclsdomain:Name=merlin_1,Type=Server
>> for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested
>exception:
>>
>> [javax.management.InvalidAttributeValueException: One of the stores
>configured
>> f
>> or JMS Server "clsjmsserver" is already configured for use by a reliable
>deliver
>> y policy on a different server (A JMS store may only be used once).]'
>> Reason: weblogic.management.configuration.ConfigurationException: Setting
>attrib
>> ute Targets with values
>> myclsdomain:Name=merlin_1,Type=Server
>> for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested
>exception:
>>
>> [javax.management.InvalidAttributeValueException: One of the stores
>configured
>> f
>> or JMS Server "clsjmsserver" is already configured for use by a reliable
>deliver
>> y policy on a different server (A JMS store may only be used once).]
>> ***************************************************************************
>>
>> ----------------------------------------------------------------------
>>
>> thanks
>> Anamitra
>>
>> ------------------------------------------------------------------------
>> Name: config.xml
>> config.xml Type: XML Document (text/xml)
>> Encoding: base64
>
-
Configuring JMS Store Data Source
Hi all,
Im relatively new over here. Sorry if this' a duplicate post.
Based on the Oracle Communications Unified Management Inventory Installation Guide Im currently in the post-installation phase: Connecting the UIM Web Service Interface to a Remote Application
+"For detailed instructions for creating SAF queues and topics between UIM and OSM, see Knowledge Article 1431235.1 - Configuring WebLogic Resources for OSM Integration+
+With ASAP And UIM On Different Domains on the My Oracle Support web site: https://support.oracle.com+
+This article is applicable to any remote application that uses a WebLogic JMS server to send and receive Web Service messages."+
Ive found the said article entitled "Configuring OSM-UIM-ASAP JSM Messaging". Under "UIM Server Configuration", the resources configured were: JMS store = uim_oss_jms_store and JMS server name = uim_oss_jms_server
My question then is, to create JMS store, Im supposed to create the data source for that as well right? May I know the properties of the data source to be created? Right now there's few pre-created data sources i.e. CMDSInventoryPersistentDS, InventoryDataSource, InventoryMapDataSource, InventoryTxDataSource,InvJMSPersistentDS,mds-commsRepository,and UIMAdapters. Kinda scoured the internet for details but to no avail. For your information, Ive installed WebLogic 10.3.5 (11g) and UIM 7.2.0.0.
Do advise. Thanks a bunch
AmosA JDBC store is a JDBC-accessible database for storing subsystem data, such as persistent JMS messages and durable subscriber information.
If you would want to use JDBC persistance for JMS,then you would either need to create a new Datasourec or use an existing/pre-configured datasource.
Please refer to the below links:-
http://docs.oracle.com/cd/E15051_01/wls/docs103/config_wls/store.html#wp1135046
http://docs.oracle.com/cd/E15051_01/wls/docs103/ConsoleHelp/taskhelp/stores/CreateJDBCStores.html
As far as the properties goes while configuring a Datasource and tables required for JDBC store,please refer to the below link and specifically the section "Guidelines for Configuring a JDBC Store":-
http://docs.oracle.com/cd/E15051_01/wls/docs103/config_wls/store.html#wp1142969
hope this helps!
-Sandeep -
JMS Store Exception with MS SQL Server in Win2K
Hello,
All my messages are persisted in some PTP queues within JMSStore and JMSState
in MSSQL Server.
When WLS is restarted, I have the following exception, any idea?
<07-Oct-02 16:28:05 BST> <Info> <JMS> <JMSServer "JMSServer", Opening JDBC store
tables "JMSStore" and "JMSState" using connection
pool "MyCMSDBConnectionPool".>
<07-Oct-02 16:28:06 BST> <Alert> <JMS> <JMSServer "JMSServer", store failed to
open, java.io.IOException: JMS JDBC store, connecti
on pool = <MyCMSDBConnectionPool>, prefix = <null>: recover
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
not re-read row data for column 1.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.validateColumnIndex(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
at weblogic.jms.store.JDBCIOStream.doRecoverBodies(JDBCIOStream.java:800)
at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:706)
at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:915)
at weblogic.jms.store.JMSStore.recover(JMSStore.java:138)
at weblogic.jms.backend.BEStore.open(BEStore.java:182)
at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy0.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy53.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:48
0)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
Hmmm. Is this a new driver version, or just coincidence? -- The same problem
was posted in this newsgroup last week. I'm beginning to suspect
there is a bug in the MS driver.
Anyhow, please contact BEA customer support. Meanwhile, the work-around is
to use WebLogic's driver.
Tom, BEA
Thierry wrote:
> Hello,
>
> All my messages are persisted in some PTP queues within JMSStore and JMSState
> in MSSQL Server.
>
> When WLS is restarted, I have the following exception, any idea?
>
> <07-Oct-02 16:28:05 BST> <Info> <JMS> <JMSServer "JMSServer", Opening JDBC store
> tables "JMSStore" and "JMSState" using connection
> pool "MyCMSDBConnectionPool".>
> <07-Oct-02 16:28:06 BST> <Alert> <JMS> <JMSServer "JMSServer", store failed to
> open, java.io.IOException: JMS JDBC store, connecti
> on pool = <MyCMSDBConnectionPool>, prefix = <null>: recover
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
> not re-read row data for column 1.
> at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
> at com.microsoft.jdbc.base.BaseResultSet.validateColumnIndex(Unknown Source)
> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
> at weblogic.jms.store.JDBCIOStream.doRecoverBodies(JDBCIOStream.java:800)
> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:706)
> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:915)
> at weblogic.jms.store.JMSStore.recover(JMSStore.java:138)
> at weblogic.jms.backend.BEStore.open(BEStore.java:182)
> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
> at weblogic.jms.JMSService.createBackEnd(JMSService.java:906)
> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1273)
> at weblogic.jms.JMSService.addDeployment(JMSService.java:1169)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy0.updateDeployments(Unknown Source)
> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
> at java.lang.reflect.Method.invoke(Native Method)
> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> at $Proxy53.start(Unknown Source)
> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:48
> 0)
> at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> at weblogic.management.Admin.finish(Admin.java:644)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> at weblogic.Server.main(Server.java:35)
-
JDBC connection pool failures when used by JMS stores
We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
a JMS Store.
<JDBCConnectionPool Name="sybaseJMSPool"
Targets="cluster00"
InitialCapacity="2"
MaxCapacity="10"
DriverName="com.sybase.jdbc2.jdbc.SybDriver"
Properties="[email protected]@;[email protected]@;charset=utf8"
URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
(note that the @xxx@ string are replaced by actual values).
We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
We deployed this configuration on a number of environments (testing, staging,
..). The actual hardware and network configuration is different for the different
system, but the WebLogic domain stays the same regarding this issue.
On the test system we frequently get the following exceptions:
<Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
<ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
<JMSServer "JMSServer00", store failure while writing message for topic
OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
<sybaseJMSPool>, prefix = <JMS00>: write failed
java.sql.SQLException: JZ006: Caught IOException:
com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
closed.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
(ErrorMessage.java:715)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
(SybStatement.java:1625)
at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
(SybPreparedStatement.java:91)
at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
(P6LogPreparedStatement.java:179)
at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
.>
java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
= <JMS00>: write failed
java.sql.SQLException: JZ006: Caught IOException:
com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
closed.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
(ErrorMessage.java:715)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
(SybStatement.java:1625)
at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
(SybPreparedStatement.java:91)
at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
(P6LogPreparedStatement.java:179)
at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.jms.store.JDBCIOStream.throwIOException
(JDBCIOStream.java:1213)
at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Before that this message appeared:
<Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
<node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
<Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
received a message over an uninitialized connection: 'JVMMessage from: 'null'
to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
offset: '34'''>
This problem did not occur on another system which was used during a 2 day stress
testing session.
It seems that the problem occurs after a period in which no user request where
made. The user requests trigger EJB's that start sending JMS messages.
When the problem occurs, the JMS messaging systems seems to lock up as no messages
are received anymore by the different listeners (MDBs).
Undeploying and redeploying the JBDC connection pool solves the problem. This
solution is unacceptable in case of a production system.
A similarly defined connection pool, which is used by the EJBs to make database
connection, does not manifest this problem.
<JDBCConnectionPool Name="sybasePool"
Targets="cluster00"
InitialCapacity="10"
CapacityIncrement="5"
MaxCapacity="50"
PreparedStatementCacheSize="150"
DriverName="com.sybase.jdbc2.jdbc.SybDriver"
Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
The JDBC connection pool is used as follows by the JDBC store
<JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
<JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
<JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
<JMSTopic JNDIName="ADIS.Status"
Name="StatusTopic" RedeliveryDelayOverride="300000"/>
<JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
Name="OrderChangeTopic" RedeliveryLimit="3"/>
</JMSServer>
Turning on the "Test Reserved Connection" with a appropriate test table does not
help.
Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
can be related to network problems. Nevertheless the connection pool should be
able to cope with this.
Can you provide any solution for this ? Or give us hints what can cause the problem
Zhenhao Qi wrote:
thanks! Joe.
The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
allowances for one thread to interrupt a second thread's JDBC call. If we
transmit your timeout request by calling setQueryTimeout() on the oracle
statement, and if you have a weblogic-controlled transaction we call
Statement.cancel() on any ongoing statement, we end up relying on whether
the Oracle driver implements and responds to those calls.
Are you doing weblogic-controlled transactions? Are you/can you
call Statement.setQueryTimeout() on your statements, or are these
generated JDBC queries?
If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
we have some other debug avenues. This would be good even if you really
want to use the thin driver, because we will do the same JDBC calls to
either driver, and the debug would prove (if) we set up a query timeout
and if we call cancel(). If we do, then we can know that it is the Oracle
driver failing in these regards.
Joe -
Using MySQL DB on Weblogic 10.3.2 for JMS Store and etc.
Hi,
I am planning to use MySQL DB w Weblogic 10.3.2 server.
I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
Can anyone please help me understand any serious issues or considerations of this combination?
Thanks
SagarHi,
I am planning to use MySQL DB w Weblogic 10.3.2 server.
I am planning to use Persistent JMS Destinations and planning to use MySQL Datasource for JMS store.
Can anyone please help me understand any serious issues or considerations of this combination?
Thanks
Sagar -
CR183190 in WLS 8.1 SP4
Hi.
I'm using WLS 8.1 SP4 (with CR132575) and just ran into a problem with my datasources using the BEA's DB2 driver(Type 4 XA). The error I receive is:
[BEA][DB2 JDBC Driver]No more available statements. Please recreate your package with a larger dynamicSections value.
When searching for this using Google I found out that this was a known issue in SP3 and SP4: CR183190 (http://e-docs.bea.com/wls/docs81/notes/issues.html#1293456). However, another page (http://e-docs.bea.com/wls/docs81/notes/resolved_sp04.html#1862094) says that it is resolved in SP4.
Can anyone confirm whether or not it should be resolved? And if it is resolved, what else could be causing the error message I am receiving.
/Michaelgarbage66 wrote:
Hi,
I would really appreciate if you could send me the CR.
My specifications:
WebLogic Temporary Patch for CR132575 01/05/2004 13:00:03
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
Regards,
MichaelHi. Contact support and get the very latest 3.4 driver package.
There was a problem in the DB2 driver that could cause that.
If that doesn't help, let me know and I'll have another
suggestion.
Joe
j ----
o ----
e ----
b
e
a
c
o
m -
Use Windows Performance Monitor on WLS 6.1 SP4?
Hi,
I wonder whether it's possible to use the Windows Performance Monitor to monitor WLS 6.1 SP4 performance counters.
I would like this obviously to be able to save counters from WLS and Windows in one file for later analysis.
If it's possible. What do I have to do to make it work? I have just installed WLS 6.1 incl SP4.John <[email protected]> wrote:
I wonder whether it's possible to use the Windows Performance Monitor
to monitor WLS 6.1 SP4 performance counters.No, not as far as I know. WLS performance counters cannot "talk" with the Win32
performance monitoring APIs or native WMI. It's a technically difficult challenge
to link these two components together (requiring knowledge of NT internals and
such) .
You may wish to contact a third-party vendor that provides J2EE black-box monitoring
and collection software. Most allow for "offline" analysis, too.
Brian J. Mitchell
Systems Administrator, TRX
email: [email protected]
office: +1 404 327 7238
mobile: +1 678 283 6530 -
Hello,
We sometimes experience application hang when a user logon due to all threads waiting to get connection from UDB server. Any help is appreciated.
Environment
App Server: WLS 6.1 SP4
Database: DB2 UDB 7.1
JDBC Adapter: Type 2 IBM Driver (COM.ibm.db2.jdbc.app.DB2Driver)
We have setup connection pool and a TX data source.
Connection pool related config.xml
<JDBCConnectionPool CapacityIncrement="1"
DriverName="COM.ibm.db2.jdbc.app.DB2Driver" InitialCapacity="40"
LoginDelaySeconds="1" MaxCapacity="50" Name="LPDSS_DB2_POOL1"
PreparedStatementCacheSize="100"
Properties="user=xxx;password=xxx;language=C"
RefreshMinutes="999999" ShrinkingEnabled="false"
Targets="ms1" TestConnectionsOnRelease="false"
TestConnectionsOnReserve="true" TestTableName="SYSIBM.SYSDUMMY1" URL="jdbc:db2:xxxx"/>
The thread dump analysis shows that getconnection() call waiting for a lock (waiting for monitor entry) and java.weblogic.Admin RESET_POOL doesn't work either. The call never returns.
"ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x494e78 nid=0x1b waiting for monitor entry [0xaf580000..0xaf5819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '15' for queue: 'default'" daemon prio=5 tid=0x495970 nid=0x1c waiting for monitor entry [0xaf481000..0xaf4819d8]
at weblogic.common.internal.ResourceAllocator.reset(ResourceAllocator.java:848)
at weblogic.common.internal.ResourceAllocator_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
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)
"ExecuteThread: '16' for queue: 'default'" daemon prio=5 tid=0x496468 nid=0x1d waiting for monitor entry [0xaf37f000..0xaf3819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:569)
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:117)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:78)
"ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x497568 nid=0x1e waiting for monitor entry [0xaf280000..0xaf2819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x494380 nid=0x1a waiting for monitor entry [0xaf680000..0xaf6819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x493888 nid=0x19 waiting for monitor entry [0xaf780000..0xaf7819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
Exception in JDBC log shows there is a communication problem.
SQLException: SQLState(40003) vendor code(-30081)
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL30081N A communication error has been detected. Communication protocol being
used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "xx.xx.xx.xx". Communication function dete
cting the error: "recv". Protocol specific error code(s): "145", "*", "*". SQLSTATE=08001
---------------------------------------------------ganesh narayanan wrote:
Hello,
We sometimes experience application hang when a user logon due to all threads waiting to get connection from UDB server. Any help is appreciated.
Environment
App Server: WLS 6.1 SP4
Database: DB2 UDB 7.1
JDBC Adapter: Type 2 IBM Driver (COM.ibm.db2.jdbc.app.DB2Driver)
We have setup connection pool and a TX data source.
Connection pool related config.xml
<JDBCConnectionPool CapacityIncrement="1"
DriverName="COM.ibm.db2.jdbc.app.DB2Driver" InitialCapacity="40"
LoginDelaySeconds="1" MaxCapacity="50" Name="LPDSS_DB2_POOL1"
PreparedStatementCacheSize="100"
Properties="user=xxx;password=xxx;language=C"
RefreshMinutes="999999" ShrinkingEnabled="false"
Targets="ms1" TestConnectionsOnRelease="false"
TestConnectionsOnReserve="true" TestTableName="SYSIBM.SYSDUMMY1" URL="jdbc:db2:xxxx"/>
The thread dump analysis shows that getconnection() call waiting for a lock (waiting for monitor entry) and java.weblogic.Admin RESET_POOL doesn't work either.
The call never returns.
>
We'd need to see all the threads, preferably before you try (repeatedly it seems) to
reset the pool. There may well be problems with the IBM driver and DBMS...
Joe
"ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x494e78 nid=0x1b waiting for monitor entry [0xaf580000..0xaf5819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '15' for queue: 'default'" daemon prio=5 tid=0x495970 nid=0x1c waiting for monitor entry [0xaf481000..0xaf4819d8]
at weblogic.common.internal.ResourceAllocator.reset(ResourceAllocator.java:848)
at weblogic.common.internal.ResourceAllocator_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
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)
"ExecuteThread: '16' for queue: 'default'" daemon prio=5 tid=0x496468 nid=0x1d waiting for monitor entry [0xaf37f000..0xaf3819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:569)
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:117)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:78)
"ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x497568 nid=0x1e waiting for monitor entry [0xaf280000..0xaf2819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x494380 nid=0x1a waiting for monitor entry [0xaf680000..0xaf6819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x493888 nid=0x19 waiting for monitor entry [0xaf780000..0xaf7819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
Exception in JDBC log shows there is a communication problem.
SQLException: SQLState(40003) vendor code(-30081)
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL30081N A communication error has been detected. Communication protocol being
used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "xx.xx.xx.xx". Communication function dete
cting the error: "recv". Protocol specific error code(s): "145", "*", "*". SQLSTATE=08001 -
WLS 6.1 SP4- SP5/SP6
Good morning,
I tried re-running weblogic.ejbc on my ejb-jar files and it failed with the same
error. I am using Javlin for a transactional cache with WebLogic and I don't think
it knows anything about the getLoadUser and setLoadUser methods. I had the same
problem when I went to WS 6.1 SP4 with the methods __WL_needsRemove and __WL_setNeedsRemove
but I was able to implement those inside my bean code and everything worked. I
figured I could just implement the __WL_getLoadUser and __WL_setLoadUser and I
would be okay. I implemented them with an empty setLoadUser and tried various
returns for getLoadUser. After implementing them, I am able to access from the
database with no problem, but when I try to create beans, the program throws a
NullPointerException. I have not seen any information on what these two methods
are supposed to do but it seems they first show up in SP5.
Thanks,
Dan
Rob Woollen <[email protected]> wrote:
Does re-running weblogic.ejbc on your ejb-jar fix the problem?
-- Rob
Dan Shelton wrote:
Hello All,
I am trying to deploy some EJBs from a system with WS 6.1 SP4 ontoa system with
SP5/SP6 and get an error stating that the bean has to be declared abstractbecause
the methods __WL_getLoadUser() and __WL_setLoadUser(..) are not implemented.These
two methods are listed in the WLEnterpriseBean interface in weblogic.ejb20.interfaces
for SP5/SP6 but not in SP4. Anybody know what these methods are supposedto do?
I have found no information at all on these. I have a case in but figuredsomeone
might already know.
Have a good one,
DanKeith,
This message gives you exact reason. Double-check classpaths
used the start weblogic and to run ejbc. There may be something
left from previous installations.
Regards,
Slava Imeshev
"Keith" <[email protected]> wrote in message news:3fb0337c$[email protected]..
>
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
Keith -
WLS 6.1 SP4 Recompilation Error
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
KeithKeith,
This message gives you exact reason. Double-check classpaths
used the start weblogic and to run ejbc. There may be something
left from previous installations.
Regards,
Slava Imeshev
"Keith" <[email protected]> wrote in message news:3fb0337c$[email protected]..
>
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
Keith -
Problem while updating record in WLS 6.1 sp4
We have been using toplink in our application with Weblogic 6.1. We have not faced any problems after migrating to TopLink oracle release 9.0.3 while deploying on WLS 6.1 sp1 or sp2. However when we deploy on WLS 6.1 sp4, we get a 'invalid column name' exception when trying to update a record. The search query does not throw any exception, only the update query is throwing exception. We use external transaction controller. the stack trace is below -
2002-11-27 11:56:25,763 ERROR com.pws.ubiquity.pr.business.TransactionTypeFacade - Error while commiting transaction (creating TransactionType):LOCAL EXCEPTION STACK:
EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-00904: invalid column name
INTERNAL EXCEPTION: java.sql.SQLException: ORA-00904: invalid column name
ERROR CODE: 904
at oracle.toplink.exceptions.DatabaseException.sqlException(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeNoSelect(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.insertObject(Unknown Source)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(Unknown Source)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedWrite(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedInsert(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(Unknown Source)
at oracle.toplink.queryframework.WriteObjectQuery.executeCommit(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.executeWrite(Unknown Source)
at oracle.toplink.queryframework.WriteObjectQuery.execute(Unknown Source)
at oracle.toplink.queryframework.DatabaseQuery.execute(Unknown Source)
at oracle.toplink.publicinterface.Session.internalExecuteQuery(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.internalExecuteQuery(Unknown Source)
at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
at oracle.toplink.internal.sessions.CommitManager.commitAllObjects(Unknown Source)
at oracle.toplink.publicinterface.Session.writeAllObjects(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.commitToDatabase(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.issueSQLbeforeCompletion(Unknown Source)
at oracle.toplink.jts.AbstractSynchronizationListener.beforeCompletion(Unknown Source)
at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:551)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:88)
at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:982)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1506)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:215)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:247)
at com.pws.ubiquity.pr.business.TransactionTypeFacade.addTransactionType(TransactionTypeFacade.java:584)
at com.pws.ubiquity.pr.business.TransactionTypeFacade_ocr0a6_EOImpl.addTransactionType(TransactionTypeFacade_ocr0a6_EOImpl.java:271)
at com.pws.ubiquity.pr.web.action.AddTransactionTypeAction.doExecute(AddTransactionTypeAction.java:120)
at com.pws.ubiquity.common.web.action.SecureAction.perform(SecureAction.java:240)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
INTERNAL EXCEPTION STACK:
java.sql.SQLException: ORA-00904: invalid column name
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
at weblogic.jdbc.jts.Statement.executeUpdate(Statement.java:503)
at weblogic.jdbc.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedStatementImpl.java:66)
at weblogic.jdbc.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedStatement.java:57)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeNoSelect(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown Source)
at oracle.toplink.internal.queryframework.CallQueryMechanism.insertObject(Unknown Source)
at oracle.toplink.internal.queryframework.StatementQueryMechanism.insertObject(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(Unknown Source)
at oracle.toplink.queryframework.InsertObjectQuery.executeCommit(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedWrite(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.performUserDefinedInsert(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(Unknown Source)
at oracle.toplink.queryframework.WriteObjectQuery.executeCommit(Unknown Source)
at oracle.toplink.internal.queryframework.DatabaseQueryMechanism.executeWrite(Unknown Source)
at oracle.toplink.queryframework.WriteObjectQuery.execute(Unknown Source)
at oracle.toplink.queryframework.DatabaseQuery.execute(Unknown Source)
at oracle.toplink.publicinterface.Session.internalExecuteQuery(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.internalExecuteQuery(Unknown Source)
at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
at oracle.toplink.internal.sessions.CommitManager.commitAllObjects(Unknown Source)
at oracle.toplink.publicinterface.Session.writeAllObjects(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.commitToDatabase(Unknown Source)
at oracle.toplink.publicinterface.UnitOfWork.issueSQLbeforeCompletion(Unknown Source)
at oracle.toplink.jts.AbstractSynchronizationListener.beforeCompletion(Unknown Source)
at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:551)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:88)
at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:982)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1506)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:215)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:247)
at com.pws.ubiquity.pr.business.TransactionTypeFacade.addTransactionType(TransactionTypeFacade.java:584)
at com.pws.ubiquity.pr.business.TransactionTypeFacade_ocr0a6_EOImpl.addTransactionType(TransactionTypeFacade_ocr0a6_EOImpl.java:271)
at com.pws.ubiquity.pr.web.action.AddTransactionTypeAction.doExecute(AddTransactionTypeAction.java:120)
at com.pws.ubiquity.common.web.action.SecureAction.perform(SecureAction.java:240)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=oracle.toplink.jts.wls.WebLogicSynchronizationListener@373d4a
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-00904: invalid column name
INTERNAL EXCEPTION: java.sql.SQLException: ORA-00904: invalid column name
ERROR CODE: 904 - with nested exception:
[EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-00904: invalid column name
INTERNAL EXCEPTION: java.sql.SQLException: ORA-00904: invalid column name
ERROR CODE: 904]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1490)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:265)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:247)
at com.pws.ubiquity.pr.business.TransactionTypeFacade.addTransactionType(TransactionTypeFacade.java:584)
at com.pws.ubiquity.pr.business.TransactionTypeFacade_ocr0a6_EOImpl.addTransactionType(TransactionTypeFacade_ocr0a6_EOImpl.java:271)
at com.pws.ubiquity.pr.web.action.AddTransactionTypeAction.doExecute(AddTransactionTypeAction.java:120)
at com.pws.ubiquity.common.web.action.SecureAction.perform(SecureAction.java:240)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
2002-11-27 11:56:25,793 DEBUG com.pws.framework.common.MessageSourceFactory - Get MessageSource for error message.:
2002-11-27 11:56:25,793 DEBUG com.pws.framework.common.MessageSourceFactory - Get MessageSource for error message.:
com.pws.framework.exception.GeneralException: There was an unexpected error. Please contact your system administrator.
at com.pws.framework.exception.GeneralException.create(GeneralException.java:111)
at com.pws.ubiquity.pr.business.TransactionTypeFacade.addTransactionType(TransactionTypeFacade.java:588)
at com.pws.ubiquity.pr.business.TransactionTypeFacade_ocr0a6_EOImpl.addTransactionType(TransactionTypeFacade_ocr0a6_EOImpl.java:271)
at com.pws.ubiquity.pr.web.action.AddTransactionTypeAction.doExecute(AddTransactionTypeAction.java:120)
at com.pws.ubiquity.common.web.action.SecureAction.perform(SecureAction.java:240)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)The SQL statement generated by TopLink is as follows -
UPDATE PR_SUPP SET CNTC_PRSN_NAME = ''
, REMK = 'Remark 123 !', LAST_CHNG_DTTM = {ts '2002-11-29 10:59:56.0'} WHERE ((S
UPP_CODE = 'A0001') AND (LAST_CHNG_DTTM = {ts '2002-11-29 10:46:01.0'}))
The coloumn name in the generated statement conform to the coloumn names in the table. The exception is being thrown for all 'update' queries for all objects in the application. -
WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log file
<b>WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log file</b>
We are using WLS 7.0.4 - One of JMS connection factory setting in admin console we selected "Server Affinity" options.
We see this messages appear in Weblogic log file,
####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster> <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <000123> <Conflict start: You tried to bi
nd an object under the name sbetrmi2 in the JNDI tree. The object you have bound from liberatenode2.dc2.adelp
hia.com is non clusterable and you have tried to bind more than once from two or more servers. Such objects ca
n only deployed from one server.>
and then,
####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster> <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <000125> <Conflict Resolved: sbetrmi2 for
the object from liberatenode5.dc2.adelphia.com under the bind name sbetrmi2 in the JNDI tree.>
Should we use 'load balancing option' instead of 'server affinity' ?
Any thuoghts?
Thanks in adv.
VijayTest Reply
<Vijay Kumar> wrote in message news:[email protected]..
> <b>WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log
> file</b>
>
> We are using WLS 7.0.4 - One of JMS connection factory setting in admin
> console we selected "Server Affinity" options.
>
> We see this messages appear in Weblogic log file,
> ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
> <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
> d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
> <000123> <Conflict start: You tried to bi
> nd an object under the name sbetrmi2 in the JNDI tree. The object you have
> bound from liberatenode2.dc2.adelp
> hia.com is non clusterable and you have tried to bind more than once from
> two or more servers. Such objects ca
> n only deployed from one server.>
>
> and then,
> ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
> <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
> d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
> <000125> <Conflict Resolved: sbetrmi2 for
> the object from liberatenode5.dc2.adelphia.com under the bind name
> sbetrmi2 in the JNDI tree.>
>
>
> Should we use 'load balancing option' instead of 'server affinity' ?
>
> Any thuoghts?
>
> Thanks in adv.
> Vijay -
Can I please have a free Diablo CD because WLS 8.1 SP4 doesnt support EL &
I understand (from your doc and from reading forum entries) that BEA WLS 8.1 SP4 does not have a container that can support EL and JSTL; however, Diablo does (which is WLS 9.0)
I'm currently studying for the SCWCD Exam which requires JSP 2.0 and Servlet 2.4 I cannot do EL and JSTL under my current WLS 8.1 and I require WLS 9.0
However it's a large download and I have a 56KB modem.
Is it possible that you can please send me a free Diablo CD for the Windows Operating System (I have Windows-2000):
currently there's not an option for this on your website.
My name and address are as follows:
Al Diovanni
450 Raritan Ave
Staten Island, NY 10305
Home EMAIL: [email protected]
Work EMAIL: [email protected]
Please let me know on this. Thanks. Take care.When I took out DOCTYPE, I received several web.xml validation errors and marshaller errors; see below:
weblogic.application.ModuleException: VALIDATION PROBLEMS WERE FOUND
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:125:8:125:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:125:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:134:8:134:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:134:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:143:8:143:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:143:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:152:8:152:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:152:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:161:8:161:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:161:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:170:8:170:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:170:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:179:8:179:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:179:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:188:8:188:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:188:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:353:5:353:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:353:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:357:5:357:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:357:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:361:5:361:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:361:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:365:5:365:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:365:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:369:5:369:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:369:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:373:5:373:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:373:5>
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:726)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:255)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:81)
at weblogic.application.internal.flow.ModuleCallbackWrapper.prepare(ModuleCallbackWrapper.java:113)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:331)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:455)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:147)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:129)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:38)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:169)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:31)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:125)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:82)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:61)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:138)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:899)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:167)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:139)
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:125:8:125:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:125:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:134:8:134:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:134:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:143:8:143:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:143:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:152:8:152:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:152:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:161:8:161:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:161:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:170:8:170:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:170:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:179:8:179:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:179:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:188:8:188:8: problem: cvc-minLength-valid.1.1: string length (string) is less than minLength facet (0) for '1':<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:188:8>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:353:5:353:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:353:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:357:5:357:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:357:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:361:5:361:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:361:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:365:5:365:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:365:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:369:5:369:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:369:5>
C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp\WEB-INF\web.xml:373:5:373:5: problem: cvc-complex-type.2.4a: Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee icon@http://java.sun.com/xml/ns/j2ee distributable@http://java.sun.com/xml/ns/j2ee context-param@http://java.sun.com/xml/ns/j2ee filter@http://java.sun.com/xml/ns/j2ee filter-mapping@http://java.sun.com/xml/ns/j2ee listener@http://java.sun.com/xml/ns/j2ee servlet@http://java.sun.com/xml/ns/j2ee servlet-mapping@http://java.sun.com/xml/ns/j2ee session-config@http://java.sun.com/xml/ns/j2ee mime-mapping@http://java.sun.com/xml/ns/j2ee welcome-file-list@http://java.sun.com/xml/ns/j2ee problem-page@http://java.sun.com/xml/ns/j2ee jsp-config@http://java.sun.com/xml/ns/j2ee security-constraint@http://java.sun.com/xml/ns/j2ee login-config@http://java.sun.com/xml/ns/j2ee security-role@http://java.sun.com/xml/ns/j2ee env-entry@http://java.sun.com/xml/ns/j2ee ejb-ref@http://java.sun.com/xml/ns/j2ee ejb-local-ref@http://java.sun.com/xml/ns/j2ee service-ref@http://java.sun.com/xml/ns/j2ee resource-ref@http://java.sun.com/xml/ns/j2ee resource-env-ref@http://java.sun.com/xml/ns/j2ee message-destination-ref@http://java.sun.com/xml/ns/j2ee message-destination@http://java.sun.com/xml/ns/j2ee locale-encoding-mapping-list@http://java.sun.com/xml/ns/j2ee' instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee:<C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp/WEB-INF/web.xml:373:5>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:195)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:171)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:127)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:194)
at weblogic.application.descriptor.AbstractDescriptorLoader.createDescriptor(AbstractDescriptorLoader.java:347)
at weblogic.application.descriptor.AbstractDescriptorLoader.createDescriptor(AbstractDescriptorLoader.java:336)
at weblogic.application.descriptor.AbstractDescriptorLoader.getDescriptor(AbstractDescriptorLoader.java:246)
at weblogic.application.descriptor.AbstractDescriptorLoader.getRootDescriptorBean(AbstractDescriptorLoader.java:226)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:107)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:722)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:255)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:81)
at weblogic.application.internal.flow.ModuleCallbackWrapper.prepare(ModuleCallbackWrapper.java:113)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:331)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:455)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:147)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:129)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:38)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:169)
at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:31)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:125)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:82)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:61)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:138)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:899)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:167)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:139)
>
####<May 15, 2005 4:29:14 AM EDT> <Error> <Deployer> <Diovanni> <examplesServer> <ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1116145754595> <BEA-149205> <Failed to initialize the application examplesWebApp due to error weblogic.application.ModuleException: [HTTP:101064][WebAppModule(examplesWebApp:examplesWebApp)] Error parsing descriptor in Web appplication "C:\bea\weblogic90b\samples\server\examples\build\examplesWebApp"
weblogic.application.ModuleException: VALIDATION PROBLEMS WERE FOUND
C:\bea\weblogic90b\samples\server\exam
Maybe you are looking for
-
Hello, I'm having trouble setting up a VPN using MAC OSX 10.4.11 Server. I have and XSAN system and one of my volumes has been down for quite a while now. There is a very kind MAC IT professional that is willing to help be troubleshoot my system but
-
RMAN 11gR2 DUPLICATE TARGET FOR STANDBY FROM ACTIVE DATABASE - Issue -HELP
First question. Can primary and standby database have the same SID name? As I recall it is yes. I believe they must have different GLOBAL or DB_UNIQUE_NAME? Anyway, RMAN I believe is telling me it is having problems copying control file on first and
-
For two weeks now the Health app on my iPhone6 shows wrong data for distance travelled. For example it says I took about 8000 steps but that converts to just 500 metres. I restarted th IPhone but that didn't help. Anybody an idea? (ios 8.2)
-
5530 XM Firmware v30 not for everyone
What's the difference between these two versions of the phone?? Product code 0581328: RM-504 North America BLACK-RED (for this one the firmware is available) Product code 0590825: 5530 XM RM-504 North America US Black/Red (for this one not) I have th
-
Using PHP MySQL to load data into div
I have one page with mulitple images and one hidden div. When one of the images are selected, the hidden div will appear and the div will be loaded with dynamic data based on the button selected. Can anyone give me any help on how to accomplish retri