JMS Persistence with WLS 8.1SP3 in a cluster
I have been following the BEA recommendations. I have configured my JMS to write to an Oracle DB for JMS persistence. This is in a clustered environment. I have had one server go down and then come back. During the outage or right before the outage there were request in the JMS queue. I would assume when the server that failed came back up it would then receive and process the JMS request that were waiting in the DB. That doesn't seem to be happening. My setup is one JMS topic for out bound. The JMS queue is set up for internal traffic. It uses Message Beans. We are also using XADrivers.
The setup is WLS8.1SP3 on Solaris hitting an Oracle 9 db. Please forward me any questions or suggestions. Thank you in advance.
WebLogic JMS won't automatically recover messages that enter an "in-doubt" state due to persistence errors that occur while they are being sent or received. To recover such messages, JMS needs to be restarted. You can contact customer support for an 8.1 sample program that automatically restarts JMS (without restarting all of WebLogic) when this problem occurs.
Tom
Similar Messages
-
Using foreign JMS providers with wls
does anybody have a clou, where i can find that article, i think it's
by steve felts on using foreign JMS providers with wls? i think the
link on dev2dev is broken?
The new article is called "Using Foreign JMS Providers with WLS" and it's
here:
http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
greg
"leopld goess" <[email protected]> wrote in message
news:[email protected]..
> does anybody have a clou, where i can find that article, i think it's
> by steve felts on using foreign JMS providers with wls? i think the
> link on dev2dev is broken?
-
Migrating JMS Persistence from WLS 4.5.2 to WLS 6.1
Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
ThanksHi.
I'm not sure that there is an automatic process to accomplish this, but you might get a
better answer by posting this on the JMS newsgroup.
Regards,
Michael
Manuel Villalta wrote:
Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
Thanks--
Michael Young
Developer Relations Engineer
BEA Support -
Looking up JMS destinations with clustered WLS
From scanning the postings, it appears that in a clustered WLS environment, the
JMS servers are not clustered. As a result, the JMS destinations must be unique
across all of the WLS in the cluster. In addition, there is no failover available
when a JMS server goes down.
With that stated, what I want to know is:
When establishing a JMS connection with a JMS server in a WLS cluster, do I need
to know the JNDI URL for each specific JMS server that is managing the destination(s)
I wish to pub/sub?
Or, is there a 'global' JNDI tree that I can reference and the clustered WLS behind
the scenes will route me to the appropriate JMS server?
If resolving the URL is a manual process, I will need to keep track of which destinations
reside on which JMS servers. This adds an additional maintenance point that I
would like to avoid if possible.
Thanks,
Bob.
One can use Connection Factory to establish connection to particular
destination (queue/topic). connection factories are clustered. so, one don't
need to have knowledge of particular WLS.
"Neal Yin" <[email protected]> wrote in message
news:[email protected]...
> Although there is only one JMS server instance, you can lookup it from
> anywhere in a cluster.
> In another words, JNDI tree is global in a WLS cluster. Just give cluster
> DNS name in your
> URL, you will be fine.
>
> -Neal
>
>
> "Bob Peroutka" <[email protected]> wrote in message
> news:[email protected]...
> >
> > From scanning the postings, it appears that in a clustered WLS
> environment, the
> > JMS servers are not clustered. As a result, the JMS destinations must
be
> unique
> > across all of the WLS in the cluster. In addition, there is no failover
> available
> > when a JMS server goes down.
> >
> > With that stated, what I want to know is:
> >
> > When establishing a JMS connection with a JMS server in a WLS cluster,
do
> I need
> > to know the JNDI URL for each specific JMS server that is managing the
> destination(s)
> > I wish to pub/sub?
> >
> > Or, is there a 'global' JNDI tree that I can reference and the clustered
> WLS behind
> > the scenes will route me to the appropriate JMS server?
> >
> > If resolving the URL is a manual process, I will need to keep track of
> which destinations
> > reside on which JMS servers. This adds an additional maintenance point
> that I
> > would like to avoid if possible.
> >
> > Thanks,
> >
> > Bob.
> >
> >
> >
>
>
-
Configuring WL JMS as a foreign JMS provider with security scope (WLS 8.1)
Hello, i have a problem accessing a queue from a foreign jms provider, if the queue has a security policy. I have the following scenario:
1) Server server1 in domain1 (WLS81) has a JMS Server with one queue queue1 with a security policy "Caller is a member of the group GROUP_QUEUE". There is also a user USER_QUEUE user defined, which belongs to the this group.
There is also a ConnectionFactory with "XA Connection Factory Enabled = true" configured.
The queue and the connection factory are visible in the jndi tree of this server.
2) Server server2 has a foreign jms server. Foreign JMSConnectionFactory and foreign JMSDestination refer to the jndi entries of server 1. For Foreign JMS Connection Factory username is set to USER_QUEUE. JNDI entries for foreign references are visible in jndi tree of this server.
I wrote a standalone client to store messages in the queue accessing server1 with USER_QUEUE sucessfully.
Now I try to deploy a MDB on server2 accessing the queue on server 1. I tried different versions of ejb-jar.xml/weblogic-ejb-jar.xml to access the queue, but with no luck.
scenario a): no security entries in both descriptors; weblogic-descr has entries <destination-jndi-name> and <connection-factory-jndi-name> pointing to the local jndi names. REsult:
<11.02.2005 19.16 Uhr CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:
CancelEasyMoneyBean is unable to connect to the JMS destination: prepaid.Cancel
EasyMoneyQueue. The Error was:
[EJB:010196]'weblogic.jms.common.JMSSecurityException: Access denied to resource
: type=<jms>, application=, destinationType=queue, resource=CancelEasyMoneyQueue
, action=receive' Linked exception = 'weblogic.jms.common.JMSSecurityException:
Access denied to resource: type=<jms>, application=, destinationType=queue, reso
urce=CancelEasyMoneyQueue, action=receive'
So entering username and password for ForeignJMSConnectionFactory doesn't do the trick.
scenario b:) trying to set additional security entries in both descriptors. I added a role queueUser to my mdb and to weblogic-descr a
<security-role-assignment>
<role-name>queueUser</role-name>
<principal-name>USER_QUEUE<principal-name>
</security-role-assignment>
I added the user USER_QUEUE and the group GROUP_QUEUE to server2.
Now server 1 throws exception after redeployment on server 2:
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE].
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE]
at weblogic.security.service.SecurityServiceManager.seal(SecurityService
Manager.java:680)
Has anybody an idea or a pointer how to define access from a mdb to a foreign queue using security ?
Thanks in advance,
RainerHello, i have a problem accessing a queue from a foreign jms provider, if the queue has a security policy. I have the following scenario:
1) Server server1 in domain1 (WLS81) has a JMS Server with one queue queue1 with a security policy "Caller is a member of the group GROUP_QUEUE". There is also a user USER_QUEUE user defined, which belongs to the this group.
There is also a ConnectionFactory with "XA Connection Factory Enabled = true" configured.
The queue and the connection factory are visible in the jndi tree of this server.
2) Server server2 has a foreign jms server. Foreign JMSConnectionFactory and foreign JMSDestination refer to the jndi entries of server 1. For Foreign JMS Connection Factory username is set to USER_QUEUE. JNDI entries for foreign references are visible in jndi tree of this server.
I wrote a standalone client to store messages in the queue accessing server1 with USER_QUEUE sucessfully.
Now I try to deploy a MDB on server2 accessing the queue on server 1. I tried different versions of ejb-jar.xml/weblogic-ejb-jar.xml to access the queue, but with no luck.
scenario a): no security entries in both descriptors; weblogic-descr has entries <destination-jndi-name> and <connection-factory-jndi-name> pointing to the local jndi names. REsult:
<11.02.2005 19.16 Uhr CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:
CancelEasyMoneyBean is unable to connect to the JMS destination: prepaid.Cancel
EasyMoneyQueue. The Error was:
[EJB:010196]'weblogic.jms.common.JMSSecurityException: Access denied to resource
: type=<jms>, application=, destinationType=queue, resource=CancelEasyMoneyQueue
, action=receive' Linked exception = 'weblogic.jms.common.JMSSecurityException:
Access denied to resource: type=<jms>, application=, destinationType=queue, reso
urce=CancelEasyMoneyQueue, action=receive'
So entering username and password for ForeignJMSConnectionFactory doesn't do the trick.
scenario b:) trying to set additional security entries in both descriptors. I added a role queueUser to my mdb and to weblogic-descr a
<security-role-assignment>
<role-name>queueUser</role-name>
<principal-name>USER_QUEUE<principal-name>
</security-role-assignment>
I added the user USER_QUEUE and the group GROUP_QUEUE to server2.
Now server 1 throws exception after redeployment on server 2:
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE].
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE]
at weblogic.security.service.SecurityServiceManager.seal(SecurityService
Manager.java:680)
Has anybody an idea or a pointer how to define access from a mdb to a foreign queue using security ?
Thanks in advance,
Rainer -
ConnectionPool problems with WLS 7.0 and Oracle 9.2
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
application on the productive system (and only there) we constantly encounter
a whole set of SQLExceptions which have all in common that the Connection from
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSet
- Connection has already been closed
- Closed Statement
- Transaction is no longer active - status committing
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()
There are no special Statements which create these errors. They are spread at
random across practically every query the application creates, and the same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSets are
closed immediately after use. As an example, I attached a code snippet and a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrent usern,
since in the approval tests on an almost identical test system these errors never
occurred.
I also followed the advice from Oracle and installed the latest Oracle JDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in the application
classpath (via a reference in the Manifest file of the application jar), not in
the system classpath? There has never been a problem with that, but in a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script creates for the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath? If
it is possible, why is it necessary?
Best regards,
Andreas Zehrt
[CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]Andreas Zehrt wrote:
Hi Joe,
Your hint that there is a threading problem was right:
On further investigation of the code I found out that the class that passes the
Connection to the DAO not only stores it as a member at some point (which is not
a good idea anyway) but is also a singleton - then, of course, it's no surprise
that the Connection gets invalid in a incalculable way when concurrent threads
share it.
The singleton instantiation was not so obvious because the way of instantiation
is controlled by a configuration parameter that can be overridden at different
levels.
I changed it and the productive logfiles indicate that the SQLExceptions related
to that class have disappeared.I am happy to have helped.
So, thanks a lot for the advice.
But I am still wondering why this code has worked for so long a time with WLS
5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
it was multi-user environment.Mo idea.
I still believe that there is a difference between WLS 5.1 and 7.0 in the way
it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
a little more explicit about those changes and possible version incompatabilities
beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
effect in this case, I will certainly do what I can to see that our documentation
is explicit about changes.
Joe
Best regards, Andreas
Joe Weinstein <[email protected]> wrote:
Hi Andreas.
Andreas Zehrt wrote:
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
application on the productive system (and only there) we constantlyencounter
a whole set of SQLExceptions which have all in common that the Connectionfrom
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSetThat is typically if the statement that created it is either re-executed
or closed.
- Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
would show
where it was originally closed.
- Closed Statementsame as above.
- Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
datasource,
and then later trying to use it after the transaction which it was associated
with,
is finished.
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
There are no special Statements which create these errors. They arespread at
random across practically every query the application creates, andthe same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSetsare
closed immediately after use. As an example, I attached a code snippetand a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrentusern,
since in the approval tests on an almost identical test system theseerrors never
occurred.
I also followed the advice from Oracle and installed the latest OracleJDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in theapplication
classpath (via a reference in the Manifest file of the applicationjar), not in
the system classpath? There has never been a problem with that, butin a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script createsfor the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath?If
it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
We also ship
an oracle thin driver, which becomes obsolete soon...
I am concerned that your code creates pool connections to be used later.
The problems
can arise if more than one thread ever gets the same connection, or if
the connection
is used in the same thread, spanning transactions. It does also seem
that there may
be a threading issue, because if two threads each call the code to create
a connection,
and two connections are made, but one over-writes the other, the two
threads can
end up using the same connection, and closing it. The over-written one
never gets closed,
resulting in that leak message you got...
Joe
The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
several classes in the business layer, but not used, until the DAOtakes it to make the query.
So, the Connection is closed where it was opened, not in the DAO class.
public class ConcernDAOImpl extends BaseDAO {
public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
throws DataAccessException, ConstraintException, ComaParseException{>
sqlMessage.append(")");
String sqlStmt = sqlMessage.toString();
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement(sqlStmt);
rs = pstmt.executeQuery();
while (rs != null && rs.next()) {
final Concern concern =
new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
return concerns;
} catch (SQLException sqle) {
// Wrapps real SQL exception
String[] message = new String[]{sqle.getMessage(), sqlStmt};
throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
sqle);
} finally {
closeAll(rs, pstmt);
_logger.exitDebug(method);
Here, the Connection is acquired and finally closed
public class ComaServiceProviderClassicImpl {
public void updateComplaint(
final Request updateRequest,
final ResponseSingleElement response,
final Principal principal)
throws SystemException {
try {
logger.info("updateComplaint", "store incident");
// store the incident in the database
incidentManager.storeIncident(getConnection(), updateIncident);
// reload the incident from Cache and / or the databaseto get the ContactReferences.
Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
getConnection(), updateIncident.getOID());
} catch (RemoteException rex) {
// remote exceptions
rollbackIfNecessary();
CoreUtils.unwrapRemoteException(rex, logger);
} catch (SystemException e) {
// all other exceptions --> rollback if necessary and rethrow
rollbackIfNecessary();
throw e;
} finally {
removeConnection();
logger.exitDebug("updateComplaint");
This is the resulting StackTrace:
sql exception: [Closed Statement: next] - sql statement: [select *
at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
was detected. A Connection leak occurs when a connection obtained from
the pool was not closed explicitly by calling close() and then was disposed
by the garbage collector and returned to the connection pool. The following
stack trace at create shows where the leaked connection was created.
Stack trace at connection create:
at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210) -
Server boot takes a lot of time due to JMS persistence file store
Hi,
We're using WebLogic 9.2 on a windows machine.
Recently, we enhanced our application to work with JMS.
We're using 2 JMS servers on 2 different servers in a cluster, and working with distributed destinations.
We're using file store as our persistence store.
Lately, we found that server boot takes a lot of time due to actions which are performed on the file-store.
Analyzing this problem, we saw that the file size is ~2GB.
We understand that the file size does not shrink (unless manually compacted), and its size is matching the highest number ever of pending messages in the queues (like a high water-mark).
We also turned store debug on, using weblogic.Debug.DebugStoreIOPhysical, and we saw a lot of recovery logs after the file-store is opened.
We've checked and verified that our JMS transactions are completed successfully. We also verified that the number of pending and current messages is 0.
We've stopped the server gracefully, verifying there are no pending messages.
However, server boot repeatedly takes ~30 minutes due to heavy work done on the persistence store.
Compacting or removing the file store eliminates the delay.
However, we want to avoid manual operations every time we want to boot the server.
Please share your ideas.
Thanks,
ItsikThe only suggestions I have off the top of my head are:
* Ensure (1) the host system has at least 2GB (file store size) of free physical memory in addition to the memory used by current processes, and (2) the host system is not rebooted between each WebLogic restart. If you make sure of these two items, then the operating system will implicitly cache the store's file contents in memory even between boots -- when WebLogic subsequently boots the file store, the O/S should serve the file contents up much more quickly.
* Consider moving to a JDBC store. JDBC store runtime performance is lower, but since you have a typically only have a small amount of records to recover, boot performance should be higher in this case.
* Not that it helps your particular case, but it happens that we have boot performance enhancements in process for a future release (hopefully a near future release).
Tom -
Using updated tools with WLS 8.1 SP3
I'm attempting to take advantage of some ant 1.6 features. However, it appears that the ant XML parsers are getting in the way of the embedded WLS xml parsers:
[servicegen] java.lang.ClassCastException
[servicegen] at weblogic.apache.xerces.parsers.SAXParser.<init>(SAXParser.java:140)
[servicegen] at weblogic.apache.xerces.parsers.SAXParser.<init>(SAXParser.java:125)
[servicegen] at weblogic.apache.xerces.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:102)
[servicegen] at weblogic.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:112)
[servicegen] at weblogic.apache.xerces.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:140)
[servicegen] at weblogic.xml.jaxp.WebLogicSAXParserFactory.setFeature(WebLogicSAXParserFactory.java:56)
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot invoke boolean constructor of processor ] - with nested exception:
[servicegen] [java.lang.reflect.InvocationTargetException - with target exception:
[servicegen] [weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[servicegen] [java.lang.ClassCastException]]]
Based on some research this appears to be an issue with WLS getting a parser that it cannot handle. Given that the version of ant included with 8.1sp3 is pretty old, is there a way to use newer versions? I'm giving up for now on macrodef's but would, as a general statement, like to keep up with new tools as they become available. I'd like to not be dependent on turning a battleship to incorporate 15 months of development work (the time between now and the release of ant 1.5.3 as included with 8.1sp3).
Thanks for any information.Had some problems like this before. Even thought I cannot offer specific advice as to how to fix this. If you do this, it could help.
Encountered a problem in eclipse while using WLS servicegen ANT task and, of course, the optional FTP task. I am using Eclipse Version: 3.0.0 Build id: 200406192000. With this comes ANT 1.6.1 standard. In order to get servicegen ANT task working I had to include the weblogic.jar in the ANT Classpath. Ofcourse this had another side effect, the FTP task that used to work earlier quit working. I still havent figured out the root cause of the problem but inorder to get around I did the following. To fix this, I added a new Task called FTP, I picked the c:\....\lib\ant-commons-net.jar in the location. The name I retained it as ftp. In the left page, I nagivated down to the lead of the tree [root]/->org->apache->...->net and in the right pane, I chose FTP. After this step when I ran I ran into an odd error Buildfile: C:\Work\JSSE-EJB.xml BUILD FAILED: java.lang.NoClassDefFoundError: com/oroinc/net/ftp/FTP Total time: 78 milliseconds I was under the impression that this is a legacy component and that the new version of the net component has org.apache....FTP structure. I am really not sure where, but to fix the issue, I had to get the NetComponents.jar from http://www.savarese.org/downloads/NetComponents/ and included it in the classpath. After this step, presto, servicegen task works fine with FTP task. However, I cannot imagine doing this for all the optional tasks. But for now there is a winding work around. -
General install and deployment problem with WLS clustering on two boxes
Hi,
I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
Any help appriecated.
Surfbum.Hi I think I've found the answer. You can build a managed server template using the pack command.
http://e-docs.bea.com/common/docs90/pack/tasks.html -
JMS Failover with Distributed Destinations in 7.0
How does JMS failover with distributed destinations in WL 7.0?
In an environment using file stores for persistent messages, can a working server
automatically pick up unprocessed and persisted messages from a failed server?
If so, what's the best way to set this up?
Or, is this completely manual? In other words, we have to bring up a new server
pointing to the location of the file store from the failed server?
It appears that two JMSServers cannot share the same file store and, I'm assuming,
two file stores cannot be using the same directory for persistence.
So the HA you're talking about is something like Veritas automatically restarting
a server (or starting a new one) to process the messages in the persistent queue
that were unprocessed at the time of failure with the file store residing on some
sort of HA disk array.
The key point is that a message once it arrives at a server must be processed
by that server or, in the case of failure of that server, must be processed by
a server similarly configured to the one that failed so that it picks up the unprocessed
messages. The message can't be processed by another server in the cluster.
Or, is there some trick that could be employed to copy from the file store of
the failed server and repost the messages to the still operating servers?
"Zach" <[email protected]> wrote:
>Unless you have some sort of HA framework/hardware, this is a manual
>operation. You either point to the existing persistent storage (shared
>storage or JDBC connection pool), or you move the physical data.
>
>_sjz.
>
>"Jim Cross" <[email protected]> wrote in message
>news:[email protected]...
>>
>>
>> How does JMS failover with distributed destinations in WL 7.0?
>>
>> In an environment using file stores for persistent messages, can a
>working
>server
>> automatically pick up unprocessed and persisted messages from a failed
>server?
>> If so, what's the best way to set this up?
>>
>> Or, is this completely manual? In other words, we have to bring up
>a new
>server
>> pointing to the location of the file store from the failed server?
>
>
-
Problems installing Axis with WLS 8.1
I'm having problems installing Apache Axis with WLS 8.1.
I'm totally new to WLS, so this may be at the heart of the problem.
I install Axis as per the installation instructions.
These are the steps I followed:
1. Installed the axis directory to
C:\bea\weblogic81\samples\domains\examples\applications\axis2. Added xml-apis.jar and xercesImpl.jar to the AXISCLASSPATH ( the complete AXISCLASSPATH is
C:\axis-1_2RC2\lib\wsdl4j.jar;C:\axis-1_2RC2\lib\axis-ant.jar;C:\axis-1_2RC2\lib\commons-discovery.jar;C:\axis-1_2RC2\lib\commons-logging.jar;C:\axis-1_2RC2\lib\jaxrpc.jar;C:\axis-1_2RC2\lib\log4j.properties;C:\axis-1_2RC2\lib\log4j-1.2.8.jar;C:\axis-1_2RC2\lib\saaj.jar;C:\axis-1_2RC2\lib\axis.jar;C:\javasoft\javamail-1.3.2\mail.jar;C:\javasoft\javamail-1.3.2\lib\smtp.jar;C:\javasoft\javamail-1.3.2\lib\mailapi.jar;C:\javasoft\javamail-1.3.2\lib\pop3.jar;C:\javasoft\javamail-1.3.2\lib\imap.jar;C:\javasoft\jaf-1.0.2\activation.jar;C:\javasoft\Xerces\xerces-2_5_0\xercesImpl.jar;C:\javasoft\Xerces\xerces-2_5_0\xml-apis.jar)3.Added weblogic.xml file to C:\bea\weblogic81\samples\domains\examples\applications\axis\WEB-INF\weblogic.xmlas per instructions with <prefer-web-inf-classes>true</prefer-web-inf-classes> 4. Started the examples server.
5. I then tried to validate the installation as per intructions using <a href="http://localhost:7001/axis"></a>
Everything looks OK with the Axis start page displayed.
6. I then tried happyaxis.jsp . All needed components are present with saaj.jar being picked up from :
Found SAAJ API (javax.xml.soap.SOAPMessage) at C:\bea\weblogic81\samples\domains\examples\examplesServer\.wlnotdelete\extract\examplesServer__appsdir_axis_dir_axis\jarfiles\WEB-INF\lib\saaj.jar7. I'm missing optional component xmlsec.jar
8. Now the trouble starts!!!
pretty much anything I try now comes back with:
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Exception - java.lang.NullPointerExceptionI get this if I try:
<a href="http://localhost:8080/axis/services/Version?method=getVersion"></a>
or
<a href="http://localhost:7001/axis/services/AdminService?wsdl"></a>
or
<a href="http://localhost:7001/axis/services/Version?wsdl"></a>
So, what's going wrong? I cant think what to do next. Please help! I need this to work fairly urgently.
Nigel
PS. here's the NP exception in detail
java.lang.NullPointerException
at weblogic.xml.jaxp.ChainingEntityResolver.popEntityResolver(ChainingEn
tityResolver.java:61)
at weblogic.xml.jaxp.RegistryDocumentBuilder.setEntityResolver(RegistryD
ocumentBuilder.java:168)
at org.apache.axis.utils.XMLUtils.releaseDocumentBuilder(XMLUtils.java:2
35)
at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:312)
at org.apache.axis.utils.XMLUtils.StringToElement(XMLUtils.java:485)
at org.apache.axis.AxisFault.addFaultDetail(AxisFault.java:654)
at org.apache.axis.AxisFault.addHostname(AxisFault.java:888)
at org.apache.axis.AxisFault.addHostnameIfNeeded(AxisFault.java:877)
at org.apache.axis.AxisFault.initFromException(AxisFault.java:280)
at org.apache.axis.AxisFault.<init>(AxisFault.java:181)
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:487)
at org.apache.axis.transport.http.QSWSDLHandler.invoke(QSWSDLHandler.jav
a:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.j
ava:1132)
at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:233
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:301)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)I'm doing exactly the same thing (adding the xerces jars to my web-inf/lib), but happyaxis.jsp is saying the jar I'm using is invalid as follows:
Error: Invalid version of SAAJ API found in D:\bea\weblogic81\server\lib\webservices.jar. Make sure that Axis' saaj.jar precedes D:\bea\weblogic81\server\lib\webservices.jar in CLASSPATH.
Axis will not work.
Maybe this worked in a previous release/SP? I'm using 8.1SP3. I've read some other post saying you cannot override stuff in the weblogic.jar, so I've tried to add the jars to the pre_classpath, which resolves the issue but I get a soap fault related to this thread. Any ideas?
Thanks,
Lou
My weblogic.xml looks as follows:
<weblogic-web-app>
<jsp-descriptor>
<!-- Comment the jspServlet param out to go back to weblogic's jspc -->
<jsp-param>
<param-name>jspServlet</param-name>
<param-value>weblogic.servlet.WlwJSPServlet</param-value>
</jsp-param>
<jsp-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
<url-match-map>
weblogic.servlet.utils.SimpleApacheURLMatchMap
</url-match-map>
</weblogic-web-app> -
Java 1.5 client with WLS 8.1 MBeans...
Hi,
I maintain http://www.hermesjms.com and am investigating a problem with Hermes, which uses a 1.5 VM, interrogating WLS MBeans with WLS on 1.4.
This thread describes what users have seen and what I have also replicated:
http://www.hermesjms.com/forum/viewtopic.php?t=126
As you can see, setting -Djmx.serial.form=1.0 fixes the serialisation problem but I now get the InstanceNotFoundException.
I invoke getMBean() from the getStatistics() method here:
http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/weblogic/WebLogicJMSAdmin.java?view=markup
Any kind soul out there know what the problem may be? I'm kinda confused...
Many thanks,
Colin.Hi Tom,
When I upgrade to 9.0 client against 8.1 server I get the exceptions at the end of this mail. The server I am talking to is a single server, not in a cluster, and is just the out-of-the-box WLS 8.1 with a JMS server and some queues and topics configured.
I don't get the ClassNotFoundException for WebLogicObjectName as this exists in weblogic.jar. Is there anything I need to do to WLS 8.1 to allow a 9.0 client to interop?
Cheers,
Colin.
2005-08-04 08:25:41,753 [Timer-7] DEBUG hermes.ext.weblogic.WebLogicJMSAdmin - Constructed JMSDestination MBean name: mydomain:JMSServerRuntime=MyJMS Server,Location=myserver,Name=MyDistributed Queue,ServerRuntime=myserver,Type=JMSDestinationRuntime
2005-08-04 08:25:41,773 [Timer-7] ERROR hermes.HermesWatchManager - Unexpected Exception
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.management.internal.MBeanHomeImpl_814_WLStub.getMBean(Unknown Source)
at hermes.ext.weblogic.WebLogicJMSAdmin.getMBean(WebLogicJMSAdmin.java:329)
at hermes.ext.weblogic.WebLogicJMSAdmin.getStatistics(WebLogicJMSAdmin.java:155)
at hermes.ext.weblogic.WebLogicJMSAdmin.getDepth(WebLogicJMSAdmin.java:119)
at hermes.impl.HermesAdminAdapter.getDepth(HermesAdminAdapter.java:108)
at hermes.impl.DefaultHermesImpl.getDepth(DefaultHermesImpl.java:1187)
at hermes.HermesWatchManager.updateWatchStatistics(HermesWatchManager.java:202)
at hermes.HermesWatchManager.doUpdate(HermesWatchManager.java:170)
at hermes.HermesWatchManager.access$000(HermesWatchManager.java:38)
at hermes.HermesWatchManager$2.run(HermesWatchManager.java:84)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.lang.ClassNotFoundException: weblogic.management.interop.WebLogicObjectName: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:155)
... 12 more
Caused by: java.lang.ClassNotFoundException: weblogic.management.interop.WebLogicObjectName: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:344)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:258)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:253)
at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(MsgAbbrevInputStream.java:327)
at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectInputStream.java:316)
at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:120)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:120)
at weblogic.management.internal.MBeanHomeImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Unknown Source)
2005-08-04 08:25:41,773 [Timer-7] DEBUG hermes.HermesWatchManager - closing Hermes WebLogic
2005-08-04 08:25:41,783 [Timer-7] DEBUG hermes.impl.jms.ThreadLocalSessionManager - all sessions closed, closing Connection -
Hi,
I am unable to start the integration server WLI 2.1 sp2 with WLS 6.1 sp3.
It gives the following errors:
1.<Aug 1, 2002 10:56:29 AM EDT> <Error> <J2EE> <Error deploying application
wlpi-ejb.jar:
Unable to deploy EJB: Audit from wlpi-ejb.jar:
There is a mismatch between the bean code and generated
code.com.bea.wlpi.Audit . Please rerun ejbc on the bean code.The error was
java.lang.NoSuchFieldException
at java.lang.Class.getField0(Native Method)
at java.lang.Class.getDeclaredField(Class.java:1113)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBean
InfoImpl.java:651)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(Client
DrivenBeanInfoImpl.java:723)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
Impl.java:823)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360) at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.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:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.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 $Proxy46.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.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:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.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 $Proxy68.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
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)
2. <Aug 1, 2002 10:58:09 AM EDT> <Critical> <WebLogicServer> <Failed to
invoke startup class "TimeProcessor", java.lang.Exception: TimeProcessor
startup failed! Check arguments.>
3.<Aug 1, 2002 10:58:13 AM EDT> <Info> <EJB> <EJB Exception during
invocation from home:
[email protected]ffc94 threw
exception: java.lang.IllegalStateException
java.lang.IllegalStateException
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.setState(Unknown Source)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(Unknown Source)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(PluginMan
agerCfgBean_gebmxi_EOImpl.java:1428)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl_WLSkel.invoke(
Unknown Source) at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:167)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:262)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy109.init(Unknown Source)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(Unknown
Source)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:262)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:214)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1865)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Unable to initialize WebLogic Integration - BPM Server:
java.rmi.RemoteException: EJB Exception: ; nested exception is:
java.lang.IllegalStateException
java.lang.IllegalStateException
<<no stack trace available>>
Am I missing something ????? Any help is appreciated.
Thanks in advance.
Sangeetha.Jim,
I tried the new upgrade installer (in Windows this time),
I din't get problem no 3.
But 2 which seemed to work before after changing the configuration file
fails. The server automatically shuts down with the following message:
<Aug 6, 2002 4:33:33 PM EDT> <Emergency> <WebLogicServer> <Server shutdown
due to fatal exception: w
eblogic.t3.srvr.FatalStartupException: Can't start server due to startup
class failure TimeProcessor
- with nested exception:
[java.lang.Exception: TimeProcessor startup failed! Check arguments.]>
<Aug 6, 2002 4:33:33 PM EDT> <Info> <WebLogicServer> <Shutdown has
completed.>
Problem no 1 still persists.
I am also attaching my configuration file.
Any help is much appreciated.
Thanks,
Sangeetha.
"Jim Hinkey" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha,
The Upgrade Installer should be available now on the support downloads.
-Jim
Sangeetha Raghavan wrote:
Hi David,
I am unable to download the file thru' the ftpserver.
The download got cancelled with a message like
'connection closed by the remote server'.
Please let me know when it is available at the support downloads.
Thanks.
Sangeetha.
"R J David Burke" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha
My apologies for the inconvenience you are experiencing. We havediscovered
a problem with the website for the WLI 2.1 SP2 upgrade installer,providing
an incorrect file.
We are working to correct this immediately. In the mean time, the
proper
file can be accessed from our FTP server. The details are:
server: ftpsupport.bea.com
user: support
password: xuquoov (expires on Sunday)
path: /pub/wli21sp2
files: wlintegration21sp2_upgrade_win.exe - upgrade installer for
Windows
wlintegration21sp2_upgrade_unix.zip - upgrade installerfor
Unix-based platforms
For security purposes, directory listings are not enabled, so you willneed
to specify the file by name.
Regards, David
"Sangeetha Raghavan" <[email protected]> wrote in message
news:[email protected]...
Hi Jim,
I upgraded from WLI 2.1 sp1 to WLI 2.1 sp2.
I am not running in a clustered environment.
Attached is my configutaion file.
Thanks.
Sangeetha.
"Jim Hinkey" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha,
Just a few questions...
Did you upgrade or migrate? From which version did you
upgrade/migrate?
Are
you running in a clustered environment? Can you send your
config.xml?
>>>>>
Thanks,
Jim
"Sangeetha.R" wrote:
Hi Jim,
I am using Linux and Oracle 8i
I made the changes in the config.xml and it did solve problem 2.
Problem 1 and 3 still persists.
Thanks in Advance.
Sangeetha.
"Jim Hinkey" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha,
Can you tell me what OS and DB you are using? Also, have you
implemented
the
changes talked about in Release Notes section "Time Services
Changes
in
BPM"? I
think that is causing problem 2.
Thanks,
Jim
"Sangeetha.R" wrote:
Hi,
I am unable to start the integration server WLI 2.1 sp2 with
WLS
6.1
sp3.
It gives the following errors:
1.<Aug 1, 2002 10:56:29 AM EDT> <Error> <J2EE> <Error
deploying
application
wlpi-ejb.jar:
Unable to deploy EJB: Audit from wlpi-ejb.jar:
There is a mismatch between the bean code and generated
code.com.bea.wlpi.Audit . Please rerun ejbc on the bean
code.The
error
was
java.lang.NoSuchFieldException
at java.lang.Class.getField0(Native Method)
at java.lang.Class.getDeclaredField(Class.java:1113)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBean
InfoImpl.java:651)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(Client
>>>>
DrivenBeanInfoImpl.java:723)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
Impl.java:823)
atweblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at
weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
atweblogic.j2ee.Application.addComponent(Application.java:170)
atweblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360) at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.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:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360) at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
>>>>>>>>
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy46.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.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:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360) at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy68.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
atweblogic.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)
>
2. <Aug 1, 2002 10:58:09 AM EDT> <Critical> <WebLogicServer>
<Failed
to
invoke startup class "TimeProcessor", java.lang.Exception:TimeProcessor
startup failed! Check arguments.>
>
3.<Aug 1, 2002 10:58:13 AM EDT> <Info> <EJB> <EJB Exception
during
invocation from home:
[email protected]ffc94
threw
exception: java.lang.IllegalStateException
java.lang.IllegalStateException
at
com.bea.wlpi.server.plugin.PluginManagerCfgImpl.setState(Unknown
Source)
at
com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(Unknown
Source)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(PluginMan
agerCfgBean_gebmxi_EOImpl.java:1428)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl_WLSkel.invoke(
Unknown Source) at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
atweblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:167)
at
weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
atweblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:262)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
atweblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy109.init(Unknown Source)
atcom.bea.wlpi.server.initlistener.InitListenerBean.onMessage(Unknown
Source)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:262)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:214)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1865)
at
weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
atweblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>>>>>>>>>
Unable to initialize WebLogic Integration - BPM Server:
java.rmi.RemoteException: EJB Exception: ; nested exceptionis:
java.lang.IllegalStateException
java.lang.IllegalStateException
<<no stack trace available>>--------------------------------------------------------------------------
>
Am I missing something ????? Any help is appreciated.
Thanks in advance.
Sangeetha.
[config.xml] -
Java ftp server which can use LDAP, how to integrate with WLS' implementation of LDAP?
Howdy.
I'm setting up a java ftp server
(http://www.mycgiserver.com/~ranab/ftp/index.html) which is capable of using
LDAP for it's user security. I would like to integrate this ftp server with
wls' implementation of LDAP so I only have to admin one user list.
Does wls put it's user list in the LDAP or in it's own proprietary setup? I
tried playing around with it, but the users don't seem to appear in the JNDI
tree. Is this where the LDAP stuff is located? I thought it was in there?
If it's in it's own setup, is there a way to propagate the users to LDAP?
If these look like newbie Q&A, I guess they kind of are, I'm new to LDAP.
Thanks for any input you might have.Peter,
If you are talking about using the embedded LDAP server in WLS 7.0 for this purpose
I think you are going done the wrong path.
Look at the following URL on how to use an external LDAP server for your custom
application
http://e-docs.bea.com/wls/docs70/secmanage/realm.html#1172008
Chuck Nelson
DRE
BEA Technical Support -
Getting PetStore to run in WLS 6.1sp3 on Mac OS X 10.2.6?
Hi all!
I've read with great interest all the articles relating to WLS running on OS X.
It's great to read this as I am pretty much the only guy in the entire organisation
here trying to keep using his Mac.
I was able to get WLS admin server to run on my PowerBook running OS X 10.2.6.
However, after stopping the admin server and trying to start the PetStore demo
server, I've got a few exceptions that prevent the server from starting.
So, I was wondering how you people, running WLS 6.1 on OS X have configured your
start scripts. When trying to use the standard jdk that comes with WLS, I'm getting
an exception. When using the Apple 1.3.1 jdk, I'm getting another exception about
a missing 'libmuxer' library. Basically, what set of libraries are you using?
Thanks in advance!
-Laurent.Thanks for the reply, Mark. I finally figured it out by replacing all references
to the WebLogic provided 1.3.1 jdk by the one provided by Apple and all is well
now!
Thanks!
-Laurent.
"Mark Griffith" <[email protected]> wrote:
All you should need (with 7.0 and 8.1) to start WLS is
"java weblogic.Server"
As long as your have your classpath set.
export CLASSPATH=$WLHOME:$WLHOME/server/lib/weblogic.jar
On my windoze box WLHOME=C:/bea/wls81/weblogic81
Libmuxer is our native socket muxing code, you don't need it to run you'll
just use java muxing.
Sam just posted the libs on another thread.
Any other exceptions?
cheers
mbg
"Laurent Daudelin" <[email protected]> wrote in message
news:3eccefbe$[email protected]..
Hi all!
I've read with great interest all the articles relating to WLS runningon
OS X.
It's great to read this as I am pretty much the only guy in the entireorganisation
here trying to keep using his Mac.
I was able to get WLS admin server to run on my PowerBook running OSX
10.2.6.
However, after stopping the admin server and trying to start the PetStoredemo
server, I've got a few exceptions that prevent the server from starting.
So, I was wondering how you people, running WLS 6.1 on OS X haveconfigured your
start scripts. When trying to use the standard jdk that comes withWLS,
I'm getting
an exception. When using the Apple 1.3.1 jdk, I'm getting anotherexception about
a missing 'libmuxer' library. Basically, what set of libraries areyou
using?
Thanks in advance!
-Laurent.
Maybe you are looking for
-
How to read a PDF file in ABAP
We are on <u><b>46C</b></u> I searched sdn and found couple of solutions which might work in higher versions of SAP but not in 46C. The classes used in the examples are not available in 46C. Could anybody please share the code to read a PDF in ABAP.
-
Hi all, i have a problem with transmission of MATMAS from ECC 6.0 to B1 8.8. In B1i i've configured everything (landscapes with connection test OK, process activated) using the BIU R3PROD2B1ITEM. In ECC I've configured all the elements of the communi
-
Hello, here is my question: I have seen many examples on the Web explaining how to resize an image in Java. All of them use AWT. The problem is, my application is web-based, hosted on a server without X11 installed. Now, I know from the Java2D FAQ th
-
How to list check in cash flow
Hello, I have a problem when I list the day cash flow and I have introduced checks with other expiration date that is not today. When I list the cash flow of a day, I cant see the checks that I have introduced with other expiration date. How I could
-
Hi, I kept getting the error: "The project was not built due to "Could not delete: C:\eclipse\workspace\USIMApp\bin\uicc\toolkit\ViewHandler.class.". Fix the problem, then try refreshing this project and building it since it may be inconsistent" when